SPF, DKIM and DMARC for Amazon SES
Set up Amazon SES so app mail passes DMARC: the three Easy DKIM CNAME records, a custom MAIL FROM subdomain with its MX and SPF records for SPF alignment, and the DMARC record.
Amazon SES
app and transactional mail
SPF
aligns after setup: aligns only with a custom MAIL FROM subdomain
DKIM
aligns after setup: three Easy DKIM CNAME records
DMARC pass
one aligned pass is enough
- CNAME
<token1>._domainkey<token1>.dkim.amazonses.comThree of these, one per token SES shows. - MX
<mail-from subdomain>10 feedback-smtp.<region>.amazonses.comOnly for a custom MAIL FROM domain, such as bounce.<domain>. - TXT
<mail-from subdomain>v=spf1 include:amazonses.com ~all
1Create the domain identity
In the SES console open Configuration › Identities and create a domain identity, in every AWS Region you send from. Easy DKIM is the default.
2Publish the three DKIM CNAMEs
Copy the three CNAME records the identity shows. SES verifies the domain and starts signing once it finds them.
3Set a custom MAIL FROM domain
On the identity, edit Custom MAIL FROM domain and choose a subdomain used for nothing else, such as bounce.<domain>. Publish the MX and SPF records it shows.
4Publish a DMARC record
At _dmarc.<your domain>, a TXT record starting at p=none with a report address, so you can see this service's mail pass before you enforce. The DMARC generator writes one.
The free tools
Set up once. Watched every day.
DNS says what a domain asks receivers to do. Only the reports receivers send say what happened to its mail. DMARC Harbor reads those reports for every client domain, every day, names each service sending as it, and says when it is safe to move to p=reject.