Contents
The 421 SMTP response code means "Service not available, closing transmission channel." It is the most common deferral type in high-volume email sending and the one that carries the most diagnostic information. Unlike the 450 series (message-level transient failures), a 421 terminates the entire SMTP session and carries ISP-specific sub-codes that indicate whether the deferral is caused by normal throttling, reputation-based restrictions, authentication failures, or IP-level policy blocks. Reading 421 codes correctly is fundamental to operational response.
421 Response Code Overview
A 421 response triggers the following PowerMTA behavior: the current SMTP connection is closed, the message is returned to the queue as deferred, and it is scheduled for retry at the retry-after interval in the domain block (or a custom interval if matched by an smtp-pattern-list). The sub-code and diagnostic text in the 421 response determine whether the correct response is patience (normal throttling) or operational intervention (reputation block).
| 421 Type | Correct Response | Wrong Response |
|---|---|---|
| Normal rate limiting (421 4.2.1) | Standard retry at retry-after interval | Increasing max-smtp-out (worsens throttling) |
| Reputation-based throttling (421 4.7.0) | Reduce volume 50%, check spam rate | Increasing connections or sending faster |
| Policy block (421 RP-001) | Stop sending from that IP for 4h+ | Retrying aggressively from same IP |
| Authentication-related (421 4.7.28) | Fix SPF/DKIM/DMARC configuration | Retrying without fixing authentication |
Gmail 421 Deferral Codes
| Code | Full Diagnostic Pattern | Meaning | Response |
|---|---|---|---|
421 4.7.0 | "Try again later, closing connection." | Reputation-based connection refusal | Reduce max-smtp-out 50%; check Postmaster spam rate |
421 4.2.1 | "The user you are trying to contact is receiving mail at a rate that prevents additional messages from being delivered." | Recipient-level rate limit (normal) | Standard retry — no action needed |
421 4.7.28 | "Gmail has detected an unusual rate of unsolicited mail." | IP-level unusual activity detection | Investigate sending pattern; reduce volume |
421 4.3.2 | "Service temporarily unavailable." | Gmail server momentarily unavailable | Normal retry; not a reputation signal |
# PowerMTA smtp-pattern-list for Gmail 421 codes
smtp-pattern-list gmail-421-patterns {
"421 4.7.0" retry-after=30m # Reputation — aggressive retry makes it worse
"421 4.7.28" retry-after=45m max-smtp-out=3 # Unusual rate detection
"421 4.2.1" retry-after=15m # Normal rate limit — standard retry
"421 4.3.2" retry-after=5m # Momentary unavailability
}
domain gmail.com {
smtp-pattern-list gmail-421-patterns
virtual-mta-pool gmail-pool
max-smtp-out 8
mx-rollup gmail.com
}
Microsoft Outlook 421 Deferral Codes
| Code | Pattern | Meaning | Response |
|---|---|---|---|
421 4.7.0 RP-001 | "The IP you're sending from has been blocked..." | Reputation policy block | Stop from this IP for minimum 4 hours |
421 4.7.0 RP-002 | "Service temporarily unavailable..." | Connection rate limit | Reduce max-conn-rate; increase retry-after |
421 4.7.0 RP-003 | "Sender domain blocked..." | Domain reputation issue | Check domain DMARC policy; investigate complaint rate |
421 4.7.500 | "Server busy..." | Temporary server load (normal) | Standard retry — not a reputation signal |
Yahoo 421 Deferral Codes
# Yahoo / AOL 421 patterns # Yahoo uses structured codes with descriptions like [TSS04]: "421 4.7.0 [TSS04] Messages from your IP are temporarily deferred..." # Response: Wait 30-60 minutes; Yahoo throttling typically self-resolves # If persistent (>2 hours): check Yahoo Postmaster DKIM/SPF status "421 4.7.0 [TS03] All messages from your IP have been blocked..." # Response: Investigate complaint rate; may require Yahoo FBL configuration report analysis "421 4.7.1 [CS04] The sending IP or domain may be..." # Response: Check for blacklisting; investigate sending pattern
PowerMTA Response Configuration for 421 Codes
# Comprehensive smtp-pattern-list for major ISP 421 codes
smtp-pattern-list major-isp-421-patterns {
# Gmail — reputation based
"421 4.7.0" retry-after=30m
"421 4.7.28" retry-after=45m max-smtp-out=3
# Microsoft — policy block (don't retry too fast)
"421 4.7.0 RP-001" retry-after=4h
"421 4.7.0 RP-002" retry-after=2h max-smtp-out=2
"421 4.7.0 RP-003" retry-after=2h
# Yahoo — standard throttle
"421 4.7.0 [TSS04]" retry-after=60m
"421 4.7.0 [TS03]" retry-after=2h
# Generic normal throttle (catch-all for other 421s)
"421 " retry-after=20m
}
# Apply globally
smtp-pattern-list major-isp-421-patterns
Monitoring 421 Rate in Accounting Logs
# Monitor 421 high deferral rate diagnosis by ISP — hourly awk -F, ' NR>1 && $2 >= "2026-01-15T00:00" && $2 <= "2026-01-15T01:00" { domain = gensub(/.*@/, "", "g", $6) if ($1 == "t" && $10 ~ /^421/) deferred[domain]++ if ($1 == "d") delivered[domain]++ } END { for (d in deferred) { total = deferred[d] + delivered[d] if (total > 10) { printf "%s: %.1f%% 421-deferred\n", d, deferred[d]/total*100 } } }' /var/log/pmta/accounting.csv | sort -t: -k2 -rn # Alert thresholds for 421 deferral rate: # Gmail: >5% unusual, >15% requires immediate action # Outlook: >5% unusual, >10% requires action (more sensitive) # Yahoo: >8% normal range; >20% investigate
Frequently Asked Questions
Operating PowerMTA at production volume?
We manage PowerMTA environments for high-volume senders — configuration, IP warming schedule, daily reputation monitoring, and operational response. Fully managed. No self-service.
