Response Route SMTP (Mail)
Introduction: Phase 6.
Note: Field values can be composed of static and variable components. Example: @var__FIRSTNAME@.smith@example.com.Here the first name is the value of a variable, the rest is a fixed string. Several field or variable values can be used.
Note: It is important to note that the size of an email to be sent is not unrestricted because most mail servers normally only allow emails up to a certain maximum size.
(1) Here you can select a channel of type Mail. Note: If possible, always use channels to centrally manage connection parameters. In addition to the increased clarity that also facilitates maintenance. If the connection parameters change, you only have to adjust the data in one place and you do not forget a profile.
(2) The IP address or the DNS name of the SMTP server. If this input field does not contain a value and no partner channel has been selected, the input fields SMTP Host, Port, User and Password will be overwritten by the entries in configuration file ./etc/startup.xml. See section Mail (channel settings). Note: A value greater than 0 for the port overrides the port of a selected channel. If value 0 is set, the port set in the channel is used.
(3) Variables can be accessed with syntax @VARIABLENNAME@. If you use prefix bcc: in email addresses in input field CC, the email will be sent as BCC and not as CC. If you use prefix reply-to: you can set the email header Reply-To (a reply address other than the sender). Important note: The email header will only be set once, i.e. further entries of this kind have no effect. Please also note the corresponding system variable below.
(4) Text in the body of the email. Variables can be accessed with syntax {--@VARIABLENNAME@--}.
(5) If this checkbox is set, you can create Rich Text with an editor. Note: If the possibilities of the editor are too limited for you, you can also uncheck the checkbox and insert self-generated HTML formatting in the text.
(6) If this checkbox is set, empty files are transferred as well.
(7) Here you can additionally attach files from the file system. You can use the usual placeholders. If you use the prefix filter:, you can use an entry to define an entire list of files instead of just one file. So all files orders*.pdf in this example. The names of the files are also used as names of the attachments. Note: The files are deleted after they have been attached. This behaviour can be prevented by creating a profile variable VAR_MAIL_SKIP_DELETE_ATTACHMENT (type Boolean) with value true. Phase 3 must be active for this.
(8) Here you can select how the data is sent (body/attachment). If you have selected to attach the data and it is empty, then this Response Route is skipped. This means that no email will be sent.
(9) If the MIME type is lobster/unzip, the payload is considered a ZIP file and the files included are added as individual attachments.
(10) The name of the main attachment. Not relevant for (7).
System Variables
If the system variables VAR_RESPONSE_MAIL_HEADER_<name of mail header> are defined and filled with values, the corresponding email headers will be set (with these values) for the email to be sent here in the Response Route. Uppercase and lowercase are considered. You should stick to the RFC notation of the header. So the system variable VAR_RESPONSE_MAIL_HEADER_Reply-To can be used to set the email header Reply-To (a reply address other than the sender). Note: If the variable has a value, it will always be used first to set the email header. See item (3) above.