Guides

Google and Yahoo bulk sender requirements explained

Google and Yahoo bulk sender requirements: the 5,000-a-day threshold, SPF, DKIM, DMARC, and what a small cold email program should set up first.

Short answer: Google's guidelines say senders of more than 5,000 messages per day to Gmail accounts must set up SPF and DKIM [[1]](#sources). Gmail and Yahoo require SPF or DKIM for all senders, and SPF, DKIM and DMARC for bulk senders [[2]](#sources). Yahoo asks for a valid DMARC policy with at least p=none [[3]](#sources).

Who this is for

This is for anyone who sends cold email from their own domain: founders, small sales teams, agencies running campaigns for a handful of clients. You may send a few hundred messages a day or a few thousand. You have seen "bulk sender requirements" in a forum thread or a deliverability tool and want to know what actually applies to you.

It is also for people who assume the rules are only for newsletters and marketing platforms. A cold email program that grows past a small size meets the same checks as anyone else.

This page covers what the providers say in their own words, which parts apply to every sender, and what a small program should set up. It does not cover everything. Some details, such as exact spam complaint limits and one-click unsubscribe rules per provider, are not covered here; the providers' own pages have them. Where that applies, the page says so and points you there.

Steps

These steps are in the order that makes sense for a small cold email program. Do them on the domain you send from, not only on your main company domain.

What Google and Yahoo actually say

Start with the primary text. Google's sender guidelines page, checked on 2026-10-22, opens its bulk sender section like this: "email senders who send more than 5,000 messages per day to Gmail accounts must meet the requirements in this section. Set up SPF and DKIM email authentication for your domain." [[1]](#sources)

Two things stand out in that quote. The threshold is a count of messages to Gmail accounts, per day. It is not a count of everything you send across all providers. And the first requirement it names is authentication: SPF and DKIM, set up for your domain.

Yahoo's sender best practices page, checked the same day, adds the DMARC requirement in one line: "Publish a valid DMARC policy with at least p=none" [[3]](#sources). The words "at least" matter. A p=none policy is the floor.

Put together, the two pages support one summary, checked on 2026-10-22: Gmail and Yahoo require SPF or DKIM for all senders, and SPF, DKIM and DMARC for bulk senders [[2]](#sources). The same split is stated against Yahoo's page [[4]](#sources).

That gives two tiers:

  • Every sender: SPF or DKIM.
  • Bulk senders: SPF, DKIM and DMARC. For Gmail, bulk means more than 5,000 messages per day to Gmail accounts [[1]](#sources).

Outlook is moving the same way

Gmail and Yahoo are not alone. Microsoft wrote about Outlook's new requirements for high-volume senders: "For domains sending over 5,000 emails per day, Outlook will soon require compliance with SPF, DKIM, DMARC." [[5]](#sources) That was checked on 2026-10-22. The word "soon" is Microsoft's. Check Microsoft's post for the current status before you plan around it.

What this page leaves to the providers

This page does not cover several requirements:

  • The spam complaint rate limits.
  • Which senders must offer one-click unsubscribe, and the exact conditions.
  • How closely the domain in your From address must match the domains that pass SPF and DKIM (the alignment rules).
  • Any daily volume threshold Yahoo sets for bulk senders.

Read those directly on Google's sender guidelines and Yahoo's sender best practices. Do not rely on a summary from a third-party blog for numbers like complaint rates.

1. Work out your volume to Gmail

Count how many messages you send per day to Gmail addresses. Google's threshold is more than 5,000 messages per day to Gmail accounts [[1]](#sources). If you are well under that, you are not a bulk sender by Google's definition today. You still need authentication, because the all-sender tier applies to you [[2]](#sources).

Also check what share of your list is Gmail, since the threshold counts messages to Gmail accounts [[1]](#sources).

2. Use a sending domain that is not your main domain

We recommend sending cold email from domains separate from your main domain.

Outlevo's managed mailboxes work this way: Outlevo buys sending domains, creates the mailboxes, sets up DNS and warms them up, so you never touch your main domain [[6]](#sources). You choose the domains Outlevo proposes and the sender names [[6]](#sources). The Self-Serve plan includes 2 domains and 4 mailboxes [[6]](#sources) and costs USD 199 per month [[7]](#sources).

If you set up domains yourself, apply every step below to each sending domain.

3. Publish SPF, and keep it within the lookup limit

SPF is one of the authentication records the providers name [[2]](#sources). RFC 7208 says: "SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation" [[8]](#sources). It was checked on 2026-10-22.

To stay within it:

  • Add only the senders you actually use.
  • Remove old entries for tools you stopped using.
  • Recount the lookups after every change.

4. Turn on DKIM

DKIM is named by both the all-sender tier and the bulk tier, either alone or with SPF [[2]](#sources). Turn it on for each domain and each sending service. Then send a test message and check that the signature passes in the message headers.

If you use Google Workspace, Outlevo has a setup page: Google Workspace SPF, DKIM and DMARC setup.

5. Publish a DMARC policy

Yahoo's line is "Publish a valid DMARC policy with at least p=none" [[3]](#sources). For a small program, publishing a valid record is the point of this step. A record with a typo is not a valid policy, so check the syntax after you publish it.

You can start at the minimum and tighten later. That decision is yours, and it depends on how many tools send mail for the domain.

6. Handle unsubscribes properly

One-click unsubscribe is defined by RFC 8058: "This document describes a method for signaling a one-click function for the List-Unsubscribe email header field." [[9]](#sources) That is the standard. Whether Google and Yahoo each require it, and for which senders, is on their pages, so read it there before assuming.

Whatever the rule, you need a working way for people to opt out, and you need to act on it. If you send through Smartlead, unsubscribe events come back to Outlevo by webhook, along with sent, reply, bounce and category changes [[10]](#sources). Treat an unsubscribe as final.

7. Put a postal address in every message

This one is not a Google or Yahoo rule. The FTC's CAN-SPAM guide for business says: "Your message must include your valid physical postal address." [[11]](#sources) The guide was read on 2026-10-22. Put the address in your signature or footer template, so every message carries it.

8. Warm the mailboxes before they send

A new mailbox has no history. With Outlevo's managed mailboxes, a new mailbox sends nothing until it is warm: at least 14 days, usually about 3 weeks [[6]](#sources). Outlevo checks each mailbox's warm-up state and reputation daily [[6]](#sources).

If you bring your own mailboxes through Smartlead, the check is explicit. Before a campaign sends, every mailbox must be connected and warmed up, and its domain must have SPF, DKIM and DMARC checked in the last 7 days [[10]](#sources). Smartlead sends the emails from the mailboxes in your Smartlead account, while Outlevo writes and schedules them [[10]](#sources).

What to check

What this means for a small cold email program

Most small programs fall under the 5,000-a-day line. That does not make the requirements optional. The all-sender tier needs SPF or DKIM [[2]](#sources), and the bulk tier is where your program may end up if it grows. Setting up all three records now means growth does not force a rushed fix.

A small program also has less room for error. Smartlead's State of Cold Email 2026, covering more than 850 million emails sent from January to June 2026, puts the median cold email reply rate at 0.74% per contact, the top quarter at 1.43% and the top tenth at 2.63% [[12]](#sources). At those rates, a campaign to a few hundred people produces a handful of replies. If a share of your mail lands in spam, you lose some of those few replies and have little data to see why.

So the practical stance for a small program is:

  • Authenticate every sending domain before the first send.
  • Keep cold sending off your main domain.
  • Remove addresses that bounce or opt out.
  • Check your records again whenever you add a tool that sends mail.

Verifying addresses before you send helps with bounces. Outlevo charges 1 credit per email verification [[7]](#sources). Standalone verification tools publish their own prices; Outlevo's pages compare email verification tools and email deliverability tools, with pricing compared.

Policy checks before send

Compliance is easier to keep when it is a check, not a memory. Outlevo checks every external action against an approved policy before it runs and records it in a ledger [[13]](#sources). Policies set who can be contacted, on which channels, how often and with what budget [[13]](#sources). Kill switches pause a campaign, a channel or the whole workspace at once [[13]](#sources). If a mailbox or domain shows trouble, you can stop sending without hunting through settings.

The checklist

Use this as a checklist before each new sending domain goes live, and again each quarter or whenever you change a sending tool.

Authentication

  • SPF is published on the sending domain and stays within the 10-term limit [[8]](#sources).
  • DKIM is on, and a test message shows a passing signature.
  • A valid DMARC record is published, at least p=none [[3]](#sources).
  • Each mailbox's domain was checked recently. Smartlead requires the check within the last 7 days before a campaign sends [[10]](#sources).

Provider pages

  • You have read the current spam complaint limits on Google's and Yahoo's pages, because this page does not state them.
  • You have read what each provider says about one-click unsubscribe and the alignment of your From domain with SPF and DKIM.
  • You know whether Outlook's requirement has moved from "soon" to in force [[5]](#sources).

Message content

  • Every message has a working opt-out.
  • The unsubscribe path is honored, and unsubscribe events reach your tools. With Smartlead, they come back by webhook [[10]](#sources).
  • Every message includes your valid physical postal address [[11]](#sources).

Mailboxes

  • New mailboxes have finished warm-up. In Outlevo's managed setup that is at least 14 days [[6]](#sources).
  • Warm-up state and reputation are visible and checked regularly. Outlevo checks managed mailboxes daily [[6]](#sources).

After sending

  • Bounces, replies and opt-outs are read, not just counted.
  • If a domain shows problems, pause that campaign or channel and fix the cause before resuming.

Next step

Pick one sending domain and run through the checklist above. Fix any gaps in SPF, DKIM and DMARC first, since those are the requirements the providers' pages quote directly. Then read the two provider pages for the parts not covered here: Google's sender guidelines and Yahoo's sender best practices.

If you use Google Workspace, start with the Google Workspace SPF, DKIM and DMARC setup. If you want to compare tools for verification, warm-up or deliverability monitoring, see Sales tools: pricing, plans and integrations and the comparisons.

If you are still deciding who to send to before you set up sending, the free ICP assessment reads up to 5 public pages of your website [[14]](#sources). It returns facts labelled as verified observations or AI inferences, and up to 5 experimental segment hypotheses [[14]](#sources).

Sources

  1. Google: Email sender guidelines
  2. Google email sender guidelines
  3. Yahoo: Sender best practices
  4. Yahoo sender best practices
  5. Microsoft: Outlook requirements for high-volume senders
  6. Managed mailboxes integration
  7. Outlevo pricing
  8. RFC 7208: Sender Policy Framework (SPF)
  9. RFC 8058: Signaling One-Click Functionality for List Email Headers
  10. Smartlead integration
  11. FTC: CAN-SPAM Act compliance guide for business
  12. Smartlead, The State of Cold Email 2026: reply rate per contact (top quartile; January to June 2026, more than 850 million emails)
  13. How Outlevo works
  14. Free ICP assessment

Related

See what Outlevo finds on your own website

Free, no sign-up, about a minute.