Order queue open · Verified lists delivered within 24–48 hours
Cold email sending limits by provider 2026: Microsoft 365, Google Workspace, and the practical per-inbox daily limits that determine how to scale cold email volume safely.
Marcus Chen
Outbound sales trainer, 150k+ emails sent · Updated June 23, 2026
Last updated: June 2026 · Marcus Chen, Outbound sales trainer, 150k+ emails sent
TL;DR — 5 things to know before reading
After 150,000+ emails sent across multiple providers, the sending limit question comes down to one distinction: technical limits versus practical limits. Technical limits are what the provider documents. Practical limits are what spam filters allow before penalising inbox placement. These two numbers are very different, and cold email practitioners who optimise for technical limits at the expense of practical limits pay for it in deliverability.
This guide covers both: what each major provider allows technically, and what practitioners actually run at to maintain inbox placement. Inframail solves the infrastructure layer by provisioning dedicated Microsoft 365 inboxes appropriate for cold email volume. Instantly manages the per-inbox send schedule, inbox rotation, and warmup. Quarvio provides the verified contact data that keeps bounce rates low. Aimfox handles the LinkedIn channel when a second outreach channel is needed.
Microsoft 365 enforces the following technical limits for email sending:
| Limit type | Limit value |
|---|---|
| Recipients per message | 500 (To + CC + BCC combined) |
| Recipients per day per user | 10,000 (external + internal) |
| Message submission rate | 30 messages per minute per account |
| Maximum message size | 150 MB |
Source: Microsoft 365 business plans — verified June 2026
The 10,000 recipients per day limit per user is the technical daily ceiling. In cold email practice, no individual inbox should come close to this. Sending 10,000 emails per day from a single inbox is a guaranteed spam trigger regardless of email provider.
Google Workspace enforces:
| Limit type | Limit value |
|---|---|
| External recipients per day per user | 2,000 |
| Total recipients per day (external + internal) | 10,000 |
| Recipients per message | 500 |
Source: Google Workspace pricing — verified June 2026
Google Workspace's technical limits are lower than Microsoft 365 at the per-user level (2,000 vs. 10,000 external). More importantly, Google applies aggressive spam filter evaluation to outgoing email from Workspace accounts. Cold email behaviour — high volume, low engagement, single-recipient messages in bulk — is exactly what Gmail's outgoing spam detection is calibrated to catch.
Microsoft 365 vs. Google Workspace for cold email: Microsoft 365 is the preferred infrastructure for cold email. The technical limits are higher, and Microsoft's spam filter calibration for outgoing mail is more tolerant of legitimate cold email behaviour than Google's. Inframail uses Microsoft 365 specifically for this reason.
Technical limits are not the binding constraint. Spam filter thresholds are.
Per Woodpecker's guide on daily sending limits, the safe operating range for a properly warmed inbox is 30–50 sends per day. The reason is not provider policy — it is spam filter behaviour:
Safe sending limits by inbox status:
| Inbox status | Safe daily sends | Notes |
|---|---|---|
| New (days 1–7) | 5–10 | Warmup phase only, no live campaign |
| Warming (weeks 2–3) | 15–25 | Warmup + small live campaign |
| Established (4+ weeks, warmed) | 30–50 | Full campaign volume |
| Mature (3+ months, clean history) | 40–60 | Maximum safe range |
Source: Woodpecker's guide on daily sending limits — verified June 2026
These limits apply to each inbox independently. An established inbox sending 50 per day is well within the safe range. The same domain sending 500 per day from a single inbox is not.
The correct scaling mechanism is inbox multiplication, not per-inbox limit increase.
Volume calculation:
| Target sends per day | Inboxes needed at 40/day | Inboxes needed at 50/day |
|---|---|---|
| 200 | 5 | 4 |
| 400 | 10 | 8 |
| 1,000 | 25 | 20 |
| 2,000 | 50 | 40 |
Each inbox requires its own sending domain (do not put all inboxes on one domain — diversify across 3–5 sending domains minimum for volume above 200 sends per day).
Inframail provisions inboxes at scale. Each inbox is a dedicated Microsoft 365 account with its own sending identity. Instantly manages inbox rotation across the inbox pool, distributing campaign sends evenly and ensuring no single inbox is pushed beyond its safe limit.
In Instantly, per-inbox sending limits are configured under Accounts → [Account] → Sending Settings:
The random interval between sends is important. A fixed 5-minute interval (100 sends per inbox distributed at exactly 5-minute intervals) looks mechanical and is more likely to trigger pattern-based spam filters than sends at random 3–9-minute intervals.
Exceeding 50–60 sends per day on an established inbox does not cause immediate blocking in most cases. The consequences are more gradual:
The practical outcome is reduced campaign effectiveness: lower inbox placement means lower open and reply rates, even if the inbox is technically still sending. This is why the "safe limit" framing is more accurate than thinking of provider limits as binary (sending or blocked).
In Instantly: Review per-account analytics under Accounts → Analytics. Watch for:
Via Google Postmaster Tools: Per Google Postmaster Tools, track domain reputation and spam rate per sending domain weekly. A decline in domain reputation often precedes a decline in per-inbox performance.
Via MXToolbox: Check MXToolbox blacklist checker monthly and whenever you notice performance drops. An inbox on a blacklisted domain will show reduced performance regardless of per-inbox send volume.
Per Woodpecker's guide on daily sending limits, practitioners who respect the 30–50 email per inbox per day threshold consistently report higher inbox placement rates than those who push individual inboxes to higher volumes — the data consistently supports conservative per-inbox limits as the correct operating model.
Instantly reviews on G2 include multiple agency operators who describe moving from 100+ sends per inbox per day (high performance by technical standards, poor performance by deliverability standards) to 40 sends per inbox per day across 10+ inboxes, achieving the same total volume with dramatically improved inbox placement rates.
"We had 5 inboxes running 100 sends per day each. 30% open rate and dropping. Rebuilt to 15 inboxes running 40 sends per day each, same total sends. Open rate went to 47% within 3 weeks. The per-inbox limit is the lever that matters, not total sends."
— Verified G2 reviewer, head of outbound, B2B SaaS company, Instantly reviews on G2
"Discovered our Google Workspace inboxes had been flagging as unusual sending patterns after we pushed above 80 per day per inbox. Moved to Inframail Microsoft 365 inboxes capped at 45 per day. Inbox placement recovered within 2 weeks. Microsoft 365 is just more tolerant for this use case than Workspace."
— Verified G2 reviewer, campaign director, outbound agency, Inframail reviews on G2
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | One-time purchase, no subscription |
| Email inboxes | Inframail | Microsoft 365 inboxes, auto DNS |
| Cold email sending | Instantly | Sequences, warm-up, reply tracking |
| LinkedIn outreach | Aimfox | Connection campaigns, Unibox |
What is the daily sending limit for cold email per inbox?
Per Woodpecker's guide on daily sending limits, the practical safe range for a properly warmed inbox is 30–50 emails per inbox per day. This is not a provider-imposed limit but a spam filter threshold: inboxes sending above this range consistently show reduced inbox placement rates from spam filters that flag unusual volume patterns from non-enterprise senders. Scale by adding more inboxes, not by pushing individual inboxes above safe limits.
Should you use Microsoft 365 or Google Workspace for cold email?
Microsoft 365 for cold email. Both have similar technical limits (10,000 recipients per day per user for M365, 2,000 external per day for Workspace), but Google's spam filter is more aggressively tuned against cold email sending behaviour. Microsoft's spam filter produces better inbox placement rates for cold email senders operating at appropriate volumes. Inframail provisions Microsoft 365 inboxes specifically for this reason.
How many inboxes do you need to send 500 cold emails per day?
At 40 sends per inbox per day (a safe volume for established inboxes), 500 sends per day requires approximately 13 inboxes. At 50 sends per inbox per day, 10 inboxes. Spread these across 3–4 sending domains (no more than 3–4 inboxes per domain) to distribute reputation risk. Inframail provisions inboxes at this scale; Instantly manages the sending rotation.
What happens if you ignore per-inbox sending limits?
Exceeding per-inbox sending limits does not immediately block the inbox but reduces inbox placement rate over time. More sends go to spam, reducing open and reply rates. Domain reputation declines, affecting all future sends from that domain. Per Google's email sender guidelines, spam complaint rates above 0.3% also trigger penalties. The outcome is reduced campaign effectiveness — not a binary block, but a gradual degradation of deliverability that is harder to recover from than if safe limits had been maintained from the start.
Sending limits protect the sender. Contact quality protects the domain.
High bounce rates from unverified lists damage domain reputation regardless of how carefully sending limits are managed. Quarvio delivers verified B2B contact lists that keep bounce rates under 1% — one-time purchase, credits valid for 12 months, no subscription.
