How to meet the Gmail and Yahoo bulk sender requirements

To meet the Gmail and Yahoo bulk sender requirements, authenticate your sending domain with SPF and DKIM, publish a DMARC record (p=none is enough), make sure the From domain aligns with SPF or DKIM, send over TLS from IPs with valid reverse DNS, add one-click unsubscribe headers plus a visible unsubscribe link, honour opt-outs within two days, and keep spam complaints below 0.3%. Both providers have enforced these since February 2024, and Gmail tightened enforcement in November 2025.
Below: who counts as a bulk sender, each rule with how to check it, what cold outbound teams in particular get wrong, and what happens when you fail. The Yahoo rules come from Yahoo Sender Hub; the Gmail rules from Google's Email sender guidelines in Gmail Help, both read on 24 October 2026. We make Nagent, whose outbound research lead is NORA; how NORA's emails handle these rules is near the end.
Who counts as a bulk sender?
Gmail: a sender that sends close to 5,000 or more messages to personal Gmail accounts in 24 hours. Google's announcement set the 5,000-a-day line (Google, 3 October 2023). Google's FAQ adds two points that catch teams out: messages from subdomains count toward the primary domain's total, and a sender that crosses the line once is treated as a bulk sender permanently.
Yahoo: sets rules for all senders and stricter ones for bulk senders, and enforcement began in February 2024 with a gradual rollout.
Practical advice: build to the bulk standard even if you send far less. The extra work is a few DNS records and two headers, and it removes the question.
What do Gmail and Yahoo require from every sender?
Both providers' baseline, which applies at any volume:
SPF or DKIM on the sending domain. Google requires a DKIM key of at least 1024 bits for personal Gmail accounts and recommends 2048.
Valid forward and reverse DNS (a PTR record) for each sending IP.
TLS for the connection (Gmail).
Messages formatted to RFC 5322, and for Yahoo, RFC 5321 too.
Spam rate below 0.3%.
No impersonating Gmail From headers (Gmail).
If you send through a service such as Google Workspace, Microsoft 365 or an email platform, items 2 and 3 are usually handled for you. Items 1 and 5 never are.
What extra do bulk senders need?
Both SPF and DKIM, not one or the other.
A DMARC record for the sending domain. Policy p=none is accepted. Yahoo says DMARC "must pass" and strongly recommends a rua tag so you receive aggregate reports.
Alignment. The domain in the From header must match the SPF domain or the DKIM domain. Relaxed alignment is acceptable to Yahoo.
One-click unsubscribe on marketing and subscribed messages, using the List-Unsubscribe and List-Unsubscribe-Post headers defined in RFC 8058, plus a clearly visible unsubscribe link in the body. Gmail requires the header to contain an HTTPS URL; a mailto link alone does not satisfy it.
Honour unsubscribes within two days. Google's announcement and Yahoo's page both say so.
Spam rate below 0.3%, measured on mail delivered to the inbox. Google recommends staying below 0.1%.
Where do the Gmail and Yahoo rules differ?
The two lists overlap almost completely, but a few details differ:
Unsubscribe header. Gmail requires an HTTPS URL in the List-Unsubscribe header. Yahoo highly recommends the RFC 8058 POST method and also accepts the mailto method.
Bulk threshold. Google names a number, close to 5,000 a day to personal Gmail accounts. Yahoo's best-practices page gives no number, so assume the bulk rules apply.
Spam rate. Both set 0.3%. Yahoo says it calculates the rate on mail delivered to the inbox; Google reports it in Postmaster Tools and recommends staying below 0.1%.
DMARC reports. Yahoo strongly recommends a rua tag so you receive aggregate reports. Gmail's requirement list asks only for a DMARC record.
Build to the stricter version of each and one setup satisfies both.
How do you set up and check each requirement, step by step?
List every system that sends as your domain. Your mailbox provider, marketing email, CRM, billing, support desk, outbound tool. Each needs to be in SPF or sign with DKIM.
Publish SPF. One TXT record at the domain root listing the senders. Keep it under the 10 DNS lookups RFC 7208 allows. Google's guide: set up SPF.
Turn on DKIM in each sending service and publish the keys it gives you. Google's guide: set up DKIM.
Publish DMARC at
_dmarc.yourdomainwithp=noneand aruaaddress. Google's guide: set up DMARC.Send a test to a Gmail account and open the message's original source. Look for SPF, DKIM and DMARC all showing pass, and the DKIM domain matching your From domain.
Add one-click unsubscribe in your sending platform. Check the raw headers for both List-Unsubscribe (with an HTTPS URL) and
List-Unsubscribe-Post: List-Unsubscribe=One-Click.Wire opt-outs to suppression. An unsubscribe from any email must reach every system that can send to that person within two days. Test with a seed address.
Register for Google Postmaster Tools and watch the spam rate and compliance status (Postmaster Tools API).
Read DMARC reports for a few weeks, then move toward quarantine once every legitimate sender passes. Apollo's guide describes the same inventory, monitor, enforce order (Apollo).
Free checkers exist if you do not want to read raw DNS; 11x, for one, publishes a DMARC checker.
What do cold outbound teams get wrong?
Sending cold email from the main domain. Complaints from a cold campaign land on the domain your customers and invoices use. Use a separate sending domain, remembering that Gmail counts subdomains toward the parent.
Leaving out unsubscribe because "it is one-to-one sales email". Google's FAQ says recipients, not Google, decide what kind of message they received. A cold email without an easy opt-out invites the spam button, which is the complaint you are trying to avoid.
Opt-outs living in a rep's inbox. "Please take me off your list" by reply is an opt-out. It has to reach suppression.
Ignoring complaint rate because volume is low. At 1,000 sends, three complaints is already 0.3%.
Forgetting other providers. Microsoft began enforcing similar authentication rules for high-volume senders to Outlook.com addresses on 5 May 2025, as Unify notes (Unify).
What happens if you do not meet the requirements?
Gmail rate-limits or rejects non-compliant mail, and the SMTP code tells you which rule failed (Google SMTP error reference):
4.7.27 / 5.7.27: SPF did not pass.
4.7.30 / 5.7.30: DKIM did not pass.
4.7.32: From header not aligned with SPF or DKIM.
4.7.40 / 5.7.40: no DMARC record.
5.7.26: unauthenticated sender, or rejected by the domain's DMARC policy.
4.7.28 / 5.7.28: unusual rate of unsolicited email.
Google says that from November 2025 it ramped up enforcement, with temporary and permanent rejections for non-compliant traffic. Senders above 0.3% spam rate lose eligibility for mitigation until the rate stays below 0.3% for seven consecutive days. Yahoo describes its enforcement as gradual and does not publish codes on its best-practices page.
How do you stay compliant after launch?
Weekly: spam rate in Postmaster Tools, bounces, unsubscribes processed, any 4.7.x or 5.7.x codes.
Monthly: DMARC aggregate reports for unknown senders; SPF lookup count after any new tool is added.
On every new tool: add it to SPF or DKIM before it sends a single email.
On every list: verify addresses and remove role accounts and people who opted out elsewhere.
Where Nagent fits
We make Nagent. "Nagent is multiplayer AI for growth: people and AI agents in one shared context, delivering the number." NORA, the AI Outbound Research Lead on SERA's Sales team, sends prospect email with several of these rules built in:
Authentication. Outbound email goes through your own sending account on a domain you verify, and the sending setup requires both the SPF and DKIM records before sending is allowed.
One-click unsubscribe. Every prospect email carries a visible unsubscribe link and the RFC 8058 header pair. The link is signed for one recipient and never expires. If it cannot be made, the send is refused.
Opt-outs honoured at once. An unsubscribe click, a reply asking to stop, a spam complaint or a hard bounce writes the address to the workspace suppression list, and every send is checked against it at the moment it leaves.
A person on the send. On a new workspace every send waits for a person.
What it does not do: Nagent does not publish your DMARC record, manage reverse DNS or report your Postmaster Tools spam rate. Those stay with you. Work is metered in credits; see pricing.
Frequently Asked Questions
Do the Gmail rules apply if I send fewer than 5,000 emails a day?
The all-sender rules do: SPF or DKIM, reverse DNS, TLS, proper formatting and a spam rate below 0.3%. The bulk rules apply from close to 5,000 a day to personal Gmail accounts, but meeting them anyway costs little.
Does cold B2B email need one-click unsubscribe?
Google requires it for marketing and promotional messages and leaves the judgement to recipients. Include it on cold email: an easy opt-out is cheaper than a spam complaint.
What spam complaint rate is too high for Gmail?
Google asks senders to stay below 0.1% and never reach 0.3%. Yahoo's limit is also 0.3%.
Is DMARC p=none enough?
Yes, for the requirement. Use the reports to find every sender, then move toward quarantine or reject once legitimate mail passes.
See how NORA adds one-click unsubscribe and suppression to every send: book a demo.