Yahoo 554 5.7.9: failed DMARC or DKIM policy

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. For a mailing list you run, put the list's own address in the From line and the original sender in Reply-To, as Yahoo recommends; for forwarding, add ARC.
  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 that receivers such as Yahoo apply to the domain in the From address. Then open a rejected or test message: the Authentication-Results header shows 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

Yahoo Mail and AOL (the same mail system) refuse a message permanently when it fails the DMARC or DKIM policy of the domain it claims to come from. Bounces of this kind usually carry 554 5.7.9, but Yahoo's Sender Hub does not publish a list of single codes; it describes the 5XX category as "Your message failed authentication checks against your sending domain's DMARC or DKIM policy." The fix is on the sending side: make SPF or DKIM pass and align with the From domain.

Yahoo's rules, quoted from its Sender Hub:

  • "All senders need to authenticate their emails with either SPF or DKIM. Bulk senders must authenticate with SPF and DKIM, and have a DMARC policy in place"
  • "If a domain is protected by DMARC with “p=reject”, any message without a proper DKIM signature or SPF alignment will be rejected by Yahoo's mail servers."
  • "Publish a valid DMARC policy with at least p=none - DMARC must pass" (bulk senders)

Yahoo also rejects on DKIM alone when the signing domain (the d= tag) publishes a policy that all its mail must be signed and the signature is missing or bad. A common cause is a service that sends with your domain in the From address but signs with its own domain, or not at all. Mailing lists and forwarding are the other cause: they change the message so DKIM breaks, and the forwarding server's IP is not in your SPF record.

Gmail rejects the same problem with 550 5.7.26 ("Unauthenticated email from domain-name is not accepted due to domain's DMARC policy."), and Microsoft 365 with 550 5.7.509.

Sources

All findings