How Many Cold Emails Should You Send Per Day Per Domain? (Full 2026 Guide)

For most B2B cold outreach in 2026, a safe daily volume is around 30 to 50 emails per mailbox on a fresh mailbox and 100 to 150 emails per mailbox once it is fully warmed. 

Per domain, the safe ceiling depends on how many mailboxes are attached and how the volume is distributed across them, but a good working rule is to keep any single domain under about 500 outbound cold emails per day, then split further volume across additional domains.

Those numbers matter less than the pattern behind them. How many emails per day per domain cold outreach programs can safely handle is a question about distribution, not just totals. 

Send 400 emails from four warmed mailboxes on one domain, and you are usually fine. Send the same 400 from one mailbox, and you have a burned mailbox by the end of the week. 

This guide walks through how many cold emails to send per day at the mailbox, domain, and fleet level, why per-domain concentration matters more than raw daily count, and what happens when your fleet drifts too far in either direction.

How many emails per day per domain can I send for cold outreach?

For cold outreach specifically, keep any single sending domain under about 500 outbound emails per day. 

This is the working ceiling most experienced cold email deliverability practitioners land on in 2026, and it holds across Google Workspace and Microsoft 365 sending, regardless of provider-level limits.

How many emails per day per domain cold outreach can safely support is not the same as how many the mail server will accept. Providers accept far more than is safe for reputation.

The reason the number is 500 and not 2,000 is not about what the provider technically allows, but about the reputation curve. 

Domains that push above 500 per day of cold outreach start accumulating spam complaints and bounces faster than warmup can offset them, and inbox providers start scoring the domain as high-volume outbound rather than as a legitimate business sender. 

You do not see this reflected in delivery rate, but 2 to 4 weeks later, when the reply rate drifts down, the open rate looks the same.

If you need to send more than 500 cold emails per day, the right move is to add more domains, not push existing ones harder. 

Two domains at 400 per day each is safer than one domain at 800. Three domains at 300 per day each is safer than two at 450.

How many cold emails per day per mailbox should I send?

For a fresh mailbox in its first 30 days, cap outbound at 30 to 50 emails per day. For a mailbox that has completed at least 2 weeks of continuous warmup and has clean bounce history, you can safely operate at 100 to 150 emails per day. 

Above 150, you are in the danger zone for most cold email programs.

The reason per-mailbox caps matter separately from per-domain totals is that inbox providers score reputation at multiple levels. Your sending IP, your domain, and your individual mailbox each carry their own reputation. 

A single mailbox pushing high volume trips different alarms than a domain with several mailboxes each sending moderate volume, which is why 4 mailboxes each sending 100 is safer than 1 mailbox sending 400 even though the totals match. 

This is also how per-domain volume gets miscounted in most cold email programs. Teams look at the domain total and think they are safe, without noticing that all the daily send volume is concentrated on one or two mailboxes.

Some teams try to get around this by rotating campaign sending randomly across a large pool. The rotation helps, but only if each mailbox in the pool is warmed and each is being watched for individual burn signals. 

Rotation without monitoring is just distributing damage across more mailboxes.

What is a safe daily cold email volume?

A safe daily cold email volume in 2026 lands in a tight range. Roughly 30 to 50 per fresh mailbox, 100 to 150 per warmed mailbox, and no more than 500 per sending domain. 

Above those thresholds, you enter territory where reputation damage accumulates faster than warmup can recover from. Below them, you are paying for capacity you are not using.

Two things shift the safe range meaningfully. 

• First, list quality. A verified list with under 2% bounce rate lets you operate at the higher end of each range, and a list with 3 to 5% bounce forces you toward the lower end because bounces damage reputation faster than sends.
• Second, mailbox age. Vendor-provided mailboxes hit a 1-year cutoff, and mailboxes in months 10 to 12 should typically send at 70 to 80% of their peak capacity to protect the transition to a replacement.

The other factor operators forget is time distribution. Sending 100 emails between 8 AM and 10 AM and then nothing all day looks different to inbox providers than sending 10 emails per hour across a normal business day. Spread the sending; do not batch it. 

These are the safe sending limits that most cold email programs settle into once they have burned a mailbox or two and understand the pattern.

Under-utilized vs. over-utilized mailboxes and what the trade-off costs you

Over-utilization is the failure mode everyone knows about. Push a mailbox to 200 emails per day when it should be at 100, and the bounce rate creeps up, the reply rate falls off, and the mailbox burns out inside 3 to 6 weeks. Everyone in cold outreach has watched this happen at least once.

Under-utilization is the failure mode nobody talks about. A team pays for 40 sending mailboxes and only actively uses 15 of them because the campaigns were built around the old smaller mailbox pool and never expanded. 

The other 25 mailboxes sit warm but idle, and that is 25 mailboxes of monthly cost producing zero pipeline. 

Over 12 months, at even a modest $8 per mailbox per month, that is $2,400 wasted plus the campaign volume that could have been sent from those mailboxes.

The trade-off between the two failure modes is not symmetric. Over-utilization is dramatic and painful, so most teams react to it quickly. 

Under-utilization is invisible and cost-only, so most teams live with it for months. Both cost money, but they show up in different places on the P&L, which is why teams tend to fix one and never notice the other.

The clean answer is not to push every mailbox to its cap. It is to see, at any moment, which mailboxes are at 20% utilization and which are at 90, and rebalance the load. That requires per-mailbox visibility, not fleet-average visibility.

How many cold emails can you send before being considered spam?

The exact volume that gets you flagged as spam varies by provider and by your history, but the practical thresholds are consistent. 

If you push above a 4% bounce rate over 14 days on a mailbox with 100 or more sends, or above a 0.3% spam complaint rate on a mailbox with 500 or more sends, inbox providers start routing your mail to spam folders regardless of how much you are sending.

Raw volume alone rarely triggers spam classification. What triggers it is volume plus bad signal. A domain sending 800 cold emails a day to a clean, verified list with strong engagement is safer than a domain sending 100 cold emails a day to a list with a 5% bounce rate. 

Inbox providers are watching the ratio of bad signal to volume, not the total volume in isolation.

Two specific patterns almost always cross the spam threshold regardless of how careful you are elsewhere. 

• Sending to a list with catch-all addresses that later bounce is one. 
• Ramping volume from 0 to 100 in the first week of a fresh mailbox is the other. 

Both look like account compromise to spam filters even when the sender is legitimate. If you are looking at how many emails you can send before being considered spam, the answer is not a specific number. It is a ratio of clean signal to volume, and the ratio moves faster than most operators expect.

Should I split sending across more mailboxes or send more per mailbox?

Split, almost always, and the math is straightforward. Two mailboxes at 100 emails per day each have double the total reputation surface area versus one mailbox at 200. If either of the two mailboxes has an issue, only half your sending is affected. 

If the one mailbox at 200 has an issue, everything is affected. This is basic risk distribution, and it is why cold email programs at scale run pools of 20 to 100 mailboxes rather than a handful pushed hard.

The other reason to split is that per-mailbox reputation caps compound in your favor. Four mailboxes each averaging 80% inbox placement give you 320 emails hitting the inbox per 400 sent. 

One mailbox at 400 sends might hit 60% inbox placement because the volume is high enough to trigger provider-level throttling, giving you 240 inbox arrivals. More mailboxes, less volume each, higher total inbox arrivals.

The reason not to split further comes when you cross the mailbox count where you cannot manage the pool. Around 15 to 20 mailboxes, manual weekly audits stop working. You cannot check bounce rate, reply rate, warmup status, and expiry date on every mailbox by hand often enough to catch the ones about to burn. 

At that point, you either accept some silent drift or you set up continuous per-mailbox monitoring so the check runs itself.

How Insights shows your setup's real utilization

Manual utilization tracking works fine for a program with 5 to 10 mailboxes. Above that, most operators end up either overloading the mailboxes they remember to use or leaving quiet capacity on the table because their spreadsheet has not been updated in a month.

Smartlead's Insights handles this by showing per-mailbox utilization continuously across every mailbox in your setup, provisioned or imported. 

The Mailbox Utilization feature flags under-utilized mailboxes so you can rebalance campaign load onto them, and it flags over-utilized mailboxes with a recommended cap before they start accumulating burn signals. 

The Daily Avg Emails Sent feature sits alongside it, so you can see the actual send patterns per mailbox, per day, without pulling a report or opening a spreadsheet.

The point is not that you get another chart to look at; rather, Insights recommends the utilization change and queues it for you. 

• You approve the cap adjustment; you do not calculate it. 
• You approve the load rebalances across your fleet; you do not run the spreadsheet yourself. 

Every recommendation is scoped to your sending setup, your ramp speed, and your current health signals, so the numbers you approve are the ones that fit your specific setup, not generic advice.

The bigger shift is what stops happening. You stop finding out about under-utilization in a quarterly cost review. You stop finding out about over-utilization when the reply rate has already dropped. 

Both are handled continuously so the pipeline that should have booked books actually does.

How to audit your current setup in 10 minutes

Before you change anything, run a quick audit on your current setup to see where you actually stand on how many emails per day per domain cold outreach is running through your setup today. 

The audit takes about 10 minutes if you have the data in a spreadsheet, longer if you have to pull it manually per mailbox.

Start with three numbers per mailbox. 

• First, the current daily send volume averaged over the last 14 days. 
• Second, the current bounce rate over the same window. 
• Third, the mailbox age in months. Group the mailboxes by domain and add up the daily send volume per domain. 

If any domain is above 500 combined daily sends of cold outreach, that domain is over the safe sending limits and needs to be split. If any individual mailbox is above 150 per day, that mailbox is over its per-mailbox cap.

Now look at utilization from the other direction. Any mailbox at under 30% of its safe cap is under-utilized. If you have 15 or more mailboxes and 8 of them are at 20% utilization while 4 are at 90%, your fleet has a load-balancing problem, not a capacity problem. The 8 idle mailboxes can absorb the load from the 4 that are getting pushed too hard.

This is the audit most cold email teams run once, panic at the results, and then never run again because it takes too long to be a weekly habit. That is the exact gap continuous utilization visibility is meant to close.

Frequently Asked Questions

Is it better to use one big domain or several smaller ones for cold email? 

Several smaller domains, almost always. One big domain concentrates reputation risk, and one bad campaign or list can drag the whole domain down. Distributing sending across 3 to 5 domains means a reputation hit on any one domain still leaves 60 to 80% of your sending capacity healthy while you diagnose and recover.

Do sending volumes vary by mailbox provider like Google Workspace and Microsoft 365? 

Yes, the operational limits are similar, but the reputation behavior differs. Google Workspace tends to be stricter on volume ramp and content signals, while Microsoft 365 is more sensitive to authentication and IP reputation. For cold outreach, the safe volumes in this guide apply to both, but if you are seeing Gmail-specific spam placement while Outlook looks fine, the fix is different from the reverse.

Can I send more from a warmed-up mailbox than a fresh one? 

Yes. A fully warmed mailbox can safely operate at 100 to 150 emails per day, where a fresh mailbox should be capped at 30 to 50 in its first month. The engagement history built during warmup is what earns the higher cap, so if you pause warmup after the initial ramp, expect your safe cap to drift back down over time.

Should I pause sending on weekends? 

No, weekend pauses are not required for deliverability, but they are usually smart for reply rate. Cold emails sent Tuesday through Thursday morning tend to have the highest reply rates because that is when your target recipients are most likely to be processing new email. Sending on weekends does not damage reputation; it just produces lower reply yield.

Does sending volume affect open rate too, or only deliverability?

Yes, sending volume affects both. Higher volume on a mailbox that has not earned the capacity produces worse inbox placement, which shows up as lower open rate even before reply rate reflects it. This is one of the reasons open rate can drift down silently before you notice the deliverability problem underneath.