Bounces and errors

What Does 554 5.7.5 Mean, and How Do I Fix It?

Outreach2dayPublished 4 min read
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

Google

Gmail SMTP errors and codes, updated November 10, 2026

Not listed; Gmail's DMARC codes include 5.7.26 and 5.7.40

Microsoft

Exchange Online NDR reference

Another error: "Remote certificate failed MTA-STS validation"

Yahoo

Sender Hub SMTP error codes

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

fail

Valid record; SPF and DKIM did not pass for a domain aligned with From

Gmail 550 5.7.26, Microsoft 5.7.509

permerror

The receiver could not finish the check

554 5.7.5 at some receivers

temperror

A temporary error, for example a DNS timeout

A 4xx deferral, such as Gmail 451 4.7.26

none

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=DMARC1 must 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

  1. Read the full bounce for the From domain and the server that refused it.

  2. Check the record with the DMARC checker. It flags duplicates, a misplaced v=DMARC1, a missing p= and report addresses without mailto:, and writes a corrected record.

  3. Keep one record, for example v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. The DMARC record generator writes one.

  4. Check SPF and DKIM with the SPF checker and the DKIM checker, or all three records with the SPF, DKIM and DMARC checker.

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

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

Unsubscribe in one click.

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

Deliverability call

Talk to our deliverability team

Book a call with the people who run our mailbox infrastructure. We look at your current setup and tell you what to change.

  • Review your domains, DNS records and current inbox placement
  • Size the setup: domains, mailboxes per domain and daily volume per mailbox
  • Plan warmup and the move from your current provider or sequencer

Free call

See open times in your time zone and book on this page.

Or open the booking page

See deliverability issues before they kill performance

Check each mailbox's daily inbox, spam and bounce rate, replace the weak ones early, and keep warmup, protection, and sending in one place.