What the message looks like
550 5.7.1 Unauthenticated email from example.com is not accepted due to domain's DMARC policy. Please contact the administrator of example.com domain if this was a legitimate mail.Common causes
- A service sends mail for your domain (newsletter tool, CRM, ticket system) but is not in your SPF and does not sign with your domain's DKIM key.
- Alignment fails: SPF or DKIM passes, but for the provider's domain, not for the domain in the From address.
- A forwarder or mailing list changes the message or the sending server, which breaks SPF and DKIM.
- The policy was set to
p=rejectbefore all senders were ready. - The SPF record is broken, for example over the lookup limit, so SPF fails for everyone.
Check
- What is your DMARC policy?
- What does your SPF record contain?
dig +short TXT example.com | grep spf1 - Which result did the recipient see? Look in the bounce or the headers
grep -iE 'authentication-results|dmarc=|spf=|dkim=' bounce.eml - Is the DKIM key for the sending selector published?
dig +short TXT selector1._domainkey.example.com
Fix
- Add the sending service to your SPF record, and keep it under 10 DNS lookups. The SPF checker counts them.
- Enable DKIM for your own domain at the service, so it signs with
d=example.comand not with its own domain. - Make sure the From address uses the same domain that SPF or DKIM authenticates (alignment).
- If senders are not ready, go back to
p=noneorquarantineand read the aggregate reports (rua) first. - For forwarded mail, rely on DKIM, which survives forwarding, not on SPF.
Typical scenario
Your company set its DMARC policy to p=reject. Marketing sends the next newsletter through a mailing tool that does not sign with your own key. Gmail rejects the mail with "550 5.7.1 … not accepted due to domain's DMARC policy". The tool passes SPF and DKIM, but for its own domain, not yours. First read the DMARC aggregate reports (rua); they show which sending sources fail.
FAQ
Why does it only fail for some recipients?
Only receivers that enforce DMARC reject. Others, such as small servers, may ignore your policy.
How do I move to p=reject safely?
Start with p=none and a report address, fix every legitimate sender from the reports, then go to quarantine and only later to reject. The DMARC generator builds the record.
What does "alignment" mean in simple terms?
The domain in the visible From address must match the domain that SPF or DKIM validated. For SPF that is the envelope sender domain (Return-Path), for DKIM the one in the d= tag. In "relaxed" mode a subdomain of the same organisation is acceptable.
Do SPF and DKIM both have to pass?
No. DMARC passes if at least one of them passes and aligns with the From domain. That is why DKIM with your own domain is recommended: it usually survives forwarding better than SPF, which is tied to the sending IP.
Can a subdomain have its own policy?
Yes. With the sp= tag in the main domain's DMARC record you set the policy for subdomains. Alternatively publish a separate record at _dmarc.news.example.com. That lets you run newsletter senders on a subdomain with a looser policy at first.