Table of Contents
- What are the Google bulk sender requirements?
- What are Yahoo's bulk sender requirements, and do they differ from Google's?
- What happens if you do not meet the requirements?
- How do you set up one-click unsubscribe for cold email?
- Do these requirements apply if you send under 5,000 emails a day?
- The Google and Yahoo compliance checklist
- Key Terms Glossary
- What this looks like on a call
- Related reading
A sales leader usually learns about the Google bulk sender requirements the hard way: reply rates fall off a cliff one week, and nobody on the team has touched the sending setup. Google and Yahoo now enforce a specific, published set of technical requirements on anyone sending meaningful volume to Gmail and Yahoo inboxes, and a sender who misses one of them does not get a warning. Messages start landing in spam, or stop arriving at all.
This is a checklist, not a theory piece. Every threshold below is stated in Google's and Yahoo's own current sender guidelines, not estimated or inferred, so you can check your own setup against it directly.
What are the Google bulk sender requirements?
The Google bulk sender requirements apply to anyone sending more than 5,000 messages a day to personal Gmail and Googlemail addresses, and they cover five things: authentication, a spam rate ceiling, unsubscribe mechanics, valid DNS records, and message formatting. In practice this is the floor for any serious cold email programme, whether or not a single domain crosses the 5,000 threshold on its own, because Google applies the same reputation signals to smaller senders too.
The requirements, taken directly from Google's current sender guidelines:
- SPF and DKIM. Both must be set up and passing for the sending domain.
- DMARC. A published DMARC policy is required, with an enforcement policy of at least "none" accepted, and the domain in the From: header must align with either the SPF domain or the DKIM domain for the message to pass DMARC alignment.
- Spam rate below 0.30%. Measured in Google Postmaster Tools. This is the number that actually determines whether a sender gets throttled.
- One-click unsubscribe. Required on marketing and subscribed messages, plus a clearly visible unsubscribe link in the message body itself.
- Valid forward and reverse DNS (PTR records), TLS for the connection, and RFC 5322-compliant formatting. The unglamorous plumbing that most warm-up tools handle automatically and most manual setups miss.
What are Yahoo's bulk sender requirements, and do they differ from Google's?
Yahoo's bulk sender requirements mirror Google's almost exactly: SPF and DKIM implemented, a published DMARC policy that passes (relaxed alignment is permitted), a spam complaint rate kept below 0.3%, and support for one-click unsubscribe. The one operational difference worth knowing is that Yahoo explicitly recommends the RFC 8058 method for one-click unsubscribe and asks senders to honour unsubscribe requests within two days, a specific window Google does not state as a number.
| Requirement | Yahoo | |
|---|---|---|
| SPF and DKIM | Required | Required |
| DMARC | Required, aligned, enforcement policy of at least "none" | Required, aligned (relaxed alignment allowed), policy of at least "none" |
| Spam complaint rate | Below 0.30%, measured in Postmaster Tools | Below 0.30%, measured on Yahoo's own delivery data |
| One-click unsubscribe | Required on marketing and subscribed messages | Required; RFC 8058 explicitly recommended |
| Unsubscribe honoured within | Not stated as a fixed number | 2 days |
Meeting Yahoo's bar without also meeting Google's is unusual in practice, since the same authentication setup on the same domain satisfies both.
What happens if you do not meet the requirements?
Missing one of these requirements does not produce a clean rejection message; it produces a slow, confusing decline in reply rates that looks like a targeting or copy problem. A DMARC misalignment, an unsubscribe link that is not truly one-click, or a spam rate that has drifted above 0.3% in Postmaster Tools can each cause Gmail to start routing a growing share of messages to spam or to bulk-fold it without notice, weeks before anyone on the sending team notices the pattern. This is exactly the kind of silent infrastructure failure worth ruling out before assuming a list or an offer has stopped working.
The gap between a professionally managed sending setup and a manual one shows up starkly in real numbers. Across recent campaigns on Danish Lead Co.'s own outbound systems, manually configured mailboxes bounced at roughly 23% while professionally warmed, monitored mailboxes on the same platforms bounced in the low single digits. A bounce rate at that level is not a rounding error against the 0.3% spam threshold; it is the kind of signal that gets a domain blocked outright before the spam rate is ever measured.
How do you set up one-click unsubscribe for cold email?
One-click unsubscribe means a recipient's mail client can unsubscribe a sender without loading a page or confirming anything, using a `List-Unsubscribe` header combined with `List-Unsubscribe-Post` (the RFC 8058 method Yahoo names directly). A visible "unsubscribe" link in the body is still required alongside the header; the header satisfies Gmail's and Yahoo's mail-client button, the body link satisfies a recipient reading in a client that does not render it. Most cold email sending platforms built after 2024 add this automatically. Hand-rolled SMTP setups and older sequencing tools frequently do not, which is one of the fastest ways an otherwise well-targeted campaign fails this requirement without anyone realising.
Do these requirements apply if you send under 5,000 emails a day?
Technically the published thresholds only bind a sender once daily volume to Gmail personal accounts crosses 5,000 messages, but the practical answer is yes anyway. Google's spam-rate and authentication signals inform sender reputation continuously, not just once a volume threshold is crossed, so a sender at 1,000 emails a day with a DMARC misalignment and no one-click unsubscribe is building the same weak reputation, just more slowly. Treating the requirements as a floor from day one avoids a rebuild later.
The Google and Yahoo compliance checklist
- Confirm SPF and DKIM pass for every sending domain, not just the primary one.
- Publish a DMARC record and check that the From: domain aligns with either the SPF or DKIM domain.
- Check your spam rate in Google Postmaster Tools and confirm it sits below 0.30%, not just close to it.
- Add List-Unsubscribe and List-Unsubscribe-Post headers, plus a visible unsubscribe link in the body, on every sequence.
- Verify PTR records resolve correctly for each sending IP and that connections use TLS.
- Re-check after every new domain or mailbox is added, since a fresh domain with no authentication configured yet will fail the whole set immediately.
Key Terms Glossary
What this looks like on a call
If your reply rate has dropped and nobody has changed the targeting or the message, infrastructure compliance is one of the first things worth ruling out, not the last. Book a call and we will check your current authentication, spam rate, and unsubscribe setup against the exact thresholds above, tell you plainly which one is failing if any are, and show you what a compliant sending setup looks like before you commit to rebuilding anything.
