Gmail and Outlook sending limits, and what happens at the ceiling

Every provider caps sending, but the cap that stops you is usually not the daily one. Gmail and Microsoft both enforce several limits at once — per day, per minute, per message, per tenant — and layer reputation-based throttling on top. Designing your sending around the published daily figure and ignoring the rest is why campaigns stall at 11am.

Find the limit that applies to you

The daily figures differ by provider, by edition, and by how you send. A Gmail consumer account, a Google Workspace mailbox sending through the Gmail interface, the same mailbox sending via API, and the Workspace SMTP relay are four different limits — and trial or newly created accounts are capped lower than established ones. On the Microsoft side, consumer Outlook.com and a Microsoft 365 Exchange Online mailbox are likewise separate, with tenant-level throttles in addition to the per-mailbox cap.

So the first step is not a number from an article. Look up the limit for your exact edition and sending method in the provider's own documentation, note it, and then build to sit comfortably under it rather than probing for the edge. Probing for the edge is how you discover the reputation-based limits, which are lower and invisible.

The limits that bite before the daily cap

Every one of these is a 4xx — temporary. The correct response is exponential backoff and a lower rate, keeping the recipients. Treating them as bounces and suppressing the addresses is the expensive mistake, and it is common because some sending tools classify any failure as a bounce.

Why the reputation limit matters more than the quota

A new mailbox with no history will be throttled well below its nominal quota, because providers accept volume in proportion to how much they trust you. That is why "my limit is 2,000 but I get deferred at 200" is not a contradiction. The published cap is the maximum; your reputation sets the effective ceiling.

Which means the useful lever is not a higher plan. It is:

1. A gradual ramp — grow by a modest proportion every few days, not by doubling.
2. Intra-day spread — a batch at the top of the hour is the single most reliable way to trip a per-minute limit.
3. A steady floor — reputation decays with silence, so a mailbox that pauses for a fortnight has to re-earn its rate.
4. More mailboxes, not harder mailboxes. Ten mailboxes at 30 a day is a different risk profile from one at 300, and it keeps each sender well inside its effective ceiling.

Per-provider behaviour at the ceiling

Google tends to return explicit rate-limit responses and recover quickly once you slow down. Watch your spam rate in Postmaster Tools v2 alongside the limits: Google's bulk-sender threshold is 0.30% and the sane target is under 0.10%. v2 also reports authentication, delivery errors and compliance status, plus a Deliverability analysis report added June 2026 — and no reputation grade, since the domain and IP reputation dashboards retired with v1, senders having been redirected from 30 September 2025 and v1 removed by the end of 2025.

Microsoft throttles more and explains less. Deferrals arrive as 451 4.7.500 or the 4.7.6xx family; tenant-level excess returns 550 5.7.705. Your only visibility is SNDS, for per-IP volume, complaint rate, trap hits and a colour grade on IPs you own, plus JMRP for junk reports — and Microsoft publishes no checkable blocklist.

Yahoo and AOL share one filtering stack and tell you plainly: 421 4.7.0 with a bracketed code naming volume or complaints.

What not to do

• Do not treat a `4xx` as a bounce. You will delete valid recipients and learn nothing.
• Do not plan a campaign at your published daily cap. The effective ceiling is lower and reputation-dependent.
• Do not send the whole batch at 09:00.
• Do not add mailboxes and send full volume from each on day one. New mailboxes need their own ramp.
• Do not use BCC to work around a recipients-per-message limit. It counts, and large BCC lists are a spam signal in their own right.
• Do not quote a limit from a blog post as fact for your own account. Editions, age and sending method all change it.

How MailPilot helps

MailPilot warms mailboxes over OAuth for Gmail and Outlook and over SMTP/IMAP for SendGrid, Amazon SES, Mailgun, Postmark and custom hosts, raising each mailbox's effective ceiling with a compounding ramp and spreading sends through the day so per-minute limits are not tripped. Every plan includes unlimited mailboxes, which is the practical answer to a per-mailbox cap, and placement is measured per provider with a seed-inbox network alongside daily reputation tracking.