Google and Yahoo bulk-sender requirements: SPF, DKIM, and DMARC
Gmail's 2024 bulk-sender rules apply to 5,000+ messages a day to Gmail, and Yahoo published matching requirements. Here is SPF, DKIM, DMARC, alignment, and unsubscribe in practice.
You searched for
“google yahoo bulk sender spf dkim requirements”
Last verified: Oct 21, 2026Published: Oct 21, 2026
You searched this because Gmail, Yahoo, or an ESP dashboard started talking about “bulk sender requirements,” or because mail to @gmail.com started bouncing. Short version: Gmail’s 2024 bulk-sender rules apply to senders of 5,000 or more messages a day to personal Gmail accounts, and Yahoo published matching requirements. The authentication bar is SPF, DKIM, a published DMARC record (at least p=none), and alignment of SPF or DKIM with the From domain. Marketing and subscribed mail also needs one-click unsubscribe (RFC 8058).
Those numbers and the exact wording live on Google’s Email sender guidelines and Yahoo’s sender docs. They have already been updated since 2024. Use this page to understand what the records have to do. Then re-check the providers before you treat 5,000 as a permanent law.
For how the three protocols split the work, see SPF vs DKIM vs DMARC. For the pass-but-fail case, see DMARC alignment explained.
Who these rules apply to
Gmail draws a bulk line at about 5,000 messages in a day to personal Gmail accounts (@gmail.com / @googlemail.com), not to Google Workspace inboxes. Google has also said that once you are classified as a bulk sender, the bulk rules keep applying even if a later day is quieter. Confirm that in the current FAQ; do not plan a “stay under 4,999 forever” exemption.
Yahoo’s public requirements cover the same authentication and unsubscribe ideas for bulk and commercial mail. Yahoo has not always published Gmail’s 5,000-a-day number. If you send real volume to Yahoo Mail, plan on the same SPF, DKIM, DMARC, alignment, and one-click unsubscribe work, then read Yahoo’s current page for how they describe volume.
Below that Gmail bulk line, Gmail still expects SPF or DKIM, valid forward and reverse DNS on sending IPs, TLS, and a low spam rate in Postmaster Tools. Crossing 5,000 is when both SPF and DKIM, plus a DMARC record and From alignment, become the stated bulk bar.
What has to be true on the message
| Requirement | What “done” looks like | Common miss |
|---|---|---|
| SPF | A single SPF TXT on the envelope domain lists every system that sends with that envelope | New ESP never added; extra v=spf1 records; forwarding IPs stuffed into the record |
| DKIM | Each sender signs with a key you published, d= on your From domain (or a parent relaxed alignment accepts) |
ESP signs as itself; selector never published; proxied DKIM CNAME fails to resolve |
| DMARC published | _dmarc.yourdomain TXT exists, policy at least p=none |
No record at all, or the record is on a subdomain Gmail is not looking up |
| Alignment | SPF or DKIM (ideally both) authenticates a domain that matches the visible From domain | SPF passes for sendgrid.net while From is [email protected] |
| One-click unsubscribe (RFC 8058) | Marketing and subscribed mail includes List-Unsubscribe (HTTPS) and List-Unsubscribe-Post: List-Unsubscribe=One-Click |
Preference-center link in the footer only; missing List-Unsubscribe-Post; applied to the wrong stream |
A starter DMARC monitor record still looks like:
v=DMARC1; p=none; rua=mailto:[email protected]
p=none is enough for the “you published DMARC” bulk-sender check. It is not enough to fix unaligned mail, and it is not a Gmail free pass. Gmail’s own inbound policy can still bounce unauthenticated bulk mail.
Alignment is the part most dashboards skip
Publishing SPF and DKIM is not the same as passing DMARC alignment. Gmail’s bulk-sender text says the domain in the From header must align with the SPF domain or the DKIM d= domain. That is ordinary DMARC identifier alignment:
- SPF alignment: the envelope-from / Return-Path domain matches the From domain (exact under strict, same organizational domain under relaxed, which is the default).
- DKIM alignment: the signature’s
d=domain matches the From domain the same way.
DMARC needs at least one aligned pass. Two unaligned passes still fail DMARC. Third-party senders often pass SPF and DKIM for their domain while putting your address in From. Their dashboard will say authentication is configured. Gmail will say it is not aligned with you.
That failure is also how Gmail 550 5.7.26 shows up: “this message does not pass authentication checks (SPF and DKIM both do not pass).” The bounce can fire under p=none. It is Gmail’s check, not your DMARC policy going to reject.
Fix it in the ESP: custom DKIM with d= on your domain, and a custom return-path if you want SPF alignment too. DKIM is usually the more durable half, because forwarding breaks SPF and an aligned signature can still satisfy DMARC.
One-click unsubscribe, and what is not marketing
For marketing and subscribed messages, Gmail’s bulk rules require one-click unsubscribe. Yahoo’s bulk rules say the same kind of thing. The on-wire form is RFC 8058:
List-Unsubscribe: <https://yourdomain.example/unsubscribe/u>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Gmail shows an unsubscribe control that POSTs to that URL. Honor it (Google has said within two days; check the current guideline). A footer link that opens a login wall does not replace the headers.
Transactional mail is a different class. Invoices, password resets, MFA codes, shipping notices, and “you just changed your email address” messages are not mailing-list traffic. They should not be mixed with a campaign. Google’s sender guidelines tell you not to put promotions inside receipts. Putting List-Unsubscribe on a password reset does not make a newsletter compliant, and skipping the headers on the newsletter because “we send transactional mail too” does not work either.
If one ESP sends both classes, split From addresses (and ideally sending identity) so Gmail can tell receipts@ from deals@. Authentication still has to align for both.
What not to do in SPF
- Do not SPF-include forwarders. Mailman, consumer forwarding, and list expanders are not your outbound senders. Their IPs do not belong in your record. Forwarding typically fails SPF; aligned DKIM is how that mail still passes DMARC.
- Do not add every vendor “just in case.” Each
include:costs DNS lookups. SPF has a hard 10-lookup cap. See SPF permerror: too many DNS lookups. - Do not publish two
v=spf1records. Merge senders into one TXT. - Do not jump to
p=rejectto satisfy a bulk-sender checklist. The checklist acceptsp=none. Enforcement without aligned legitimate mail is how invoices disappear.
How to check your domain today
- List every system that puts your domain in From: primary mail, ESP, CRM, billing, helpdesk, forms, calendars.
- Run the free DMARC checker on the From domain you actually send as.
- Run the SPF checker and DKIM checker for any piece that looks missing or unaligned.
- In each ESP, enable DKIM signing as your domain, not only as the ESP.
- Add only real envelope senders to SPF. Leave forwarders out.
- Publish DMARC at
p=nonewithrua=if you do not have a record yet, then read reports before tightening policy. - For marketing streams, confirm RFC 8058 headers on a real received message, not only in the ESP’s “we support one-click” checkbox.
- Re-read Google’s Email sender guidelines and Yahoo’s current sender requirements before you freeze a volume number in an internal wiki.
Email Watch’s checkers read live DNS. They do not send mail, honor unsubscribes, or override Gmail or Yahoo. If you point rua= at Email Watch later, the dashboard classifies sources in those aggregate reports so an unaligned ESP is visible as your own sender, not guessed from raw XML.
Run the free check to confirm
Applied the fix above? Run the freeDMARC Checkeragainst your domain and see your grade update in real time.
Run the free check: DMARC CheckerCommon follow-up questions
Who counts as a Gmail bulk sender?
Gmail's 2024 bulk-sender rules apply to senders of 5,000 or more messages a day to personal Gmail accounts. Google has described that classification as sticky once you cross the line. Thresholds and wording change, so read Google's current Email sender guidelines rather than treating 5,000 as a permanent law.
Did Yahoo use the same 5,000-message threshold as Gmail?
Yahoo published matching authentication and one-click unsubscribe requirements for bulk and commercial mail. It has not always used Gmail's 5,000-a-day wording. Check Yahoo's current sender documentation for volume language, and treat the authentication bar as the part that matches.
Is a DMARC record at p=none enough for bulk senders?
For the published-record requirement, yes: Gmail's bulk-sender rules accept p=none. You still need SPF and DKIM set up, and the From domain must align with SPF or DKIM on the message. p=none does not exempt you from alignment or from Gmail's own inbound checks.
Do I need both SPF and DKIM aligned, or is one enough?
Bulk senders should publish and pass both SPF and DKIM. DMARC alignment is satisfied when at least one of those passes aligns with the visible From domain. Aim for both aligned. One aligned pass is what DMARC counts.
Does one-click unsubscribe apply to invoices and password resets?
No. Gmail requires one-click unsubscribe (RFC 8058 List-Unsubscribe plus List-Unsubscribe-Post) on marketing and subscribed mail. Transactional mail such as invoices, password resets, and shipping notices is a different class. Do not mix a promo into a receipt and call it transactional.
Why does Gmail bounce with 550 5.7.26 if we already have SPF?
That bounce means SPF and DKIM both failed DMARC alignment on the message. An SPF pass on a vendor envelope domain does not count if From shows your brand. See the Gmail 550 5.7.26 guide. Fix aligned DKIM for your domain, and an aligned envelope if the vendor supports it.
Should I add forwarding services to my SPF record?
No. Do not SPF-include forwarders. Their IPs are not your senders, and forwarding usually breaks SPF anyway. Keep SPF limited to systems you control or hire to send, and rely on aligned DKIM so forwarded mail can still pass DMARC.
If we send under 5,000 messages a day, can we skip DMARC?
You can be below Gmail's bulk threshold and still want a DMARC record. Gmail still expects SPF or DKIM from all senders, and a published DMARC policy (even p=none) is how you see who is sending as you. Under 5,000 is not a reason to skip authentication.
More guides
DMARC p=none vs quarantine vs reject
p=none watches without asking receivers to block. Quarantine asks for junk. Reject asks them to refuse the message. Here is when to move, and what still happens at none.
Multiple SPF records: why two v=spf1 TXT records is a permerror
RFC 7208 allows one v=spf1 TXT record per domain. Two or more is a permerror, and receivers do not merge them. Here is how extras appear, how to check, and how to combine includes.
Parked domain DMARC p=reject: records for domains that never send
Domains that never send mail should still publish DMARC, usually p=reject, plus SPF v=spf1 -all and a null MX. Here is the record set and why p=none is the wrong default.
Don't want to catch this by hand next time?
Email Watch ingests your DMARC reports daily and flags an authentication failure like this one the day it appears — free for 7 days, no credit card.
Start free trial →