The honest answer is not a single number, and anyone who gives you one is selling something. Safe daily volume depends on your mailbox provider, how warmed the domain is, and a handful of factors that pull the ceiling up or down. Here are concrete ranges you can plan around, the one distinction that matters most (per mailbox, not per domain), and how to scale total volume without tripping a spam filter.
Once a domain is fully warmed, plan on roughly 30 to 50 emails per mailbox per day on Google Workspace, a little lower on Microsoft 365, and lower again on a custom SMTP setup with no built-in reputation tooling. A brand-new domain should start much lower, around 8 to 15 a day, and ramp up over several weeks. Critically, these are per-mailbox numbers. You scale total volume by warming and rotating more mailboxes, never by pushing a single one past its ceiling.
This is the single most common misunderstanding, and getting it wrong is how careful senders still end up in spam. Mailbox providers track sending reputation at the level of the individual mailbox, so the safe daily limit applies to each sending address, not to the domain as a whole. One mailbox sending 400 a day looks like an unknown sender blasting volume; ten mailboxes each sending 40 look like ten normal people sending normal amounts of mail. Same total, completely different risk profile. This is the entire logic behind inbox rotation, and it is why high-volume tools are built around unlimited sending accounts rather than higher per-account limits.
These are widely used cold email benchmarks for a starting daily volume on a fresh mailbox and a steady-state cap once warmed, per mailbox. Treat them as safe planning numbers rather than hard cliffs; the exact figure your domain tolerates depends on the factors below.
| Mailbox provider | Start (new mailbox) | Steady-state cap (warmed) |
|---|---|---|
| Google Workspace | ~15 / day | ~50 / day |
| Microsoft 365 / Outlook | ~10 / day | ~40 / day |
| Custom SMTP / other | ~8 / day | ~30 / day |
Google Workspace tolerates a higher starting volume and ceiling than a custom setup because it comes with sender-reputation infrastructure a bare SMTP server does not. These are the same numbers our calculator uses to build a ramp, and it adjusts them for your content type, vertical, and target volume.
A domain's age and warm-up progress set where in that range you can safely sit. A domain under 30 days old starts at the bottom, near the starting figure, and climbs toward the cap over the warm-up period. Skipping that ramp, and sending a new domain straight at its steady-state cap, is precisely the sudden-volume spike that mailbox providers read as a compromised account or a spammer. The ramp is not caution for its own sake; it is Google's own published advice to "start with a low sending volume and slowly increase it over time". We cover the mechanism in what email warmup is and whether it works.
Our calculator reads your domain's age and live authentication, then builds a week-by-week schedule with per-mailbox and total daily volumes, and tells you how many mailboxes your target actually needs. No signup.
If your target is more than one mailbox can safely carry, the answer is arithmetic, not effort. Divide your target daily volume by the safe per-mailbox cap for your provider, and that is roughly how many warmed mailboxes you need.
Each of those mailboxes needs its own warm-up before it carries full load, so scaling volume is really scaling the number of warmed, rotated mailboxes over time, not turning a dial up.
The ranges above assume a reasonable setup. Several things make filters more cautious and should push you to the lower end and a slower ramp:
Staying under the per-mailbox cap keeps you off the "unknown sender blasting volume" list, but it does not save a bad list. The metric that quietly kills domains is the spam complaint rate, which Google wants under 0.30% and ideally under 0.10%. A perfectly paced ramp to a poorly targeted list still generates complaints, and complaints sink the domain faster than volume does. Pace and list quality are two halves of the same job; our guide on Gmail's 2026 bulk sender rules covers the complaint-rate side.
Plan on roughly 30 to 50 per mailbox per day once a domain is fully warmed on Google Workspace, a little lower on Microsoft 365 and lower again on custom SMTP setups. A brand-new domain should start far lower, often 8 to 15 a day, and ramp up over several weeks. The number is per sending mailbox, not per domain, so you scale total volume by adding more mailboxes, not by pushing any single one past its safe ceiling. Exceeding the per-mailbox cap is the fastest way to get filtered regardless of how carefully you warmed up.
Per mailbox. Mailbox providers track reputation at the sending-mailbox level, so the safe daily limit applies to each individual sending address, not to the domain as a whole. This is why high-volume senders run inbox rotation: several mailboxes, each sending a modest, safe number, spread across one or more domains. Ten mailboxes sending 40 a day is far safer than one mailbox sending 400, even though the total is identical.
Add mailboxes, do not raise the per-mailbox number. Each mailbox has a ceiling set by its provider and its warm-up stage, and pushing past that ceiling triggers spam filtering no matter how good your list is. To send more, warm up additional mailboxes and rotate sending across them. If you need 500 sends a day, that is roughly 10 to 13 mailboxes at a safe cap, not one or two mailboxes working overtime.
Start low and ramp. A domain under 30 days old has no sending reputation, so begin at around 8 to 15 emails a day per mailbox and increase gradually over the warm-up period, which is typically several weeks depending on domain age and authentication. Jumping a new domain straight to its steady-state cap is exactly the sudden-volume spike that mailbox providers treat as a spam signal. Our warm-up calculator builds the week-by-week ramp for your specific domain.
Several things pull the ceiling down: heavy HTML with lots of links or images rather than plain text, sending from a high-scrutiny vertical such as finance, crypto, legal, or recruitment, weak or missing SPF, DKIM, and DMARC, and sending from your root business domain rather than a dedicated subdomain. Each of these makes filters more cautious, so a domain with those traits should sit at the lower end of the ranges and ramp more slowly.
Warming and rotating multiple mailboxes by hand gets unmanageable fast. lemwarm runs the schedule inside a live network of inboxes, across all your senders, in the same account you send from. Start a 14 day free trial.
Start your free trial