Gmail and Yahoo Bulk Sender Requirements
Updated
Short answer: Since February 2024, Gmail and Yahoo have required every sender to authenticate with SPF or DKIM, keep the spam rate below 0.3% and have valid forward and reverse DNS. Bulk senders also need both SPF and DKIM, a DMARC record of at least p=none, a From domain that aligns, and one-click unsubscribe on marketing mail. Google draws the bulk line at about 5,000 messages a day, while Yahoo publishes no number.Who the rules cover
- Gmail: mail to personal Gmail accounts. "A personal Gmail account is an account that ends in @gmail.com or @googlemail.com." Business accounts are out of scope: "The Email sender guidelines don’t apply to messages sent to Google Workspace accounts."
- Yahoo: "These requirements apply for all domains and consumer email brands hosted by Yahoo Mail."
When you count as a bulk sender
Google words its threshold three ways. A heading in its sender guidelines says "5,000 or more messages per day", and the text under it says "more than 5,000 messages per day". Its FAQ says: "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. Messages sent from the same primary domain count toward the 5,000 limit."
The status also sticks: "Senders who meet the above criteria at least once are permanently considered bulk senders."
Yahoo sets no number at all: "A “bulk” sender is classified as an email sender sending a significant volume of mail. We will not specify a volume threshold." It judges senders "at the authenticated domain or From header domain level." So a sender well under 5,000 a day can still be treated as a bulk sender by Yahoo.
The requirements side by side
| Requirement | Gmail | Yahoo |
|---|---|---|
| Authentication, every sender | SPF or DKIM | SPF or DKIM at a minimum |
| Authentication, bulk senders | Both SPF and DKIM | Both SPF and DKIM |
| DMARC, bulk senders | A DMARC record, whose policy can be p=none | A valid policy of at least p=none, and DMARC must pass |
| From alignment, bulk senders | The From: domain aligns with the SPF or the DKIM domain | The same, and relaxed alignment is acceptable |
| DKIM key | 1024 bits or longer | 1024 bits or greater |
| Forward and reverse DNS | Valid for sending domains or IPs | Valid for sending IPs |
| Message standards | RFC 5322 format, sent over a TLS connection | RFCs 5321 and 5322 |
| Spam rate | Below 0.3%, with a target below 0.1% | Below 0.3% |
| One-click unsubscribe, bulk marketing mail | List-Unsubscribe headers as in RFC 8058, with one HTTPS URL; mailto doesn't count | A list-unsubscribe header that supports one-click; the RFC 8058 POST method is "highly recommended" and mailto is acceptable |
| Visible unsubscribe link | Required in marketing and subscribed mail | Required, and it may lead to a preference page |
| Acting on unsubscribes | Google recommends within 48 hours | Within 2 days |
Neither requires one-click unsubscribe on transactional mail. Google: "One-click unsubscribe is required only for marketing and promotional messages. Transactional messages are excluded from this requirement." Yahoo gives order confirmations and password resets as examples of transactional mail that is exempt.
For the details, read SPF, DKIM and DMARC Explained and One-Click Unsubscribe (RFC 8058) Explained.
Spam rate: 0.3% is a ceiling, not a target
Google: "Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher." It adds that "Spam rate is calculated daily." From June 2024, "bulk senders with a user-reported spam rate greater than 0.3% will be ineligible for mitigation." They become eligible again "when their spam rates remain below 0.3% for 7 consecutive days."
Yahoo's limit is also 0.3%, but it measures differently: "Spam rate is calculated in our system based on mail delivered to the inbox". A rate you calculate over all the mail you sent can come out lower than Yahoo's.
What happens if you fall short
At Gmail:
- From November 2025, Google says it is stepping up enforcement: "Messages that fail to meet the email sender requirements will experience disruptions, including temporary and permanent rejections."
- Failing the authentication, alignment, DNS, TLS or formatting rules can bring "Temporary or Permanent Failure codes, or spam foldering". Unauthenticated mail "might be marked as spam or rejected with a 5.7.26 error."
- Gmail rate-limits mail with code
4.7.31when the sending domain has no DMARC record or the record sets no policy, and with4.7.32when the From: header isn't aligned. - A missing DMARC record, missing one-click unsubscribe or a spam rate above 0.3% makes Google's delivery support (it calls this mitigation) unavailable.
Missing one-click unsubscribe on its own doesn't send mail to spam. Google: "We don’t automatically reject messages or mark messages as spam when they don’t meet the one-click unsubscribe requirements in our Email sender guidelines." But "only bulk senders that meet all the requirements in our Email sender guidelines, including one-click unsubscribe, are eligible for mitigation."
At Yahoo: "If you do not meet the requirements, your mail may be sent to the spam folder or rejected." Enforcement began in February 2024 and was rolled out gradually, and enforcement of the unsubscribe rule began in June 2024.
Checklist
- Count your daily mail to personal Gmail accounts per primary domain. If you get close to 5,000 even once, you are a bulk sender for good.
- Set up SPF and DKIM for your sending domain, with a DKIM key of 1024 bits or longer.
- Publish a DMARC record with a policy of at least
p=none, and check that DMARC passes. - Make sure the From: domain aligns with your SPF or DKIM domain.
- Give your sending IPs valid forward and reverse DNS (PTR) records, and send over TLS.
- Add one-click unsubscribe headers and a visible unsubscribe link to marketing and subscribed mail.
- Remove people who unsubscribe within 2 days.
- Watch your spam rate in Postmaster Tools, and keep it below 0.1%.
Common mistakes
- Using 5,000 a day as Yahoo's line. The number is Google's. Yahoo "will not specify a volume threshold."
- Treating a mailto link as one-click for Gmail. Google: "We’ll continue to support mailto links but they don’t meet our one-click unsubscribe requirement."
- Relying on a link in the body. Yahoo: "you must implement the list-unsubscribe header (preferably according to RFC 8058) in order to meet the requirement for one-click unsubscribe."
- Assuming bulk status ends when volume drops. At Gmail it is permanent.
- Publishing DMARC without alignment. DMARC needs the From: domain to align with SPF or DKIM.
Microsoft has its own rules for Outlook.com, Hotmail and Live addresses. See Outlook.com Rules for High-Volume Email Senders.
Precheckly's free SPF, DKIM and DMARC checker looks up your domain's SPF, DKIM, DMARC and MX records and suggests a fix for each problem. It checks DNS only, not message headers, so it won't see your unsubscribe headers.
Sources
- Email sender guidelines, Google
- Email sender guidelines FAQ, Google
- Sender Best Practices, Yahoo Sender Hub
- FAQs, Yahoo Sender Hub
- Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders, Microsoft
Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.