Get instant support with our search!
Why do MX Records need to be implemented for Custom Domains in AWS?
Another form of personalisation offered by the MyCompliance platform is the ability to customise the email 'From Address' used when sending content notification emails to staff. This service allows you to spoof your internal email domain to deliver emails.
To enable this, a representative from the MetaCompliance Support team will provide the required CNAME records and an MX record that are both generated when an entry is created for the domain.
The customer must add the MX record to their public DNS record. This requirement exists because of how AWS handles both the sending of emails and the receiving of data back from end users' interactions with emails.
AWS sends emails from one server and receives interaction data—such as clicks, opens, deliveries, and other engagement metrics—on a different server. As a result, an MX record must be configured on the customer’s public DNS so that AWS can safely receive data back from the custom email domain.
You must also publish an SPF (type TXT) record to confirm that Amazon SES is authorised to send emails from your domain.
If the customer does not add the MX record to their public DNS record, the domain will fail AWS verification, and they will be unable to use the domain on their MyCompliance tenant.
⚠️ Please note:
(a) This is a requirement from AWS over which MetaCompliance has no control.
(b) It is not mandatory to configure a custom 'From Address' in order to send emails from the MyCompliance Cloud platform.
If you do not wish to proceed with these changes, you can use the default email address no-reply@metacompliance.com to send Content notification emails from the platform.
For more information, please refer to the following AWS documentation: Using a custom MAIL FROM domain