Google and Yahoo bulk sender rules, explained for cold email teams
What counts as a bulk sender, the three requirements that are enforced rather than advised, how the 5,000-a-day threshold is actually measured, and what to do if you are anywhere near it.
Since February 2024, Google and Yahoo have treated some senders differently from everyone else. If you cross their bulk-sender threshold, three things stop being best practice and start being requirements: authenticated and aligned mail, a one-click way out, and a complaint rate under 0.3%. Cold email teams trip over this constantly, because the tools they use count something other than what Google counts.
Who is a bulk sender
Google's definition is a sender of close to 5,000 or more messages a day to personal Gmail accounts. Two details matter:
- It is per domain, not per mailbox. Google aggregates across the primary domain, and subdomains count toward it. Twenty mailboxes on one domain sending 250 each is a bulk sender. Most sequencers show you per-mailbox limits, which is why so many teams cross the line without noticing. More on the arithmetic here.
- Once you cross, you stay classified. Google says the designation is not reversed if your volume later drops. Plan for the requirements before you approach the threshold, not after.
Yahoo's guidance is similar in substance without publishing a single hard number. In practice, meet Google's bar and you meet Yahoo's.
The three requirements
1. Authentication — and alignment
SPF and DKIM must both pass, and DMARC must be published with at least p=none. The word that catches people is alignment: the domain in the visible From address must match the domain that passed SPF or the domain in the DKIM signature. Sending “from” you@yourcompany.com through a tool that signs with its own domain passes DKIM but fails alignment. Fix it by having your mailbox provider or sending tool sign with your domain's key.
2. One-click unsubscribe
Marketing and promotional mail must carry the List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058) so Gmail can show an unsubscribe control in the interface, and you must honour the request within two days. Cold email is promotional mail for this purpose. A text line saying “reply STOP” does not satisfy the requirement.
3. Spam complaint rate under 0.3%
Measured in Google Postmaster Tools as the share of delivered mail that recipients mark as spam. Google's stated ceiling is 0.3%; its stated target is under 0.1%. Complaints are driven by relevance and frequency, not copy — the fix is a tighter list and less contact pressure, not a different subject line.
What actually happens when you fail
Not a bounce, usually. Gmail starts placing your mail in spam, then rate-limits it with temporary errors (421-4.7.28 and similar), then rejects it outright (550-5.7.26 for unauthenticated mail). By the time you see the rejection, the reputation damage has been accumulating for days. That is why the checks belong before the send, not in the bounce log.
A practical compliance plan
- Count per domain. Add up every mailbox on the domain and its subdomains. If the total is above 2,000 a day, treat yourself as a bulk sender now.
- Publish and align. SPF listing every sender, DKIM signed with your own key, DMARC with a reporting address. Check alignment on a real message, not just the DNS records.
- Add the headers. Make sure your sending tool adds RFC 8058 headers to every cold email and processes the unsubscribe automatically and globally.
- Watch Postmaster Tools. Verify the domain, then look at the spam rate and domain reputation weekly. Elevated complaint rate is a stop signal.
- Limit contact pressure. One sequence per person at a time; a weekly ceiling per company; suppression shared across the workspace.
- Ramp new domains. A new domain should not be near 5,000 a day for months. Start low and let bounces and complaints decide when the cap rises.
Why a guardrail, not a checklist
Every item above is measurable, which means it can be enforced. Quotarider's Sequence Guardrail checks authentication, unsubscribe headers, complaint and bounce rates, contact pressure and per-domain volume before each send, and holds the sequence when one of them fails. The daily cap is the lower of what you set and what the guardrail allows, so an “unlimited” setting cannot walk you over the line. Whatever tool you use, the principle is the same: the rules are only useful if something enforces them before the message leaves.
Quotarider keeps the touch, the reply, the deal and the paid invoice in one database, behind a deliverability guardrail. Free plan, no card.