Skip to content
DMARC Pulse

Email errors

Amazon SES DMARC fail: why it happens and how to fix it

Amazon SES DMARC fail means no domain passed SPF or DKIM and aligned with your From domain. Set up Easy DKIM and a custom MAIL FROM to fix it.

What this means

Amazon SES DMARC fail means the receiving server found no domain that passed SPF or DKIM and also matched your visible From domain. That match is called alignment, and DMARC needs one aligned pass. By default, SES authenticates with amazonses.com, not your domain.

SES mail can pass both checks and still fail DMARC:

  • SPF checks the MAIL FROM domain (the hidden envelope address), and SES uses a subdomain of amazonses.com there.
  • SES adds a DKIM signature with d=amazonses.com to every message.

Neither aligns with example.com. Easy DKIM makes SES sign with your domain. A custom MAIL FROM domain moves the envelope address to your subdomain.

Why it happens

  • No DKIM on your domain. Verifying an email address does not set up DKIM for its domain, so the mail carries only the amazonses.com signature.
  • Missing records or another Region. Easy DKIM needs three CNAME records and is set up separately in each Region and account. If the records are removed, SES disables signing there and emails you.
  • An address with its own settings. An email address identity can override the domain's DKIM settings and send without its signature.
  • Default MAIL FROM. With no custom domain, SPF passes only for amazonses.com. A custom domain also falls back to your Behavior on MX failure choice whenever its state is not Success.
  • Strict alignment. AWS says SPF alignment with SES needs a DMARC record without aspf=s. With adkim=s, a signature for example.com fails on mail from news.example.com.
  • Forwarding or a specific receiver. Forwarding can break SPF. AWS also reports that Microsoft Enterprise Outlook randomly validates only one of the two DKIM signatures.

How to fix it

  1. Paste the full header of a failed message into the Email Header Analyzer. Compare your From domain with smtp.mailfrom and each header.d or header.i.

  2. In the SES console, open Identities in the Region that sent the mail. Your domain should show Verified, with DKIM configuration at Successful. If it is missing, choose Create identity, then Domain, and keep the default Easy DKIM.

  3. Publish the three CNAME records from the Authentication tab exactly as shown. Check that your DNS host did not add the domain a second time.

    Caution: switching a BYODKIM domain (your own key) to Easy DKIM can send mail unsigned until verification finishes.

  4. Confirm DKIM signatures is enabled in every Region and account that sends for the domain. If the From address is also an email address identity, check its setting too.

  5. In Custom MAIL FROM domain, choose Edit, select Use a custom MAIL FROM domain and enter a subdomain used for nothing else, such as bounce.example.com.

    Caution: Reject message under Behavior on MX failure makes SES refuse mail from this identity while the MX record is wrong. Keep Use default MAIL FROM domain during setup.

  6. On that subdomain, publish the MX and TXT records SES shows. In us-east-1, the MX value is feedback-smtp.us-east-1.amazonses.com, with priority 10. The TXT value, in quotation marks if your DNS host needs them:

    TXT
    v=spf1 include:amazonses.com ~all

    Publish exactly one MX record there, or the setup fails. Keep one SPF record on that name and leave your root domain's SPF as it is.

  7. If your DMARC record has aspf=s, or adkim=s while you send from a subdomain, remove that tag. Both default to relaxed.

    Caution: do not tighten p= to solve this. AWS advises moving from p=none in phases, because the wrong policy can stop delivery.

Confirm the fix

  1. Wait until DKIM configuration shows Successful and the custom MAIL FROM state shows Success. DNS changes can take up to 72 hours.
  2. Send a new message to a mailbox you control. In Authentication-Results, look for dmarc=pass, plus dkim=pass with your domain in header.d or header.i, or spf=pass with your subdomain in smtp.mailfrom.
  3. Check your record with the DMARC Checker. In your next aggregate reports, dkim or spf under policy_evaluated should read pass for SES rows.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Why does DMARC fail on Amazon SES when SPF and DKIM both pass?
DMARC also needs the passing domain to align with your From domain. By default, SES uses a subdomain of amazonses.com for SPF and adds a signature with d=amazonses.com. Both can pass without matching your domain. Set up Easy DKIM on your domain, a custom MAIL FROM domain, or both.
Do I need both Easy DKIM and a custom MAIL FROM domain?
One aligned pass is enough for DMARC, so either can carry a message. AWS says using both gives DMARC the best chance. Forwarding can invalidate SPF, while DKIM keeps working if the content is not modified.
Can I remove the d=amazonses.com signature?
AWS says SES adds it automatically, that you can ignore it, and that SES cannot stop adding it because complaint feedback loops need it. DMARC only needs one aligned pass. Where a receiver validates a single signature, as AWS reports for Microsoft Enterprise Outlook, an aligned custom MAIL FROM gives the message a second route.
Can I fix this when I send from a Gmail address through SES?
AWS does not let you toggle DKIM signing or set a custom MAIL FROM domain for addresses on domains you do not own, such as gmail.com, because you cannot add the DNS records. Send from a domain you own and verify it in SES.
What does dmarcVerdict FAIL mean in an SES notification?
That field appears in notifications for mail SES receives, so it describes the incoming message. FAIL means the message failed DMARC. GRAY means SPF or DKIM passed but the sending domain has no DMARC policy or uses p=none. The dmarcPolicy field appears only on failures and shows that domain's policy.
Does SES tell me when DKIM is not aligned?
If you enable Virtual Deliverability Manager, its advisor can show the message 'DKIM record is not aligned.' when the signature domain does not match the From domain. It also flags missing DMARC, DKIM and SPF records.

Sources consulted

AWS: Easy DKIM in Amazon SES
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.