Executive Summary: Resolve Yahoo TS01, TS02, TS03, and TSS04 SMTP errors: decoding deferral codes, configuring Yahoo CFL complaint feedback loops, connection throttle parameters, and postmaster escalation.
Yahoo Mail’s temporary deferral codes — TS01, TS02, TS03, TS06, and TSS04 — are some of the most misunderstood SMTP errors in bulk email. Unlike Gmail’s 550 codes, which are permanent rejections, Yahoo’s 421 TS codes are deferrals: Yahoo is accepting connection attempts but refusing to queue the message, asking your MTA to retry later. The challenge is knowing why Yahoo is deferring, and what specific fix each code requires. Getting it wrong — especially with TS03 — can escalate a temporary hold into a permanent block.
Yahoo TS Code Reference — What Each Code Means
Yahoo’s error taxonomy has evolved over 2024–2025. The AT&T domains (att.net, sbcglobal.net, bellsouth.net, and others) migrated to Yahoo’s infrastructure in mid-2025 and now return the same TS codes. Understanding the precise meaning of each code is the foundation of any fix strategy.
| Code | Full error | Root cause | Severity | Auto-clears? |
|---|---|---|---|---|
| TS01 | 421 4.16.55 [TS01] Messages temporarily deferred — new/cold IP | IP has no or insufficient sending history at Yahoo | Low — normal during warm-up | Yes, as volume and engagement build |
| TS02 | 421 4.16.56 [TS02] Messages temporarily deferred — excessive complaints | Complaint rate exceeded Yahoo threshold (~0.10%) | Medium — escalates to TS06 if unresolved | Partially — requires list cleanup to clear fully |
| TS03 | 421 4.7.1 [TS03] All messages permanently deferred | Sustained high complaint rate, spam traps, or abuse signal | High — permanent until root cause fixed | No — requires active remediation |
| TS06 | 421 [TS06] Service unavailable — repeated violations | Escalated after repeated TS02/TS03 without remediation | Critical — manual intervention required | No — requires Yahoo postmaster contact |
| TSS04 | 421 4.7.0 [TSS04] Temporary rate deferral | Volume spike or connection rate too high | Low — rate-limit response | Yes — back off and retry |
| TS07 | 550 5.7.1 [TS07] Message rejected — abusive content | URL, content, or link domain flagged as abusive | High — 550 permanent rejection | No — content fix required |
>> EHLO mail.yourdomain.com
<< 250-mta123.mail.mud.yahoo.com
>> MAIL FROM:<bounce@yourdomain.com>
<< 250 OK
>> RCPT TO:<user@yahoo.com>
<< 421 4.16.56 [TS02] Messages from 203.0.113.42 temporarily deferred
due to excessive user complaints - see
https://postmaster.yahooinc.com/smtp-error-codes for more information.
mta1234.mail.yahoo.com
# 421 = temporary deferral (not a 550 permanent rejection)
# [TS02] = complaint rate threshold exceeded on this IP
# 203.0.113.42 = your sending IP (the one with the complaint signal)
# Your MTA should retry after 5 minutes, then 30 minutes, then 2 hours
# If still deferring after 24 hours, escalate to list cleanupFixing TS01 — Cold IP / No Sending History
TS01 is the most benign Yahoo error and almost always appears during IP warming. Yahoo’s infrastructure has no complaint, engagement, or delivery history for your IP, so it applies conservative throttling until trust is established. The fix is patience combined with correct warm-up technique — not list changes or content rewrites.
The critical mistake with TS01 is treating it like a reputation problem and suppressing large list segments. This reduces the engagement signals Yahoo needs to see. Instead, send small volumes of highly engaged recipients — users who opened or clicked in the last 7 days — and let Yahoo’s reputation system build a positive history for your IP.
▶ TS01 resolution workflow
dig -x [your-IP] and confirm it resolves to a hostname, and that hostname resolves back to the same IP. Missing PTR = TS01 that never clears.Fixing TS02 — Complaint Rate Too High
TS02 means Yahoo has detected an excessive user complaint rate from your sending IP. The threshold is approximately 0.10% — similar to Gmail’s enforcement threshold but applied more aggressively. Unlike Gmail, which provides Postmaster Tools to see your complaint rate, Yahoo’s only feedback mechanism is the FBL. If you are not subscribed to Yahoo’s FBL, you have no visibility into which specific sends triggered the complaint spike.
Yahoo TS02 Escalation Path — Time Without Remediation
▶ TS02 resolution workflow
Fixing TS03 — Permanent Deferral
TS03 is the most serious Yahoo error. Unlike TS01 and TS02, which are temporary throttles, TS03 is a permanent deferral — Yahoo will not accept messages from the affected IP until the underlying complaint rate, spam trap rate, or abuse signal is resolved. The full bounce code is 421 4.7.1 [TS03] All messages from x.x.x.x permanently deferred. In practice, your MTA will continue retrying and bouncing every message as a 4XX until you intervene.
Situation: TS03 on two sending IPs. Yahoo delivery went from 94% to 0% overnight. FBL showed 0.38% complaint rate on a re-engagement campaign sent to 180K contacts inactive for 14 months.
Action taken: Stopped all Yahoo sends on affected IPs. Switched to a third clean IP for critical transactional flows only (receipts, password resets). Suppressed the entire 180K inactive segment permanently. Cleaned FBL complaints from all active lists. Submitted Yahoo postmaster request with remediation documentation.
Outcome: Yahoo postmaster responded in 4 business days. IP released from TS03 after confirming complaint rate below 0.05% on test sends. Full delivery restored week 2. Re-engagement campaigns permanently discontinued on Yahoo.
▶ TS03 escalation workflow
Fixing TSS04 — Volume Rate Deferral
TSS04 is a rate-limiting response — Yahoo is throttling your connection rate because you are sending too many messages too quickly. This is the least serious Yahoo code and typically self-resolves if your MTA backs off automatically. The error code is 421 4.7.0 [TSS04]. It fires when you exceed Yahoo’s inbound connection or message-rate thresholds for a single IP, which are approximately 5 concurrent connections and 80–120 messages per minute.
The fix is configuration, not list cleanup. Reduce your MTA’s concurrent connections to Yahoo to 5, add a rate delay of 0.3–0.5 seconds between messages to Yahoo destinations, and spread sends over a longer time window instead of bursting. If you are seeing TSS04 on a previously clean IP with no TS02 or TS03, it means your send architecture is not ISP-aware — a fixable infrastructure problem.
# /etc/postfix/transport
yahoo.com smtp:[smtp.mail.yahoo.com]:25 rate_delay=0.4s concurrency_limit=5
ymail.com smtp:[smtp.mail.yahoo.com]:25 rate_delay=0.4s concurrency_limit=5
att.net smtp:[mx-att.mail.am0.yahoodns.net]:25 rate_delay=0.5s concurrency_limit=3
# Apply with:
# postmap /etc/postfix/transport
# postfix reload
# AT&T domains (att.net, sbcglobal.net etc.) migrated to Yahoo MX in mid-2025
# Use the yahoodns.net endpoint for these domains
# Stricter rate limit than @yahoo.com — use concurrency_limit=3Yahoo FBL Setup — Essential Before Any Send
Yahoo’s Feedback Loop (FBL) delivers complaint reports to a designated mailbox every time a Yahoo user clicks “this is spam” on your message. Without FBL, you are operating blind — you will not know your complaint rate until Yahoo starts issuing TS02 codes. FBL registration is free and takes under 10 minutes at senders.yahooinc.com.
FBL reports arrive as ARF-format emails (Abuse Reporting Format). Each report contains the original message headers, enough to identify the sending campaign, list segment, and timestamp. Your MTA or ESP should process these automatically and suppress the complaining address. If you are processing FBL manually, the volume from a large list can be unmanageable — automate suppression before scaling Yahoo sends.
Last updated: May 8, 2025