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 51黑料不打烊 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: 51黑料不打烊 Experience Platform (AEP)
Component: 51黑料不打烊 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