Fix Yahoo and AOL 554 5.7.9 Message Not Accepted

What the Yahoo and AOL bounce 554 5.7.9 Message not accepted for policy reasons means, how it relates to DMARC p=reject and forwarding, how to tell it from other Yahoo 554 policy errors, and how to fix authentication.

Home › Guides › Yahoo / AOL 554 5.7.9

Last updated 17 November 2026

Quick answer

Yahoo Help quotes this delivery error as:

554 5.7.9 Message not accepted for policy reasons

Yahoo's help article for that exact string says it may be due to the sender not using DMARC, and that mail automatically forwarded from one provider to another may appear to come from an unauthorized server if DMARC is not being used. It tells you to open the raw message and look for:

Yahoo Mail, AOL and other Yahoo-hosted domains share this sending infrastructure, so the same bounce shows up for those recipients. This is a permanent 5xx error: Yahoo's Sender Hub says you should not retry a 5xx bounce; list owners should remove addresses that generate them.

Fix aligned SPF and DKIM on the From domain, publish at least p=none (and understand that p=reject will reject unauthenticated or unaligned mail, including many forwarded copies). Check the domain with the Email Deliverability Checker, the SPF Record Checker, the DKIM Checker and the DMARC Record Checker.

What Yahoo requires

Yahoo Sender Hub's sender requirements (enforcement described as beginning in February 2024) are:

All sendersBulk senders
AuthenticationSPF or DKIM at a minimumSPF and DKIM, plus a valid DMARC policy of at least p=none that passes, with the From domain aligned to the SPF domain or the DKIM domain (relaxed alignment is acceptable)
DNSValid forward and reverse DNS for sending IPs
ComplaintsKeep the spam complaint rate below 0.3%
Message formatComply with RFC 5321 and RFC 5322
UnsubscribeA working List-Unsubscribe header that supports one-click unsubscribe for marketing and subscribed mail, plus a visible unsubscribe link, honoured within two days

Yahoo also strongly urges every sending domain to publish DMARC, recommends DKIM keys of at least 1024 bits, and tells forwarders to implement ARC. The bulk sender requirements checklist compares these rules with Gmail and Outlook.com. For Gmail's closest bounce, see Gmail 550 5.7.26; for Outlook.com, see Outlook.com 550 5.7.515.

How to tell which policy was applied

The 554 5.7.9 wording Yahoo publishes is generic: it says "policy reasons", not which check failed. Use the bounce and a copy of the message together.

  1. Read the full bounce. If it mentions DMARC or a domain policy, treat it as an authentication or DMARC-policy rejection first.
  2. If you have a copy that was forwarded, Yahoo Help says to look in the raw headers for X-Yahoo-Forwarded and for p=reject on the original domain's DMARC policy.
  3. Send a new test message to a Yahoo or AOL mailbox you control, or to a mailbox that will accept it, and paste the headers into the Email Header Analyzer. You want spf=pass and/or dkim=pass with a domain that aligns with From, and dmarc=pass.
  4. Check the published records with the Email Deliverability Checker, then the individual SPF, DKIM and DMARC checkers. Confirm the sending IP's PTR with DNS Lookup (reverse lookup). See whether the destination is actually a Yahoo-hosted domain with MX Record Lookup.

Other Yahoo 554 (and 550) policy rejections

Yahoo's Sender Hub SMTP error-codes page does not list a unique meaning for every status. It does say that a 553 or 554 is permanent, and that delivery can fail because the address is invalid, the message failed authentication against the sending domain's DMARC or DKIM policy, the message has characteristics Yahoo will not accept for policy reasons, the sending behaviour looks suspicious, or the IP is listed by Spamhaus. Separate sections cover:

If the bounce text is the 554 5.7.9 string Yahoo Help documents, start with DMARC, forwarding and authentication. If the bounce instead carries a PH-style code or talks about content, complaints or Spamhaus, those Sender Hub sections are the better match; do not force an authentication fix on a content or reputation rejection. This guide does not invent any bounce wording beyond the 554 5.7.9 sentence Yahoo published.

Fixes

1. Authenticate and align the From domain. Publish SPF, sign DKIM with your domain, and publish a DMARC record. Bulk senders need all three, and DMARC must pass with alignment. A correct SPF record on your root domain does not help if the service uses its own bounce domain, and a DKIM signature with the vendor's d= does not help DMARC either. Have the service sign with your domain and, if it offers a custom return-path, use that too. Details are in DMARC fail with SPF pass.

Build and check records with the SPF Record Builder, SPF Record Checker, DKIM Checker, DMARC Record Generator and DMARC Record Checker. Stay under 10 SPF lookups and avoid a missing include (see too many DNS lookups and void lookups).

2. Treat p=reject and forwarding as a pair. If the rejected message was forwarded, Yahoo Help's own steps are the ones to follow: look for X-Yahoo-Forwarded and p=reject. A domain at p=reject is asking receivers to refuse unauthenticated mail that claims it. Forwarding often breaks SPF, and sometimes DKIM, so the forwarded copy fails DMARC and is rejected. The sending domain can keep reject and still survive forwarding by signing aligned DKIM and, where the forwarder supports it, ARC or envelope rewriting. See DMARC fail after forwarding and the p=none to p=reject rollout plan.

3. PTR, complaints and lists. Yahoo requires valid forward and reverse DNS for sending IPs. Check the IP with the DNS Lookup reverse lookup; the PTR is set by the IP owner. Keep complaint rates below 0.3%, honour unsubscribes, and remove 5xx addresses from lists instead of retrying them.

Verify the fix

  1. The Email Deliverability Checker should show a valid SPF record, at least one aligned DKIM key and a valid DMARC policy.
  2. After DNS changes, confirm them with the DNS Propagation Checker.
  3. Send a new message to a Yahoo or AOL mailbox and read the headers in the Email Header Analyzer: spf=pass or dkim=pass aligned with From, and dmarc=pass.
  4. Watch aggregate reports in the DMARC Report Analyzer for Yahoo as a reporter, and confirm legitimate sources pass.

Audit hundreds of domains at once

Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).

Related tools and guides

Check the domain with the Email Deliverability Checker, SPF Record Checker, DKIM Checker and DMARC Record Checker. Read a test message in the Email Header Analyzer, confirm MX with MX Record Lookup and PTR with DNS Lookup, and watch reports in the DMARC Report Analyzer. Related guides: bulk sender requirements, Gmail 550 5.7.26, Outlook.com 550 5.7.515, DMARC fail with SPF pass, DMARC fail after forwarding and DMARC p=none to p=reject rollout.

FAQ

What does Yahoo 554 5.7.9 Message not accepted for policy reasons mean?

Yahoo Help quotes that exact sentence and says it may be caused by the sender not using DMARC, especially when mail is automatically forwarded and appears to come from an unauthorized server. It is a permanent rejection. Other Yahoo 554 responses can also be content, reputation or RFC-policy blocks, so read the rest of the bounce before you decide.

Does this bounce always mean my DMARC record is wrong?

No. It often appears when the original domain publishes p=reject and the copy Yahoo received failed authentication, which is common after forwarding. It can also appear when the message never passed aligned SPF or DKIM in the first place. Check both the published records and the headers of a test message.

How do I tell a 554 5.7.9 DMARC rejection from a Yahoo content block?

Start with the bounce text. Yahoo Help documents 554 5.7.9 Message not accepted for policy reasons together with X-Yahoo-Forwarded and p=reject. Yahoo Sender Hub documents separate content-based blocks that use a PH-style code and talk about viruses, phishing or malware. If you see a PH code, fix content and account compromise, not just DNS.

Do AOL recipients use the same rules as Yahoo?

Yahoo and AOL share sending requirements and mail infrastructure in Yahoo Sender Hub, and the same 554 5.7.9 bounce is reported for those domains. Confirm the recipient MX with MX Record Lookup if you need to be sure where the mailbox is hosted.

Should I retry a message that got 554 5.7.9?

No. Yahoo's Sender Hub says a 5xx error is permanent and you should not retry that message. Fix authentication or the forwarding path, then send a new message. List managers should remove addresses that generate 5xx bounces.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.