Map Extract

554 5.7.5 Permanent Error Evaluating DMARC Policy means the receiving server tried to read your domain's DMARC record and could not. It is almost always a broken DNS record on your side: a syntax error, two DMARC records at once, the record published under the wrong name, or a malformed report address. Look up _dmarc.yourdomain, compare it with the examples below, fix it, test with a seed mailbox and resend.

This is one of the authentication codes in our SMTP error codes guide for cold email.

Who returns this string and why

The wording is used by several receiving systems and security gateways; the brand in the bounce is not always the system that wrote it. Variants you may see:

554 5.7.5 Permanent Error Evaluating DMARC Policy
451 4.7.5 Temporary Error Evaluating DMARC Policy

The 4xx form usually means a DNS lookup failed for the moment (a timeout or server failure), and a retry may work. The 5xx form means the receiver got an answer and could not use it. RFC 3463 calls X.7.5 a "Cryptographic failure", which is a loose fit; this is a vendor's use of the code, not the registry's.

It is different from an ordinary DMARC failure. Gmail, for example, rejects real failures with 550 5.7.26 Unauthenticated email from [domain] is not accepted due to domain's DMARC policy; see Gmail 550-5.7.26. A DMARC failure means "your policy says reject and this message did not pass". An evaluation error means "I cannot work out what your policy is".

Strictly, the DMARC standards are forgiving. RFC 7489 says a record whose version tag is missing or wrong "MUST be ignored", unknown tags "MUST be ignored", and multiple records mean "DMARC processing is not applied". The newer RFC 9989 (May 2026), which replaces RFC 7489, keeps that approach and adds that a missing p tag in an otherwise valid record is treated as p=none. Some receivers are stricter than the standard and reject instead. You cannot change their software, so make your record unambiguous.

Five broken records and their fixes

All examples use the fictional domain northfield-consulting.example. The record lives at the DNS name _dmarc.northfield-consulting.example as a TXT record.

1. Version tag not first

Broken:  p=quarantine; v=DMARC1; rua=mailto:[email protected]
Fixed:   v=DMARC1; p=quarantine; rua=mailto:[email protected]

RFC 7489 says the v tag "MUST be the first tag in the list" and that v and p "MUST appear in that order". The value is case sensitive: DMARC1, not dmarc1.

2. Two DMARC records at the same name

Broken:  "v=DMARC1; p=none; rua=mailto:[email protected]"
         "v=DMARC1; p=reject; rua=mailto:[email protected]"
Fixed:   "v=DMARC1; p=none; rua=mailto:[email protected],mailto:[email protected]"

This happens when a reporting service tells you to "add this record" and you add it next to the old one. Merge into one record; multiple report addresses go in one rua tag, separated by commas.

3. Report address without mailto:

Broken:  v=DMARC1; p=none; [email protected]
Fixed:   v=DMARC1; p=none; rua=mailto:[email protected]

The rua and ruf tags take URIs, and receivers "MUST implement support for a "mailto:" URI". A bare address is not a valid URI.

4. Wrong separators or pasted punctuation

Broken:  v=DMARC1, p=none, rua=mailto:[email protected]
Broken:  “v=DMARC1; p=none”
Fixed:   v=DMARC1; p=none; rua=mailto:[email protected]

Tags are separated by semicolons. Commas only separate multiple URIs inside rua or ruf. Curly quotes copied from a word processor or chat message become part of the record.

5. Invalid policy value

Broken:  v=DMARC1; p=block; rua=mailto:[email protected]
Broken:  v=DMARC1; p=; sp=reject
Fixed:   v=DMARC1; p=quarantine; rua=mailto:[email protected]

p must be none, quarantine or reject. An empty or invented value gives a strict receiver nothing to evaluate.

Duplicate TXT records and DNS host quirks

Many broken records are created by the DNS control panel rather than the person typing:

QuirkWhat you seeFix
Host field appends the domainRecord ends up at _dmarc.northfield-consulting.example.northfield-consulting.exampleEnter only _dmarc in the host field
Quotes stored literallyLookup returns "\"v=DMARC1; p=none\""Remove the quotes you typed; the panel adds its own
Record on the root domainv=DMARC1 appears among the root TXT recordsMove it to the _dmarc name
CNAME and TXT at the same nameA vendor's CNAME at _dmarc plus an old TXTKeep one or the other, never both
Two providers managing DNSRecords changed at the registrar while the real nameservers are elsewhereEdit the zone at the nameservers the domain actually uses

Check what the world sees, not what the panel shows:

dig +short TXT _dmarc.northfield-consulting.example

You want exactly one line, beginning "v=DMARC1;.

The SPF lookup limit as a hidden cause

DMARC depends on SPF and DKIM results, so a broken SPF record can sit behind DMARC trouble even when the DMARC record is perfect.

RFC 7208 sets hard limits. SPF implementations "MUST limit the total number of those terms to 10", where the terms are include, a, mx, ptr, exists and redirect, and they "SHOULD limit 'void lookups' to two". Exceeding either produces a permerror. And if a domain publishes more than one SPF record, check_host() "produces the 'permerror' result".

Broken:  v=spf1 include:spf.protection.outlook.com -all
         v=spf1 include:_spf.google.com ~all
Fixed:   v=spf1 include:spf.protection.outlook.com include:_spf.google.com -all

Some receivers fold an SPF permerror into a DMARC evaluation error; at the very least, a permerror means SPF cannot provide the aligned pass, so DMARC rests entirely on DKIM. Each include can pull in further lookups, which is how a record with four includes ends up over ten. Our guide to SPF PermError: too many DNS lookups shows how to count and flatten them.

Validation checklist

  • Exactly one TXT record at _dmarc.yourdomain.
  • It starts with v=DMARC1; in that exact case.
  • p= is none, quarantine or reject.
  • Tags are separated by semicolons; no stray quotes or commas.
  • Every rua and ruf address starts with mailto:.
  • Report addresses on another domain are authorised by that domain (RFC 7489 section 7.1 requires a _report._dmarc record there, or receivers ignore the address).
  • Exactly one SPF record at the envelope domain, within 10 DNS lookups.
  • DKIM signs with your own domain, so DMARC can pass even when SPF does not.

How to test with a seed mailbox

  1. Wait for DNS. Changes appear after the record's TTL; check with dig until the new value is returned.
  2. Send one plain message from the affected mailbox to a personal Gmail address you control. Use the same route the campaign uses.
  3. Open Show original. The summary lists SPF, DKIM and DMARC. You want DMARC: PASS, and in the Authentication-Results header a dmarc=pass with header.from set to your domain.
  4. If you can, repeat with an Outlook.com and a Yahoo address, since receivers parse records differently.
  5. Resend the bounced messages only after all tests pass, at a reduced rate.

A safe DMARC policy for a cold sending domain

StageRecordWhen
Startv=DMARC1; p=none; rua=mailto:[email protected]New domain, or after any change of mail provider or tool
Enforcev=DMARC1; p=quarantine; rua=mailto:[email protected]Reports show every legitimate source passes aligned SPF or DKIM
Strictv=DMARC1; p=reject; rua=mailto:[email protected]Optional, after weeks of clean reports

Google's sender guidelines require bulk senders to have a DMARC record and say "Your DMARC enforcement policy can be set to none", so p=none already meets the requirement. Moving to quarantine protects your domain from spoofing, which matters for a domain whose reputation you are building. Avoid the pct tag for staged roll-outs: RFC 9989 removes it, so newer receivers may ignore it.

If you use a separate domain for outreach, publish DMARC on that domain too; a subdomain inherits the parent's policy through sp or p only if it has no record of its own.

How Map Extract helps

Map Extract's bulk email sender sends through your own SMTP accounts and cannot repair a DNS record. It helps contain the problem:

  • Bounce auto-pause. A broken DMARC record produces a burst of 5xx bounces across many recipients. Bounces are read over IMAP and the campaign pauses itself when they reach the threshold (5% by default).
  • Bounces are there to review. Bounces read over IMAP appear under Replies and bounces. Before you resume, check that addresses which bounced only because of your DNS have not been added to suppression or marked invalid in your own list.
  • A controlled restart with hourly and daily caps and an optional warm-up ramp.

The product does not check SPF, DKIM or DMARC records for your sending domain; that is stated on its page. Validate your records with your DNS host and a seed test as above before you start a campaign.

Key takeaways

  • 554 5.7.5 means the receiver could not evaluate your DMARC policy; fix the record, not the list.
  • One record only, v=DMARC1 first, semicolons between tags, mailto: on every report address, a valid p value.
  • DNS panels cause many errors: check the live record with dig.
  • A second SPF record or more than 10 SPF lookups gives a permerror and weakens DMARC.
  • Start a cold sending domain at p=none with reports, then move to quarantine once every source aligns.

Frequently asked questions

What causes 554 5.7.5 permanent error evaluating DMARC policy?

The receiving server tried to read your domain's DMARC policy and could not make sense of it. The usual causes are a syntax error in the _dmarc TXT record, two DMARC records at the same name, a record published at the wrong DNS name, or a report address missing its mailto: prefix. Fix the record in DNS and the bounce stops; the recipients are not at fault.

Is 554 5.7.5 the same as a DMARC fail?

No. A DMARC fail means the receiver read your policy and your message did not pass aligned SPF or DKIM. A permanent error evaluating DMARC policy means the receiver could not evaluate the policy at all, usually because the record is malformed. The first is fixed by authentication and alignment, the second by repairing the DNS record.

Can I have two DMARC records?

No. Only one DMARC TXT record may exist at _dmarc for a domain. RFC 7489 says that if more than one record is found, policy discovery stops and DMARC is not applied, and the newer RFC 9989 says multiple records returned for one name are all discarded. Some receivers treat this as an error and reject. Merge everything into a single record.

What DMARC policy should a cold email domain use?

Start with p=none and a working rua report address, so you can see every source sending as your domain without risking legitimate mail. Once reports show your mailbox provider and any sending tools pass aligned SPF or DKIM, move to p=quarantine. Gmail and Outlook.com accept p=none for bulk senders, so a stricter policy is good practice, not a requirement for delivery.

Sources

  1. RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)
  2. RFC 9989: DMARC (May 2026)
  3. RFC 7208: Sender Policy Framework (SPF)
  4. Google: Email sender guidelines
  5. RFC 3463: Enhanced Mail System Status Codes
  6. Suped: What causes the permanent error evaluating DMARC policy bounce
  7. Google Workspace: Gmail SMTP errors and codes

Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top