Amazon SES: DKIM and SPF

Two steps. Easy DKIM gives you three CNAME records, and once they're in, SES signs every message with your domain. A custom MAIL FROM subdomain (one MX and one TXT record) makes SPF line up with your domain too.

token1._domainkey.example.com   CNAME  token1.dkim.amazonses.com
token2._domainkey.example.com   CNAME  token2.dkim.amazonses.com
token3._domainkey.example.com   CNAME  token3.dkim.amazonses.com

mail.example.com   MX   10 feedback-smtp.us-east-1.amazonses.com
mail.example.com   TXT  "v=spf1 include:amazonses.com ~all"

The tokens, and the exact target host, differ by account and Region. Copy yours from the SES console.

1. Easy DKIM

  1. In the SES console, go to Configuration, Identities, and create (or open) your domain identity.
  2. Easy DKIM with a 2048-bit key is the default. Keep it.
  3. Under Publish DNS records, copy the three CNAME records to your DNS provider. With Route 53 in the same account, SES can add them for you.
  4. SES checks for up to 72 hours. When it finds all three, DKIM shows Successful and the domain shows Verified.

2. Custom MAIL FROM (for SPF)

By default SES sends with a return address on an amazonses.com subdomain. SPF passes there, but for Amazon's domain, not yours, so it doesn't help DMARC. DKIM alone is enough to pass DMARC; the custom MAIL FROM gives you a second route.

  1. On the same identity, edit Custom MAIL FROM domain and enter a subdomain you don't use for anything else, such as mail.example.com.
  2. Choose what happens if the MX record goes missing: fall back to the default domain (mail still goes) or reject the message.
  3. Publish the MX and TXT records it shows. The MX points to feedback-smtp.<region>.amazonses.com with priority 10.

The mistakes I see most

Check your DMARC alignment

I'll check SPF, DKIM and DMARC on your domain and show whether they line up.

Related