Email Throttling: Why ISPs Defer Your Email and How to Handle It

What Throttling Actually Is

Throttling is a mailbox provider telling your server: "Slow down." It's not a rejection — it's a deferral. Your sending server gets a 4xx SMTP response code, which means "try again later."

This is fundamentally different from a bounce (5xx code). A bounced message is permanently rejected. A throttled message can still be delivered if your server retries correctly.

Common Throttling SMTP Codes

Code	Meaning	Typical Cause
421	Too many connections	Exceeding connection limits per IP
451	Temporary policy block	Reputation issues, rate limits
452	Too many recipients	Per-session recipient limits exceeded
421 4.7.28	Gmail rate limit	Exceeding Gmail's hourly limits
451 4.7.1	Outlook temp block	IP reputation or volume spike

Why ISPs Throttle

Volume spikes. Sending 100K emails in an hour when you normally send 10K/day is the fastest way to get throttled. ISPs expect consistent patterns.

Low reputation. If your domain or IP reputation is marginal, ISPs reduce the amount of mail they'll accept from you per hour. Good reputation senders get higher rate limits.

New IP or domain. Unestablished senders get very low initial rate limits. This is why warmup exists — you're gradually earning higher throughput.

Receiving server load. Sometimes it's not about you. Providers throttle all inbound traffic during peak load periods (holidays, Monday mornings).

Practitioner note: Gmail's throttling is the most aggressive. I've seen new dedicated IPs limited to 50-100 messages per hour to Gmail for the first week. If you try to blast through it, you'll get temporarily blocked entirely.

How to Handle Throttling

1. Honor Retry Logic

Your MTA (mail transfer agent) should automatically retry deferred messages with exponential backoff. Most ESPs handle this, but if you're running your own infrastructure, verify your retry queue is configured correctly.

Standard retry schedule: first retry at 5 minutes, then 15, 30, 60, then every 2-4 hours for up to 72 hours.

2. Reduce Send Rate

If you're seeing consistent throttling to a specific provider, reduce your per-hour volume to that provider. Most ESPs let you set domain-level throttling. For self-hosted setups, configure this in your MTA.

3. Spread Volume Over Time

Instead of sending 50K messages at 9:00 AM, spread them across 9:00 AM to 2:00 PM. This matches natural sending patterns and stays under rate limits.

4. Separate by Provider

Gmail, Outlook, and Yahoo have different rate limits. Configure your sending to respect each provider's limits independently rather than using a single global rate.

Practitioner note: The biggest throttling mistake I see is agencies sending all their clients' campaigns at the same time through the same IP pool. Stagger your sends by at least 30 minutes per client, or use separate IPs per client if volume justifies it.

Throttling vs. Blocking

Throttling is temporary and self-resolving if you back off. Blocking (5xx permanent rejection or extended 4xx with no recovery) means something is fundamentally wrong — you're on a blacklist, your authentication is broken, or your reputation is severely damaged.

If throttling persists for more than 72 hours to the same provider, treat it as a block and investigate root cause.

Provider-Specific Rate Limits

Gmail: Doesn't publish exact limits, but new IPs typically start at 50-500/hour. Established good-reputation senders can push 10K+/hour per IP. Check Google Postmaster Tools for reputation data.

Outlook/Hotmail: Stricter than Gmail. New IPs may be limited to 100 messages/hour. Use Microsoft SNDS to monitor.

Yahoo: Generally more lenient than Outlook but still throttles aggressively on new IPs. Honors feedback loops for reputation signals.

Practitioner note: If you're migrating ESPs and your volume is over 100K/month, plan for 4-6 weeks of throttling on the new infrastructure. I always build this into migration timelines so clients don't panic.

When to Worry

Occasional throttling during volume spikes is normal. Consistent throttling at your regular volume means your reputation is degrading. Check complaint rates, bounce rates, and engagement signals before it turns into a full block.

If you're dealing with persistent throttling that's affecting delivery timelines, a deliverability audit can identify whether the problem is reputation, infrastructure, or volume-related.

Sources

• Google: Email Sender Guidelines
• Microsoft: Outlook.com Postmaster
• RFC 5321: Simple Mail Transfer Protocol
• RFC 7504: SMTP 521 and 556 Reply Codes
• M3AAWG: Best Practices for Managing Bounces

---

v1.0 · March 2026