Gmail, Yahoo and Outlook sender requirements in 2026, with the errors they return
Gmail, Yahoo and Outlook.com reject or junk mail from domains that skip their authentication rules [2][5][6]. Since November 2025, Gmail has been ramping up enforcement, and mail that misses its requirements gets temporary and permanent rejections [2]. Outlook.com rejects the same gap with 550 5.7.515 [6].
The short answer
Gmail and Yahoo ask every sender for SPF or DKIM, valid forward and reverse DNS, and a spam rate below 0.3% [1][4]. Bulk senders to Gmail, Yahoo and Outlook.com also need both SPF and DKIM, a DMARC record of at least p=none, and a From domain aligned with SPF or DKIM [1][4][6]. Gmail also requires TLS [1].
What the rejections look like
Gmail’s codes and texts come from its SMTP error reference [3]. Each block below is the first part of the text on that page, with the reply code in front and an ellipsis (…) where the page goes on.
A message with neither SPF nor DKIM passing, from any sender:
A bulk sender whose message fails SPF, or fails DKIM:
A bulk sender whose domain has no DMARC record:
Gmail’s FAQ gives the temporary version of this error as 4.7.31 [2], while its error reference lists 4.7.40 [3].
A From address that matches neither the SPF domain nor the DKIM domain, as a temporary error:
A sending IP without a matching PTR record:
Outlook.com, for a high-volume domain that misses Microsoft’s authentication rules [6]:
The requirements side by side
| Requirement | Gmail | Yahoo | Outlook.com |
|---|---|---|---|
| SPF or DKIM, every sender | Required [1] | Required [4] | Not listed below the bulk threshold [6] |
| Forward and reverse DNS (PTR) for sending IPs, every sender | Required [1] | Required [4] | Not listed [6] |
| TLS, every sender | Required [1] | Not listed [4] | Not listed [6] |
| Spam rate | Below 0.3%, every sender [1] | Below 0.3% [4] | Not listed [6] |
| SPF and DKIM both, bulk senders | Required [1] | Required [4] | Both must pass [6] |
| DMARC record, bulk senders | Required, p=none is enough [1] |
Required, at least p=none, and DMARC must pass [4] |
Required, p=none in Microsoft’s example [6] |
| From domain aligned with SPF or DKIM, bulk senders | Required [1] | Required, relaxed alignment accepted [4] | Required [6] |
| One-click unsubscribe, bulk marketing mail | Required, plus a visible link in the body [1] | A List-Unsubscribe header is required (RFC 8058 POST highly recommended, mailto: accepted), plus a visible link in the body [4] |
Recommended: a working unsubscribe link [7] |
| Unsubscribes honored | Recommended within 48 hours; without it, no delivery support [2] | Within 2 days [4] | Not listed [6] |
| Message format | RFC 5322 [1] | RFC 5321 and RFC 5322 [4] | Not listed [6] |
Who counts as a bulk sender
- Gmail: anyone who sends close to 5,000 messages or more to personal Gmail accounts in 24 hours [2]. That is how the FAQ defines a bulk sender; Google’s sender guidelines put the line at more than 5,000 messages a day [1]. Mail from subdomains counts toward the main domain, and a sender that crosses the line once stays a bulk sender for good [2]. The rules cover mail to personal accounts, those ending in
@gmail.comor@googlemail.com, and do not apply to mail sent to Google Workspace accounts [1][2]. - Yahoo: Yahoo says it “will not specify a volume threshold” [5].
- Outlook.com: domains that send 5,000 or more messages to Microsoft’s consumer services (Outlook.com, Hotmail, Live.com, MSN), all with the same domain in the From address [6]. Microsoft’s 2025 announcement put the line at more than 5,000 messages a day [7]; its current support page says 5,000 or more messages and gives no time window [6]. The April 2025 update to that announcement says non-compliant messages are rejected with
550 5.7.515, starting 5 May 2025 [7], and the support page describes that rejection today [6].
What each requirement means for your DNS
SPF and DKIM
Both are DNS records on your domain. SPF lists the servers that may send with your domain in the envelope sender, and DKIM publishes the key that checks each message’s signature. Gmail requires a DKIM key of 1024 bits or longer and recommends 2048 [1]. Yahoo requires a key of 1024 bits or longer and recommends 2048 [5]. The details are in the SPF guides and the DKIM guides.
DMARC
The minimum that all three accept:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
p=none means the domain owner “offers no expression of preference” [9], so this record meets the requirement without asking receivers to block anything. Yahoo strongly recommends the rua tag so you receive reports [4]. A DMARC record at none does not stop anyone from sending as your domain [9]. To raise the DMARC policy safely, follow from p=none to p=reject.
Alignment
Alignment means the domain in the visible From address matches the SPF or DKIM domain. In relaxed mode, the default, the two only need the same organizational domain [9]. Mail with From: news@example.com and an envelope sender at bounce.example.com is aligned. Mail whose SPF and DKIM domains both belong to your email service is not aligned, and Gmail answers it with 4.7.32 [3].
PTR and TLS
If a provider sends your mail, its servers carry the PTR record and the TLS setup. If you run your own server, both are your job: see running your own mail server in 2026.
One-click unsubscribe
Gmail requires bulk senders to include both of these headers in marketing and subscribed messages [1]:
List-Unsubscribe: <https://example.com/unsubscribe/opaque-id>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
RFC 8058 requires the List-Unsubscribe header to contain one HTTPS URI, and the message to carry a valid DKIM signature that covers both headers [8]. Transactional mail, such as password resets and reservation confirmations, does not need one-click unsubscribe [2].
What a DNS check can see, and what it cannot
DNS shows your SPF, DKIM and DMARC records and where they point. It does not show:
- Your spam rate. Gmail measures it in Postmaster Tools [1], which also has a compliance status dashboard for these requirements [2].
- Your unsubscribe headers and TLS. Both live in the messages and the connection. Look at the headers of a message you sent to a Gmail account.
- The PTR records of your provider’s sending IPs. They belong to whoever owns those IPs.
Gmail’s own DMARC policy
Google warns that “Gmail will begin using a DMARC quarantine enforcement policy” and that impersonating Gmail From headers might affect delivery [1]. Google’s FAQ describes the case: a message with a Gmail address in the From header that was not sent from a Gmail server [2].
Mistakes to avoid
- Thinking the rules start at 5,000 messages. SPF or DKIM, forward and reverse DNS, and the spam rate apply to every sender at Gmail and Yahoo, and TLS to every sender at Gmail [1][4].
- Publishing DMARC only on a subdomain. A receiver looks for the record at the From domain and then walks up toward the organizational domain [9]. A record at
_dmarc.news.example.comdoes nothing for mail fromexample.com. - Offering unsubscribe only by
mailto:. Yahoo accepts it, but Gmail requires one-click unsubscribe [1][4], and RFC 8058 one-click needs an HTTPS URI [8]. - Letting your email service sign with its own domain. SPF and DKIM pass, alignment fails, and Gmail answers with
4.7.32[3]. Set up DKIM with your domain in the service’s settings. - Treating
p=noneas protection. It meets the requirement and expresses no preference about forged mail [9].
Check your domain against the DNS requirements
The checker reads your domain’s SPF, DKIM and DMARC records from your browser and tells you which of the DNS requirements above it meets.
Runs in your browser. Your domain is not sent to this site or stored.
Related guides
From DMARC p=none to p=reject without blocking your own mail
Move DMARC from p=none to quarantine and then reject without losing real mail. What to fix first, how long to wait, and how t=y, pct and subdomains behave.
SPF permerror: too many DNS lookups, and how to get back to 10 or fewer
Your SPF record gets 10 DNS lookups. The eleventh turns the result into permerror. Count yours, find the costly includes and cut them without breaking mail.
Running your own mail server in 2026: what it takes to get delivered
A self hosted email server needs a static IP, matching PTR and open port 25. It also needs TLS, SPF, DKIM, DMARC and a clean blocklist record. What each costs.
