DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
mail¶
The mail postProcessor sends submitted data by mail.
Mail¶
Configuration options for the mail to deliver.
ccEmail¶
- Property:
- ccEmail
- Data type:
- string
- Description:
- Email address the submitted data is sent to as a carbon copy.
organization¶
- Property:
- organization
- Data type:
- string
- Description:
- Organization mail header.
priority¶
- Property:
- priority
- Data type:
- integer
- Description:
- Priority of the email. Integer value between 1 and 5. If the priority is configured, but too high, it will be set to 5, which means very low priority.
- Default:
- 3
recipientEmail¶
- Property:
- recipientEmail
- Data type:
- string
- Description:
- Email address the submitted data is sent to.
senderEmail¶
- Property:
- senderEmail
- Data type:
- string
- Description:
- Email address which is shown as sender of the email (from header).
- Default:
- TYPO3_CONF_VARS['MAIL']['defaultMailFromAddress']
senderEmailField¶
- Property:
- senderEmailField
- Data type:
- string
- Description:
Name of the form field which holds the sender's email address (from header).
Normally, you can find the (filtered) name in the HTML output between the square brackets like tx_form[name] where name is the name of the object.
Only used if senderEmail is not set.
senderName¶
- Property:
- senderName
- Data type:
- string
- Description:
- Name which is shown as sender of the email (from header).
- Default:
- TYPO3_CONF_VARS['MAIL']['defaultMailFromName']
senderNameField¶
- Property:
- senderNameField
- Data type:
- string
- Description:
Name of the form field which holds the sender's name (from header).
Normally you can find the (filtered) name in the HTML output between the square brackets like tx_form[name] where name is the name of the object.
Only used if senderName is not set.
subject¶
- Property:
- subject
- Data type:
- string
- Description:
- Subject of the email sent by the form.
- Default:
- Formmail on 'Your_HOST'
subjectField¶
- Property:
- subjectField
- Data type:
- string
- Description:
Name of the form field which holds the subject.
Normally you can find the (filtered) name in the HTML output between the square brackets like tx_form[name] where name is the name of the object.
Only used if subject is not set.
[tsref:(cObject).FORM->postProcessor.mail]
htmlMailTemplatePath¶
- Property:
- htmlMailTemplatePath
- Data type:
- string
- Description:
Name of the template to use for HTML-Content.
Default is
Html. Useful to use multiple Mail Postprocessors with different templates.
plaintextMailTemplatePath¶
- Property:
- plaintextMailTemplatePath
- Data type:
- string
- Description:
Name of the template to use for Plaintext-Content.
Default is
Plain. Useful to use multiple Mail Postprocessors with different templates.
Messages¶
messages.error¶
- Property:
- messages.error
- Data type:
- string/ cObject
- Description:
Overriding the default text of the error message, describing the error.
When no cObject type is set, the message is a simple string. The value can directly be assigned to the messages.error property. If one needs the functionality of cObjects, just define the message appropriately. Any cObject is allowed.
For more information about cObjects, take a look in the document TSREF.
Example:
messages.error = TEXT messages.error { data = LLL:EXT:theme/Resources/Private/Language/Form/locallang.xlf:messagesError }
Example:
messages.error = Error while submitting form
- Description:
- Local language:"There was an error when sending the form by mail"
messages.success¶
- Property:
- messages.success
- Data type:
- string/ cObject
- Description:
Overriding the default text of the confirmation message.
When no cObject type is set, the message is a simple string. The value can directly be assigned to the messages.success property. If one needs the functionality of cObjects, just define the message appropriately. Any cObject is allowed.
For more information about cObjects, take a look in the document TSREF.
Example:
messages.success = TEXT messages.success { data = LLL:EXT:theme/Resources/Private/Language/Form/locallang.xlf:messagesSuccess }
Example:
messages.success = Thanks for submitting
- Default:
- Local language:"The form has been sent successfully by mail"