WarningSMTP Error · Temporary (4.x.x)
421 4.7.0 [TSS04]

Yahoo temporarily deferred your mail

A 421 4.7.0 bounce with [TSS04] (or another code starting with TS) comes from Yahoo and AOL. Yahoo is slowing down mail from your server for now. Your server will retry; the mail is not lost yet.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>  421 4.7.0 [TSS04] Yahoo temporarily deferred your mail
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

421 4.7.0 [TSS04] is a temporary SMTP reply meaning yahoo temporarily deferred your mail. Yahoo groups its temporary deferrals as "TS" errors. Its sender documentation names the causes: many complaints from Yahoo users, content Yahoo objects to, a poor IP reputation, or unusual traffic. Yahoo says to review your outgoing mail and queues, and to contact Yahoo Sender Support if the error does not stop.

What 421 4.7.0 [TSS04] means

Yahoo groups its temporary deferrals as "TS" errors. Its sender documentation names the causes: many complaints from Yahoo users, content Yahoo objects to, a poor IP reputation, or unusual traffic. Yahoo says to review your outgoing mail and queues, and to contact Yahoo Sender Support if the error does not stop.

ℹ️
This is a 4.x.x temporary failure — a correctly configured mail server retries on a backoff schedule, and the message frequently delivers on a later attempt.

Common causes

📨
#1

Yahoo users marked your mail as spam

Most common

High complaint rates are the most common reason. Yahoo, like Gmail, expects bulk senders to keep complaints low and to offer one-click unsubscribe.

🔁
#2

A sudden rise in volume or unusual traffic

Common

A new IP or domain, a cold domain, or a large send after a quiet period looks suspicious.

⚙️
#3

Poor IP reputation or authentication problems

Common

A shared IP with bad neighbours, or SPF, DKIM or DMARC that does not pass for bulk mail.

How to fix 421 4.7.0 [TSS04]

  1. 1

    Let your server retry slowly

    Do not resend by hand. Lower the sending rate to Yahoo and let the queue retry over several hours.

  2. 2

    Check authentication and blocklists

    Bulk senders to Yahoo need SPF, DKIM and DMARC. Run a free EmailHealth check to confirm they pass and that the domain is not listed.

  3. 3

    Reduce complaints, then ask Yahoo

    Send only to people who opted in, remove inactive addresses, add one-click unsubscribe, and join the Yahoo Complaint Feedback Loop. If deferrals continue, submit a Sender Support Request at senders.yahooinc.com.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check