Yahoo SMTP Error Codes

Yahoo documents its SMTP errors (Delivery Status Notifications) by category rather than as an exhaustive per-code table. Extended tokens such as TS* (temporary deferrals) and PH* (content/phishing blocks) appear in the DSN text alongside the numeric code. When contacting Yahoo about persistent errors, include the exact error and diagnostic codes from your logs in a Sender Support Request.

Top-level classes

Class	Codes	Meaning	Retry?
4XX temporary	421, 451	Temporary problem blocking delivery	Yes — retry later
5XX permanent	550, 553, 554	Permanent problem; message refused	No — never retry; remove addresses that generate 5xx bounces

4XX (421 / 451) temporary errors — causes

• Unusual traffic patterns observed from your sending server's IP.
• The message included characteristics of spam.
• Mail from your server has been generating complaints from Yahoo users.
• Yahoo mail servers were busy at connection time.
• Other suspicious behavior triggering dynamic deprioritization of your server.
• Your name server was temporarily unavailable.
• Authentication results for your domain could not be determined due to a temporary error.

Action: review Yahoo's Sender Requirements & Recommendations (see Yahoo Sender Requirements); retry later. If you don't administer the mail server, contact its administrator.

5XX (553 / 554) permanent errors — causes

• Invalid recipient address.
• Message failed authentication against the sending domain's DMARC or DKIM policy.
• Content Yahoo won't accept for policy reasons.
• Other suspicious behavior leading to permanent rejection of the SMTP connection.
• IP listed by Spamhaus — check https://www.spamhaus.org.

Action: do not retry. Consistent 5xx errors signal a widespread problem; list managers should have a policy for removing addresses that generate 5xx bounces.

Error categories

Category	Typical codes	Cause	Recommended action
RFC compliance failures	4xx/5xx	Duplicate headers, incorrectly formatted headers, incorrect MIME types, and more (RFC 5321/5322 violations)	Fix message construction to be RFC-compliant
Unresolvable RFC 5321/5322 From domain	451 (timeout/servfail) or 554 (permfail)	The domain right of the @ in MAIL FROM or Header-From doesn't appear valid. Yahoo checks existence with an SOA query — subdomains used in MAIL FROM / Header-From need SOA records, not just A/MX (even wildcard) records	Ensure every From/MAIL FROM subdomain resolves and has SOA coverage
Excessive user complaints	deferral/rejection	Mail generating excessive spam votes from Yahoo users	Monitor reputation (even good-reputation senders get spam votes); if the error persists >48h or follows content/policy changes, review outgoing mail for objectionable content or practices; on shared IPs, other domains' traffic may be hurting you — consider dedicated IPs; verify proper opt-in
Excessive unsolicited messages	deferral/rejection	Excessively high volume from a single IP — characteristic of unsolicited bulk mail; often a new IP ramped too fast	Don't resend until practices reviewed; warm IPs slowly (see IP Warm-Up); confirm all recipients requested the mail; if error persists >48h, review content/practices
Excessive unknown recipients	rejection	Server sending to many invalid recipients; may be an open relay/open proxy (Yahoo doesn't accept mail from these)	Secure servers; remove bouncing addresses from lists; examine outbound queues for spammer abuse
Authentication failures	rejection	Failed SPF/DKIM/DMARC verification. Yahoo rejects for DKIM failure when: the signing domain publishes a policy requiring all mail to be DKIM-signed, the domain is in the DKIM d= tag, and the message couldn't be authenticated (missing/bad signature)	All senders: SPF or DKIM; bulk senders: SPF + DKIM + DMARC. Microsoft 365 / Google Workspace senders: configure DKIM per their guides. Mailing lists (listservs): put the list address in From: and the actual sender in Reply-To:. Forwarded mail: consider ARC
Content-based blocks	PH* errors	Content Yahoo won't accept: viruses, phishing, ransomware, other malware, or links/URLs to any of these	Examine outbound queues for objectionable content; secure servers against abuse
Recipient does not exist	554 (e.g. 554 delivery error: dd This user doesn't have a yahoo.com account (user@yahoo.com) [-5])	The Yahoo account doesn't exist	Never retry; remove the address from your list; confirm the address with the recipient directly
Message temporarily deferred	TS* errors (421)	Substantial complaints from Yahoo users; objectionable/spam-like content; poor IP reputation (the IP or its /24 subnet); unusual traffic patterns	Retry later is acceptable; review outgoing content; non-bulk servers (personal/corporate/edu/ISP) should check queues for spammer abuse; if consistent over an extended period, submit a Sender Support Request with error and diagnostic codes
Resources temporarily unavailable	4xx	Yahoo mail servers busy at connection time	Brief; retry after a short period
Other policy errors	550, 554	Null MX record (RFC 7505); header too big (From, Subject, To); Date outside of range; header value can't be decoded (From, Subject); address contains exotic/forbidden characters (e.g. ,$%?{}<>)	Fix the offending record/header/address

Reading a Yahoo bounce

A Yahoo failure notice ("MAILER-DAEMON" / "Mail Delivery Subsystem", subject like "Failed Delivery") has two parts: the reason for the bounce, then a copy of the original message. Example remote-host line:

Remote host said: 554 delivery error: dd This user doesn't have a yahoo.com account (testing123@yahoo.com) [-5] - mta123.mail.mud.yahoo.com

The most common failure cause is an invalid recipient address; if the account "doesn't exist", check spelling, and if bounces continue, the account may be closed or moved.

Related articles

• Yahoo Sender Requirements — the requirements whose violation produces most of these errors.
• Yahoo Complaint Feedback Loop — head off complaint-driven deferrals.
• IP Warm-Up — avoiding "excessive unsolicited messages" errors on new IPs.