Skip to content
DMARC Pulse

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.

  • 554 is a permanent SMTP failure (SMTP is the protocol servers use to exchange mail).
  • 5.7.5 says 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 v tag. v must be the first tag and its value must be DMARC1, which is case-sensitive, or the whole record is ignored.
  • An invalid p, sp or np value (the policy for the domain, its subdomains and non-existent subdomains; only none, quarantine and reject are valid), such as p=rejct. RFC 9989 §4.10.1 tells receivers to act as if the record said p=none when rua (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

  1. Find who refused it. The Diagnostic-Code and Remote-MTA fields, when present, show the error and the server behind it.

  2. 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

  3. 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, sp or np in place. If the query times out or returns SERVFAIL/Server failed, go to step 4 first. If no level up to the organizational domain has a record (NXDOMAIN or no text = line), see no DMARC record found. A minimal valid record, with a mailbox you control in rua:

    TXT
    v=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 quarantine or reject in p, sp or np and your reports do not yet show every legitimate sender passing, publish none in those tags first and raise them in stages. Otherwise failing mail can go to spam or be refused.

  4. If the query times out or returns SERVFAIL, look at DNS. Repeat it against 8.8.8.8, then ask your DNS host to check the domain's name servers.

  5. 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.

  6. If everything is clean, write to the receiver. Send the full bounce to postmaster@ at the recipient's domain.

Confirm the fix

  1. Repeat the nslookup query. Each name that has a record should show only one, starting with v=DMARC1 and with a valid p, plus valid sp and np if present.

  2. If the old value appears, wait for its TTL (the DNS cache lifetime) to expire and query again.

  3. Run our DMARC checker.

  4. Send a new message to the address that bounced.

  5. Read your aggregate reports. policy_published shows the policy each receiver observed, and an error element can name problems such as multiple records.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Is 554 5.7.5 a Gmail error?
We cannot confirm that. Google's and Yahoo's published error lists include neither this code nor this text, although Yahoo lists a failed DMARC or DKIM policy among the reasons for a 553 or 554. Microsoft's list has 5.7.5 only for a certificate that fails MTA-STS (encrypted delivery) validation, and does not include this text. Google says gsmtp is added to all Gmail errors, so look for that string in your bounce and check the server named in Remote-MTA.
What does the 5.7.5 code mean?
RFC 3463 defines X.7.5 as a cryptographic failure: a system could not validate or decrypt a message because a key or similar information was missing or invalid. The IANA registry lists no code for DMARC, and Microsoft uses 5.7.5 for a certificate that fails MTA-STS validation. Read the text that follows the code.
Is a permanent error evaluating DMARC policy the same as failing DMARC?
We cannot confirm which result this bounce reflects. RFC 9989 registers fail and permerror as separate results. A fail means a DMARC record exists and no authenticated identity aligns with the From: domain. A permerror means the evaluation hit an unrecoverable error, such as an improperly formatted record. No receiver we checked documents which result produces this bounce, so check the record and DNS first, then SPF, DKIM and alignment.
Should I set p=none to make this bounce stop?
Changing the policy value does not repair a duplicate record, a bad v tag or a DNS failure. Keep the policy you have unless you are repairing a broken record and your reports do not yet show every legitimate sender passing. In that case publish p=none first and raise it once the reports are clean.
What if the domain in the From: address is not mine?
Only that domain's administrator can change its DMARC record, so send them the full bounce. If the domain is yours and the record is clean but the refusals continue, write to the postmaster address at the recipient's domain.

Sources consulted

RFC 1035 §3.2.1 (TTL)
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.