TL;DR: Email sending limits come in two kinds, and confusing them ruins campaigns. The published hard caps - 500 a day for free Gmail, around 2,000 for Google Workspace, roughly 10,000 for Microsoft 365 - are ceilings you will almost never reach safely. The real limit is reputation-based throttling, which kicks in at a tiny fraction of those numbers for cold email, often 20 to 50 sends per new mailbox per day. The "2,000 a day" figure everyone repeats is a myth for cold senders. Your true cap is set by domain age, warmup status, and complaint rate, not by the provider's published number.

#Table of Contents

• The Two Kinds of Sending Limits
• Published Hard Caps by Provider
• The 2,000-a-Day Myth
• Reputation-Based Throttling Explained
• How Caps Interact With Warmup and Domain Age
• A Practical Table of Real Limits
• What Triggers a Throttle or a Block
• How to Scale Volume Without Burning Domains
• Monitoring Your Real Limit
• FAQs
• Conclusion

#The Two Kinds of Sending Limits

Almost every argument about email sending limits is confused because people mix two completely different things into one number. There are hard caps and there are reputation limits, and they have nothing to do with each other.

A hard cap is the provider's published maximum. It is a fixed rule. Free Gmail will not let you send to more than 500 recipients in a 24-hour window, full stop. Hit it and you get a clear error. This is the number documentation pages quote and the number most blog posts repeat. It is also almost useless for cold email, because you will trip the other kind of limit long before you reach it.

A reputation limit is the volume at which the provider decides your sending looks suspicious and starts pushing back. There is no published number for this. It floats based on your domain reputation, how warmed your mailbox is, your complaint rate, your engagement signals, and the time the provider has known your sending pattern. For a brand-new cold email mailbox, the reputation limit might be 20 sends a day. For a year-old mailbox with great engagement, it might be several hundred. The provider never tells you the number. You discover it by watching your placement.

Here is the rule that matters: your real email sending limit is always the lower of the two, and for cold email it is almost always the reputation limit. The hard cap is a fence at the edge of a field you will never cross. The reputation limit is the ground you are actually standing on, and it can give way under you with no warning.

Everything else in this article is about understanding the reputation limit, because that is the one that decides whether your campaign works. If you take one idea away, take this: stop quoting the published cap and start respecting the reputation limit.

#Published Hard Caps by Provider

It helps to know the published numbers, even though they are not your operating limits, because they set the absolute boundary and they reveal how the providers think.

Free Gmail (consumer accounts): roughly 500 recipients per 24 hours through the web interface. This is a consumer product. It is not built for outbound sending and you should not run cold email on it.

Google Workspace (paid): approximately 2,000 external recipients per day through the Gmail interface. Some SMTP relay configurations allow higher message-level throughput, but the 2,000 external-recipient figure is the one people quote. It is a hard cap, not a recommendation.

Microsoft 365 (paid): around 10,000 recipients per mailbox per day, with a rate limit of roughly 30 messages per minute. The per-minute throttle matters as much as the daily figure, because it caps burst sending.

Outlook.com (consumer): lower than Microsoft 365 business, in the range of 300 recipients per day, with its own throttling layered on top. Like free Gmail, it is a consumer product not meant for outbound.

Most third-party ESPs and SMTP relays: vary widely, from a few hundred to many thousands per day depending on plan and your standing with the provider. These often carry their own reputation systems on top of the inbox providers' systems, which means two layers of limits.

Notice the pattern. The consumer products have low hard caps and are unsuitable for cold email entirely. The business products have high hard caps that lull people into thinking they can send thousands a day. They cannot, because the reputation limit sits far below the hard cap. Microsoft's 10,000 figure in particular is dangerous, because a beginner reads it and assumes Outlook is the high-volume platform, then gets a hard 550 rejection at a fraction of that number. We covered why in our breakdown of the Outlook 5,000/day sender rules.

#The 2,000-a-Day Myth

The single most repeated piece of cold email advice is that you can send 2,000 emails a day from a Google Workspace account. It is technically the published cap. It is also, for cold email, a fantasy that has burned more domains than almost any other myth.

Here is why it is wrong. The 2,000 number is a hard cap on a warm, established, engaged mailbox sending mostly to people who want the mail. Cold email is the opposite of every one of those conditions. Your mailbox is often new. Your domain is often new. Your recipients did not ask for your message. Your engagement signals are weak because cold prospects rarely reply and sometimes complain. Under those conditions, sending anywhere near 2,000 a day is a reputation suicide pact.

The reality is that a new cold email mailbox should start at single-digit daily sends and ramp over weeks to maybe 20 to 50 a day, depending on engagement and domain age. That is one to two percent of the published cap. The gap between the myth and the reality is enormous, and people fall into it constantly because the published number feels official and the reputation limit is invisible.

The myth persists for a structural reason. The hard cap is documented and quotable. The reputation limit is undocumented and squishy. When someone asks "how many emails can I send a day," the easy answer is the number on the documentation page, even though it is the wrong answer for cold email. Easy and wrong beats hard and right in most repeated advice.

What makes the myth especially costly is that it encourages the worst behavior - cranking volume fast. A sender who believes 2,000 is the target ramps aggressively, trips the reputation limit, watches placement collapse, and concludes that cold email does not work. The tool was fine. The volume was insane. This is the exact failure pattern we describe in the cold email volume trap, and it starts with believing the published cap is the target.

Kill the 2,000 myth in your head. The number you should care about is the reputation limit, and for a new mailbox it is two orders of magnitude smaller.

#Reputation-Based Throttling Explained

Reputation-based throttling is the real governor on your sending, so it is worth understanding the mechanics rather than treating it as a black box.

Inbox providers - Google and Microsoft especially - maintain a reputation score for your sending domain and IP. The score is built from signals: do recipients open your mail, reply, star it, rescue it from spam? Or do they delete without reading, mark as spam, or never engage? Authentication pass rates feed in. Sending pattern consistency feeds in. Complaint rate feeds in heavily. The score is dynamic and updates continuously based on how each batch of mail performs.

When your reputation is high, the provider extends you more rope. It accepts more volume, places more mail in the inbox, and tolerates the occasional misstep. When your reputation is low or unknown - which is the default for a new cold email domain - the provider is cautious. It accepts less volume, places more mail in spam, and reacts fast to anything that looks like abuse.

Throttling is how the provider applies that caution. Instead of a hard error, you get friction. Messages get deferred with temporary failure codes that ask you to retry later. A larger share of mail lands in spam. Your effective send rate slows even though you have not hit any published cap. This is the provider saying "I do not trust you enough to deliver this much, this fast." Google is especially fond of this gradual, reversible throttle.

The crucial insight is that throttling is reputation talking, and reputation is recoverable. A throttled mailbox is not a dead mailbox. Pull back your volume, fix whatever triggered the distrust - usually targeting or complaints - keep sending clean mail, and the reputation rebuilds. This is very different from a hard block, which is the provider deciding you are spam and shutting the door, a state that is much harder to climb out of. Throttling is a warning. Treat it as one.

It is worth being precise about how reputation is scoped, because people often misunderstand this. Reputation attaches to both your sending domain and the IP you send from, and the two interact. On shared sending infrastructure, your IP reputation is partly outside your control - other senders on the same IP affect it. On dedicated infrastructure, you own your IP reputation entirely, which is better for serious senders but requires enough volume to maintain. Domain reputation, by contrast, is always yours, and it is the more durable of the two. This is why burning a domain is so costly: the IP can be changed, but the domain reputation you spent months building is gone with it. Protecting domain reputation is the whole game.

There is also a subtle point about how providers handle unknown senders. A brand-new domain does not start at zero reputation in a neutral sense - it starts at "untrusted," which is functionally negative for a cold sender. Providers assume new domains sending unsolicited mail are more likely to be spam than not, because statistically they are. This is why the early days of a new mailbox are the most fragile: you are not building from neutral, you are climbing out of a default suspicion. Every clean, engaged send in the first weeks is you proving you are not what the provider assumes you are. Understanding this reframes the low early limit. It is not the provider being stingy. It is the provider being skeptical until you earn otherwise.

#How Caps Interact With Warmup and Domain Age

Your real sending limit is not a fixed number. It grows over time as a function of warmup and domain age, and understanding that growth curve is how you scale without breaking things.

A brand-new domain has no reputation. To the inbox providers, it is a stranger, and strangers sending cold email are exactly what spam filters are built to catch. A domain registered yesterday that immediately starts sending outbound mail is the most suspicious possible pattern. This is why domain age matters: an older domain that has sent legitimate mail over time has a track record, and a track record is reputation. You cannot fake age. You can only let time pass while sending cleanly.

Warmup is the deliberate process of building reputation on a new mailbox before you use it for real campaigns. You send small volumes of mail that get opened, replied to, and engaged with - often through warmup networks or genuine internal traffic - so the inbox providers see positive signals accumulating. A properly warmed mailbox arrives at its first cold campaign with a reputation foundation instead of a blank slate. The full mechanics are in our guide to how to warm up an email, and the data on why it works is in our email warmup statistics breakdown.

These two factors compound. A warmed mailbox on an aged domain has a far higher reputation limit than a cold mailbox on a fresh domain, even though both have the same published hard cap. The published cap never changes. The reputation limit climbs from near-zero to something usable as warmup and age do their work. Your sending plan should track this curve: start tiny, ramp as reputation builds, and never get ahead of the reputation your mailbox has actually earned.

The mistake people make is treating the reputation limit as static and the warmup as a one-time chore. It is neither. The limit grows with sustained healthy sending and shrinks if you go quiet or send badly. Warmup is not a setup step you finish - it is an ongoing condition. We make that case in detail in our piece on ongoing email warmup, because the single most common scaling mistake is warming a mailbox, then immediately blasting it past the limit the warmup earned.

Domain age deserves a practical note, because people try to game it. Some buy aged domains hoping to skip the slow reputation build. This sometimes helps and sometimes backfires. An aged domain with a clean sending history carries genuine reputation value. But an aged domain that was previously used for spam, or that has a poisoned history you cannot see, can be worse than a fresh one, because you inherit its baggage. If you buy aged domains, check their history carefully, and either way, do not assume age alone lets you skip warmup. Age plus a clean record plus warmup is the combination that produces a high reputation limit. Age by itself guarantees nothing.

The interaction also runs the other direction in a way that surprises people: your reputation limit can shrink even on an aged, warmed mailbox if you stop sending or send badly. Reputation is built on recent behavior, so a mailbox that earned a high limit through months of clean sending will see that limit decay if it goes quiet for weeks. The earned capacity is not banked permanently. It reflects what you have done lately. This is the core reason warmup has to be ongoing rather than one-time, and it is why a mailbox you parked and forgot cannot simply be switched back on at its old volume.

#A Practical Table of Real Limits

Numbers are more useful than prose here. The figures below are directional working guidance based on what cold email practitioners consistently report in 2026, not published provider caps. Treat them as starting points to validate against your own placement data, not laws.

A few things to read from this table. First, look at the gap between the rightmost column and every other column. The published hard cap is 20 to 100 times higher than the safe volume. That gap is the whole point of this article. Second, notice that Microsoft's safe volume is slightly lower than Google's despite Microsoft's far higher published cap - because Microsoft rejects harder, the safe operating margin is tighter. Third, notice that consumer accounts are simply off the table for cold email regardless of their published cap.

These numbers are per mailbox. To send more total volume, you do not push a single mailbox harder - you add more mailboxes across more domains, each operating within its own safe limit. That is the core mechanic of scaling cold email, and it is why serious operators run dozens of low-volume mailboxes rather than a few high-volume ones. We cover the rotation approach in email domain rotation.

#What Triggers a Throttle or a Block

Knowing the limit is only half the job. You also need to know what trips it, because the triggers are often things people do not associate with sending volume at all.

Volume spikes. The most obvious trigger. Going from 10 sends a day to 200 overnight looks like a compromised account or a spam run. Providers throttle sudden jumps even if the absolute number is modest. Ramp gradually.

Complaint rate. The biggest one. Both Google and Microsoft enforce a 0.3 percent spam-complaint threshold. Cross it and your reputation drops fast, which tightens your effective limit. A handful of complaints from a small list can blow past 0.3 percent quickly. We explain the math in our piece on the spam complaint rate threshold.

High bounce rate. Sending to dead or invalid addresses signals a poorly maintained or purchased list, which is a classic spam pattern. High bounces tighten your limit and can trigger blocks. Verify your list before you send.

Poor engagement. Mail that nobody opens, replies to, or interacts with builds no positive reputation and can build negative reputation. Cold email is engagement-poor by nature, which is exactly why targeting and personalization are deliverability mechanics, not just conversion mechanics.

Authentication failures. Missing or misaligned SPF, DKIM, or DMARC tells providers you might be a spoofer. This alone can collapse your limit to near zero on Microsoft. Get your records right first.

Inconsistent sending patterns. Erratic timing, bursts followed by silence, wild volume swings - all of it reads as unnatural. Steady, human-paced sending builds trust. Robotic blasting erodes it.

The common thread is that providers are trying to distinguish legitimate senders from spammers, and every one of these triggers is a spam tell. Your real sending limit is the provider's estimate of how trustworthy you are, and every trigger above lowers that estimate.

It is worth noting that these triggers compound rather than add. A small volume increase on a clean mailbox is usually fine. The same increase on a mailbox that already has a borderline complaint rate and a few authentication hiccups can tip it over, because the provider is reading the whole picture. This is why a mailbox can run fine for weeks and then collapse seemingly out of nowhere - several minor issues accumulated until one more small push crossed the threshold. Treat your sending health holistically. Do not assume that because no single metric looks alarming, you have margin. The triggers interact, and the interaction is where surprises come from.

#How to Scale Volume Without Burning Domains

If your real per-mailbox limit is 30 to 50 sends a day, how does anyone run meaningful outbound? The answer is horizontal scaling, and it is the defining mechanic of professional cold email.

You do not push individual mailboxes past their reputation limit. You add mailboxes. If one mailbox safely sends 40 a day and you need 400 sends a day, you run ten mailboxes, each operating comfortably inside its own limit. Spread those mailboxes across several secondary domains so that no single domain carries dangerous concentration, and so that a reputation hit on one domain does not take down your whole operation. This is domain and mailbox rotation, and it is why serious senders have infrastructure that looks like a fleet rather than a single account.

The discipline that makes this work is keeping every mailbox in its safe zone. The temptation is always to push the mailboxes you have rather than add more, because adding more costs money and setup time. Resist it. A mailbox sending 40 clean emails a day for months is an asset. A mailbox blasting 300 a day for a week before getting throttled into uselessness is a liability you have to replace. The slow path is the only path that compounds.

Scaling also means scaling your warmup and monitoring in parallel. Every new mailbox needs its own warmup before it sends real campaigns, and every mailbox needs its placement watched. A fleet of mailboxes is a fleet of reputations, each of which can degrade independently. The operational overhead of running many low-volume mailboxes is real, which is why this is where good tooling earns its keep - managing warmup, rotation, and monitoring across a fleet by hand does not scale.

The mental shift is from "how hard can I push this mailbox" to "how many clean mailboxes can I run." The first question burns domains. The second builds an outbound machine that lasts.

There is a math reality here that makes the horizontal approach less daunting than it sounds. If a mailbox safely sends 40 a day and you run three mailboxes per domain across five domains, that is fifteen mailboxes producing 600 safe sends a day, or roughly 18,000 a month, all while every individual mailbox sits comfortably inside its reputation limit. That is meaningful outbound volume built entirely from restraint. The operators who claim cold email is dead are almost always the ones who tried to extract that 600-a-day from one or two mailboxes and burned them. The volume was always achievable. The distribution was the missing piece.

The cost calculus follows from this. Each mailbox and domain has a small monthly cost, so fifteen mailboxes across five domains is a real but modest line item - a few hundred dollars a month for infrastructure that produces 18,000 safe sends. Compared to the cost of a burned primary domain or a dead campaign, that infrastructure spend is trivial. People resist it because adding mailboxes feels like overhead, but the overhead is what makes the volume safe. Trying to save the infrastructure cost by overloading fewer mailboxes is false economy that ends in replacement costs and lost pipeline.

#Monitoring Your Real Limit

Because your real limit is invisible and dynamic, you have to infer it from signals. Monitoring is how you find the limit before you cross it.

The most important signal is inbox placement - what share of your mail actually lands in the inbox versus spam. If placement is high and stable, you are inside your limit. If placement starts sliding, you are approaching or crossing it, and you should pull back volume before the slide becomes a collapse. Placement is the early warning system that the published cap can never give you.

Google Postmaster Tools is the best free reputation dashboard for Google sending. It shows your domain and IP reputation, spam rate, and authentication pass rates. The spam rate metric maps directly to the 0.3 percent complaint threshold, so watching it tells you when you are nearing the line that tightens your limit. If you send cold email through Google and you do not use Postmaster Tools, you are operating blind. Microsoft's equivalent visibility is weaker, which is part of why Microsoft sending requires more caution.

Beyond placement and reputation dashboards, watch your reply rates, bounce rates, and any deferral codes in your sending logs. Rising deferrals are throttling in action - the provider telling you to slow down. Rising bounces signal list-quality problems that tighten your limit. Falling replies signal weak targeting that fails to build the positive reputation you need to raise your limit.

The practice that ties it together is treating your sending limit as a number you are constantly re-discovering, not a number you set once. Send, watch placement, adjust. When placement is strong, you can ramp a little. When it weakens, pull back. This continuous loop is how experienced senders stay just inside their real limit while extracting maximum safe volume. The published cap is irrelevant to this loop. Your placement data is everything.

#FAQs

#How many cold emails can I send per day from one mailbox?

For a new mailbox on a fresh domain, start at 5 to 10 sends per day and ramp over weeks to roughly 20 to 50 per day after proper warmup. The published caps - around 2,000 for Google Workspace and 10,000 for Microsoft 365 - are hard ceilings you will never safely reach with cold email. Your real limit is set by reputation, not by the published number.

#Is the 2,000 emails per day Gmail limit real?

The 2,000-per-day figure is the published hard cap for Google Workspace sending to external recipients, but it is meaningless for cold email. It assumes a warm, established mailbox sending to engaged recipients. A cold email mailbox trips reputation-based throttling at a tiny fraction of that number, often 1 to 2 percent of it, so treating 2,000 as a target will get your domain throttled or blocked.

#What is the difference between a hard cap and reputation throttling?

A hard cap is the provider's fixed published maximum, like 500 a day for free Gmail. Reputation throttling is the invisible, dynamic limit at which the provider decides your sending looks suspicious and starts deferring messages or routing them to spam. For cold email, the reputation limit is almost always far lower than the hard cap, so it is the limit that actually governs you.

#Does warming up an email increase my sending limit?

Yes, indirectly. Warmup builds the sender reputation that raises your reputation-based limit. A warmed mailbox on an aged domain can safely send several times more than a cold mailbox on a fresh domain, even though both share the same published hard cap. Warmup does not change the published cap - it raises the invisible reputation limit that actually constrains cold senders.

#Why did my emails get throttled even though I was under the daily limit?

Because the daily published limit is not the limit you hit. You crossed your reputation-based limit, which sits far below the published cap. Common causes are ramping volume too fast, a complaint rate near or above 0.3 percent, high bounce rates from a poor list, weak engagement, or authentication problems. The provider throttled you based on reputation, not on the published number.

#How do I send more total volume without burning my domain?

Scale horizontally, not vertically. Instead of pushing a single mailbox past its safe limit, add more mailboxes across several secondary domains, each sending within its own safe range. Ten mailboxes sending 40 clean emails a day produce 400 daily sends without any single mailbox crossing its reputation limit. This rotation approach is how professional cold email operations scale safely.

#Conclusion

Email sending limits are not the number on the documentation page. They are two different things stacked on top of each other - a high published hard cap you will never reach, and a low, invisible reputation limit that actually governs every cold email you send. Free Gmail caps at 500, Google Workspace at around 2,000, Microsoft 365 at around 10,000, but your real working limit for cold email is a fraction of any of those, often 20 to 50 sends per new mailbox per day. That limit grows with warmup and domain age and shrinks with volume spikes, complaints, bounces, and bad targeting. The 2,000-a-day figure everyone repeats is a myth that burns domains. Forget the published cap. Respect the reputation limit, monitor your placement, and scale by adding clean mailboxes rather than overloading the ones you have.

Operating inside that real limit by hand is genuinely hard. You have to warm every mailbox, ramp every send schedule, watch every reputation signal, and rotate across domains - all while writing email good enough to keep complaints under 0.3 percent. That is the work, and it does not scale through willpower.

This is where FirstSales fits. FirstSales drafts a personalized cold email for each prospect, a human reviews and approves it, then it sends within safe, reputation-aware volume limits across your mailboxes - so you stay inside your real sending limit automatically instead of guessing where it is and crossing it by accident. Start for $1 and run your first volume-safe campaign this week.