Am I a Bulk Sender? The 5,000-a-Day Rule, Explained

The short answer
You are a bulk sender if you send close to 5,000 or more messages to personal Gmail accounts in any 24-hour period. Gmail counts that total across your primary domain and all its subdomains together, not per subdomain. Once you cross it, the classification is permanent. Mail to Google Workspace inboxes does not count.
"Does the 5,000 emails a day rule apply to me?" How Gmail counts the bulk sender threshold across your domain and subdomains, and why it never expires.
On this page
- 01What counts as a bulk sender for Gmail
- 02How the 5,000-a-day threshold is counted
- 03Why it matters: what breaks once you cross the line
- 04Bulk senders vs. all senders: two requirement sets
- 05How to tell if the rule applies to you
- 06Common misconceptions about the bulk sender rule
- 07How this shows up in AI Emaily
If you are asking whether the 5,000-emails-a-day rule applies to you, the short answer is that it depends on who you email and how much, not on which tool you use to send. Google's sender guidelines draw a line at bulk senders — accounts that push large volumes of mail to personal Gmail addresses — and attach a stricter set of requirements to everyone above that line.
This post explains how the threshold is actually counted, why the count is measured across a whole domain rather than a single address, and the detail most guides skip: once Gmail classifies you as a bulk sender, that status does not expire. All of it is drawn from Google's own sender guidelines, dated to August 2026, with the exact pages linked at the end.
What counts as a bulk sender for Gmail#
Google defines a bulk sender as any sender that sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period. Two words there carry weight: personal and close. The rule counts messages delivered to consumer @gmail.com and @googlemail.com addresses, and it treats anything near 5,000 as enough to qualify — not only a clean 5,001.
The requirements do not apply to mail sent to Google Workspace accounts, the paid business mailboxes on custom domains. Google states plainly that its sender guidelines and enforcement apply only when you send to personal Gmail accounts. A company emailing its own staff on a Workspace domain is not counted, even at high volume.
Yahoo runs a parallel program with the same shape: SPF and DKIM, a DMARC policy of at least p=none, one-click unsubscribe on marketing mail, and a spam rate below 0.3%. Yahoo's own sender best-practices page frames these as requirements without restating Gmail's 5,000-a-day counting mechanics, so the precise threshold detail below is Gmail's documented rule specifically.
How the 5,000-a-day threshold is counted#
The count is not per email address and not per subdomain. Gmail aggregates every message sent from the same primary domain, then rolls the subdomains beneath it into that same total. If marketing goes out from news.example.com and receipts from billing.example.com, both streams count toward example.com. Split a campaign across ten subdomains and you have not split the total — you have one total measured across all of them.
The window is any rolling 24-hour period, so a single heavy send day can trip the threshold even when your monthly average is modest. And the classification is sticky. Google states that bulk sender status has no expiration date: once you are classified, you stay classified, and changing your sending habits afterwards does not reverse it.
Slowing down does not undo it
Why it matters: what breaks once you cross the line#
Before late 2025, non-compliant bulk mail mostly landed in spam. That changed. Google's FAQ states that starting November 2025 it is ramping up enforcement, and that messages failing the requirements will experience disruptions including temporary and permanent rejections — not just spam-foldering. A rejection means the message never arrives at all.
The requirement that trips most senders is the spam rate. Google asks bulk senders to keep the user-reported spam rate below 0.1% and to prevent it from ever reaching 0.3%. Both are measured in Postmaster Tools, and 0.3% is a hard ceiling, not a soft target: cross it and delivery degrades.
Recovery is slow by design. Google says a bulk sender becomes eligible for mitigation only once its spam rate stays below 0.3% for 7 consecutive days. There is no fast appeal — you earn your way back over a clean week. On top of the spam rate, bulk senders must authenticate with SPF and DKIM, publish a DMARC policy of at least p=none with From-header alignment, and support one-click unsubscribe on marketing and subscribed messages.
The error you may see
Bulk senders vs. all senders: two requirement sets#
The bulk sender rules sit on top of a baseline that applies to everyone. Google publishes two tiers: requirements for all senders, which even a one-person mailbox must meet, and additional requirements that switch on at the bulk threshold. Knowing which tier you are in tells you exactly what you have to do.
| Requirement | All senders (any volume) | Bulk senders (~5,000+/day to personal Gmail) |
|---|---|---|
| SPF or DKIM | At least one of the two | Both SPF and DKIM required |
| DMARC policy | Recommended | Required — at least p=none, with From alignment |
| Valid reverse DNS (PTR) on sending IP | Required | Required |
| Spam rate in Postmaster Tools | Keep it low | Below 0.1%, must never reach 0.3% |
| One-click unsubscribe (RFC 8058) | Not required | Required on marketing and subscribed mail |
| Status permanence | Not applicable | Permanent once classified |
How to tell if the rule applies to you#
Put your own sending through three questions and the answer falls out. First, are the recipients personal Gmail addresses rather than Workspace mailboxes? Second, across your primary domain and every subdomain under it, does the combined volume to those addresses approach 5,000 in any 24 hours? Third, is this a repeatable pattern or a genuine one-off?
If the first two are yes, you are a bulk sender under Google's definition, and the permanence rule means it stays that way. If you are nowhere near 5,000 a day to personal Gmail — which describes almost anyone sending individual, human email — the bulk requirements do not apply to you, though the all-senders baseline still does.

Common misconceptions about the bulk sender rule#
Most of the confusion comes from articles that describe the rule as looser or more forgiving than Google's own wording. These are the ones that cause trouble.
- "It is measured per subdomain." No — subdomains aggregate into the primary domain's total, so spreading volume across them does not lower the count.
- "It resets if I slow down." No — Google states the classification has no expiration date and is permanent; dropping below 5,000 a day later does not remove it.
- "It applies to all my Gmail-hosted recipients." No — it applies to personal @gmail.com accounts only. Mail to Google Workspace business inboxes is excluded, even at volume.
- "Only marketing email counts toward the 5,000." The volume count is not limited to marketing; transactional mail to personal Gmail counts too. It is the one-click unsubscribe requirement that applies specifically to marketing and subscribed messages.
- "I need exactly 5,000 to qualify." Google's wording is close to 5,000 or more, so plan for the requirements as you approach the threshold, not only after you pass a round number.
How this shows up in AI Emaily#
If you landed here because you use an AI email client and wondered whether it makes you a bulk sender, it does not. The threshold counts near-identical mail blasted to thousands of personal Gmail inboxes from one domain in a day — marketing and transactional territory that belongs on an email service platform. A person answering their inbox, even a busy one, sends individual replies, and those never approach the count.
AI Emaily is that kind of client, not a sending platform. It drafts and sends one-to-one replies through your own connected Gmail, Outlook or IMAP account, using your provider's already-authenticated servers — so it neither makes you a bulk sender nor helps you become a compliant one. It is not an email service provider, a deliverability tester or a DMARC monitor; if you genuinely need to send 5,000 a day, use an ESP built for that job. Where AI Emaily does touch these rules is on the receiving side: it reads the SPF, DKIM and DMARC results the sender requirements produce, so its spam protection can flag a message that failed authentication and looks like phishing. We build AI Emaily, and it runs on a 7-day free trial on the Pro and Autopilot plans.
Frequently asked
See it in AI Emaily
Keep reading
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.