- Email throttling is when a receiving mail server limits the number of messages it will accept from a sender during a specific time period, causing delivery delays or temporary rejections.
- Throttling typically produces 4XX SMTP deferral codes (like 421 or 451) with messages such as "too many connections" or "rate limit exceeded."
- Proactive throttling (controlling your own send rate) is a key strategy for maintaining sender reputation and avoiding ISP-imposed rate limits.
- Sudden volume spikes are the #1 trigger for ISP throttling. Gradual warm-up and consistent sending patterns are essential.
- Different ISPs have different limits, and those limits vary based on your reputation, sending history, and engagement metrics.
You have a time-sensitive campaign ready to go, you hit send, and then watch as your delivery dashboard fills with deferrals instead of deliveries. Your emails are not bouncing permanently; they are being held back. This is email throttling in action, and it is one of the most common yet misunderstood obstacles in email delivery.
Throttling sits at the intersection of sender behavior and ISP enforcement. Understanding how it works, why it happens, and how to prevent it is critical for anyone sending email at scale, whether you are a marketing team, a transactional sender, or managing cold outreach campaigns.
What Is Email Throttling?
Email throttling is the process of limiting the rate at which emails are accepted or delivered. It operates on two sides:
ISP-side throttling (reactive): The receiving mail server (Gmail, Outlook, Yahoo, etc.) temporarily limits or defers incoming email from a sender that exceeds acceptable volume or velocity thresholds. The server returns a temporary failure code, instructing the sending server to retry later.
Sender-side throttling (proactive): The sender deliberately controls their sending rate, spacing out emails over time to avoid triggering ISP limits. This is a strategic choice that protects sender reputation and ensures consistent delivery.
Throttling is a temporary delivery delay, not a permanent rejection. Your emails are not lost; they are queued for retry. The key difference from a bounce is that throttled emails will eventually be delivered if the underlying issue is resolved, while hard bounces are permanent failures.
Throttling vs Deferral vs Bounce
These three terms are related but distinct. Understanding the differences is important for correct diagnosis and response:
| Term | What Happens | SMTP Code | Who Rejects | Retry? |
|---|---|---|---|---|
| Throttling | Sending server prevents the email from being sent because the send rate has been exceeded | N/A (internal) | Sending server / ESP | Yes, automatically |
| Deferral | Receiving server temporarily refuses the email and asks the sender to retry later | 4XX (e.g., 421, 451) | Receiving server | Yes, after delay |
| Soft Bounce | Delivery attempt fails temporarily after retries are exhausted | 4XX | Receiving server | Possible, next campaign |
| Hard Bounce | Delivery permanently fails | 5XX (e.g., 550) | Receiving server | No |
Some ESPs group throttling and deferrals under the same umbrella. Technically, a throttled email never leaves the sending server, while a deferred email reaches the receiving server but gets temporarily rejected. In practice, the effect on your campaign is similar: delayed delivery.
Why ISPs Throttle Your Email
ISPs throttle email to protect their users from spam and to manage server resources. Here are the most common triggers:
Sudden Volume Spikes
This is the number one trigger for throttling. If your daily sending volume jumps dramatically, such as going from 5,000 emails per day to 50,000 overnight, ISPs interpret this as suspicious behavior. Spammers often exhibit exactly this pattern: acquire a list, blast it, and move on. Even if your list is legitimate and opt-in, a sudden spike in volume without a gradual ramp-up will trigger rate limits.
New or Unknown IP/Domain
When you send from a new IP address or domain that has no sending history, ISPs have no reputation data to evaluate your trustworthiness. They respond by applying strict rate limits until you build a track record of good sending behavior. This is why IP warm-up and domain warm-up are critical for new senders.
Poor Sender Reputation
If your IP or domain has a low sender reputation due to previous high bounce rates, spam complaints, or blacklisting, ISPs will throttle your email more aggressively. A damaged reputation takes time and consistent good behavior to repair.
Low Engagement Rates
ISPs, particularly Gmail, heavily weight recipient engagement in their filtering decisions. If a large portion of your recipients are ignoring, deleting, or marking your emails as spam, the ISP may throttle future sends to protect the inbox experience for those users.
Content and Authentication Issues
Emails with spammy content patterns, missing or misconfigured SPF, DKIM, or DMARC records, or messages that trigger content filters can contribute to throttling. Authentication failures in particular signal to ISPs that you may not be a legitimate sender.
How to Recognize Throttling in Your Logs
Throttling does not always announce itself clearly. Here are the signs to watch for in your mail server logs and ESP reports:
SMTP Response Indicators
Look for 4XX response codes in your delivery logs, particularly:
421 Too many concurrent SMTP connections421 4.7.28 Unusual rate of unsolicited mail(Gmail)421 RP-001 Too many connections from your IP(Microsoft)451 4.7.1 Try again later452 Too many recipients- Any 4XX code containing phrases like "rate limit," "try again later," "too many connections," or "temporarily deferred"
Dashboard and Metric Indicators
- Spike in deferrals or soft bounces: A sudden increase in temporary failures, especially concentrated to a single receiving domain
- Delayed delivery times: Emails that normally deliver in seconds are taking minutes or hours
- Domain-specific patterns: Deferrals only to Gmail, or only to Microsoft domains, suggest provider-specific rate limiting
- Declining open rates on time-sensitive campaigns: Emails arriving hours late miss their optimal delivery window
Set up real-time alerting on your deferral rates. If your deferral rate to any single domain exceeds 5% within an hour, pause sending to that domain immediately and investigate. Many ESPs offer webhook notifications for delivery events that can power these alerts.
Rate Limits by Major ISP
ISPs do not publish their exact rate limits, and the limits vary dynamically based on your reputation and sending history. However, here are general guidelines based on industry experience:
| ISP | General Behavior | Key Considerations |
|---|---|---|
| Gmail | Highly reputation-based limits. New senders start with strict throttling that loosens as reputation builds. | Gmail weighs engagement heavily. Low open/click rates accelerate throttling. Monitor via Google Postmaster Tools. |
| Microsoft (Outlook/Hotmail) | Strict connection and message-per-connection limits. Uses BCL (Bulk Complaint Level) scoring. | Keep complaint rate below 0.2%. Use Microsoft SNDS to monitor. Aggressive on new IPs. |
| Yahoo/AOL | Moderate limits. Relies heavily on Spamhaus data and feedback loop complaints. | Ensure you are not listed on Spamhaus blocklists. Register for Yahoo CFL (Complaint Feedback Loop). |
| Apple (iCloud Mail) | Conservative limits for unknown senders. Less transparent about reputation signals. | Limited monitoring tools available. Focus on clean list practices and low complaint rates. |
Important: Rate limits are not static. An IP with excellent reputation at Gmail may be able to send 10,000+ messages per hour, while a new IP might be limited to a few hundred. The only way to know your effective limit is to monitor your delivery logs and adjust based on actual deferral patterns.
How to Prevent Email Throttling
Warm Up New IPs and Domains Gradually
Never start sending at full volume from a new IP or domain. Follow a structured warm-up plan that gradually increases volume over 2-4 weeks. Start with your most engaged recipients first, as positive engagement signals will build your reputation faster. See our IP warm-up guide for detailed schedules.
Maintain Consistent Sending Patterns
ISPs prefer predictable senders. If you normally send 10,000 emails per day, do not suddenly jump to 100,000 for a promotional campaign. If you need to increase volume, ramp up gradually over several days. Avoid irregular patterns like sending nothing for two weeks and then blasting a large campaign.
Segment and Stagger by Receiving Domain
Rather than sending your entire campaign at once, segment your list by recipient domain and stagger delivery. Send to Gmail recipients first, then Microsoft, then Yahoo. This prevents you from hitting any single ISP's rate limit. Space your sends across business hours rather than sending everything in a single burst.
Implement Sender-Side Rate Controls
Configure your ESP or mail server to enforce your own sending rate limits. Recommended baseline settings for most senders:
- Per-domain hourly limit: Start at 200-500 messages per hour per receiving domain, then increase based on deferral feedback
- Connection limits: Limit simultaneous SMTP connections to any single receiving server to 2-5
- Messages per connection: Send 10-20 messages per SMTP connection before opening a new one
- Inter-message delay: Add a 1-3 second pause between individual message deliveries
Fix Authentication Issues
Ensure your SPF, DKIM, and DMARC records are correctly configured. Authentication failures contribute to a negative reputation signal that lowers your effective rate limit with ISPs. Use the SPF checker, DKIM checker, and DMARC checker to verify your setup.
Maintain List Quality
High bounce rates and complaint rates directly impact your reputation, which in turn lowers your throttling threshold. Implement list hygiene practices including regular email verification, prompt hard bounce suppression, and engagement-based segmentation to ensure you are only sending to recipients who want your messages.
How to Respond When You Are Being Throttled
If you detect active throttling in your logs, follow this response plan:
- Reduce volume immediately. Cut your sending rate to the affected domain by 50-75%. The ISP is telling you to slow down; ignoring that signal will make things worse.
- Check your reputation. Use Sender Reputation Checker, Google Postmaster Tools, and Microsoft SNDS to assess your current IP and domain reputation. Look for any recent drops.
- Review your blacklist status. Throttling can be an early indicator that you have been listed on a blocklist. Check major DNSBLs for your sending IPs.
- Audit recent campaigns. Look for any changes that coincided with the throttling: new list segments, different content, increased volume, or changes to your sending infrastructure.
- Gradually rebuild. Once the throttling subsides, slowly increase your sending rate over several days, monitoring deferral rates closely at each step. Do not immediately return to your previous volume.
Tip: If throttling persists after reducing volume and fixing any identified issues, it may indicate a deeper reputation problem. In this case, consider a full warm-up cycle where you start with very low volume (100-200 per day) and rebuild gradually over 2-4 weeks, prioritizing your most engaged recipients.
Throttling Considerations: Transactional vs Marketing Email
Throttling affects transactional email and marketing email differently, and your strategy should account for this:
Transactional email (password resets, order confirmations, account notifications) must be delivered in near-real-time. If your transactional email is being throttled, it creates a terrible user experience. The best practice is to send transactional email from a separate IP address and domain (or subdomain) from your marketing email. This isolates your transactional reputation from any marketing reputation issues.
Marketing email is more tolerant of slight delays, but throttling can still hurt time-sensitive campaigns like flash sales or event reminders. Use segment-and-stagger strategies for large marketing sends, and avoid scheduling all campaigns to go out at the same time.
Gmail uses machine learning models that evaluate sender behavior in real-time, including how quickly recipients delete emails, whether they click or reply, and scroll patterns. These signals feed directly into throttling decisions. A sender with high engagement can send at much higher rates than one whose emails are routinely ignored.
Tools for Monitoring Throttling
Effective throttle management requires visibility into your delivery metrics. Here are the key monitoring tools:
- Google Postmaster Tools: Provides domain and IP reputation data, spam rate metrics, and delivery error details for messages sent to Gmail recipients.
- Microsoft SNDS (Smart Network Data Services): Shows your IP reputation, complaint rates, and spam trap hits for messages sent to Microsoft domains.
- ESP delivery dashboards: Most ESPs (SendGrid, Mailgun, Amazon SES, Postmark) provide real-time delivery event data including deferrals and throttling events.
- Sender Reputation Checker: Monitor your overall sender reputation and identify reputation issues before they trigger throttling.
- Mail server logs: For self-hosted infrastructure, parse your MTA logs for 4XX response codes and deferral patterns.
Frequently Asked Questions
Throttling is a temporary delay where the ISP asks you to slow down and retry later (4XX response codes). Blocking is a permanent rejection where the ISP refuses your email entirely (5XX response codes). Throttling is a warning; blocking is a penalty. If you ignore throttling signals and continue sending at high rates, it can escalate to blocking.
There is no universal number. ISPs set dynamic rate limits based on your sender reputation, sending history, engagement metrics, and authentication status. A sender with excellent reputation at Gmail might deliver thousands of messages per hour without issues, while a new sender could be limited to a few hundred. The only reliable approach is to start conservatively, monitor your deferral rates, and scale gradually.
Throttling itself is a symptom, not a cause, of reputation issues. However, how you respond to throttling matters. If you respect the ISP's signals and reduce your volume, your reputation should recover. If you continue blasting emails despite deferrals, the ISP may escalate to blocking your messages entirely, which will cause significant reputation damage.
Generally, no. ISPs like Gmail and Yahoo do not offer manual rate limit adjustments. Your limits increase automatically as you build a positive sending reputation through consistent volume, good engagement, low complaints, and proper authentication. Microsoft does offer a support process for delivery issues, but it is focused on troubleshooting rather than manually raising limits.
Having an opt-in list is necessary but not sufficient to avoid throttling. ISPs also evaluate volume consistency, engagement quality, bounce rates, complaint rates, and authentication status. You can have a perfectly legitimate opt-in list but still trigger throttling by sending too much too fast, having poor engagement, or using a new IP without proper warm-up. Focus on sending to engaged segments first and ramping volume gradually.