Key takeaway
Authentication is the part you can finish in an afternoon. Staying under the spam-rate limit depends on whether recipients wanted to hear from you.
Gmail and Yahoo require every sender to authenticate their mail and keep spam reports below 0.3%. Bulk senders also need DMARC, an aligned From domain and one-click unsubscribe, and should process unsubscribes within two days. Google introduced its requirements in February 2024 and says that since November 2025, mail that misses them can be temporarily or permanently rejected.
This guide sets out what each provider asks, who counts as a bulk sender, what Outlook.com expects, and how the rules apply when you write to prospects rather than subscribers.
Know which mailboxes the rules cover
Google’s requirements apply to mail sent to personal Gmail accounts, meaning addresses that end in @gmail.com or @googlemail.com. Google states that they do not apply to messages sent to Google Workspace accounts, although Workspace users must meet them when they write to personal Gmail addresses. Yahoo’s requirements apply to all domains and consumer email brands hosted by Yahoo Mail.
Business outreach often goes to company addresses hosted by Google Workspace, Microsoft 365 or other providers. Those receivers make their own filtering decisions, but the same basics are a sensible standard everywhere: authenticated mail, few complaints and an easy way to opt out.
What every sender needs
These requirements apply whatever your volume.
| Requirement | Gmail | Yahoo |
|---|---|---|
| SPF or DKIM authentication | Required | Required |
| Spam rate | Below 0.3%, with 0.1% as the target | Below 0.3% |
| Valid forward and reverse DNS for sending servers | Required | Required |
| Standard message format | Required (RFC 5322) | Required (RFCs 5321 and 5322) |
| Encrypted connection (TLS) | Required | Not in the list |
The spam rate is the share of your mail that recipients mark as spam: 0.3% means three reports for every 1,000 messages. Google calculates it daily and shows it in Postmaster Tools. It asks senders to stay below 0.1% and never reach 0.3%, and says that rates above 0.1% already hurt inbox delivery for bulk senders. Yahoo bases its rate on mail delivered to the inbox.
What bulk senders need on top
Senders who reach bulk volume also need to:
- Authenticate with both SPF and DKIM.
- Publish a DMARC record. A policy of p=none is accepted, but messages must pass DMARC.
- Align the From domain with the domain that passed SPF or signed the message with DKIM.
- Support one-click unsubscribe in marketing and subscribed messages, and show a clearly visible unsubscribe link in the body.
- Process unsubscribe requests within two days. Yahoo requires it; Google recommends 48 hours, and a sender that misses it loses access to Google’s delivery support and mitigations.
One-click unsubscribe is defined in RFC 8058: the message carries a List-Unsubscribe header with an HTTPS link and a List-Unsubscribe-Post header, and its DKIM signature must cover both. Google requires the HTTPS link; Yahoo also accepts a mailto: address but highly recommends the one-click method. For the DNS side, see how to set up a domain for cold email.
Who counts as a bulk sender
Google defines a bulk sender as one that sends close to 5,000 messages or more to personal Gmail accounts within 24 hours. Messages from the same primary domain count together, so mail from subdomains adds to the total, and a sender that reaches the threshold once is treated as a bulk sender permanently.
Yahoo deliberately gives no number. It describes a bulk sender as one sending a significant volume of mail and says it will not specify a threshold.
A small outreach program may never send 5,000 messages a day to Gmail users. It is still worth meeting the bulk requirements from the start: the count includes all mail from your primary domain, not just outreach, the status never expires, and most of the extra steps only need to be set up once.
What the rules mean for cold outreach
The requirement lists do not mention cold email, but two parts of the providers’ guidance matter most for it.
First, Google requires one-click unsubscribe for marketing and promotional messages and excludes transactional ones. It adds that recipients, not Google, determine the nature of the messages they receive. A prospecting email is unlikely to look transactional to the person reading it, so if you send at bulk volume, plan as if the requirement applies.
Second, Google’s wider guidelines say to send only to people who want your messages and not to buy address lists, and warn that people who did not sign up may mark your messages as spam. Yahoo says that sending unsolicited commercial email can negatively affect your reputation. Cold outreach is mail people did not sign up for, which makes the spam-rate limit the requirement that matters most. Staying under it depends on whether each recipient can see a real reason for your message:
- Contact a short list of companies that fit, chosen with a customer profile that says no.
- Give the first message a real reason to talk.
- Make opting out easy, and treat every opt-out as final.
- Start a subject line with Re: or Fwd: only when the message really is a reply or a forward, as Google’s guidelines ask.
What Outlook.com expects
Microsoft set similar rules for its consumer service, which covers outlook.com, hotmail.com and live.com addresses. Domains that send more than 5,000 emails a day to it must pass SPF and DKIM and publish a DMARC policy of at least p=none that aligns with SPF or DKIM, preferably both.
Microsoft’s announcement says that from May 5, 2025, Outlook.com rejects mail from these senders that fails the checks, with the error “550 5.7.515 Access denied”, and its support page for that error describes the same rejection. Older text on some Microsoft pages still mentions routing such mail to the Junk folder first. Microsoft lists unsubscribe links and recipient consent as recommendations rather than requirements.
Google’s and Yahoo’s pages carry no revision dates, and the requirements have changed since they were introduced. Check the sources below before you rely on a detail, including one in this guide.
Sources
- Email sender guidelines · Gmail Help
- Email sender guidelines FAQ · Gmail Help
- Sender requirements and recommendations · Yahoo Sender Hub
- FAQs · Yahoo Sender Hub
- Strengthening Email Ecosystem: Outlook’s New Requirements for High-Volume Senders · Microsoft Community Hub
- Fix NDR error “550 5.7.515” in Outlook.com · Microsoft Support
- RFC 8058: Signaling One-Click Functionality for List Email Headers · RFC Editor
Summarizes the providers’ published requirements. Providers change these pages without notice, so check the sources before relying on a detail.