Skip to content
All articles

Deliverability · 17 November 2026 · 8 min read

Gmail, Yahoo and Outlook sender requirements: a practical checklist

Rampsend team

What inbox providers require

In February 2024, Gmail and Yahoo started enforcing a shared set of rules for anyone sending email to their users. Microsoft followed for Outlook.com in May 2025. Together they cover most consumer inboxes, so in practice these rules are now the baseline for every sender, not a niche concern for large mailers. The good news is that the list is short and mostly a one-off setup job. This post turns all three providers' requirements into a checklist you can work through in an afternoon.

Who the rules apply to

The providers split senders into two groups.

All senders. Anyone sending to a personal Gmail account must meet a basic set of rules regardless of volume: authenticate with SPF or DKIM, have valid forward and reverse DNS for sending servers, use TLS, keep the spam rate under 0.3% and format messages according to RFC 5322.

Bulk senders. Google defines a bulk sender as one that has sent close to 5,000 or more messages to personal Gmail accounts in a single day, counting all mail from the same primary domain. Once you cross that line you are treated as a bulk sender permanently, even if your volume later drops. Yahoo applies the same requirements without publishing a fixed number. Microsoft's rules apply to domains sending more than 5,000 messages a day to Outlook.com, Hotmail.com and Live.com addresses.

Two things follow. First, the 5,000 counts all mail from your domain, transactional and marketing together. Second, the bulk rules are cheap to meet, so most teams treat them as the standard from day one rather than waiting to be caught by the threshold.

The requirements side by side

RequirementGmail (bulk)Yahoo (bulk)Outlook.com (high volume)
SPFRequiredRequiredRequired (must pass)
DKIMRequiredRequiredRequired (must pass)
DMARC recordAt least p=noneAt least p=noneAt least p=none
AlignmentFrom domain aligned with SPF or DKIMFrom domain aligned with SPF or DKIMAligned with SPF or DKIM, ideally both
One-click unsubscribeRequired for marketing, honoured within 2 daysRequired, honoured within 2 daysFunctional unsubscribe link recommended
Spam complaint rateBelow 0.3%, aim for 0.1%Below 0.3%No published number; list hygiene expected

The primary sources are Google's email sender guidelines and Yahoo's sender best practices. Microsoft published its rules on its Defender for Office 365 blog in April 2025.

The checklist

Work through these in order. Each item builds on the one before.

1. Send from your own domain

Every requirement below is about your domain's reputation, so mail has to come from a domain you control: hello@acme.eu, not a free mailbox address. Sending "from" a Gmail or Yahoo address through a third-party service will fail DMARC alignment, and providers such as Yahoo publish a strict DMARC policy for their own domains that tells receivers to reject exactly that kind of message.

2. Publish SPF

SPF lists the servers allowed to send for a domain. The check runs against the envelope sender (the Return-Path, also called MAIL FROM), not the visible From address. That detail matters for alignment in step 5.

3. Sign with DKIM

DKIM adds a cryptographic signature to each message, which receivers verify against a public key published in your DNS. Use 2048-bit keys where your DNS provider supports them. Your sending platform signs; you publish the key records it gives you.

4. Publish a DMARC record

DMARC tells receivers what to do when a message fails authentication, and where to send reports. The minimum record is:

DNS
_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

p=none meets the requirement without affecting delivery. The rua address receives aggregate reports, which show who is sending mail using your domain and whether it passes. Read them for a few weeks before tightening the policy.

5. Make sure the From domain aligns

Alignment is the requirement people most often miss. DMARC passes only if SPF or DKIM passes for a domain that matches your From domain. If your platform signs with its own DKIM domain and uses its own bounce domain for SPF, both checks can pass while DMARC still fails.

The fix is to have DKIM sign with your domain, and to use a custom MAIL FROM subdomain such as mail.example.com so SPF passes for your organisational domain too. The SPF, DKIM and DMARC setup guide walks through both, with example records.

6. Add one-click unsubscribe to marketing mail

Gmail and Yahoo require bulk marketing and subscription mail to support one-click unsubscribe as defined in RFC 8058. That means two headers:

HTTP
List-Unsubscribe: <https://example.com/unsubscribe/abc123>, <mailto:unsubscribe@example.com?subject=abc123>List-Unsubscribe-Post: List-Unsubscribe=One-Click

The mail client sends a POST to the HTTPS address when the recipient clicks "unsubscribe" next to your name. Your endpoint has to process it without asking the person to log in or confirm. Gmail also expects a clearly visible unsubscribe link in the message body.

Transactional mail such as receipts and password resets is exempt from Google's one-click rule, but the line between transactional and marketing is easy to blur — see transactional vs marketing email. If in doubt, add the header.

7. Honour unsubscribes within two days

An unsubscribe has to take effect within two days. The simplest way to guarantee that is a suppression list that every send checks automatically, so an unsubscribed address can never be emailed again by any tool or script. The suppression list guide explains how to build one that holds up.

8. Keep spam complaints low

Google's ceiling is 0.3%, measured in Postmaster Tools as user-reported spam divided by mail delivered to the inbox. The practical target is under 0.1%, about one complaint per thousand. Senders who stay above 0.3% lose eligibility for mitigation from Google when they run into delivery problems.

The levers are permission, expectations and an unsubscribe that is easier to find than the spam button. Bounce and complaint rates covers how the rate is calculated and when to stop sending.

9. Format messages correctly

Valid RFC 5322 messages, a real From name, a monitored Reply-To, no deceptive subject lines, and no impersonating Gmail in the From header. Microsoft's guidance also asks for valid, working From and Reply-To addresses.

10. Monitor

Verify your domain in Google Postmaster Tools to see your Gmail spam rate and authentication results. Microsoft offers SNDS for IP-level data. Gmail does not send per-message complaint reports to senders, so Postmaster Tools is the only place you see the Gmail rate.

What happens if you do not comply

Enforcement started gently. In 2024 Gmail returned temporary errors on a small share of non-compliant traffic, then increased the share and moved to rejections. Microsoft announced that non-compliant mail would first go to Junk, then switched to outright rejection with the error 550 5.7.515 Access denied, sending domain does not meet the required authentication level.

In practice, a sender who misses the requirements sees one of three things: mail rejected at the door, mail landing in spam, or mail delivered fine to one provider and failing at another. The last one is the most confusing, which is why monitoring per provider matters.

How Rampsend maps to the checklist

If you send through Rampsend, most of the setup is done when you verify a domain. Under Deliverability → Domains the app gives you the DKIM records to publish, a custom MAIL FROM subdomain so SPF aligns with your From domain, and a DMARC record to add. An AI assistant connected over MCP can run check_domain and tell you which record is still missing.

For unsubscribes, set unsubscribe_header: true on a send and Rampsend adds the RFC 8058 headers. Unsubscribes, hard bounces and complaints are suppressed automatically, and suppressed recipients are skipped and not charged. If bounce or complaint rates spike, sending pauses itself before the damage spreads. The developer docs list every send option.

The short version

Meeting these rules is a one-off job: publish three kinds of DNS records, add one header to marketing mail, honour unsubscribes promptly and watch your complaint rate. Senders who do it rarely think about the requirements again. Senders who do not tend to find out from a sudden drop in opens or a wall of bounce messages. If you are setting up a new domain, pair this checklist with a sensible warm-up plan so your first large sends build reputation instead of spending it.

Frequently asked questions

Do the Gmail and Yahoo rules apply if I send fewer than 5,000 emails a day?

Some do. Every sender to Gmail needs SPF or DKIM, valid reverse DNS, TLS and a spam rate under 0.3%. The stricter rules (both SPF and DKIM, DMARC, alignment, one-click unsubscribe) apply to bulk senders, but meeting them anyway costs little and protects you as you grow.

Is DMARC p=none really enough?

For the requirement, yes: a published DMARC record at p=none passes. It does not protect your domain from spoofing, though. Move to quarantine and then reject once your reports show all legitimate mail passing.

Do transactional emails need a one-click unsubscribe?

Google's rule targets marketing and subscribed messages; receipts, password resets and similar transactional mail are exempt. Adding the header to anything that is not strictly transactional is still the safer default.

What happens if I do not comply?

Non-compliant mail is increasingly rejected or sent to spam. Gmail started with temporary errors in 2024 and has tightened enforcement since; Microsoft rejects non-compliant high-volume mail to Outlook.com with a 550 5.7.515 error.

How do I check my spam complaint rate at Gmail?

Verify your domain in Google Postmaster Tools. It shows the user-reported spam rate for mail to Gmail recipients, which your sending platform cannot see directly.