Gmail bulk sender status explained: what counts toward the 5,000/day threshold, how subdomains are counted, and why the classification is permanent

Admins keep asking the same three questions about Gmail's bulk sender rules.

Does the 5,000/day threshold count per subdomain? Does it count only mail sent to @gmail.com users, or all Google-hosted mail? And if a domain crosses the line once during a launch, a migration, or a holiday campaign, can it later go back to being treated as a non-bulk sender?

Google's own FAQ answers all three. The useful part is that the answers are much less fuzzy than the folklore.

The short answer

For Gmail's sender-guideline classification:

• Google looks at email sent to personal Gmail accounts in a 24-hour period
• senders that send close to 5,000 messages or more in that window are treated as bulk senders
• messages sent from the same primary domain are counted together, including subdomains
• once a sender meets that bulk-sender criteria at least once, the classification is permanent

Those points come directly from Google's Email sender guidelines and the newer Email sender guidelines FAQ.

What actually counts toward the 5,000/day threshold

Google's wording matters here.

The main sender-guidelines page says the higher requirement tier applies if you send more than 5,000 messages per day to Gmail accounts, and it defines those as personal Gmail accounts ending in @gmail.com or @googlemail.com.

The FAQ then sharpens the definition of a bulk sender further: a bulk sender is any sender that sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period.

That means the threshold is not described as:

• all email your organization sends everywhere
• all messages sent to Google-hosted domains in general
• a monthly average
• a cleanly reset "we stayed below 5,000 yesterday, so now we are small again" status

It is specifically about how much mail reaches personal Gmail recipients over a 24-hour window.

The same FAQ also says the sender guidelines do not apply to mail sent to Google Workspace accounts. That distinction matters more than people expect. Sending to user@gmail.com counts toward this classification. Sending to a company that happens to use Google Workspace for user@example.com does not fall under this personal-Gmail rule.

A practical example

Imagine one day looks like this:

• 2,400 messages to @gmail.com
• 2,200 messages to @googlemail.com
• 1,500 messages to Google Workspace recipients at customer domains

For Gmail's bulk-sender classification, the first two buckets are the important ones. That is already 4,600 messages to personal Gmail accounts, which is exactly the kind of volume Google means by "close to 5,000."

The last 1,500 messages may matter operationally for other reasons, but they are not what Google's FAQ is talking about when it defines bulk sender status for the Gmail sender guidelines.

How subdomains are counted

This is the part that settles most of the debate.

Google's FAQ says: Messages sent from the same primary domain count toward the 5,000 limit. It gives a direct example where solarmora.com sends 2,500 messages and promotions.solarmora.com sends another 2,500 messages. Google says that sender is a bulk sender because all 5,000 messages came from the same primary domain: solarmora.com.

Operationally, that means subdomain sharding does not get you out of the bulk-sender bucket.

If these are all part of the same registered base domain:

• example.com
• news.example.com
• offers.example.com
• bounce.mail.example.com

Google can count that traffic together for bulk-sender classification.

So if a team tries to split streams across subdomains like this:

• 1,800 messages from example.com
• 1,700 messages from news.example.com
• 1,900 messages from alerts.example.com

the safer assumption is not "three separate senders under 5,000." The safer assumption is "one primary domain whose Gmail-facing volume is now well into bulk-sender territory."

That matches the way domain boundaries are usually discussed elsewhere in email authentication too. If the domain-tree side of this still feels slippery, DMARC subdomain policy guide and Public Suffix Domain (PSD) DMARC explained are useful background for thinking about base domains versus subdomains.

What about different registered domains?

Different registered domains are a different story.

For example, example.com and example.net are not subdomains of one another, so Google's specific example about the same primary domain does not automatically combine them.

That said, treating separate domains as a compliance escape hatch is still a bad plan. Gmail's sender rules are about keeping large-scale mail authenticated, aligned, and low-complaint. Splitting traffic across domain names does not remove that operational obligation.

Why the classification is permanent

Google is unusually explicit here.

Its FAQ asks: Does bulk sender status expire? The answer is no. Google says bulk sender status doesn't have an expiration date, and senders that have been classified as bulk senders are permanently classified as such.

That means:

• a one-time campaign spike can be enough to put the domain into the bulk-sender category
• reducing volume later does not remove the classification
• changing sending cadence later does not remove the classification
• "we only crossed it once" is still crossing it

This is the point many teams miss during migrations and warm-up periods.

They assume bulk-sender status behaves like a temporary quota flag. Google's wording says it behaves more like a lasting classification. Once the sender crosses into that category, Gmail expects the sender to keep meeting the bulk-sender requirements from then on.

What permanent bulk-sender status means in practice

Once a domain is in the bulk-sender bucket, the real question stops being "can this be reversed?" and becomes "are all of the bulk-sender requirements already in place everywhere this domain sends mail from?"

For Gmail, that means keeping the baseline bulk-sender controls healthy:

• SPF and DKIM configured for the sending domain
• a DMARC record published for the From: domain, at least with p=none
• DMARC alignment between the visible From: domain and either SPF or DKIM
• valid forward and reverse DNS for sending IPs
• TLS for SMTP delivery
• low spam rates in Postmaster Tools
• one-click unsubscribe for marketing and subscribed mail

If those requirements need a refresher, Gmail, Yahoo, and Microsoft email sender requirements is the broader checklist, and Gmail bulk sender error codes explained covers what happens when Gmail starts rejecting traffic for missing pieces.

The important mindset shift is this: once a domain has ever behaved like a bulk sender to personal Gmail accounts, build and operate it as a bulk sender permanently.

The mistake to avoid

The common bad assumption is:

"We will keep the parent domain under 5,000/day and send the rest from subdomains, so Gmail should still see us as non-bulk."

Google's own example says otherwise.

The second common bad assumption is:

"We crossed the threshold during one busy week, but now volume is low again, so the extra Gmail requirements should no longer apply."

Again, Google's FAQ says otherwise.

If a domain is even near the threshold, the lower-risk approach is simple:

1. Assume all Gmail-facing traffic from that primary domain may be counted together.
2. Assume future spikes will not be treated as special exceptions.
3. Implement the bulk-sender requirements before Gmail has to remind you with SMTP errors.

Bottom line

For Gmail sender-guideline purposes, the threshold is about personal Gmail recipients in a 24-hour window. Subdomains under the same primary domain are not a reliable way to stay outside the bulk-sender category, because Google says those messages count together. And once the domain qualifies as a bulk sender, the classification is permanent.

So the practical answer is not to game the boundary. It is to prepare the domain as if Gmail will treat it as bulk mail infrastructure for the long term, because once the line has been crossed, that is exactly how Google says it will be treated.