Skip to content
DMARC Pulse

Email errors

SPF, DKIM and DMARC errors, explained

Find the message you received, see what it means and fix it step by step.

550 5.7.0 Local Policy Violation: meaning and how to fix it

550 5.7.0 local policy violation means a mail server refused your email under its own rule. See which rule it might be and what you can fix.

Read →

550 5.7.1 relaying denied: what it means and how to fix it

550 5.7.1 relaying denied means a mail server refused to forward your message. Find out if the cause is sign-in, an MX record or a relay allowlist.

Read →

550 5.7.26: why Gmail blocked your email and how to fix it

550 5.7.26 means Gmail blocked your message because it failed sender authentication. Identify your bounce and fix SPF, DKIM or DMARC alignment.

Read →

550 5.7.367: fix relay denied on forwarded Microsoft 365 mail

550 5.7.367 means a remote server refused mail sent by Microsoft 365, such as forwarded mail from its relay pool. See how to fix it.

Read →

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.

Read →

Amazon SES DMARC fail: why it happens and how to fix it

Amazon SES DMARC fail means no domain passed SPF or DKIM and aligned with your From domain. Set up Easy DKIM and a custom MAIL FROM to fix it.

Read →

DKIM body hash did not verify: causes and how to fix it

DKIM body hash did not verify means the message no longer matches the bh= value in its signature. Find what changed it and confirm dkim=pass.

Read →

DKIM fail: what dkim=fail means and how to fix it

DKIM fail means the receiver could not verify your signature. Read dkim=fail in your headers, find the cause of the DKIM failure and fix it.

Read →

DMARC Quarantine/Reject Policy Not Enabled: How to Fix It

DMARC Quarantine/Reject policy not enabled means your record does not ask receivers to quarantine or reject failing mail. See how to enforce it safely.

Read →

DMARC reports not received: causes and how to fix it

DMARC reports not received? Check the rua tag, the _report._dmarc record for outside addresses, the mailbox and whether the receiver sends reports.

Read →

MTA-STS Policy Is Missing: What STSFetchResult.NONE Means

MTA-STS policy is missing: STSFetchResult.NONE means no usable _mta-sts TXT record was found. See why Mail-in-a-Box shows it and how to fix it.

Read →

Multiple SPF Records: Why It Fails and How to Merge Them

Multiple SPF records on one DNS name cause SPF permerror. Merge them into a single v=spf1 record with multiple includes, step by step.

Read →

No DMARC record found: what it means and how to fix it

No DMARC record found means no usable TXT record exists at _dmarc on your domain. See why a lookup misses it and how to publish one safely.

Read →

SPF fail: softfail vs hardfail and how to fix each

SPF fail means the sending IP is not authorized by the domain's SPF record. See how softfail and hardfail differ and how to fix each one.

Read →

SPF PermError: Fix Too Many DNS Lookups and Other Causes

SPF permerror means the receiver could not interpret your SPF record. Check the 10 DNS lookup limit, duplicate records and syntax, then fix the cause.

Read →

DMARC fail: what it means and how to fix it

DMARC fail means no SPF or DKIM pass aligned with the From domain. See what receivers do with the message, why it happens and how to fix it.

Read →

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.