Mail Exchanger error on setting up API-triggered transactional email campaigns in AJO
This article addresses the inability to create a new channel configuration due to a Mail Exchanger (MX) error when setting up an API-triggered transactional email campaign in Adobe Journey Optimizer (AJO). The resolution involves ensuring proper DNS configuration and verifying product limitations for Domain-based Message Authentication, Reporting, and Conformance (DMARC) policies.
Description description
Environment
Product: Adobe Experience Platform (AEP)
Component: Adobe Journey Optimizer (AJO)
Issue/Symptoms
Creating a new channel configuration for transactional emails results in an MX error. However, an older channel configuration for marketing emails that use the same subdomain works without issues.
Resolution resolution
Follow these steps to address the issue:
-
Ensure that all necessary DNS records, including CNAME and MX records, are correctly configured. A missing CNAME record can prevent proper resolution of the subdomain.
-
Verify if there is any DMARC policy applied to the subdomain.
If the DMARC record specifies
p=none,it indicates no strict policy is enforced, allowing email campaigns to proceed even with broken DNS links.
Related reading
DMARC policies in our Journey Optimizer Guide
API-triggered campaigns in Journey Optimizer