Back to dashboard

Amazon SES: Easy DKIM and MAIL FROM domain

What this guide is for

Amazon SES sends your applications' emails. For them to be authenticated with your domain, you verify the domain as an identity in SES with Easy DKIM, then, preferably, set up a custom MAIL FROM domain to align SPF.

Expected records

Type Name (host) Value
CNAME (x3) <token>._domainkey <token>.dkim.amazonses.com
MX mail (MAIL FROM subdomain, e.g. mail.example.com) 10 feedback-smtp.<region>.amazonses.com
TXT (SPF) mail (same subdomain) v=spf1 include:amazonses.com ~all
TXT (DMARC) _dmarc v=DMARC1; p=none; rua=mailto:[email protected]
  • Easy DKIM provides three CNAME records with random tokens. Copy them from the console: the target zone can vary by region (SigningHostedZone value in the API).
  • Do not add an underscore in front of the token. If your host appends the domain, enter the relative name or end the full name with a period.
  • The MX and SPF records of the MAIL FROM domain go on the subdomain, not on your root domain. That subdomain must not be used to receive email or be your From domain.

Steps in the AWS console

  1. Open the Amazon SES console in the right region, then Configuration > Identities and Create identity.
  2. Choose Domain, enter your domain and keep Easy DKIM with a 2048-bit RSA key (you can go down to 1024 bits if your host does not support 2048).
  3. Create the identity, then copy the three CNAME records shown to your DNS host. With Route 53 in the same account, SES can create them automatically.
  4. SES looks for the records for up to 72 hours. The identity becomes verified and DKIM signing is turned on.
  5. For an existing identity: open the identity, Authentication tab, then edit the DKIM section.
  6. MAIL FROM domain: in the identity, set up a Custom MAIL FROM domain (e.g. mail.example.com), publish the MX and SPF TXT records shown, and choose the behavior on MX failure (fall back to amazonses.com or reject the message).

Exact button names can change between console versions: refer to the AWS documentation.

Check the setup

  1. In Identities, the domain should be verified and DKIM successful.
  2. Send a test email to Gmail: DKIM: PASS with your domain, and SPF: PASS with mail.example.com if the MAIL FROM domain is set up.
  3. Run a new scan in this tool. Easy DKIM tokens are random: the tool cannot guess these selectors. It recognizes Amazon SES when amazonses.com appears in the SPF record of the scanned domain (the MAIL FROM subdomain's SPF record is not read).

DMARC

Publish a single TXT record at _dmarc.<your domain>, starting with monitoring:

v=DMARC1; p=none; rua=mailto:[email protected]

Read the reports for a few weeks, check that all your legitimate mail passes, then move gradually to p=quarantine and p=reject.

Official documentation

Amazon SES: setup guide - SEKOIA