schedule 7-min read

Google and Yahoo Sender Requirements: What DMARC Means for Businesses

DMARC AI editorial team · Last updated

Yes: Google and Yahoo require bulk senders to publish DMARC, at least p=none, aligned with SPF or DKIM. What each provider asks for and how to comply.

01

Introduction

Yes. Google and Yahoo both require bulk senders to publish a DMARC record with at least p=none, authenticate with both SPF and DKIM, and align the From domain with at least one of them. Google defines a bulk sender as one sending around 5,000 or more messages a day to personal Gmail accounts; Yahoo sets no published number.

Both providers began enforcing in February 2024, and Google says it has been ramping up enforcement since November 2025, including temporary and permanent rejections of non-compliant mail. This article sets out what each provider requires, what applies to all senders, and how a business or its MSP gets a domain compliant. The DMARC guide covers the protocol itself, and Microsoft's Outlook.com requirements are covered separately.

02

Key takeaways

  • Bulk senders to Gmail and Yahoo need SPF, DKIM, DMARC at p=none or stronger, and From-domain alignment with SPF or DKIM.
  • Google's threshold is about 5,000 messages a day to personal Gmail accounts, and a sender that crosses it once is treated as a bulk sender permanently.
  • Google's rules do not apply to mail sent to Google Workspace accounts; they apply to personal Gmail accounts.
  • Marketing mail needs one-click unsubscribe, and unsubscribes must be honoured within two days.
  • Keep spam complaints below 0.3%, and ideally below 0.1%.
03

What do Google and Yahoo require from bulk senders?

The core requirements are the same for both providers. The details differ slightly:

Requirement Google (Gmail) Yahoo
Bulk threshold Close to 5,000 or more messages in 24 hours to personal Gmail accounts Not published
SPF and DKIM Both required Both required
DMARC Published, minimum p=none Valid policy, minimum p=none; DMARC must pass
Alignment From domain aligned with SPF or DKIM From domain aligned with SPF or DKIM; relaxed alignment is acceptable
One-click unsubscribe Required for marketing and promotional mail, using an HTTPS URL as defined in RFC 8058 Required for marketing and subscribed mail; RFC 8058 POST highly recommended
Honour unsubscribes Within 48 hours Within 2 days
Spam complaint rate Below 0.3%; aim for below 0.1% Below 0.3%
Enforcement since February 2024, ramped up from November 2025 February 2024, rolled out gradually

Sources: Google's email sender guidelines FAQ and Yahoo's sender best practices.

04

What applies to all senders, not just bulk senders?

Both providers set a baseline for every sender, whatever the volume. Yahoo asks all senders to implement SPF or DKIM at a minimum, keep spam rates below 0.3%, have valid forward and reverse DNS for sending IPs, and comply with RFC 5321 and RFC 5322. Google's enforcement table also lists valid forward and reverse DNS, TLS for transmission and RFC 5322 formatting.

In practice: if your domain sends any mail to Gmail or Yahoo users, fix authentication now. Volume decides how strictly you are judged, not whether authentication matters.

05

Who counts as a bulk sender?

For Google, a bulk sender is one that sends close to 5,000 or more messages to personal Gmail accounts within 24 hours. Messages from the same primary domain count together, so a client's newsletter platform, CRM, help desk and billing system add up under one domain. Google also states that a sender that meets the threshold once is permanently considered a bulk sender.

Two details often surprise businesses:

  • Only mail to personal Gmail accounts counts for Google. Google states that the guidelines do not apply to messages sent to Google Workspace accounts. B2B senders that mainly email Workspace customers may fall below the threshold, but should comply anyway, because the same practices decide inbox placement everywhere.
  • Yahoo publishes no threshold. Treat its bulk requirements as applying to any significant volume of marketing or automated mail.
06

What happens to non-compliant mail?

Google's FAQ lists the consequences per requirement. Mail that is not aligned, not authenticated with both SPF and DKIM, lacks valid forward and reverse DNS, is not sent over TLS or is badly formatted can receive temporary or permanent failure codes, or go to spam. Missing DMARC, missing one-click unsubscribe, slow unsubscribe handling or a spam rate above 0.3% make a sender ineligible for delivery support and mitigation.

Google's error codes point to the failing control: 4.7.27 or 5.7.27 for SPF, 4.7.30 or 5.7.30 for DKIM, 4.7.31 for a missing DMARC record (Google's SMTP error reference uses 4.7.40 and 5.7.40 for this) and 4.7.32 when the From domain is not aligned. Our guide to Gmail 550 5.7.26 and other authentication bounce codes maps each code to its fix. Yahoo groups its codes into families rather than publishing one per failure: see Yahoo TSS04 and other Yahoo bounce codes for which ones DNS fixes and which it cannot.

07

How do you get a domain compliant?

Work through the requirements in order, because each depends on the one before:

  1. Inventory every service that sends as the domain: mail platform, marketing, CRM, billing, help desk.
  2. Set up SPF for the services that need it, and keep within the 10 DNS lookup limit.
  3. Enable DKIM signing with your own domain on every service, so DKIM aligns with the From address.
  4. Publish DMARC at p=none with a reporting address: v=DMARC1; p=none; rua=mailto:dmarc@example.com.
  5. Read the aggregate reports to confirm every service passes and aligns. DMARC aggregate reports explained shows what to look for.
  6. Add one-click unsubscribe to marketing mail and check that your platform honours requests within two days. The headers must be covered by your DKIM signature; see one-click unsubscribe: what Gmail and Yahoo require.
  7. Watch spam complaint rates in Google Postmaster Tools (see how Postmaster Tools and DMARC reports fit together).

p=none satisfies the requirement, but it does not stop anyone spoofing the domain. Plan the move to p=quarantine and then p=reject once reports show every legitimate sender aligned. How to move from monitoring to enforcement safely sets out the steps.

08

What should an MSP check for each client?

An MSP can turn the requirements into a short, repeatable check per client domain:

  1. DMARC published at p=none or stronger, with reports going somewhere that is read.
  2. SPF and DKIM passing for every sending service, with DKIM aligned.
  3. Bulk risk: does the client send to consumer Gmail or Yahoo addresses at volume?
  4. Unsubscribe: does each marketing platform add the one-click headers?
  5. Next step to enforcement, recorded with a target date.

Clients that pass all five are compliant with Google, Yahoo and, for authentication, Microsoft's consumer rules too. How MSPs should audit client domains for DMARC risk covers the wider audit.

09

FAQ

Do Google and Yahoo require DMARC?

Yes, for bulk senders. Both require a published DMARC record with at least p=none, plus SPF and DKIM, with the From domain aligned to one of them. Yahoo also requires DMARC to pass. For lower-volume senders, DMARC is strongly recommended rather than mandated.

Is p=none enough for Google and Yahoo?

Yes, p=none meets the minimum both providers require. It does not protect the domain from spoofing, though, because receivers take no action on failing mail. Treat it as the starting point and plan the move to p=quarantine and p=reject.

Do the rules apply to Google Workspace recipients?

Google states that its email sender guidelines do not apply to messages sent to Google Workspace accounts. They apply to mail sent to personal Gmail accounts. Workspace still filters spoofed and unauthenticated mail, so authentication remains worth doing for B2B senders.

What spam complaint rate do Google and Yahoo allow?

Both set a ceiling of 0.3%. Google advises keeping the rate below 0.1% and says delivery mitigation is unavailable above 0.3% until the rate stays below it for seven consecutive days.

Does SPF need to be -all for compliance?

No. Neither provider requires a hard fail. What matters is that SPF passes for your legitimate senders, that DKIM signs with your domain, and that DMARC aligns. The DMARC policy is what tells receivers how to handle failures.

10

Final thoughts

Google and Yahoo turned DMARC from good practice into a condition of delivery for bulk senders. The minimum is modest: SPF, DKIM, an aligned DMARC record at p=none, one-click unsubscribe and low complaint rates. Meet it for every sending domain, then use the reports you now receive to finish the job and reach p=reject.

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.