On this page
Short answer
554 5.7.5 Permanent error evaluating DMARC policy means the receiver could not complete the DMARC check for your From domain and refused the email. RFC 7489 calls this result permerror; its example is a syntactically incorrect DMARC record. A DMARC fail means a valid record and no aligned SPF or DKIM pass. Publish one DMARC record starting with v=DMARC1 and a valid p= tag, then check SPF and DKIM.
What the bounce says
The text usually reads 554 5.7.5 Permanent error evaluating DMARC policy: the receiving server tried to run DMARC on your email, hit an error it treats as final and refused the message.
Google, Microsoft and Yahoo do not list this wording in their official error references (checked November 15, 2026):
Provider | Official list | 5.7.5 there |
|---|---|---|
Gmail SMTP errors and codes, updated November 10, 2026 | Not listed; Gmail's DMARC codes include 5.7.26 and 5.7.40 | |
Microsoft | Another error: "Remote certificate failed MTA-STS validation" | |
Yahoo | Not listed |
So the explanation comes from the DMARC standard. The code is generic: RFC 3463 defines X.7.5 as "Cryptographic failure". A 5.7.5 that mentions MTA-STS points to the destination server's certificate and has nothing to do with your DMARC record.
What "permanent error" means in DMARC
RFC 7489 gives a DMARC check five results (section 11.2). The bounce matches permerror: "A permanent error occurred during DMARC evaluation", with a syntactically incorrect DMARC record as the example. RFC 9989, the May 2026 standard that replaces RFC 7489, keeps the result and the example.
Result | What happened | Typical bounce |
|---|---|---|
| Valid record; SPF and DKIM did not pass for a domain aligned with From | Gmail 550 5.7.26, Microsoft 5.7.509 |
| The receiver could not finish the check | 554 5.7.5 at some receivers |
| A temporary error, for example a DNS timeout | A 4xx deferral, such as Gmail 451 4.7.26 |
| No DMARC record | Gmail 5.7.40 for bulk senders |
A fail is a verdict on the email. A permerror means there was no verdict, so new copy, another IP or a slower pace will not change it. Microsoft's header reference says of action=permerror that resending "isn't likely to have a different result". For the fail case, see why DMARC fails.
What breaks a DMARC evaluation
Two DMARC records at
_dmarc, for example after a switch of report service. RFC 7489 then applies no DMARC (section 6.6.3); RFC 9989 discards both.A wrong first tag.
v=DMARC1must come first and match exactly (section 6.3).A missing or invalid policy. RFC 7489 requires
p=with none, quarantine or reject. Gmail's code for a record without a policy is 5.7.40.Broken syntax: commas instead of semicolons, quote marks pasted from a document, a report address without
mailto:.A permanent DNS error in the SPF or DKIM check. RFC 7489 leaves the handling to the receiver (section 6.6.2). See SPF PermError and why DKIM fails.
A malformed From header. DMARC needs one From domain; mail with no From, two From fields or several addresses in one is "typically rejected" (section 6.6.1).
A receiver that follows the RFC to the letter skips DMARC for some of these records. Final disposition "is always a matter of local policy" (section 6.7), and the server that sent your bounce chose to reject.
How to fix it
Read the full bounce for the From domain and the server that refused it.
Check the record with the DMARC checker. It flags duplicates, a misplaced
v=DMARC1, a missingp=and report addresses withoutmailto:, and writes a corrected record.Keep one record, for example
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. The DMARC record generator writes one.Check SPF and DKIM with the SPF checker and the DKIM checker, or all three records with the SPF, DKIM and DMARC checker.
Align DKIM with From. Microsoft 365 can still pass composite authentication despite a DMARC error when the SPF or DKIM domain aligns with From (reason 111). The server that bounced you gave no such credit, so fix the record too.
Send a test to a mailbox you control and paste its headers into the email header analyzer. You want
dmarc=pass.
Free guide19 min read
Send 100,000 cold emails a month
Domains and mailboxes you need, DNS, warmup, lists, copy and follow-ups, with a launch checklist, sent to your inbox.
What it means for cold email
When the DMARC records of many sending domains are copied from one template, one typo repeats on all of them. Check every sending domain, starting with the one in the bounce.
Pause campaigns from that domain until a test passes: every email to that receiver bounces permanently and raises your bounce rate. After the fix, return the bounced prospects to the campaign within your usual daily volume: none of them received the email.
Questions
Is 554 5.7.5 the same as DMARC fail?
No. A DMARC fail means a valid record and no aligned SPF or DKIM pass (under a reject policy, Gmail answers with 550 5.7.26). 554 5.7.5 means the evaluation itself broke, so start with the DMARC record in your DNS.
What does "remote server returned 554 5.7.5" mean?
The recipient's server refused the email and your own mail system passed its reply on. In an Exchange Online NDR, "Diagnostic information for administrators" names that remote server and quotes its SMTP response. Microsoft picks the text at the top of the NDR by the status code, so go by the quoted response. The fix is the same as above.
What if the bounce says temporary error?
That is temperror, for example a DNS timeout, and RFC 7489 lets the receiver defer the email so your server retries (section 6.6.3). If it lasts for hours, check your DNS host.
What we recommend at Outreach2day
Domains you buy in Outreach2day, or connect by pointing their NS to us, get SPF, DKIM and DMARC records automatically. If you edit DNS on a domain later, run the DMARC checker before the next campaign and watch the warmup bounce rate of its mailboxes in the per-mailbox analytics.
Sources
- RFC 7489: DMARC, results and policy discovery: rfc-editor.org/rfc/rfc7489
- RFC 9989: DMARC (obsoletes RFC 7489 and RFC 9091): rfc-editor.org/rfc/rfc9989
- RFC 3463: Enhanced Mail System Status Codes: rfc-editor.org/rfc/rfc3463
- Microsoft Learn: Anti-spam message headers (Authentication-Results): learn.microsoft.com/en-us/defender-office-365/message-headers-eop-mdo
- Microsoft Learn: Email nondelivery reports (NDRs) and SMTP errors in Exchange Online: learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/non-delivery-reports-in-exchange-online
- Google Workspace Admin Help: Gmail SMTP errors and codes: knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes
- Yahoo Sender Hub: SMTP error codes: senders.yahooinc.com/smtp-error-codes
Related answers
- Why Does DMARC Fail When SPF and DKIM Pass?Bounces and errors
- What Causes SPF PermError, and How Do I Fix It?Bounces and errors
- What Does 550 5.7.26 Mean, and How Do I Fix It?Bounces and errors
- Why Does DKIM Fail, and How Do I Fix It?Bounces and errors
In depth on the blog
- SPF, DKIM and DMARC Test: Check Your Records15 min read
- Google Workspace SPF, DKIM and DMARC Setup12 min read

