Skip to content
  • There are no suggestions because the search field is empty.

Google and Yahoo sender requirements

Gmail's bulk sender rules and Yahoo's sender requirements say almost the same thing. Every sender needs SPF or DKIM, valid reverse DNS, and a low spam rate. Bulk senders need SPF and DKIM, a DMARC record that can be as light as p=none but must actually pass with alignment, and one-click unsubscribe on marketing mail. Where they differ is in the detail: Google publishes a volume threshold and Yahoo doesn't, and Google requires the one-click HTTP POST method where Yahoo also accepts mailto.

This is the deep version for Gmail and Yahoo. For the short three-provider comparison, see Google, Yahoo, and Microsoft sender requirements. Microsoft's rules are in Microsoft and Outlook authentication rules.

Gmail sender requirements

Google's rules apply to mail sent to personal Gmail accounts (addresses ending in @gmail.com or @googlemail.com). Its FAQ says the requirements and enforcement "apply only when sending email to personal Gmail accounts," not to mail sent to Google Workspace accounts. Your Workspace users still have to meet them when they send to Gmail.

Every sender

For Gmail, every sender needs:

  • SPF or DKIM for your sending domain.
  • Valid forward and reverse DNS (a PTR record for each sending IP that resolves back to the same IP).
  • A TLS connection for sending.
  • A spam rate reported in Postmaster Tools below 0.3%.
  • Correctly formatted Internet messages (a valid From, Date, and Message-ID, and so on).
  • No impersonating Gmail in the From header.

Bulk senders

Gmail treats you as a bulk sender if you send close to 5,000 messages or more to personal Gmail accounts within a 24-hour period. Two details catch people out. The count is per primary domain, so news.example.com and billing.example.com add up under example.com. And the status is permanent: senders who meet the criteria at least once are permanently considered bulk senders. You may also see the threshold worded as more than 5,000 messages per day; plan around the closer, more precise figure.

The google bulk sender guidelines add:

  • SPF and DKIM, both.
  • A DMARC record. "Your DMARC enforcement policy can be set to none." So v=DMARC1; p=none; rua=mailto:dmarc@example.com meets the requirement.
  • Alignment for direct mail. The domain in the sender's From header must be aligned with either the SPF domain or the DKIM domain. One aligned pass is enough. Alignment isn't required for forwarded or mailing list messages, which Gmail also calls indirect messages. If your ESP passes SPF with its own bounce domain and signs DKIM with its own domain, nothing aligns, even though both pass (Identifier alignment for SPF and DKIM).
  • One-click unsubscribe for marketing and subscribed messages, plus "a clearly visible unsubscribe link in the message body." Honor requests within 48 hours.
  • Spam rate below 0.3%, with Google's target below 0.1%.

What Gmail does if you miss one

Gmail's enforcement is in two bands. Missing alignment, SPF plus DKIM, reverse DNS, TLS, or a correctly formatted message can get temporary or permanent failure codes, or land in spam. A spam rate over 0.3%, a missing DMARC record, missing one-click unsubscribe, or unsubscribes not honored within 48 hours means delivery support or mitigations may be unavailable.

Since November 2025, Gmail has been ramping up enforcement on non-compliant traffic, with temporary and permanent rejections. Unauthenticated mail might be marked as spam or rejected with a 5.7.26 error. The same 5.7.26 code also appears for other authentication failures, so use the bounce text, not only the code. When you have a bounce in hand, start with our Troubleshooting articles.

Gmail spam rate

The spam rate is calculated daily, and its impact on delivery is graduated. User-reported spam rates greater than 0.1% have a negative impact on email inbox delivery for bulk senders. Above 0.3% you're ineligible for mitigation, and you become eligible again once the rate stays below 0.3% for 7 consecutive days. For what the rate measures and how to lower it, see What is a spam complaint rate?.

One click unsubscribe, done right

Gmail and Yahoo both use the same one-click unsubscribe method. It needs two headers on the message:

List-Unsubscribe: <https://example.com/unsub/8f3k2q9z>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

The rules are short and strict:

  • The list unsubscribe header "MUST contain one HTTPS URI." A mailto URI can sit alongside it, but at Gmail a mailto alone doesn't satisfy the requirement.
  • List-Unsubscribe-Post must contain exactly List-Unsubscribe=One-Click.
  • The message "MUST have a valid DomainKeys Identified Mail (DKIM) signature that covers at least the List-Unsubscribe and List-Unsubscribe-Post headers." In practice, both header names must appear in the h= tag of your DKIM signature, for example h=from:to:subject:date:list-unsubscribe:list-unsubscribe-post. If your ESP adds the headers after signing, they aren't covered (DKIM selectors and DNS records).
  • The URL should carry an opaque, hard-to-forge token that identifies the recipient and list. The POST must not rely on cookies or a login, and the server "MUST NOT return an HTTPS redirect."

Who needs it: marketing and subscribed mail. Transactional messages are excluded, with password resets, reservation confirmations, and form confirmations as examples.

Yahoo sender requirements

Yahoo's list is:

Every sender

  • SPF or DKIM at a minimum.
  • Spam rate below 0.3%.
  • Valid forward and reverse DNS for sending IPs.
  • Compliance with standard SMTP and Internet message format.

Bulk senders

Yahoo won't say what counts as bulk. Its FAQ: "We will not specify a volume threshold". If you send meaningful volume to Yahoo addresses, plan as if the yahoo bulk sender requirements apply:

  • SPF and DKIM, both.
  • "Publish a valid DMARC policy with at least p=none - DMARC must pass." An rua tag is "strongly recommended," and "relaxed alignment is acceptable."
  • From aligned with the SPF or DKIM domain.
  • One-click list-unsubscribe for marketing and subscribed mail. The HTTP POST method is highly recommended; the mailto method is acceptable. A visible body link is required too.
  • Honor unsubscribes within 2 days.
  • Spam rate below 0.3%, calculated "based on mail delivered to the inbox."

Yahoo also recommends ARC if you forward mail (Email forwarding, SRS, and ARC) and enrolling every DKIM domain in its Complaint Feedback Loop, which sends you a copy of each spam complaint. And its FAQ says that if you have a spoofing problem, you should be using p=quarantine or p=reject regardless.

Where Gmail and Yahoo differ

Gmail Yahoo
Bulk threshold Close to 5,000 in 24 hours, per primary domain; permanent Not published
DMARC Record required, p=none allowed; aligned for direct mail At least p=none; "DMARC must pass"
One-click method HTTP POST; mailto alone doesn't count POST highly recommended; mailto acceptable
Unsubscribe deadline 48 hours 2 days
Spam-rate tool Postmaster Tools Complaint Feedback Loop

If you build to Gmail's version, you meet Yahoo's too.

Checking where you stand

Gmail Postmaster Tools shows your spam rate, authentication results, delivery errors, and a Compliance status dashboard. Don't expect the old reputation charts: the Domain and IP Reputation dashboards will be retired and aren't in the new version (v2). As of 15 Nov 2026, Google has postponed retiring the old interface, so some accounts may still see them. More in IP and domain reputation.

DMARC aggregate reports show which of your sources pass SPF, DKIM, and aligned DMARC at Gmail and Yahoo. That's how you prove the "must pass" part. BIMI Certifications' DMARC reporting and visual analysis shows this per source. Neither the reports nor any compliance dashboard shows inbox placement (Authentication vs inbox placement).

Common mistakes

  • Counting volume per subdomain. Google counts per primary domain.
  • Passing SPF on the ESP's domain only. It passes, but it doesn't align with your From domain.
  • One-click headers outside the DKIM signature. The headers are there, but they don't count.
  • Treating a 0.2% spam rate as fine. It's under the 0.3% line, but anything over 0.1% already hurts.
  • Stopping at p=none for good. It meets the minimum. It doesn't protect your domain from spoofing, and it doesn't qualify for BIMI (Why staying at p=none is a problem).

For why DMARC matters beyond these provider rules, see Why DMARC on our main site. If you send from Google Workspace, the setup steps are in DMARC for Google Workspace.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Do I need DMARC at enforcement for Gmail?

No. The policy "can be set to none," and Yahoo accepts "at least p=none." Mail still has to pass DMARC with alignment.

Does one-click unsubscribe apply to receipts?

No. Google excludes transactional messages, and Yahoo's requirement is for marketing and subscribed mail.

What's Yahoo's bulk threshold?

Yahoo doesn't publish one.

Can I lose bulk-sender status at Gmail?

No. The classification is permanent and that "changes in email sending practices will not affect" it.

Does meeting these rules get us into the inbox?

It gets you past the floor. Placement still depends on complaints, reputation, and engagement. See Why are my emails going to spam and Authentication vs inbox placement.