How Many Cold Emails One Inbox Can Safely Send Per Day

A well-established sending domain with a clean history can typically handle a few dozen cold emails per inbox per day without triggering provider-side throttling or spam flags, spread across the working day rather than sent in one burst. Multiple inboxes on the same domain each carry their own limit, which is why teams scaling volume add inboxes rather than pushing one inbox past a safe ceiling.

The exact number varies by provider and by how clean your list and copy are, but the pattern matters more than the precise ceiling: steady, spread-out sending during business hours reads as human behavior, while a burst of sends at 3 a.m. reads as automation regardless of the actual number.

A brand-new domain or a newly created inbox needs weeks, not days, to build the sending reputation that lets it reach a mature inbox's daily ceiling. Start at a small fraction of that number and step it up gradually over several weeks, sending real, varied emails rather than warmup-only traffic, since providers watch for genuine engagement (opens, replies, and being moved out of spam) as much as they watch for volume.

Skipping the ramp and sending at full volume on day one is the single most common way a new domain earns an early reputation problem it then has to spend months recovering from.

Hitting the daily cap in one automated burst is nearly as risky as exceeding it, since the burst pattern itself is a spam signal independent of the total count. Spread the day's sends across business hours with randomized gaps between them, mimicking how a person actually works through an inbox rather than a script firing on a fixed interval.

A sequencing tool like lemlist handles this spacing automatically, which matters most in the early weeks of a domain's life, when the margin for a mistake is thinnest.

A domain rarely goes from healthy to blacklisted overnight; it usually shows warning signs first. A rising bounce rate, replies that stop arriving even though the message hasn't changed, or a growing gap between opens and clicks can all signal that a provider has quietly started routing your mail to spam before anything shows up on a public blocklist.

Check deliverability signals weekly rather than waiting for a hard bounce back from a provider telling you the domain is blocked. By the time that notice arrives, the reputation damage has usually been building for weeks.

Early warning signs that a provider may be routing your mail to spam:

• A rising bounce rate on lists and messages that have not changed.
• Replies that stop arriving even though the message and the audience are the same as before.
• A growing gap between opens and clicks, which can mean mail is landing somewhere prospects rarely look.
• Any of these signals showing up in a weekly deliverability check, while the problem is still recoverable.

If an inbox has already been pushed too hard, the fix is to cut volume back sharply, sometimes to a small fraction of the previous send rate, and hold it there for a couple of weeks while watching bounce and reply signals recover before ramping back up. Trying to push through a reputation problem with more volume almost always makes it worse.

In parallel, add a second, healthy inbox to carry current sending load so the recovering one has time to rebuild without pressure to hit a quota it currently can't support.

The same daily ceiling behaves differently depending on when you use it. Sends that go out early in the recipient's morning tend to get opened and, when a reply is coming, replied to sooner, which itself looks like healthier engagement to a mailbox provider than a message that sits unopened for days. Weekend sends generally underperform weekday sends for B2B outreach and are worth scaling back regardless of how much daily headroom is left.

A new domain still building reputation benefits most from concentrating its limited early volume into the strongest weekday windows rather than spreading it evenly across all seven days, since faster engagement during the ramp period speeds up how quickly providers trust the domain.