Email finisher
The EmailFinisher sends an email to one recipient. EXT:form uses two EmailFinisher declarations with the identifiers EmailToReceiver and EmailToSender.
Important
Finishers are executed in the order defined in your form definition.
Table of contents
Working with BCC recipients
Both email finishers support different recipient types, including Carbon Copy
(CC) and Blind Carbon Copy (BCC). Depending on the configuration of the server
and the TYPO3 instance, it may not be possible to send emails to BCC recipients.
The configuration of the
$GLOBALS
value is crucial. As documented in CORE API,
TYPO3 recommends the parameter
-bs
(instead of
-t -
) when using
sendmail
. The parameter
-bs
tells TYPO3 to use the SMTP standard
and that way the BCC recipients are properly set. Symfony
refers to the problem of using the
-t
parameter as well. Since TYPO3 7.5
(#65791)
the
transport_
is automatically set from the PHP runtime
configuration and saved. Thus, if you have problems with sending emails to BCC
recipients, check the above mentioned configuration.
About FluidEmail
Changed in version 12.0
The
Email
always sends email via
Fluid
.
FluidEmail allows to send mails in a standardized way.
The option
title
is available which can
be used to add an email title to the default FluidEmail template. This option is
capable of rendering form element variables using the known bracket syntax and can
be overwritten in the FlexForm configuration of the form plugin.
To customize the templates being used following options can be set:
template
: The template name (for both HTML and plaintext) without the extensionName template
: The paths to the templatesRoot Paths partial
: The paths to the partialsRoot Paths layout
: The paths to the layoutsRoot Paths
Note
The formerly available field
template
is not evaluated
anymore.
A finisher configuration could look like this:
identifier: contact
type: Form
prototypeName: standard
finishers:
-
identifier: EmailToSender
options:
subject: 'Your Message: {message}'
title: 'Hello {name}, your confirmation'
templateName: ContactForm
templateRootPaths:
100: 'EXT:my_site_package/Resources/Private/Templates/Email/'
partialRootPaths:
100: 'EXT:my_site_package/Resources/Private/Partials/Email/'
addHtmlPart: true
In the example above the following files must exist in the specified template path:
EXT:
my_ site_ package/ Resources/ Private/ Templates/ Email/ Contact Form. html EXT:
my_ site_ package/ Resources/ Private/ Templates/ Email/ Contact Form. txt