550 5.7.509 sending domain does not pass DMARC

Quick fix

Turn on DKIM signing with your own domain in the sending service, so the d= domain aligns with the From domain. Or set a custom bounce (Return-Path) domain under your domain and add the service to its SPF record.

How to fix it

  1. Find the service that sent the rejected message and the domain in its From address.
  2. Turn on DKIM signing with your own domain in that service and publish its key, so the d= domain aligns with the From domain.
  3. Or set a custom bounce (Return-Path) domain under your domain in the service and add the service to that domain's SPF record, so SPF aligns.
  4. If forwarding breaks the message, ask the forwarding side to use ARC or to rewrite the envelope sender; DKIM usually survives plain forwarding.
  5. Until every sender passes, you can step back to p=quarantine; read the DMARC aggregate reports before you move to reject again.

Learn more: DMARC explained: policy, alignment and reports

How to check

The email spoofing check shows the DMARC policy receivers apply to the domain in the From address. Then open the bounce: the diagnostic part shows the sending server, and the headers of a test message show which of SPF and DKIM passed and for which domain.

The Email spoofing check opens with your domain filled in; it runs when you press Check.

Tools to check it

What the error means

Full error text: 550 5.7.509 Access denied, sending domain does not pass DMARC verification

550 5.7.509 is the bounce Microsoft 365 (Exchange Online) sends when a message fails DMARC for the domain in its From address and that domain publishes p=reject. Microsoft's list of SMTP errors gives the text as "Access denied, sending domain [$SenderDomain] does not pass DMARC verification and has a DMARC policy of reject." The fix is on the sending side: make SPF or DKIM pass and align with the From domain.

Microsoft describes the cause as "The sender's domain in the 5322.From address doesn't pass DMARC." DMARC passes only when SPF or DKIM passes for a domain that aligns with the From domain (RFC 9989, section 4.4). A message can pass SPF for the sending service's own bounce domain and still fail DMARC; see SPF passes but DMARC fails.

Microsoft's own list of reasons under "Why does DMARC fail?" is:

  • "Missing or incorrect DMARC/DNS records: Alignment issues, missing SPF, and policy issues"
  • "Missing DKIM or DKIM records: Missing DKIM DNS record (public key) or the message isn't DKIM-signed at the time of sending (private key)"
  • "Forwarding emails: Message forwarding that breaks SPF or DKIM"

A bounce with 550 5.7.23 instead means the receiver rejected the message on SPF alone. The rejection is the receiver following your own policy, so it also hits legitimate mail from a service you forgot to set up. With the Honor DMARC record policy setting on, Microsoft 365 records it as dmarc=fail action=oreject in Authentication-Results.

Sources

All findings