421 Try Again Later: What to Do About This SMTP Deferral

Understanding 421 Deferrals

SMTP 421 means "Service not available, closing transmission channel." In plain terms: "Go away and come back later."

This is a temporary failure. Your mail server should:

1. Queue the message
2. Wait (with backoff)
3. Retry delivery

If everything is working, 421s resolve automatically.

Common Causes

1. Rate Limiting

You're sending too fast for this destination.

Signs:

• 421 responses increase with send volume
• Same message eventually delivers after delays
• Error message mentions "too many connections" or "rate exceeded"

Common messages:

• "421 4.7.0 Try again later, closing connection"
• "421 Too many concurrent SMTP connections"
• "421 Rate limited, try again later"

Fix:

1. Reduce concurrent connections to destination
2. Slow sending rate (throttle)
3. Spread sends over time
4. Use multiple IPs if legitimate volume requires it

2. Greylisting

First-time sender verification (common with smaller domains).

How it works:

1. Unknown sender connects
2. Server returns 421/450
3. Server records the attempt
4. Legitimate servers retry 5-30 minutes later
5. Retry succeeds because sender is now "known"

Signs:

• First email to domain defers
• Same message delivers 15-30 minutes later
• Only affects first contact

This is normal. Your MTA handles it automatically.

3. Server Congestion

Receiving server is overloaded.

Signs:

• Affects all senders (not just you)
• Temporary (resolves in hours)
• Error mentions "resources" or "busy"

Fix:

• Nothing to do but wait
• Your MTA will retry
• Not your problem

4. Reputation-Based Throttling

Server is accepting some of your email but slowing you down due to reputation concerns.

Signs:

• Persistent 421s lasting hours
• Combined with successful deliveries (mixed results)
• New IP or domain
• Check Postmaster Tools shows reputation issues

Fix:

1. Check Google Postmaster Tools
2. Check Microsoft SNDS
3. Reduce volume
4. Focus on engaged recipients
5. Allow reputation to build

Practitioner note: Gmail especially uses 421 as a soft warning. They're not rejecting outright, but they're not trusting you either. If you see persistent 421s from Gmail, it's a reputation signal. Treat it like the warning it is.

5. Too Many Connections

You're opening more connections than allowed.

Typical limits:

• Gmail: ~20 concurrent connections
• Outlook: ~10 concurrent connections
• Yahoo: ~5-10 concurrent connections
• Smaller providers: ~2-5 concurrent connections

Fix:

1. Configure MTA to limit concurrent connections per destination
2. Implement connection pooling
3. Close idle connections promptly

Provider-Specific 421s

Gmail

Message	Cause
"421-4.7.0"	Rate limited or reputation
"421-4.7.28"	IP sending limit exceeded
"421 Try again later"	General throttling

Actions:

1. Check Google Postmaster Tools
2. Reduce sending rate
3. Verify authentication
4. Warm IP if new

Microsoft/Outlook

Message	Cause
"421 RP-001"	Excessive connection rate
"421 RP-002"	Too many messages per connection
"421 RP-003"	Connection throttled

Actions:

1. Check SNDS status
2. Reduce connections
3. Fewer messages per connection
4. Review Microsoft's sending limits

Yahoo

Message	Cause
"421 Message from X.X.X.X deferred"	Reputation/volume
"421 4.7.0"	Temporary policy rejection

Actions:

1. Reduce volume to Yahoo domains
2. Verify authentication
3. Check for blacklists

Handling 421 in Your Infrastructure

MTA Configuration

Configure your mail server for proper retry:

Postfix example:

# Retry intervals
queue_run_delay = 300
minimal_backoff_time = 300
maximal_backoff_time = 4000

# Queue lifetime
bounce_queue_lifetime = 5d
maximal_queue_lifetime = 5d

Good retry schedule:

• First retry: 5-15 minutes
• Second retry: 15-30 minutes
• Third retry: 1 hour
• Further retries: Exponential backoff
• Maximum queue time: 72 hours (then bounce)

ESP Handling

Most ESPs handle 421 automatically. Check your ESP dashboard for:

• Deferral rates
• Delivery delays
• Provider-specific issues

Connection Management

Limit concurrent connections:

Per-domain limits (recommendations):
Gmail: 20 connections max
Outlook: 10 connections max
Yahoo: 5 connections max
Default: 5 connections max

When 421 Becomes a Problem

Normal

• Occasional 421s that resolve within minutes
• First-message deferrals (greylisting)
• Brief spikes during high-send periods

Warning Signs

• 421s lasting 4+ hours consistently
• High percentage of sends deferred
• 421s converting to 5xx bounces
• Specific provider always defers

Investigation Needed

• All emails to one domain get 421
• 421s started after specific change
• Combined with reputation warnings in Postmaster Tools

Diagnosis Workflow

Persistent 421 Received
│
├── Check error message text
│   └── Specific reason mentioned?
│       ├── Rate limit → Reduce speed
│       ├── Too many connections → Limit connections
│       └── Reputation → Check Postmaster Tools
│
├── Check timing
│   └── First message to domain?
│       └── Probably greylisting → Wait for retry
│
├── Check reputation tools
│   └── Issues shown? → Address reputation
│
├── Check MTA retry settings
│   └── Proper backoff configured? → Adjust if needed
│
└── Check volume/rate
    └── Sending too fast? → Throttle

Prevention

1. Implement proper throttling — Don't blast as fast as possible
2. Respect connection limits — Configure per-domain connection caps
3. Monitor deferral rates — Catch issues before they become problems
4. Maintain reputation — Good reputation = less throttling
5. Use multiple IPs for volume — Spread load if legitimately high volume

If you're experiencing persistent 421 deferrals and can't identify the cause, schedule a consultation — I'll analyze your sending patterns and optimize your delivery infrastructure.

Sources

• RFC 5321: Simple Mail Transfer Protocol
• Google: Bulk sender guidelines
• Microsoft: Troubleshooting mail delivery
• Yahoo: Postmaster guidelines

---

v1.0 · March 2026