Bulk Sender
A bulk sender is, by Gmail and Yahoo’s definition, anyone who sends 5,000 or more messages a day to their users. The label matters because, since February 2024, crossing that threshold triggers a set of mandatory requirements: authenticate with SPF and DKIM, publish DMARC, offer one-click unsubscribe, and keep your spam-complaint rate under 0.3%.
- Defined by Gmail and Yahoo as sending 5,000 or more messages a day to their users
- The threshold is counted per sending domain, across the whole day, to each provider
- Triggers mandatory SPF, DKIM, and DMARC plus one-click unsubscribe
- You must keep your spam-complaint rate below 0.3% and ideally near 0.1%
What counts as a bulk sender
The term used to be loose, but Gmail and Yahoo gave it a hard edge in their joint 2024 sender rules: a bulk sender is any domain that sends 5,000 or more messages in a single day to that provider’s accounts. The count is per provider and per day, measured against the sending domain, so 5,000 to Gmail and 5,000 to Yahoo each trigger that provider’s rules independently.
Two details trip people up. First, once you cross 5,000 in a day you are treated as a bulk sender from then on, even on lighter days. Second, the count includes all the mail under your domain, so marketing, newsletters, and transactional notices add together. A business that thinks of itself as low-volume can cross the line on a single send to a large list.
What bulk senders must do
Since February 2024, Google and Yahoo require every bulk sender to meet the same baseline. Microsoft applied a comparable set of rules to high-volume senders into Outlook and Hotmail in 2025. The core requirements are:
- Authenticate fully. Publish SPF and DKIM, and a DMARC record of at least
p=none. The visibleFrom:domain must align with the SPF or DKIM domain. - Offer one-click unsubscribe. Marketing and subscribed mail must carry a List-Unsubscribe header supporting one-click unsubscribe, and you must honour requests within two days.
- Stay under the spam-rate cap. Keep your user-reported spam-complaint rate below 0.3% in Postmaster Tools, and never let it reach 0.3%.
- Use valid reverse DNS and TLS. Each sending IP needs a matching PTR record (forward-confirmed reverse DNS), and mail must be transmitted over a TLS connection.
The 0.3% spam-rate line
The single number a bulk sender lives or dies by is the spam-complaint rate: the share of delivered mail that recipients mark as spam. Google asks bulk senders to keep this below 0.3% and warns against ever reaching 0.3% or higher; the practical target most deliverability teams aim for is around 0.1%, because reputation damage starts well before the hard ceiling.
You read this number in Google Postmaster Tools for Gmail and through a feedback loop for other providers. Because the rate is a percentage of delivered mail, a small spike in complaints or a sudden drop in volume can push it over the line, which is why bulk senders watch it daily rather than monthly.
How the rules are enforced
Enforcement has tightened in stages rather than all at once. After the February 2024 start date, non-compliant mail first saw temporary 4xx rejections; from late 2025 Gmail escalated to permanent rejection of traffic that fails the baseline. In practice, a bulk sender that ignores the rules sees mail bounce or land in spam, not a formal notice.
The reliable way to confirm you are compliant is to test the building blocks directly. Verify your records with the SPF, DKIM, and DMARC checkers, confirm your reverse DNS with the reverse DNS checker, and follow the deliverability guide to keep complaint rates and list quality in line.
Are you a bulk sender, and what then?
From: domainBulk-sender requirements: Gmail and Yahoo
| Requirement | |
|---|---|
| Threshold | 5,000+ messages per day to the provider |
| SPF + DKIM | Both required, aligned to From: |
| DMARC | Required at minimum p=none |
| One-click unsubscribe | Required for marketing mail, honoured in 2 days |
| Spam-complaint rate | Below 0.3%, never reaching 0.3% |
| Reverse DNS + TLS | Valid PTR record and TLS transmission |
By the numbers
Common mistakes
p=none and stoppingquarantine and reject.Frequently asked questions
p=none, with the visible From domain aligned to SPF or DKIM. Provide a one-click unsubscribe via the List-Unsubscribe header and honour it within two days. Keep your user-reported spam-complaint rate below 0.3%. Use a valid reverse-DNS (PTR) record on every sending IP and transmit over TLS.