# 554: Yahoo 553 / 554 authentication failures: message rejected

URL: https://iblockspam.com/smtp-errors/yahoo-554-authentication-failed
Last updated: 2026-10-22

Code: 554 (permanent failure, the message bounced)
Provider: Yahoo / AOL

Yahoo permanently rejected your message because it failed authentication checks against the sending domain's DMARC or DKIM policy. Don't retry until authentication is fixed.

Yahoo's Sender Hub lists failing authentication checks against your sending domain's DMARC or DKIM policy among the reasons for a permanent 553 or 554 error. Under its "Authentication failures" heading, Yahoo says your email failed one or more of the checks it uses to verify that mail really comes from the domain it claims.

Yahoo's baseline: all senders need to authenticate with either SPF or DKIM, and bulk senders must authenticate with SPF and DKIM and have a DMARC policy in place. Yahoo also rejects mail for failing DKIM when the signing domain (the d= tag) publishes a policy that all its mail must be DKIM-signed and the message couldn't be authenticated against that policy, for example because of a missing or bad signature.

Yahoo adds advice for two common situations. Mailing lists should put the list's own address in the From line and the real sender in Reply-To. For forwarded mail, consider ARC (Authenticated Received Chain). If you send through Microsoft 365 or Google Workspace, Yahoo points to those providers' DKIM setup guides. As with every 5xx from Yahoo, don't retry the same message unchanged.

## Common causes

- The message failed the DMARC policy published for the From domain.
- DKIM is missing or broken for a domain that requires all its mail to be signed.
- A mailing list or forwarder changed the message and broke SPF or DKIM.
- A bulk sender without SPF, DKIM and a DMARC policy.

## How to fix it (sender)

- Set up SPF and DKIM for your domain, and publish a DMARC record if you send in bulk.
- If you send through Microsoft 365 or Google Workspace, turn on DKIM signing with your own domain.
- Run mailing lists with the list's address in From and the sender in Reply-To.
- If you forward mail, consider adding ARC signing.

## How to fix it (recipient or admin)

- No action needed at Yahoo: the sender has to fix authentication.

**Q: Should I retry after a Yahoo 554 authentication failure?**
No. Yahoo says you shouldn't retry a message that comes back with a 5xx error. Fix SPF, DKIM or DMARC for the sending domain first, then send again.

**Q: What authentication does Yahoo require from bulk senders?**
Yahoo says all senders need SPF or DKIM, and bulk senders must authenticate with both SPF and DKIM and have a DMARC policy in place.

Sources:
- SMTP Error Codes (Yahoo Sender Hub): https://senders.yahooinc.com/smtp-error-codes/
- RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC): https://www.rfc-editor.org/rfc/rfc9989

---

Source: iBlockSpam, https://iblockspam.com/smtp-errors/yahoo-554-authentication-failed (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt