As a Campaign administrator, you can configure email channel settings. These advanced settings include general email channel parameters, email routing accounts, email processing rules and email properties. On this page, learn how to edit the default values for the general email and sending parameters.
The email configuration screen allows to define the parameters for the email channel. Administrators can access these configurations in the Administration > Channels > Email > Configuration menu.
Authorized masks fields
The Header parameters of sent emails section lists the authorized email addresses that you can use to send emails to your recipients (sender address) and to enable them to send back automated replies like asynchronous bounces, out-of-office replies, etc. (error address). Adobe Campaign checks that the addresses entered are valid during the message preparation stage. This operating mode ensures that no addresses are used that could trigger deliverability issues.
The Delivery reports ID is provided by the Adobe Customer Care team. It identifies each instance with a deliverability ID which is used in the technical deliverability reports.
Adobe Campaign sends the messages beginning on the start date.
When a message in a delivery is rejected due to a temporary error or a soft bounce, Campaign retries to send this message each day. Use the Message delivery duration field to specify the timeframe during retries can happen.
This parameter in Campaign is now only used if set to 3.5 days or less. If you define a value higher than 3.5 days, it will not be taken into account.
The Online resources validity duration field is used for uploaded resources, mainly for the mirror page and images. The resources on this page are valid for a limited time (to save disk space).
Temporarily undelivered messages are subject to an automatic retry. For more on this, see Retries after a delivery temporary failure.
The maximum number of retries to be performed and the minimum delay between retries are now based on how well an IP is performing both historically and currently at a given domain. The Retry period and Number of retries settings in Campaign will be ignored.
Email quarantine parameters
In the Time between two significant errors field, enter a value to define the time the application waits before incrementing the error counter in case of a soft-bounced failure. The default value is “1d”, for 1 day.
When the Maximum number of errors before quarantine value is reached, the email address is then quarantined. The default value is “5”: the address is quarantined on the fifth error. This means that the contact will be automatically excluded from subsequent deliveries.
For more on quarantines, see Understanding quarantine management.
The Integrated email routing external account is provided by default. It contains the technical parameters that allow the application to send emails.
The account type must always be set to Routing, the channel to Email and the delivery mode set to Bulk delivery.
The Email processing rules can be accessed by administrators through the Administration > Channels > Email menu.
The email domains and the MX rules are now automatically managed and cannot be changed.
Asynchronous bounces are still qualified by the Campaign inMail process through the Bounce mails rules.
These rules contain the list of character strings which can be returned by remote servers and which let you qualify the error (Hard, Soft or Ignored).
Synchronous delivery failure error messages are now qualified by the Adobe Campaign Enhanced MTA, which determines the bounce type and qualification, and sends back that information to Campaign.
For more on bounce mail qualification, see this section.
This section details the list of parameters available in the properties screen of an email or email template.
Some parameters are only available in templates. Parameters you can access depend on your permissions.
To edit the properties of an email or an email template, use the Edit properties button.
On the top of the email parameter screen, identify the email using the Label and ID fields. This information appears in the interface but is not visible to the message recipients.
The ID must be unique.
Use the Brand field to select the brand linked to the delivery. For more information on using and configuring brands, refer to the Branding section.
In the Campaign field, enter the campaign associated to the email.
You can also add a Description in the corresponding field and edit the image displayed on the email thumbnail in the lists.
The Send section is only available for email templates. It contains the following parameters:
Temporarily undelivered messages are subject to an automatic retry. For more on this, see Retries after a delivery temporary failure.
The minimum delay between retries and the maximum number of retries to be performed are now based on how well an IP is performing both historically and currently at a given domain. The Retry period and Max. number of retries settings in Campaign will be ignored.
The delivery duration setting (defined in the Validity period parameters section) set up in Campaign will still be honored but only up to 3.5 days. At that point, any message in the retry queue will be removed from the queue and sent back as a bounce. For more on delivery failures, see this section.
You can configure the format of emails to be sent. There are three options available:
Use recipient preferences (default mode): the message format is defined according to the data stored in the recipient profile and stored by default in the Email format field (@emailFormat). If a recipient wishes to receive messages in a certain format, this is the format sent. If the field is not completed, a multipart-alternative message is sent (see below).
Let recipient mail client choose the most appropriate format (multipart-alternative): the message contains both formats: text and HTML. The format displayed upon reception depends on the configuration of the recipient’s mail software (multipart-alternative).
This option includes both versions of the message. It therefore impacts the delivery throughput, because the message size is greater.
Send all messages in text format: the message is sent in text format. HTML format will not be sent, but used for the mirror page only when the recipient clicks the link in the message.
Use the Enable SMTP test mode option to test sending emails via an SMTP connection without actually sending messages. The delivery is processed up to connection to the SMTP server but is not sent: for every recipient of the delivery, Campaign connects to the SMTP provider server, executes the SMTP RCPT TO command, and closes the connection before the SMTP DATA command.
This option is available for emails and email templates.
If you enable the SMTP test mode option for an email template, all email messages created from this template will have this option enabled.
When this option is enabled for an email, no messages will be sent until it is unchecked.
A warning will be displayed in the email or email template dashboard.
For more information on configuring SMTP, refer to the List of email SMTP parameters section.
The Validity period section contains the following parameters:
Explicitly set validity dates: when this box is unchecked, you must enter a duration in the Delivery duration and Resource validity limit fields.
Check this box if you would like to define specific times and dates.
Delivery duration / Validity limit for sending messages: Adobe Campaign sends the messages beginning on the start date. Use this field to specify the period during which the messages can be sent.
You must define a value up to 3.5 days. If you set a value higher than 3.5 days, it will not be taken into account.
The Delivery duration parameter does not apply to transactional messages. For more on transactional messaging, see this section.
Resource validity duration / Validity limit date for resources: this field is used for uploaded resources, mainly for the mirror page and images. The resources on this page are valid for a limited time (to save disk space).
Mirror page management: the mirror page is an HTML page accessible online via a web browser. Its content is identical to the email content. By default, the mirror page is generated if the link is inserted in the mail content. Use this field to modify how this page is generated:
The mirror page is generated only if an HTML content has been defined for the email.
The Tracking section contains the following parameters:
The Advanced parameters section contains multiple parameters.
The first fields allow you to enter information necessary to elaborate email message headers. You can manage here the reply address and text as well as the sender address (which fills the field “From:”). This information can be personalized.
Click the button to the right of the field that is going to be changed, then add the personalization field, content block or dynamic text.
Inserting and using the personalization content is detailed in the Personalizing email content documentation.
Use the targeting context to define a set of tables that will be used for email targeting (in the audience definition screen) and personalization (defining personalization fields in the HTML content editor).
This field indicates the routing mode used. It references an external account. For example, this can be used if you would like to use an external account containing specific branding configurations.
External accounts are accessible via the Administration > Application settings > External accounts menu.
Preparing messages is detailed in the Approving messages section.
Typology: before any send, messages must be prepared in order to validate the content and configuration. The verification rules applied during the preparation phase are defined in a typology. For example, for emails, preparation involves checking the subject, URLs and images, etc. Select the typology to apply in this field.
Typologies, which can be accessed via the Administration > Channels > Typologies menu, are presented in this section.
Compute the label during delivery preparation: use this option to calculate the label value of the email during the message preparation phase using personalization fields, content blocks, and dynamic text.
It is also possible to personalize the delivery label with events variables that have been declared into the workflow’s external signal activity. For more on this, refer to this section.
Save SQL queries in the log: use this option to add SQL query logs in the journal during the preparation phase.
In this section, you can configure the default prefix to use in the subject line of the proof messages. Learn more about proofs in this section.
The SMTP section contains the following parameters:
Character encoding: check the Force encoding box if you would like to force message encoding, then select the encoding you want to use.
Bounce mails: by default, bounce mails are received in the platform’s error inbox (defined in the Administration > Channels > Email > Configuration screen). To define a specific error address for an email, enter the address in the Error address field.
Additional SMTP headers: this option allows for additional SMTP headers to be added to your messages. The script entered in the Headers field must reference one header per line, in the form of name:value. Values are encoded automatically if necessary.
Adding a script for inserting additional SMTP headers is reserved for advanced users. The syntax of this script must comply with the requirements of this content type: no unused space, no empty line, etc.
The Access authorization section contains the following parameters:
The Organizational unit field is used to restrict access to this email to certain users. The users associated with the specified unit or parent units will have read and write access to this email. Users associated with child units will only have read access to this email.
You can configure organizational units via the Administration > Users & Security menu.
The Created by, Created, Modified by and Last modified fields are automatically completed.
If you are NOT running the latest version of Campaign, the parameters and UI sections described below still apply to you.
The Retries settings in the Configuration menu and in the Sending parameters of the email properties indicate how many retries should be performed the day after the send is started (Number of retries / Max. number of retries) and the minimum delay between retries (Retry period).
The number of retries can be changed globally (contact your Adobe technical administrator) or for each delivery or delivery template.
By default, five retries are scheduled for the first day with a minimum interval of one hour, spread out over the 24 hours of the day. One retry per day is programmed after that and until the delivery deadline, which is defined globally in the Delivery parameters section of the Configuration menu, or in the Validity period section at the delivery level (see the Delivery duration section below).
Use the Message delivery duration parameter in the Configuration menu to specify the time frame in which any message in the delivery that encounters a temporary error or soft bounce will be retried.
Use the Delivery duration or Validity limit for sending messages parameter in the Validity period parameters section to specify the duration during which the messages can be sent.
The MX management, Bounce mails and Domain management rules can be accessed and modified by administrators through the Administration > Channels > Email > Email processing rules menu. Learn more.
To list the various bounces, and their associated error types and reasons, click the Adobe logo, in the top-left, then select Administration > Channels > Quarantines > Message qualification.
Bounces can have the following qualification statuses:
In case of an outage of an ISP, emails sent through Campaign will be wrongly marked as bounces. To correct this, you need to update bounce qualification. Learn more.
In the Summary view of each message, the Delivered percentage progressively goes up throughout the validity period of the delivery, as the soft and hard bounces get reported back.
Soft-bouncing messages show as Failed on the first day after the delivery. These messages are retried each day, until the validity period of the delivery ends.