Yahoo · AOL · Sender requirements
Yahoo (and AOL) are spam-foldering or rejecting your mail: the requirements, in Yahoo's own words
Not of mail sent. Not of mail delivered anywhere. Of mail that reached the inbox. That denominator is why your platform's complaint stat can look fine while Yahoo is already foldering you.
The fast answer — Yahoo's checklist
- Authenticate everything: SPF and DKIM passing, and DMARC published (p=none minimum) that passes — relaxed alignment is acceptable to Yahoo.
- DKIM key ≥ 1024-bit (2048 recommended).
- Spam rate under 0.3% — calculated on inbox-delivered mail, continuously evaluated.
- List-Unsubscribe header on marketing/subscribed mail (a body link alone is not enough) and a visible body unsubscribe link; honour requests within 2 days; one-click (RFC 8058) highly recommended, mailto acceptable. Transactional mail is exempt.
- No whitelist exists. Yahoo says so itself. The only door is a Sender Support Request with your diagnostic/error codes.
AOL is not a separate problem: Yahoo's rules cover “all domains and consumer email brands hosted by Yahoo Mail,” AOL included.
First: are you even “bulk” in Yahoo's eyes? Almost certainly, treat yourself as yes
Yahoo's FAQ refuses a number on purpose: bulk means “a significant volume of mail,” full stop — “We will not specify a volume threshold.” Two consequences most guides miss. First, the small-sender exemption people assume from Google's 5,000/day line does not exist at Yahoo. Second, Yahoo judges at the authenticated domain level — and mail spoofed in your domain's name can count toward your enforcement review. A domain with DMARC at reject and clean reports is protected from that; a domain with nothing is exposed to strangers' behaviour. If that is you, our rollout guide just became a Yahoo fix too.
The fixes, in order
1 — Authentication that passes, not just exists
- SPF: one record, your real senders inside it (mind the lookup budget).
- DKIM: turned on for your domain with a key of at least 1024 bits — for Microsoft 365 owners this is the step that is off by default (GoDaddy / Cloudflare editions).
- DMARC: published and passing via alignment.
- Verify: send to a Yahoo address you control; the headers should show all three passing with your domain. Yahoo folds failures into its error responses — a bounce carrying an authentication/complaint error code is Yahoo telling you which requirement you missed; keep that code, it is your support currency.
2 — The complaint rate you cannot see (and how to see it)
- Accept the measurement problem honestly: Yahoo's 0.3% is computed on inbox-delivered mail, so as foldering worsens the graded rate can worsen with it — a spiral your ESP dashboard won't show you.
- Enrol in Yahoo's Complaint Feedback Loop (CFL) per Yahoo's Sender Hub instructions: complaint reports from Yahoo users come back to you as data instead of silence. (Yahoo is also rolling out Sender Hub Insights with aggregated domain statistics; enrol in what's offered for your domain rather than assuming a dashboard exists.)
- Then do the only things that move a complaint rate: mail people who asked, remove the unengaged before they complain, never buy lists, and make leaving easier than reporting — which is exactly what requirement 3 enforces.
- Verify: CFL reports arriving; complaint volume trending down over successive sends.
3 — Unsubscribe, Yahoo's way
- Every marketing/subscribed message carries a List-Unsubscribe header — header, not just the footer link; Yahoo's FAQ is explicit that the body link alone is insufficient — and keeps the visible body link too.
- Implement RFC 8058 one-click (POST) if your platform offers it (Yahoo: “highly recommended”); a mailto List-Unsubscribe is the acceptable floor. Every serious ESP supports this; if yours doesn't, that's a platform problem Yahoo will grade as yours.
- Honour every request within 2 days — Yahoo grants no grace period — including across tools: an unsubscribe in the shop platform must silence the newsletter platform.
- Verify: send yourself the message, read its headers for List-Unsubscribe and List-Unsubscribe-Post, click through, and confirm suppression inside 48 hours.
Yahoo vs Google — where they genuinely differ
| Requirement | Yahoo | |
|---|---|---|
| Bulk threshold | Refuses to specify | 5,000/day to Gmail accounts |
| Complaint ceiling | < 0.3% of inbox-delivered | 0.3% hard line, 0.1% operating target — of delivered |
| DMARC minimum | p=none, must pass; relaxed alignment OK | Required for bulk; alignment required |
| One-click unsubscribe | Highly recommended; mailto acceptable | Required for bulk marketing mail |
| TLS | Not in Yahoo's requirements | Required |
| Your visibility | CFL reports; Insights rolling out | Postmaster Tools dashboards |
The myths this guide refuses to repeat
- “Yahoo's threshold is 5,000/day.” Google's number, Yahoo's FAQ contradicts it outright.
- “Keep Yahoo complaints under 0.1%.” Yahoo publishes no 0.1% — that's Google's target wearing Yahoo's name.
- “Yahoo requires p=quarantine or reject.” That's the BIMI logo rule. The sender rule is p=none minimum, passing.
- “Yahoo requires ARC.” Yahoo recommends ARC for forwarders. Senders: recommended reading, not a requirement.
- “There's a whitelist application.” There is not. Sender Support Request, with codes, or nothing.
FAQ
My ESP shows 0.08% complaints. Yahoo still folders me. Who's lying?
Neither — different denominators. Your ESP divides by sends or deliveries; Yahoo divides by inbox-delivered mail. As foldering increases, Yahoo's denominator shrinks and your graded rate climbs. Trust Yahoo's framing when Yahoo is the judge.
Transactional mail (receipts, password resets) — same rules?
Authentication expectations apply to your domain generally, but the unsubscribe machinery is explicitly for marketing/subscribed mail; transactional is exempt from List-Unsubscribe. Don't mix marketing content into transactional streams to dodge it — receivers grade the stream, not your label.
How long until Yahoo lets me back into the inbox?
Yahoo publishes no timeline — enforcement is continuous, so recovery is earned the same way: requirements met, complaint data trending down over real sends. Anyone quoting you a fixed number of days is inventing it.
Sources
Yahoo Sender Hub (senders.yahooinc.com) — Sender Requirements & Best Practices, FAQs (bulk definition, List-Unsubscribe, complaint rate), SMTP error-code categories, Complaint Feedback Loop pages; enforcement began February 2024 with List-Unsubscribe enforcement from June 2024 · Google Email Sender Guidelines (read for the difference table) · Yahoo Sender Hub homepage (Insights announcement).
Did this guide work for you?
Your reaction tells us whether this guide solved the problem it promised to solve.