This article answers the Frequently Asked Questions about the Enhanced MTA for Campaign Classic and Campaign Standard.

The Adobe Campaign Enhanced MTA (Mail Transfer Agent) provides an upgraded sending infrastructure allowing for improved deliverability, reputation, throughput, reporting, bounce handling, IP ramp up and connection setting management.

It is implemented to improve scalability, increase delivery throughput and help send more emails faster. This is achieved with new adaptive delivery techniques that alter email sending settings in real-time based on feedback from Internet Service Providers.

  • If you’re using Adobe Campaign Standard, you’re already using the Enhanced MTA. No action is required.
  • If you’re using Adobe Campaign Classic and if you were provisioned a Campaign Classic instance after September 2018, no action is required as you’re already using the Enhanced MTA. For all other Campaign Classic customers, see the Frequently asked questions below.

Caution:

The Adobe Campaign Enhanced MTA is only available for Campaign Classic hosted or hybrid customers. Campaign Classic on-premise installations cannot be upgraded to use the Enhanced MTA. 

The Enhanced MTA implementation may impact some of the existing Campaign functionality. For more on this, consult the section below.

Frequently asked questions

General

Adobe Campaign can now be upgraded to use our new MTAs (Mail Transfer Agents) which run SparkPost’s commercial email MTA called Momentum.

Momentum represents innovative, high-performance MTA technology which includes smarter bounce handling and an automated deliverability optimization capability that helps senders achieve and maintain optimal inbox delivery rates. More than 37% of the world’s business email is sent using SparkPost’s MTA technology.

  • Adobe Campaign clients using the Enhanced MTA have seen a 300% increase in overall throughput speed, and a 90%+ reduction in soft bounces.
  • The Enhanced MTA uses the latest MTA technology to provide you with the optimal throughput speeds for your email delivery.
  • By adapting instantly and automatically to the feedback it receives, it also ensures more accurate and intelligent email delivery with real-time delivery data.

No. Upgrading does not require switching to new IPs, so you can continue using your existing, warmed email IPs.

No. We will be moving all Adobe Campaign instances over to the Enhanced MTA, and only the Enhanced MTA will be used for your email deliveries after your instance has been upgraded.

No, there is no extra fee associated with the upgrade process to enable the use of the Enhanced MTA.

Campaign Classic customers

  • If you’re new to Adobe Campaign Classic, you’re already using the Enhanced MTA. 
  • For Adobe Campaign Classic existing customers, we’ve implemented a phased rollout that covers all hosted or partially hosted (hybrid) instances. If you’re not already using it, we’ll be contacting you in the near future with the dates and details for upgrading your Adobe Campaign Classic instances to the Enhanced MTA.

Caution:

The Enhanced MTA is not available for on-premise installations. 

If you were provisioned a Campaign Classic instance after September 2018, no action is required as you’re already using the Enhanced MTA.

For all other customers, the Adobe Campaign team will reach out to coordinate a date for migration and will provide details on the appropriate steps needed to migrate.

Any deliveries that were prepared before your instance was upgraded to use the Enhanced MTA will need to be re-prepared in order to properly use the new MTA. 

For customers using Adobe Campaign transactional messaging functionality, any API calls to trigger an email will be queued during the very short upgrade downtime and will be attempted upon completion of the upgrade.

The entire process for your hosted instances requires a few minutes of downtime. We will monitor the email throughput and deliverability for up to 24 hours post-upgrade to assess any impact to your email deliveries. 

In case we discover any issues, we can quickly and temporarily revert your instance back to the native Adobe Campaign MTA. 

Currently, the Enhanced MTA only affects the email channel. Your push notifications and SMS deliveries will continue to use the native Campaign MTA and will not be affected in any way by the upgrade.

Enhanced MTA impacts

How upgrading to the Enhanced MTA will impact my Adobe Campaign instance(s)?

There will be some differences, at least initially. Your existing Adobe Campaign functionality may be impacted as follows:

The latest Campaign Classic instances include code that adds the required Enhanced MTA headers to every message.

If you're using an older instance that doesn't include this code, a new typology rule named Typology Rule for Enhanced MTAs must be added to all the existing typologies in your Campaign instance.

This rule is added by a Typology package installed as part of the upgrade to the Enhanced MTA.

Caution:

If you see this typology rule in your typologies, do not delete or modify it in any way. Otherwise, your email deliveries could be adversely affected.

This Typology package needs to be installed on the Adobe Campaign marketing instance.

If you're a hybrid client, the Adobe Campaign team will provide you with instructions on how to install the Typology package on your marketing instance as part of the upgrade to the Enhanced MTA. Contact your account executive to get the full instructions.

Caution:

Instructions provided by the Adobe Campaign team on how to install the Typology package should be carefully followed. Otherwise you may encounter major issues with your IPs used to send emails.

For more on typologies, see About campaign typologies in Campaign Classic.

The MX management delivery throughput rules are no longer used. The Enhanced MTA has its own MX rules that allow it to customize your throughput by domain based on your own historical email reputation, and on the real-time feedback coming from the domains where you’re sending emails.

For more on MX management, see MX configuration in Campaign Classic and MX management in Campaign Standard.

The bounce qualifications in the Campaign Delivery log qualification/Message qualification table are no longer used. The Enhanced MTA determines the bounce type and qualification, and sends back that information to Campaign.

Note:

The Enhanced MTA qualifies the SMTP bounce and sends that qualification back to Campaign in the form of a bounce code mapped to a Campaign bounce reason and qualification.

All messages will show as Sent as soon as they are successfully relayed from Campaign to the Enhanced MTA. They will stay in that state unless or until a bounce for that message is communicated back from the Enhanced MTA to Campaign.

Consequently:

  • In the Summary view of each message, the Success (Classic) or Delivered (Standard) percentage will start out at 100% and then go down throughout the validity period of the delivery as the soft and hard bounces get reported back from the Enhanced MTA to Campaign.
  • Soft-bouncing messages will no longer show as Failed after day one of the delivery, and be retried on each additional day of the validity period for the delivery. They will stay in the Enhanced MTA retry queue throughout the delivery validity period.

Note:

You should wait until the end of the validity period to see the final Success/Delivered percentage, and the final number of Sent and Failed messages.

The fact that the Success/Delivered percentage will go to 100% very quickly indicates that your instance has been upgraded to the Enhanced MTA.

The Campaign Delivery throughput graph will no longer display the throughput to your email recipients. That graph will now show the throughput speed for the relay of your messages from Campaign over to the Enhanced MTA.

For more on the delivery throughput, see Accessing deliveries throughput information in Campaign Classic and Delivery throughput in Campaign Standard.

The validity period setting in your Campaign deliveries will be used by the Enhanced MTA only if set to 3.5 days or less. If you define a value higher than 3.5 days in Campaign, it will not be taken into account.

Note:

For example, if the validity period is set to the default value of 5 days in Campaign, soft-bouncing messages will go into the Enhanced MTA retry queue and be retried for only up to 3.5 days from when that message reached the Enhanced MTA. In that case, the value set in Campaign will not be used.

Once a message has been in the Enhanced MTA queue for 3.5 days and has failed to deliver, it will time out and its status will be updated from Sent to Failed in the delivery logs.

DKIM (DomainKeys Identified Mail) email authentication signing is done by the Enhanced MTA. DKIM-signing by the native Campaign MTA will be turned off within the Domain management table as part of the Enhanced MTA upgrade.

For more on DKIM, see DKIM authentication in Campaign Classic and Managing email domains in Campaign Standard.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy