Email Sending Throttling Settings: Per-Mailbox Ramp Mechanics

Most cold email problems get blamed on copy or lists. Plenty of them are actually throttle settings nobody touched. You connect a fresh mailbox, the tool ships with aggressive defaults, and within a week your sends are spiking, bursting, or hitting a provider ceiling you didn't know existed.

This guide covers the narrow mechanics of email sending throttling settings: the per-mailbox dials that govern how fast a single inbox releases messages. We won't relitigate how many mailboxes you need or how to rotate across a pool. Those are scaling decisions, and our inbox rotation strategy guide owns them. This is about the settings inside one mailbox.

What email sending throttling settings actually control

Throttling settings are the rate controls that sit between your campaign and the SMTP server. They decide how many emails a mailbox sends in a day, how much time passes between each send, and how that daily number climbs over weeks.

Think of it this way. Your provider sets a hard ceiling. Your reputation sets a much lower safe ceiling. Throttling settings are how you keep every send comfortably under both, while looking like a person rather than a script.

Three dials do almost all the work:

1. Daily send cap per mailbox: the maximum messages this inbox sends in 24 hours.
2. Send interval (spacing) : the gap between consecutive sends, usually with randomization.
3. Ramp increment: how much the daily cap grows day over day.

Everything else (sending windows, timezone restrictions, warmup overlap) modifies how those three behave. Get the three right and the rest is tuning.

One clarification before we go further. Throttling is not warmup. Warmup builds reputation by exchanging seeded messages between inboxes; throttling governs the rate of your real campaign sends. They run together, but they're different systems. If you need the reputation-building side, start with our email warmup guide. This article assumes warmup is handled and focuses on the send-rate dials.

Dial 1: setting the per-mailbox daily cap

The daily cap is the single most consequential throttle setting, and it's the one people set wrong most often. They see the provider's published limit and treat it as a target. It isn't. It's the point where the provider stops you, not the point where your reputation stays healthy.

Here are the real ceilings, straight from the providers.

Google Workspace caps a paid user at 2,000 messages sent per day and 3,000 external recipients per day, measured over a rolling 24-hour window, per the Gmail sending limits documentation. Trial accounts drop to 500. Cross the line and Gmail locks sending for up to 24 hours.

Microsoft 365 works differently. Exchange Online enforces a recipient rate limit of 10,000 recipients per day and a message rate limit of 30 messages per minute, both documented in the Exchange Online limits service description. The per-minute cap is fixed and can't be raised.

Now look at the gap between those numbers and what a cold mailbox should actually send. A safe per-mailbox volume for cold outreach is a small fraction of the provider maximum, typically a couple dozen messages a day rather than thousands. The exact figure depends on domain age, warmup state, and reply quality, so we keep that number in its own guide: how many cold emails per day per mailbox is safe. For the hard caps and what triggers a lockout, see Gmail sending limits for cold outreach.

The throttle setting itself is simple once you've picked the number. Set the daily cap field to your conservative target, not the provider max. If your tool ships with a default of 100 or 200 per mailbox, that default was built for newsletters with opt-in lists, not cold outreach. Lower it.

A useful mental check: if your daily cap times your number of mailboxes overshoots your actual prospect list for the week, your cap is too high and you're tempted to dump volume. Cold email rewards restraint. The cap is where you enforce it.

Dial 2: send spacing and randomized intervals

The daily cap tells the mailbox how much to send. The send interval tells it how to release that volume across the day. This is where a lot of otherwise-fine setups quietly look automated.

Picture two mailboxes, both set to 30 emails a day. The first fires all 30 in a four-minute burst at 9:00 a.m. The second spaces them out, one every several minutes, across a working day. Same volume, completely different signal. Mailbox providers and filtering systems watch send patterns, and a tight burst of near-identical messages is one of the more obvious robotic tells.

There's a hard technical reason to space sends too, at least on Microsoft. Exchange Online's 30-messages-per-minute limit means a burst gets throttled regardless of your intent. Microsoft's documentation is specific about the behavior: when outbound volume passes the rate limit, "any excess in message submission will be throttled and successively carried over to the following minutes," and it notes that Exchange Online "isn't suited to accommodate bulk-mailing scenarios." So a burst doesn't even buy you speed. It just queues.

Gmail doesn't publish a per-minute throttle, but the reputation logic still reads cadence. Bursting from a Gmail mailbox won't bounce, but it feeds the pattern signals that filters use.

So how should per-mailbox send spacing be configured?

• Compute the natural gap. Take your sending window length and divide by your daily cap. Thirty emails across an eight-hour window is one every 16 minutes on average. That's a comfortable, human pace.
• Randomize the interval. A perfect send every 16 minutes on the dot is its own fingerprint. Set a randomized range (say, anywhere from 8 to 20 minutes) so the rhythm varies. Most cold email tools expose this as a min/max delay or a jitter setting.
• Never set the interval to zero. A zero or near-zero gap means the tool dumps the whole daily cap as fast as the SMTP connection allows. That's the burst pattern you're trying to avoid.

The setting names vary. You might see "delay between emails," "send interval," "minimum gap," or "throttle delay." They all do the same job: convert a daily number into a paced trickle. Configure the range, not a single fixed value.

Dial 3: the ramp curve over time

A brand-new mailbox should not start at its target daily cap on day one of live sending. The ramp increment controls how the cap climbs, and it's the throttle setting most directly tied to reputation.

Google is unambiguous here. Its sender guidelines say to "start with a low sending volume to engaged users, and slowly increase the volume over time," and to "avoid introducing sudden volume spikes if you do not have a history of sending large volumes." The Messaging, Malware and Mobile Anti-Abuse Working Group makes the same point in its Sender Best Common Practices: reputation forms through consistent, predictable growth, and sharp swings in volume hurt it.

Translate that into a throttle setting and you get a ramp: a starting cap, a step size, and a cadence for raising it.

Here's a conservative live-send ramp for a mailbox that has already finished warmup. This is your real campaign volume climbing, separate from the warmup messages running underneath it. (For the warmup-phase volume curve specifically, the 30-day warmup schedule owns that table.)

The exact numbers matter less than the shape. Small steps, raised on a fixed cadence, with the cap holding flat once you hit your safe ceiling. Raising the cap by a handful of emails every couple of days reads as steady growth. Doubling it overnight reads as a spike.

Two ramp mistakes worth calling out:

• Resetting to zero on weekends, then spiking Monday. A mailbox that goes silent Saturday and Sunday, then dumps a backlog Monday morning, creates exactly the volume swing the guidelines warn against. Keep weekend volume low but nonzero, or pause cleanly without a Monday flood.
• Ramping faster after a good week. One clean week is not permission to skip steps. The ramp is a floor for caution, not a reward schedule.

Provider rate limits your throttle has to respect

Your throttle settings live on top of provider-enforced limits, and the two providers behave differently when you hit the wall. This matters because the consequence shapes how much headroom you leave.

Sources: Gmail sending limits and Exchange Online limits.

The practical takeaway: Gmail punishes the overshoot with a hard lockout, so you want real distance from its caps. Microsoft just slows you down, but its fixed 30-per-minute throttle means your spacing has to keep bursts under that rate or your queue backs up. Either way, the soft caps and spacing recommended above keep you nowhere near these numbers, which is the point. If you're picking between providers for a new sending operation, our email provider comparison breaks down the tradeoffs.

One Microsoft footnote worth knowing if you're on a default tenant: outbound mail from onmicrosoft.com domains is throttled to 100 external recipients per organization per 24 hours, per Exchange Online's limits. Never send cold campaigns from the default domain. Use a real custom domain.

Sending windows and timezone settings

A sending window restricts when a mailbox is allowed to send, usually to business hours in the recipient's timezone. It's a throttle setting because it directly changes your effective send rate.

Here's the interaction people miss. If you cap a mailbox at 30 a day but restrict sending to a four-hour window, you've compressed those 30 sends into 240 minutes, which forces a tighter interval. Widen the window to eight hours and the same 30 sends breathe, one every 16 minutes instead of one every 8.

So set the window and the cap together:

• Match the window to working hours in the recipient timezone, not yours. A 9-to-5 send pattern in the prospect's local time looks natural. For why timing matters to response rates as well as cadence, see timing and scheduling for cold email.
• Check that your window can hold your cap at a human pace. Window minutes divided by daily cap should land comfortably above a few minutes per send. If it doesn't, widen the window or lower the cap.
• Stagger windows across mailboxes if you run several. You don't want every mailbox firing in the same hour.

Throttling while warmup is still running

If warmup is active on the same mailbox, the warmup messages and your live sends both count toward the load that mailbox is carrying. Most warmup engines run quietly in the background at a modest volume, so the combined number stays reasonable, but you should be aware it's additive.

The general rule: don't push your live-send cap to its ceiling while warmup is still ramping aggressively. Let warmup do its job underneath, keep live volume conservative, and raise the live cap as warmup stabilizes. The methodology for the warmup side lives in our email warmup guide; here we're just noting that your throttle setting should account for it rather than ignore it.

Throttle settings that quietly hurt deliverability

A few configurations look fine in the dashboard and cause damage anyway. Watch for these.

• High cap, narrow window. The classic burst maker. A big daily number squeezed into a short window forces fast sends. Either lower the cap or widen the window.
• Fixed interval, no randomization. A metronome-perfect gap is a pattern. Always set a range.
• Provider-max daily cap. Setting the cap to 2,000 because Gmail allows it confuses the technical ceiling with a safe target. The safe number is a fraction of that.
• Ramping by doubling. Big jumps in the daily cap are the volume spikes Google explicitly warns against. Step up in small increments.
• Ignoring the per-minute ceiling on Microsoft. If your tool can burst, and your spacing is loose, you can clip the 30-per-minute throttle and queue messages. Keep the interval honest.
• Identical throttle on every mailbox. Mailboxes of different ages and reputations shouldn't carry the same cap. Newer mailboxes ramp from lower.

Recommended starting throttle settings

These are conservative starting points for a cold outreach mailbox that has finished warmup, not a maximum. Tighten further if you're on a young domain or seeing any bounce or spam-rate movement.

Pair these with disciplined list hygiene and authentication. Throttling protects a healthy sender; it can't rescue a mailbox with a bad list or broken records. If you're connecting a non-Google mailbox, our custom SMTP setup guide covers the connection side.

Common questions

Do throttling settings guarantee inbox placement?

No. Throttling reduces the odds of looking automated and keeps you under provider limits, which removes a category of self-inflicted problems. It does nothing for weak copy, an unverified list, or missing authentication. Treat it as one control among several, not a fix on its own.

What's the difference between throttling and warmup?

Warmup builds reputation by exchanging seeded messages that get opened and replied to. Throttling controls the rate of your actual campaign sends. They run at the same time and complement each other, but they're separate systems with separate settings. Our warmup guide covers the reputation side.

Should every mailbox use the same throttle settings?

No. A mailbox that's two days into live sending should carry a lower cap and tighter ramp than one that's been sending cleanly for two months. Set the spacing logic consistently, but let the daily cap and ramp track each mailbox's age and health. How many mailboxes you need in the first place is covered in how many email accounts you need for cold outreach.

How is throttling different from inbox rotation?

Throttling is a per-mailbox setting: it governs the rate of one inbox. Inbox rotation is a pool-level strategy: it distributes a campaign across many mailboxes so no single one carries too much. You configure throttling on each mailbox; rotation decides which mailbox sends the next message. The strategy side lives in our inbox rotation guide.

Why does Microsoft cap at 30 messages per minute when Gmail doesn't?

The two providers chose different enforcement models. Microsoft publishes a fixed per-minute rate and defers anything over it to later minutes. Gmail publishes daily caps and locks the mailbox if you blow past them, but doesn't document a per-minute figure. Your spacing should respect both behaviors: stay under Microsoft's per-minute throttle, and stay well under Gmail's daily caps.

Sources

• Google Workspace, Gmail sending limits in Google Workspace
• Google, Email sender guidelines
• Microsoft, Exchange Online limits
• M3AAWG, Sender Best Common Practices