Email Sending Limits by Provider: Gmail, Outlook, SMTP (2026).

Email sending limits are one of the most practically important deliverability variables for cold outreach, and one of the least well-documented. Every provider has a daily cap, a per-hour sub-limit, and behaviors that trigger temporary sending restrictions - but the numbers are scattered across support docs and change without notice. This guide consolidates the 2026 sending limits for Gmail, Outlook 365, Zoho, and the major SMTP relay providers, along with the warm-up ramp schedules and inbox rotation strategies that let you scale cold email volume without triggering rate limits or spam filters.

Why Email Sending Limits Matter for Cold Outreach

Cold email depends on sender reputation. Every inbox provider - Gmail, Outlook, Zoho - evaluates the sending behavior of each account and domain. When an account sends volume that spikes above its established pattern, exceeds provider-side limits, or generates a high rate of spam complaints, the provider throttles or suspends the sending account. The damage compounds: a suspended sending account affects domain reputation, which in turn affects deliverability for all other inboxes on the same domain.

Two types of limits govern cold email volume:

• Provider-side hard limits: the daily caps set by Gmail, Outlook, Zoho, and SMTP relay services. Hitting these limits triggers automatic sending suspension until the next calendar day (or longer). These limits are non-negotiable and published in provider documentation, though the specific thresholds change periodically.
• Practical safe limits: the volume below which spam filters and sender reputation algorithms do not flag the account as anomalous. For cold email, these are typically 30-50% lower than the provider-side hard limit. Sending at 90% of your daily cap every day is a fast path to spam folder placement even without hitting the formal limit.

Understanding both types - and building a sending architecture that stays below both - is what separates cold email infrastructure that delivers consistently from infrastructure that slowly degrades until campaigns produce 20% inbox placement.

Gmail Sending Limits: Personal vs Workspace (2026)

Google operates two email products with different sending limits: Gmail (free, @gmail.com addresses) and Google Workspace (paid, custom domain addresses). The distinction matters for cold email because cold email at scale requires custom domain addresses - @gmail.com addresses have lower limits and are immediately recognized as personal accounts, which signals mass outreach to spam filters.

Practical considerations for Google Workspace cold email accounts:

• New Workspace accounts start restricted: a brand-new Google Workspace account cannot send 2,000 emails on day one. Google applies progressive sending limits to new accounts - a new account may be limited to 500 or fewer emails per day until it has established a sending history. This is separate from domain warm-up; it is a Google account-level restriction that lifts after 90 days of consistent, complaint-free sending.
• Per-hour sub-limits: Google does not publish specific per-hour limits, but sending bursts (100+ emails in 30 minutes from a single account) can trigger temporary rate limiting even if you are below the daily cap. Distribute sends throughout the day - 20-40 emails per hour is a safe pace for a warmed account sending 200-300 per day.
• Cold email safe volume for Google Workspace: we cap a Google Workspace inbox at 30 cold emails per day, with no more than 2 mailboxes per domain - 60 per day per domain. The 2,000 figure is a hard ceiling, not a recommended operating volume, and it is not remotely the same order of magnitude as the safe volume.

Outlook and Microsoft 365 Sending Limits

Microsoft 365 (formerly Office 365) has higher published sending limits than Google Workspace, but the practical safe volume for cold email is also lower than the published limit. Microsoft's anti-spam filters are aggressive - Outlook inboxes are among the hardest to reliably deliver to in cold email infrastructure.

• Microsoft 365 Business plans: 10,000 recipients per day, 500 recipients per message, 30 messages per minute. The 10,000 per day limit is the hard cap - sending beyond it triggers account suspension for the day.
• Exchange Online limits: same as M365 in cloud-hosted configurations. On-premise Exchange configurations are set by the server administrator and vary widely.
• Practical cold email limit for Outlook/M365 inboxes: this depends entirely on how the mailbox was provisioned. A properly licensed M365 mailbox on a domain you intend to keep behaves like a Google Workspace mailbox: 30 cold emails per day, 2 mailboxes per domain. A bulk-provisioned mailbox in a cheap dedicated tenant carries far less sender trust and must be held to 5 per day. Microsoft's anti-spam filters include Defender for Office 365, which uses machine learning to identify bulk commercial sending patterns. An M365 inbox consistently sending 200+ cold emails per day will see inbox placement decline over time even if it stays below the 10,000 cap.
• Outlook.com (personal) limits: Microsoft's free email product (@outlook.com, @hotmail.com) has a 300-email daily limit for personal accounts. These are not suitable for cold email infrastructure - use Microsoft 365 Business accounts on custom domains instead.

A note on how you connect, not how much you send: separate from these volume limits, Microsoft is retiring Basic authentication for SMTP AUTH. It still works today and behavior is unchanged through December 2026, when it becomes disabled by default for existing tenants (administrators can still re-enable it). Tenants created after that date will not have it by default. If you connect M365 mailboxes to a sequencer with a username and password, plan the move to OAuth or Microsoft Graph. Full timeline in Microsoft 365 SMTP basic auth: what actually changed in 2026.

Zoho, Fastmail, and Other Business Email Limits

Zoho Mail and other business email providers are commonly used as cold email infrastructure alternatives to Google Workspace and M365, primarily because they are cheaper at scale and have less aggressive outbound anti-spam filtering in some configurations.

• Zoho Mail free plan: 500 emails per day. Appropriate for a low-volume test inbox but not for production cold email campaigns.
• Zoho Mail paid plans (Zoho Workplace): 2,000 emails per day on Lite and Professional plans. Zoho's sending limits are similar to Google Workspace, but Zoho inboxes generally have lower brand recognition with recipients, which can affect open rates slightly.
• Fastmail (business plans): no officially published daily sending limit, but Fastmail's terms of service prohibit bulk commercial sending. Fastmail accounts flagged for cold email activity are suspended quickly. Not recommended as cold email infrastructure.
• Amazon WorkMail: 1,000 emails per day per user. Lower limits than Google Workspace but a useful alternative for organizations already in the AWS ecosystem. Amazon SES (SMTP relay) is separate from WorkMail and has its own limit structure.

SMTP Relay and Transactional Email Provider Limits

SMTP relay services (SendGrid, Mailgun, Postmark, Amazon SES, Brevo) are transactional email infrastructure, not cold email infrastructure. They are designed for application-generated email (receipts, notifications, password resets). Using them for cold email campaigns violates their terms of service and results in account suspension - sometimes within hours of the first campaign.

That said, understanding their limits is useful context for deliverability architecture:

• SendGrid: free tier is 100 emails per day. Paid plans start at 40,000 emails per month. Strict anti-spam enforcement - cold email campaigns detected on SendGrid accounts result in account suspension without warning.
• Mailgun: free tier is 5,000 emails for the first 3 months, then 100 per day. Paid plans from 50,000/month. Same anti-spam enforcement as SendGrid.
• Postmark: designed specifically for transactional email with strict terms against bulk commercial sending. Fast delivery to inbox for transactional mail but not suitable for cold email.
• Amazon SES: starts in sandbox mode with a 200-email daily limit. Production access (after sandbox approval) allows up to 50,000 emails per day. Amazon SES is sometimes used for cold email infrastructure by sophisticated users, but it requires careful list hygiene and complaint management - Amazon's abuse handling is automated and aggressive.

The correct infrastructure for cold email is a business email provider (Google Workspace, M365, Zoho) with a custom domain, full DNS authentication, and a domain warm-up period - not a transactional SMTP relay. The SPF, DKIM, and DMARC setup guide covers the authentication configuration that every cold email domain needs before sending begins.

Warm-Up Phase Limits and Safe Ramp Schedules

Domain and inbox warm-up is the process of gradually increasing sending volume from a new domain or inbox to establish a positive sending reputation before running production cold email campaigns. Skipping warm-up results in immediate spam folder placement or sending suspension, regardless of how good the email copy or list quality is.

A safe ramp schedule for a new Google Workspace inbox on a new domain:

• Week 1-2: warm-up pool sends only, no cold prospects. Warm-up tools automate this by sending between a pool of inboxes that automatically reply to each other. The goal is to establish an opening and reply pattern that signals legitimate use before any cold traffic touches the mailbox.
• Week 3: introduce cold sends at roughly a third of target - about 10 per day on a standard provider mailbox, 2 on a bulk-provisioned one - while warm-up pool sends continue underneath. Monitor spam placement rate closely at this stage.
• Week 4: raise to roughly two thirds of target - about 20 per day standard, 3-4 bulk-provisioned - if spam placement is clean and complaints are at zero.
• Week 5+: steady state at target and no higher - 30 per day on a standard provider mailbox, 5 per day on a bulk-provisioned Microsoft 365 mailbox. There is no later stage where these numbers go up. Additional volume comes from more mailboxes and more domains, never from raising a mailbox past its ceiling.

Domain age matters: a brand-new domain (registered in the last 30 days) should not be used for any cold email sends in the first 2-4 weeks, even with a warm-up tool running. Spam filters treat new domains with heightened suspicion. Registering sending domains 4-8 weeks before campaign launch is standard practice in cold email infrastructure setup. The email warmup guide covers the full warm-up process and the tools that automate it.

Inbox Rotation and ACA: Staying Within Limits at Scale

Sending 300 cold emails per day from a single inbox exceeds the safe operating volume even for a warmed Google Workspace account. The solution is inbox rotation: distributing sends across multiple inboxes on multiple sending domains so each individual inbox stays within its safe daily volume while the aggregate campaign volume scales.

The math, on standard provider mailboxes: 30 per inbox per day and 2 mailboxes per domain means 60 per day per domain. Hitting 400 per day therefore takes about 7 sending domains carrying 14 warmed mailboxes. On bulk-provisioned Microsoft 365 tenants the shape inverts - 50 mailboxes at 5 per day is 250 per day, but each domain lives in its own tenant, so 400 per day means 2 tenants. Each domain needs its own SPF, DKIM, and DMARC records, and each mailbox needs its own warm-up period before entering the rotation pool.

ACA's sending infrastructure manages inbox rotation natively:

• Inbox pool management: configure your sending accounts in ACA's inbox rotation pool and set per-inbox daily limits. ACA distributes sends across the pool automatically, respecting each inbox's daily cap without manual monitoring.
• Warmup integration: ACA connects with warmup services to track each inbox's current reputation health and sending history. Inboxes below a health threshold are automatically de-prioritized in the rotation until their reputation recovers.
• Sending schedule distribution: ACA distributes sends throughout the day with natural variation in timing (not a rigid hourly batch schedule), which avoids the burst-send patterns that trigger rate limiting at Gmail and Outlook.
• Domain rotation for reply-to addresses: ACA can route replies back to a single inbox even when sending from multiple domains, keeping conversation management clean while the sending side rotates across the pool.

For the full cold email infrastructure setup covering domain registration, DNS authentication, warm-up, and inbox rotation, the cold email deliverability guide walks through the complete architecture. The inbox rotation guide covers the specific mechanics of building and managing a rotation pool for high-volume cold email campaigns.

FAQ

What is Gmail's daily sending limit for cold email?

Google Workspace (paid, custom domain) allows up to 2,000 emails per day. Gmail personal accounts (@gmail.com) are limited to 500 per day. For cold email purposes, the practical safe limit is 30 emails per day from a single warmed Google Workspace inbox, with no more than 2 mailboxes per domain - far below the hard cap. Sending at the full 2,000-per-day cap from a single inbox every day will trigger spam classification and inbox placement degradation even without hitting the formal suspension threshold.

How many cold emails can I send per day from Outlook 365?

Microsoft 365 Business plans allow up to 10,000 recipients per day and 30 messages per minute. The practical safe cold email limit is 30 per day from a properly licensed M365 mailbox, or 5 per day from a bulk-provisioned mailbox in a dedicated tenant. Microsoft's Defender for Office 365 is aggressive about classifying bulk commercial sending, and M365 sender accounts consistently sending 200+ cold emails per day will see declining inbox placement at Outlook recipient addresses over time. Staying below 100 per day per inbox and running multiple inboxes in rotation is more reliable than pushing a single M365 inbox toward its hard cap.

How long does email warm-up take before I can send cold emails?

4-5 weeks minimum for a new inbox on a new domain. The first 2 weeks should be warm-up pool sends only (automated inbox-to-inbox exchanges that build a sending history). Weeks 3-4 ramp cold sends from roughly a third to two thirds of target. Full production volume - 30 per day on a standard provider mailbox, 5 on a bulk-provisioned one - is safe from week 5 if the inbox has maintained clean spam metrics. New domains less than 4 weeks old should not be used for any cold email sends - register sending domains well in advance of campaign launch.

What happens if I exceed my email provider's sending limit?

The response depends on the provider and how far over the limit you go. Google temporarily suspends outbound sending until the next calendar day and logs the account as having exceeded its limit - repeated violations escalate to longer suspensions. Microsoft 365 applies a similar pattern. More significantly, regularly approaching or hitting your daily cap signals to spam filters that you are running bulk sending from the account, which damages sender reputation and inbox placement even after the suspension lifts. Stay at 50-80% of your provider's limit as a sustained operating maximum.

Do I need a separate domain for cold email sending?

Yes. Sending cold email from your primary business domain puts that domain's reputation at risk. If a cold email campaign generates spam complaints, the sending reputation damage applies to your primary domain, which can affect transactional emails (invoices, contracts, product notifications) sent from that same domain. The standard practice is to register one or more sending domains - variants of your primary domain with different TLDs or a slight name variation - and send all cold email from those domains. Your primary domain stays protected for high-value transactional communication.