421 4.7.0 "Try again later, closing connection" — Gmail Rate Limit Decoded

If Gmail's MX is responding with this line, you've hit a 4xx temporary deferral:

421 4.7.0 [203.0.113.10      15] Our system has detected that this message is
421 4.7.0 suspicious due to the very low reputation of the sending IP address.
421 4.7.0 To best protect our users from spam, the message has been blocked.

Or sometimes the simpler:

421 4.7.0 Try again later, closing connection.

Both are 4xx codes — the message will be retried by your sending server. But "retried" does not mean "delivered." Persistent 421s pile up in your queue, slow downstream deliveries, and signal a reputation problem that needs fixing.

What 421 4.7.0 Actually Means

Gmail uses 421 as a generic temporary throttling response with multiple triggers:

Trigger	Typical message
IP reputation low	...suspicious due to the very low reputation of the sending IP address
Volume spike	...IP isn't normally seen with this volume
Per-connection limit	Try again later, closing connection. (after N messages on one TCP connection)
Domain reputation slipping	...domain reputation mentioned in the deferral

Read the full SMTP response, not just the code. Most ESPs truncate it in the UI — check the raw logs.

Trigger 1: Low IP Reputation

The most common cause. Gmail's reputation system has decided your sending IP is sending too many spam-marked or unauthenticated messages relative to legitimate ones.

Confirm it: check Google Postmaster Tools → IP Reputation. If you see Low or Bad for your sending IP, you've found it.

Fix it:

• Pause aggressive sending immediately.
• Send only to your most engaged contacts (opened in last 30 days) for at least 14 days.
• Verify SPF, DKIM, and DMARC are aligned — run our Email Headers Analyzer on a recent send.
• If you're on a shared IP, your neighbours may be the problem; consider moving to a dedicated IP and warming it up.

Trigger 2: Volume Spike

Gmail builds a profile of your normal sending volume per day. If you suddenly 5x or 10x your usual count, Gmail will start deferring overflow even if your reputation is healthy.

Fix it:

• Ramp gradually — no more than +30% per day during warmup.
• Split large campaigns across multiple sending windows.
• If you're a new sender, follow a 4-6 week warmup curve (e.g. 50 → 100 → 250 → 500 → 1k → 2.5k → 5k per day).

Trigger 3: Per-Connection Message Limit

Gmail will close a TCP connection after roughly 100 messages, returning 421 4.7.0 Try again later, closing connection. This is normal and expected. Most decent MTAs (KumoMTA, PowerMTA, Postfix with tuning) reconnect automatically.

If you see this constantly and your MTA isn't reconnecting, it's an MTA configuration issue, not a reputation issue.

Fix it (Postfix example):

smtp_destination_concurrency_limit = 10
smtp_destination_rate_delay = 1s

For KumoMTA, set per-MX connection caps in your egress shaping config.

Trigger 4: Domain Reputation Slipping

If your IP is fine but your domain reputation is dropping (e.g. Yellow or Red in Postmaster Tools), Gmail will defer even from a clean IP.

Fix it:

• Audit your last 7 days of sends for high spam complaint rates.
• Remove any segments that haven't opened in 90+ days.
• Check for compromised auth — is someone else (or a stale tool) sending from your domain? DMARC aggregate reports will tell you.

Should I Retry Manually?

No. 421 is a 4xx — your MTA will retry on its own schedule (typically every 5-15 minutes for the first hour, then backing off). Manual retries from the same IP just trigger the same defer and inflate queue depth.

The right move is to slow down sending for a few hours and let the queue drain at Gmail's pace.

How to Tell If 421 Is "Just Throttling" or a Real Problem

Healthy throttling looks like: a small percentage of messages deferred during volume peaks, all delivered within 1-2 hours, no impact on placement.

Real problem looks like: deferral rate climbing day over day, messages timing out after 24-72 hours of retries, Postmaster Tools showing reputation degradation.

If you're in the second bucket, stop sending campaigns and treat it as a reputation incident.

FAQ

Will 421 4.7.0 eventually become a 550 bounce? Yes — if your MTA gives up retrying (default ~3-5 days for most), the message returns as a hard bounce to the sender. Don't let messages sit in the queue indefinitely; tighten retry windows.

Does 421 4.7.0 hurt my reputation? The 421 itself doesn't. But whatever caused the 421 (spam complaints, alignment failures, suspicious volume) absolutely does. Treat the 421 as a symptom.

How long does Gmail throttling last? Volume-based: hours. Reputation-based: days to weeks of clean sending to recover. New IP warmup: 4-8 weeks to reach full throughput.

Catch Throttling Before It Catches You

MailVitals monitors your sending IPs, domain reputation signals, and authentication health 24/7. When something starts to drift — before Gmail starts throttling — you get an alert. Stop discovering deliverability problems from your bounce log.