How Many Cold Emails Per Inbox Per Day (and Why the Number Dropped)
The question has a published answer and a useful answer, and they are far apart.
The published answer is the provider ceiling: the volume at which Google or Microsoft stops accepting messages from the account. The useful answer is the volume a mailbox can sustain without its reputation degrading, which is a fraction of that, and which has been drifting downward as mailbox providers tightened enforcement.
Planning from the first number is the most common way a correctly configured domain gets burned anyway.
The published ceilings
Google Workspace publishes a limit of 2,000 external recipients per user per day, or 10,000 through the SMTP relay. Trial accounts are held at 500 per day until the account has both passed 60 days and reached a cumulative payment threshold. Mail merge sends are capped lower, at 1,500.
Microsoft 365 publishes a recipient rate limit of 10,000 per rolling 24-hour period, with a maximum of 500 recipients on any single message, and a separate rate limit of 30 messages per minute over SMTP AUTH.
Outlook.com consumer accounts publish 5,000 recipients per day, but cap messages to new contacts at 1,000, which is the figure that matters for outreach.
These are worth knowing because hitting them produces a hard error rather than degraded delivery. They are not worth planning around, because nothing about your campaign will reach them before something else breaks.
What actually constrains the number
Four things throttle a mailbox long before its formal ceiling.
Complaint rate. The enforced ceiling is 0.3%, and 0.1% is the figure to aim for. Three complaints in a thousand messages is a small absolute number and an easy one to hit with a poorly matched list.
Bounce rate. Bounces signal a list that was not verified, which is one of the clearest indicators of bulk sending. A spike undoes warm-up faster than warm-up built it.
Engagement. Replies, opens and messages moved out of spam are positive signals. Mail that arrives and is ignored across thousands of sends is a negative one, and cold campaigns are structurally low-engagement.
Account age and history. A mailbox created three weeks ago has no track record to fall back on. Domains with no bulk sending history before January 2024 face tighter scrutiny from the start, which covers essentially every secondary domain registered for outreach.
None of these appear in a published limit, and all of them bite earlier.
The numbers people actually use
Commonly recommended volumes, across vendor guidance and operator practice, sit at roughly 100 to 150 messages per day from a warmed Google Workspace mailbox, and somewhat higher on Microsoft 365, where the platform tolerates more but behavioural enforcement still arrives before the published ceiling.
Treat those as starting points rather than targets. They are conventions, not measurements of your list, your offer or your reply rate — and reply rate is the variable that most changes what a mailbox can carry. A campaign that earns replies builds the engagement signal that sustains volume. One that does not degrades the mailbox at any volume.
Ramping a new mailbox
The ramp matters more than the destination.
- Start warm-up and leave it running, rather than treating it as a phase that ends.
- Begin live sending at a small fraction of target volume.
- Increase in steps across weeks, not days.
- Watch bounce rate and complaint rate at each step rather than the calendar.
- On any rise in either, reduce and hold rather than continuing the schedule.
- Spread sends across working hours with randomised intervals instead of one batch.
The step that gets skipped is the fifth. A ramp schedule is a plan, not an instruction, and the mailbox will tell you when it is not working before the provider does.
Getting to real volume
Per-mailbox limits are why volume comes from the structure rather than from any single inbox. Target volume divided by a conservative per-mailbox figure gives the mailbox count; those mailboxes spread across several domains, a small handful each, gives the domain count.
That structure also keeps each domain clear of the bulk sender threshold, which is 5,000 messages per day per sending domain and permanent once crossed. Concentrating volume on one domain reaches that line quickly and cannot be undone by reducing volume afterwards.
The setup is covered in secondary domains for cold email, and inbox rotation — distributing sends across the pool automatically rather than splitting campaigns by hand — is one of the features that most differentiates sending platforms.
Where this sits in the stack
Volume planning depends on everything underneath it. Authentication has to be correct and aligned, covered in SPF, DKIM and DMARC setup. Warm-up has to be running, covered in email warm-up tools and the WarmupInbox review. The list has to be verified, because bounce rate is the fastest constraint of the four — see the EmailListVerify review.
The full build order is in the complete cold email stack. Platform-side controls are compared in the Woodpecker review and the best sales engagement software roundup.