Gmail and Yahoo Bulk Sender Requirements Explained
Gmail bulk sender requirements and Yahoo sender rules in one checklist: SPF, DKIM, DMARC, one-click unsubscribe the 0.3% spam threshold and how to meet each.
Gmail bulk sender requirements and Yahoo sender rules in one checklist: SPF, DKIM, DMARC, one-click unsubscribe the 0.3% spam threshold and how to meet each.
| Rule | Gmail (5,000+ messages/day) | Yahoo (bulk senders) | All senders |
|---|---|---|---|
| SPF | ✅ Required | ✅ Required | SPF or DKIM |
| DKIM | ✅ Required (1024-bit minimum, 2048 recommended) | ✅ Required | SPF or DKIM |
| DMARC | ✅ Required, p=none accepted | ✅ Required, p=none accepted | ⚠️ Recommended |
| From domain aligned | ✅ With SPF or DKIM | ✅ Relaxed alignment accepted | — |
| One-click unsubscribe | ✅ For marketing messages | ✅ Honoured within 2 days | ⚠️ Recommended |
| Spam complaint rate | Below 0.30%, aim for under 0.10% | Below 0.3% | Below 0.3% |
| Valid forward and reverse DNS | ✅ | ✅ | ✅ |
| TLS and RFC 5322 formatting | ✅ | ✅ (RFC 5321 and 5322) | ✅ |
A bulk sender is any email sender that sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period.Two consequences follow. Google counts messages from the same primary domain together, so spreading traffic across subdomains does not keep you under the line. And, per Google's own FAQ, the status does not expire: "Email senders that have been classified as bulk senders are permanently classified as such." One big launch day is enough to stay a bulk sender forever. Yahoo defines no threshold and simply applies its bulk rules to senders of significant volume. Microsoft joined in May 2025: Outlook.com, Hotmail.com and Live.com now expect SPF, DKIM and DMARC from domains sending more than 5,000 emails a day, and route non-compliant mail to Junk before rejecting it. The practical answer: treat every marketing list as bulk. The rules cost a few DNS records and a header, and they protect you the day a campaign goes further than planned.
p=none, which observes without rejecting anything.Alignment is the part people miss: the domain in your visible From address must match the domain that passed SPF or DKIM. A newsletter signed by your email provider's domain but sent "from" yours passes DKIM and still fails DMARC.<selector1>._domainkey.mail.example.com. CNAME <value shown in your settings>
<selector2>._domainkey.mail.example.com. CNAME <value shown in your settings>
<selector3>._domainkey.mail.example.com. CNAME <value shown in your settings>
_agentmail-challenge.mail.example.com. TXT "<ownership token>"
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"{{unsubscribeUrl}} merge tag, and rendering refuses one that does not. The one-click header is handled for you: AgentsMail answers the List-Unsubscribe-Post request when a recipient uses Gmail's or Yahoo's own button, and the contact stops receiving that list at once.
p=none. Start there, read the aggregate reports for a couple of weeks, then tighten to quarantine and reject once no legitimate sender fails.