--- title: "Email finisher" manual: "Form" version: "main" permalink: "https://docs.typo3.org/permalink/typo3/cms-form:concepts-finishers-emailfinisher@main" source: "I/Concepts/Finishers/ReadyToUseFinishers/EmailFinisher/Index.rst" rendered: "2026-09-19T16:47:20+00:00" --- # Email finisher {#concepts-finishers-emailfinisher} The EmailFinisher sends an email to one recipient. EXT:form has two EmailFinishers with the identifiers EmailToReceiver and EmailToSender. **Table of contents** - [Using email finishers in the backend form editor](https://docs.typo3.org/permalink/typo3/cms-form:using-email-finishers-in-the-backend-form-editor@main) - [Options of the email finisher](https://docs.typo3.org/permalink/typo3/cms-form:options-of-the-email-finisher@main) - [Additional email finisher options](https://docs.typo3.org/permalink/typo3/cms-form:additional-email-finisher-options@main) - [Email finishers in the YAML form definition](https://docs.typo3.org/permalink/typo3/cms-form:email-finishers-in-the-yaml-form-definition@main) - [Using Email finishers in PHP code](https://docs.typo3.org/permalink/typo3/cms-form:using-email-finishers-in-php-code@main) - [Working with BCC recipients](https://docs.typo3.org/permalink/typo3/cms-form:working-with-bcc-recipients@main) - [About FluidEmail](https://docs.typo3.org/permalink/typo3/cms-form:about-fluidemail@main) > [!IMPORTANT] > Finishers are executed in the order defined in your form definition. > > See [Finisher execution order](https://docs.typo3.org/permalink/typo3/cms-form:concepts-finishers-execution-order@main). ## Using email finishers in the backend form editor {#finishers-email-to-receiver} Editors can use two email finishers in the backend form editor: - **Email to sender (form submitter)** This finisher sends an email with the contents of the form to the user submitting the form . - **Email to receiver (you)** This finisher sends an email with the contents of the form to the owner of the website. The settings of this finisher are the same as the "Email to sender" finisher ## Options of the email finisher {#apireference-finisheroptions-emailfinisher-options} - **Subject \[subject\]** - *Type:* string - *Required:* true Subject of the email. - **Recipients \[recipients\]** - *Type:* array - *Required:* true Email addresses and names of the recipients (To). - ****Email Address**** Email address of a recipient, e.g. "[some.recipient@example.com](mailto:some.recipient@example.com)" or "{email-1}". - ****Name**** Name of a recipient, e.g. "Some Recipient" or "{text-1}". - **Sender address \[senderAddress\]** - *Type:* string - *Required:* true Email address of the sender, for example "[your.company@example.org](mailto:your.company@example.org)". If [smtp](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Mail/Index.html#mail-configuration-smtp) is used, this email address needs to be allowed by the SMTP server. Use `replyToRecipients` if you want to enable the receiver to reply to the message. - **Sender name \[senderName\]** - *Type:* string - *Default:* `''` Name of the sender, for example "Your Company". - **Reply-to Recipients \[replyToRecipients\]** - *Type:* array - *Default:* `[]` Email address which will be used when someone replies to the email. - ****Email Address**:** Email address for reply-to. - ****Name**** Name for reply-to. - **CC Recipient \[carbonCopyRecipients\]** - *Type:* array - *Default:* `[]` Email address to which a copy of the email is sent. The information is visible to all other recipients. - ****Email Address**:** Email address for CC. - ****Name**** Name for CC. - **BCC Recipients \[blindCarbonCopyRecipients\]** - *Type:* array - *Default:* `[]` Email address to which a copy of the email is sent. The information is not visible to any of the recipients. - ****Email Address**:** Email address for BCC. - ****Name**** Name for BCC. - **Add HTML part \[addHtmlPart\]** - *Type:* bool - *Default:* `true` If set, emails will contain plaintext and HTML, otherwise only plaintext. In this way, HTML can be disabled and plaintext-only emails enforced. - **Attach uploads \[attachUploads\]** - *Type:* bool - *Default:* `true` If set, all uploaded items are attached to the email. - **Title \[title\]** - *Type:* string - *Default:* `undefined` The title shown in the email. - **Translation language \[translation.language\]** - *Type:* string - *Default:* `undefined` If not set, the finisher options are translated depending on the current frontend language (if translations exist). This option allows you to force translations for a given language isocode, e.g. `da` or `de`. See [Translate finisher options](https://docs.typo3.org/permalink/typo3/cms-form:concepts-frontendrendering-translation-finishers@main). ## Additional email finisher options {#apireference-finisheroptions-emailfinisher-options-options} Additional options can be set in the form definition YAML and programmatically in the options array but **not** in the backend editor: - **Properties excluded from translation \[translation.propertiesExcludedFromTranslation\]** - *Type:* array - *Default:* `undefined` If not set, the finisher options are translated depending on the current frontend language (if translations exists). This option allows you to force translations for a given language isocode, e.g 'da' or 'de'. See [Translate finisher options](https://docs.typo3.org/permalink/typo3/cms-form:concepts-frontendrendering-translation-finishers@main). It will be skipped for all specified finisher options. - **translation.translationFiles** - *Type:* array - *Default:* `undefined` If set, this translation file(s) will be used for finisher option translations. If not set, the translation file(s) from the `Form` element will be used. Read [Translate finisher options](https://docs.typo3.org/permalink/typo3/cms-form:concepts-frontendrendering-translation-finishers@main). - **layoutRootPaths** - *Type:* array - *Default:* `undefined` Fluid layout paths. - **partialRootPaths** - *Type:* array - *Default:* `undefined` Fluid partial paths. - **templateRootPaths** - *Type:* array - *Default:* `undefined` Fluid template paths; all templates get the current `FormRuntime` assigned as `form` and the `FinisherVariableProvider` assigned as `finisherVariableProvider`. - **variables** - *Type:* array - *Default:* `undefined` Associative array of variables which are available inside the Fluid template. ## Email finishers in the YAML form definition {#concepts-finishers-emailfinisher-yaml} This finisher sends an email to one recipient. EXT:form has two email finishers with identifiers `EmailToReceiver` and `EmailToSender`. **public/fileadmin/forms/my_form.yaml** ```yaml identifier: example-form label: 'example' type: Form finishers: - identifier: EmailToReceiver options: subject: 'Your message' recipients: your.company@example.com: 'Your Company name' ceo@example.com: 'CEO' senderAddress: 'form@example.com' senderName: 'form submitter' ``` ## Using Email finishers in PHP code {#apireference-finisheroptions-emailfinisher} Developers can create a confirmation finisher by using the key `EmailToReceiver` or `EmailToSender`. ```php createFinisher('EmailToReceiver', [ 'subject' => 'Your message', 'recipients' => [ 'your.company@example.com' => 'Your Company name', 'ceo@example.com' => 'CEO' ], 'senderAddress' => $GLOBALS['TYPO3_CONF_VARS']['MAIL']['defaultMailFromAddress'], 'senderName' => $GLOBALS['TYPO3_CONF_VARS']['MAIL']['defaultMailFromName'], ]); } } ``` This finisher is implemented in `\TYPO3\CMS\Form\Domain\Finishers\EmailFinisher`. ## Working with BCC recipients {#concepts-finishers-emailfinisher-bcc-recipients} Email finishers can work with different recipient types, including Carbon Copy (CC) and Blind Carbon Copy (BCC). Depending on the configuration of your server and TYPO3 instance, it may not be possible to send emails to BCC recipients. The `$GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport_sendmail_command']` configuration value is important here. As documented in [CORE API](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Mail/Index.html#mail-configuration-sendmail), TYPO3 recommends using the parameter `-bs` (instead of `-t -i`) with `sendmail`. The parameter `-bs` tells TYPO3 to use the SMTP standard so that BCC recipients are properly set. [Symfony](https://symfony.com/doc/current/mailer.html#using-built-in-transports) also mentions the `-t` parameter problem. Since TYPO3 7.5 ([#65791](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/7.5/Feature-65791-UsePHPConfiguredSendmailPathIfMAILtransportSendmailIsActive.html)) the `transport_sendmail_command` is automatically set from the PHP runtime configuration and saved. If you have problems sending emails to BCC recipients, this could be the solution. ## About FluidEmail {#concepts-finishers-emailfinisher-fluidemail} The EmailFinisher always sends email via FluidEmail. The FluidEmail finisher allows emails to be sent in a standardized way. The finisher has an `option` property `title` that adds an email title to the default FluidEmail template. Variables can be used in options using the bracket syntax. These variables can be overwritten by FlexForm configuration in the form plugin Use these options to customize the fluid templates: - `templateName`: The template name (for both HTML and plaintext, without the extension) - `templateRootPaths`: The paths to the templates - `partialRootPaths`: The paths to the partials - `layoutRootPaths`: The paths to the layouts > [!NOTE] > The field `templatePathAndFilename` is no longer evaluated. Here is an example finisher configuration: **public/fileadmin/forms/my_form_with_email_finisher.yaml** ```yaml 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 ``` These template files must exist: - `EXT:my_site_package/Resources/Private/Templates/Email/ContactForm.html` - `EXT:my_site_package/Resources/Private/Templates/Email/ContactForm.txt`