Email Throttling and Rate Limiting: Sending Speed and Deliverability
You have a list of 5,000 verified emails ready to go. Your content is polished, your authentication is set up, and your domain has a solid reputation. So you hit send on all 5,000 at once and watch your deliverability tank within hours.
Sending speed is one of the most overlooked factors in email deliverability. Mailbox providers do not just care about what you send and who you send to. They care about how fast you send it. Blast too many emails too quickly and you trigger rate limiting, throttling, and in severe cases, temporary blocks that can take days to resolve.
What Is Rate Limiting?
Rate limiting is when a receiving mail server restricts the number of emails it will accept from your sending IP or domain within a given time period. Every major mailbox provider implements rate limits, though they rarely publish the exact thresholds.
When you exceed a rate limit, the receiving server responds with a temporary failure code (typically 421 or 452). This is a soft bounce. The server is saying "you are sending too fast, slow down and try again later." Your sending platform should automatically retry these messages after a delay.
Rate limits vary by provider, by your sender reputation, and by the receiving server's current load. A sender with excellent reputation can typically send more emails per hour to Gmail than a sender with mediocre reputation. New senders with no established reputation face the strictest limits.
Gmail, for example, applies much tighter rate limits to new or low-reputation senders. A brand new sending domain might be limited to a few hundred messages per hour to Gmail addresses, while an established sender might handle thousands per hour without hitting limits.
What Is Throttling?
Throttling is a broader concept than rate limiting. While rate limiting is an explicit rejection at the server level, throttling includes all the ways providers slow down or deprioritize your email when you send too aggressively.
One form of throttling is delayed delivery. The provider accepts your email but holds it in a queue for hours before delivering it to the recipient's inbox. Your email arrives, but it arrives 4-6 hours after you sent it, buried under newer messages.
Another form is increased spam filtering. When providers see a sudden spike in volume from a sender, they increase the scrutiny applied to those messages. Emails that would normally pass content filters might get spam-foldered during a volume spike because the provider's algorithms interpret the sudden increase as suspicious behavior.
Throttling is harder to detect than rate limiting because you do not get explicit error codes. Your delivery rate might look fine, but your inbox placement quietly degrades. You only notice when reply rates drop or seed testing shows increased spam placement.
Why Speed Matters to Mailbox Providers
From Gmail's perspective, there is a meaningful behavioral difference between a person sending individual emails throughout the day and a system blasting 10,000 messages in 30 minutes.
Legitimate person-to-person email happens in patterns. People send a few emails, wait for replies, send more. The volume is moderate and distributed over time. Marketing and outreach email also follows patterns, but the volume tends to come in bursts.
Spam follows a very different pattern: maximum volume in minimum time. Spammers want to blast their message to as many addresses as possible before their sending infrastructure gets blocked. Speed is a survival tactic for spammers.
So when a mailbox provider sees a sudden, large burst of email from a single domain or IP, they treat it with suspicion. The faster and larger the burst, the more it looks like spam behavior. Rate limiting and throttling are the provider's defense mechanisms against this pattern.
Optimal Sending Speeds by Provider
While exact rate limits are not published, the email community has established reasonable sending speed guidelines through collective experience.
Gmail: For new or low-reputation senders, keep to 50-100 messages per hour to Gmail addresses. For established senders with good reputation, 500-1,000 per hour is generally safe. High-reputation, high-volume senders can push higher, but most cold email senders should stay conservative.
Microsoft (Outlook, Hotmail, Live): Microsoft tends to be more aggressive with rate limiting than Gmail. Start at 50-100 per hour for new senders. Microsoft is also more likely to temporarily block your entire sending domain if you trip their volume thresholds, which can take 24-48 hours to resolve.
Yahoo: Yahoo's rate limits are generally more forgiving than Microsoft but stricter than Gmail for new senders. Start at 100-200 per hour and adjust based on bounce patterns.
Corporate mail servers: Companies running their own mail infrastructure have widely varying rate limits. Some large enterprises accept thousands of messages per hour. Smaller companies running basic mail server configurations might rate-limit at 20-50 messages per hour from unknown senders.
Batch Sending vs Drip Sending
There are two fundamental approaches to managing sending speed, and each has its place.
Batch sending is when you send a large group of emails in a short burst. A campaign of 1,000 emails sent over 30 minutes is batch sending. This approach is simple, fast, and appropriate for marketing emails going to engaged subscribers through a reputable ESP with established sending infrastructure.
Drip sending is when you spread your emails out over a longer period. The same 1,000 emails might be sent at a rate of 50 per hour over 20 hours. This approach mimics more natural sending patterns and is less likely to trigger rate limits or throttling.
For cold email outreach, drip sending is almost always the better choice. Cold emails go to recipients who have not opted in to hear from you, which means the provider relationship starts from a place of uncertainty. Sending them slowly reduces the risk of triggering defensive mechanisms.
Most cold email platforms (Instantly, Smartlead, Lemlist, Woodpecker) implement drip sending automatically. They send your campaign messages in small batches throughout the day rather than all at once. This is one of the key advantages of using a dedicated cold email tool versus sending cold outreach through a general-purpose ESP.
For marketing email, batch sending through an established ESP is usually fine. The ESP manages sending speed across their infrastructure, and their established IP reputation gives them higher rate limit allowances at major providers.
The Warmup Connection
Sending speed is intimately connected to domain warmup. The warmup process is essentially about gradually increasing your sending speed over time until mailbox providers trust you at your target volume.
If your warmup plan says to send 20 emails per day in week one, those 20 emails should not all go out in the first 5 minutes of the day. Spread them across the entire day. Four emails per hour over 5 hours looks much more natural than 20 emails in a burst followed by silence.
As you ramp up volume during warmup, you are simultaneously ramp up the sending speed that providers will tolerate from your domain. By the time you reach full volume at week 6-8, providers have seen your domain sending consistently at increasing speeds and have adjusted their rate limits accordingly.
Jumping ahead of your warmup schedule, even for a single day, can undo weeks of progress. A domain that has been sending 30 per day for three weeks and suddenly sends 300 in an hour will trigger the same suspicion as a brand new domain blasting at scale.
Detecting Rate Limiting in Your Campaigns
How do you know if you are being rate-limited? Look for these signals in your sending reports.
A sudden increase in soft bounces, especially 421 or 452 error codes, is the most direct signal. These codes explicitly tell you the receiving server is temporarily refusing your messages due to volume.
Delivery delays are another signal. If your emails normally reach recipients within seconds but suddenly take hours, you are likely being throttled. Some email platforms report delivery timing data. If yours does not, ask your ESP about average delivery latency.
Provider-specific delivery failures are a clue. If your Gmail delivery is fine but Outlook is bouncing half your messages, you are likely hitting Outlook's rate limits. Segment your bounce data by receiving provider to identify provider-specific throttling.
A drop in inbox placement despite no changes to your content or list is a subtler signal of throttling. The provider is accepting your messages but downgrading them to spam because your sending pattern triggered increased scrutiny.
Practical Sending Speed Guidelines
For cold email campaigns, limit each sending inbox to 50 emails per day maximum. Most cold email experts recommend even lower, around 30-40 per day per inbox. Spread sends across 6-8 hours of the business day.
If you need to send more volume, add more sending inboxes (from different domains) rather than increasing volume per inbox. Ten inboxes at 40 emails per day gives you 400 daily sends with low per-inbox volume.
For marketing emails through an ESP, trust the ESP's infrastructure to manage sending speed. Reputable ESPs have established relationships with mailbox providers and manage rate limit compliance at the infrastructure level. Your main concern is list quality and engagement, not sending speed.
For transactional emails, sending speed is rarely an issue because these emails are triggered by individual user actions (purchases, signups, password resets) and naturally occur in distributed patterns. If you have high-volume transactional needs (thousands per hour), use a dedicated transactional email service like Postmark, SparkPost, or Amazon SES.
Never send your entire list at once for the first campaign after any list change, verification, or domain modification. Start at reduced volume, monitor for throttling signals, and ramp up over 2-3 sends once you confirm deliverability is stable.
The fundamental principle is simple: send like a human, not like a machine. Distribute your volume over time. Start slow and ramp up. Match your sending speed to your reputation. The patience you invest in proper sending speed management pays off in consistently better inbox placement and fewer deliverability incidents.
