Email errors
554 5.7.5 permanent error evaluating DMARC policy: how to fix it
554 5.7.5 permanent error evaluating DMARC policy is a refusal citing a DMARC error. Check your record and DNS, then resend.
What this means
554 5.7.5 Permanent error evaluating DMARC policy is a bounce saying the receiving server refused your message because its DMARC check ended in an error. DMARC is a DNS record that tells receivers how to handle mail failing authentication for your domain.
554is a permanent SMTP failure (SMTP is the protocol servers use to exchange mail).5.7.5says little. RFC 3463 calls X.7.5 "Cryptographic failure".
Where "Permanent error evaluating DMARC policy" comes from
The error lists from Google, Microsoft and Yahoo do not contain this wording.
The closest standard term is permerror, an unrecoverable evaluation error in RFC 9989, the current DMARC standard. Gmail and Microsoft document other codes for a message that fails DMARC: 550 5.7.26 and 5.7.509.
Why it happens
The policy checked belongs to the domain in the visible From: address or, if that subdomain has no valid record, to a domain higher up, usually the organizational domain (example.com for mail.example.com). No provider we checked documents what triggers this bounce, so use the cases in RFC 9989 as a checklist:
- Two DMARC records at one name. Receivers discard them all.
- A bad
vtag.vmust be the first tag and its value must beDMARC1, which is case-sensitive, or the whole record is ignored. - An invalid
p,spornpvalue (the policy for the domain, its subdomains and non-existent subdomains; onlynone,quarantineandrejectare valid), such asp=rejct. RFC 9989 §4.10.1 tells receivers to act as if the record saidp=nonewhenrua(the report address) is valid, and to skip DMARC if not. §4.8 gives a different rule for syntax errors, so handling can vary. - A DNS error during the lookup. The message then cannot pass or fail DMARC, and its handling is up to the receiver.
RFC 9989 does not ask for a rejection in these cases and recommends a 4xx code for deferring delivery, so the 554 is this receiver's local decision.
How to fix it
-
Find who refused it. The
Diagnostic-CodeandRemote-MTAfields, when present, show the error and the server behind it. -
Read the record, with your domain in place of
example.com. If you send from a subdomain, also query each level above it, up to the organizational domain.nslookup -type=TXT _dmarc.example.com 1.1.1.1 -
Leave no more than one valid record at each name. A subdomain's record and its parent's are separate, so keep both. Merge duplicates into one, delete the rest and correct a bad
v,p,spornpin place. If the query times out or returnsSERVFAIL/Server failed, go to step 4 first. If no level up to the organizational domain has a record (NXDOMAINor notext =line), see no DMARC record found. A minimal valid record, with a mailbox you control inrua:TXTv=DMARC1; p=none; rua=mailto:dmarc@example.com
Caution: receivers that ignored the broken record can start applying its policy once it is valid. If it sets
quarantineorrejectinp,spornpand your reports do not yet show every legitimate sender passing, publishnonein those tags first and raise them in stages. Otherwise failing mail can go to spam or be refused. -
If the query times out or returns
SERVFAIL, look at DNS. Repeat it against8.8.8.8, then ask your DNS host to check the domain's name servers. -
Check SPF and DKIM, the sender list and message signature DMARC relies on. One of them must pass aligned with the From: domain. If neither does, see DMARC fail.
-
If everything is clean, write to the receiver. Send the full bounce to
postmaster@at the recipient's domain.
Confirm the fix
-
Repeat the
nslookupquery. Each name that has a record should show only one, starting withv=DMARC1and with a validp, plus validspandnpif present. -
If the old value appears, wait for its TTL (the DNS cache lifetime) to expire and query again.
-
Run our DMARC checker.
-
Send a new message to the address that bounced.
-
Read your aggregate reports.
policy_publishedshows the policy each receiver observed, and anerrorelement can name problems such as multiple records.