Email errors
DMARC fail: what it means and how to fix it
DMARC fail means no SPF or DKIM pass aligned with the From domain. See what receivers do with the message, why it happens and how to fix it.
What this means
DMARC fail means a message had no SPF or DKIM pass for a domain aligned with its visible From address. SPF lists the servers allowed to send for a domain. DKIM adds a signature tied to a domain.
Mail servers record the result in the Authentication-Results header. Microsoft documents this example, shown here with other domains. SPF and DKIM pass, and DMARC still fails:
Authentication-Results: spf=pass (sender IP is 198.51.100.10)
smtp.mailfrom=bounces.example.net; dkim=pass (signature was verified)
header.d=example.net; dmarc=fail action=oreject
header.from=example.com;compauth=fail reason=000
The wording varies by mail server. dmarc=none means the domain has no DMARC record.
What happens after a DMARC failure
The p= tag in the domain's DMARC record states a preference. The receiver makes the final decision.
p=none: no preference. RFC 9989 says it must not change how the receiver already handles mail. Other filters can still send the message to spam.p=quarantine: the owner considers the mail suspicious. Receivers may move it to spam or quarantine.p=reject: the owner considers the use of its domain invalid. Receivers may refuse it.
RFC 9989 shows 550 5.7.1 Email rejected per DMARC policy for example.com as an example. The same code can mean a different refusal on another server, so read the text after it.
DNS authentication: DMARC fail
DNS Authentication: DMARC Fail is the label the University of Sussex shows under Policies Triggered when Mimecast holds a message there. If you received that notice, tell the sender, because the domain is theirs to fix. Ask your IT team if you need the message released.
Why it happens
Only an aligned pass counts. Aligned means the domains match or, in the default relaxed mode, share an organizational domain (usually the registered domain, such as example.com for news.example.com). That is why DMARC failed on a message showing spf=pass and dkim=pass: each check passed for a domain that does not align with From.
- A sending platform is not set up for your domain. SPF and DKIM can pass, but only for its own domains. Amazon SES defaults to a MAIL FROM under
amazonses.com. - Forwarding or a mailing list. The forwarder's IP address is outside your SPF record. DKIM generally survives plain forwarding, but a list's footer or subject tag breaks it.
- Strict alignment. With
aspf=soradkim=s,bounces.example.comno longer aligns withexample.com. - Spoofing. Someone else used your domain, and
dmarc=failis the correct result.
How to fix it
- Paste a failing message's full headers into the email header analyzer.
- Compare
header.from(the visible From),smtp.mailfrom(the envelope sender that SPF checks) andheader.d(the DKIM signing domain; some receivers showheader.i). Ifheader.fromis not yours, only its owner can fix this. - Find the source's IP address in your aggregate reports. They need a
rua=tag in your_dmarcrecord, so add one if it is missing. Do not authorize a source you do not recognize. - If a check failed for a source you recognize, correct its SPF record or DKIM key. Caution: edit the existing SPF record. A second record, or more than 10 terms that trigger DNS queries, makes SPF return
permerror. - In each real platform, publish the DKIM records it gives you, then turn on signing with your domain.
- If the platform allows it, set its MAIL FROM (bounce) domain to a subdomain of yours that handles no other mail, and publish the records it lists. Caution: some platforms require an MX record there, so never reuse a name that receives mail. An
include:alone does not align mail whose MAIL FROM stays on the platform's domain. - If strict alignment is the cause, change
aspf=soradkim=storin your DMARC record (TXT at_dmarc.example.com). - Do not tighten the policy to clear the failure. Caution:
p=quarantineorp=rejectrepairs nothing and can send real mail to spam or get it refused.
Confirm the fix
- Once the DNS change is visible, send a new message through the same platform to another mailbox you control.
- Paste its headers into the analyzer. You want
dmarc=pass. Arrival alone proves nothing. - Watch your aggregate reports for several days. Under
<policy_evaluated>,<dkim>or<spf>should readpassfor that source.
Some forwarded mail and spoofing will keep failing. That alone does not point to a setup error.