emailrules.today

Providers · verified 4 Aug 2026

Yahoo

Yahoo Mail, AOL and the rest of the Yahoo estate, which share one sender policy and one postmaster team.

senders.yahooinc.com/their postmaster page

What they published

In their own words.

  • All senders need SPF or DKIM; bulk senders need both, plus DMARC that passes.

    “Publish a valid DMARC policy with at least p=none - DMARC must pass”

    Yahoo Sender Hub, Best practices · publisher states no date

  • Unsubscribes must be honoured within two days.

    “Honor unsubscribes within 2 days”

    Yahoo Sender Hub, Best practices · publisher states no date

  • One-click unsubscribe is required, and Yahoo names the POST method specifically.

    “The Post (RFC 8058) method is highly recommended”

    Yahoo Sender Hub, Best practices · publisher states no date

  • Reputation attaches to the IP and to the DKIM domain — Yahoo names both.

    “Each IP and DKIM domain has a reputation, which can impact the delivery of your email”

    Yahoo Sender Hub, Best practices · publisher states no date

  • Marketing and user mail should not leave from the same IPs.

    “Don't send bulk/marketing email from the same IPs you use to send user mail”

    Yahoo Sender Hub, Best practices · publisher states no date

The numbers

Only the ones they printed themselves.

The negative space

2 things everybody repeats that Yahoo has never said.

An absence is harder to check than a claim, so each one links the page where you can confirm the words are not there — and where Yahoo states outright that it will not publish something, that refusal is quoted.

  • There is a safe number of concurrent connections to Yahoo.

    Yahoo says in as many words that it will not tell you. Every connection-limit number in circulation is somebody's measurement of their own traffic on one day, repeated until it sounded official.

    “while we do not publish specific guidelines for the numbers of connections you can concurrently use”

    Yahoo Sender Hub, Best practices · publisher states no date

  • Yahoo publishes a messages-per-connection limit.

    It states that a limit exists and does not give the number. Treat any specific figure as folklore, and read the deferral codes your own MTA is receiving instead.

    Yahoo Sender Hub, Best practices · publisher states no date

Getting unblocked

The removal path, and whose job it is to file it.

Every delisting guide tells you where the form is. The half nobody prints is whether you can complete it: on a shared sending pool the listed address is your platform’s and the submission is theirs to make, so a marketer sent to the form arrives without the one thing it asks for.

  • Yahoo's sender support form, through the Sender Hub. There is no self-service portal that removes a block on its own.

    senders.yahooinc.com/

    Part platform, part you

    On a shared pool the listed address belongs to your sending platform and only they can file for it. On a dedicated IP it is yours. Check which you are on before filling in anything.

    Yahoo Sender Hub, Best practices · publisher states no date

The dated rules behind this

A quote wrong, a path moved, or something Yahoo has said that is missing here? corrections@emailrules.today. Corrections are published and dated on /corrections, never quietly swallowed.

FAQ

Awkward questions

Who is this actually for?

People who ship email and are too busy to re-read every PDF: week-one marketers, lifecycle/CRM, deliverability, multi-country ops, DTC brands, agencies — on Klaviyo, Mailchimp, Braze, HubSpot, SFMC, or something else. Pick your tool and geos so product-specific pages only appear when they match. EU and UK are first-class filters. Not for people who sell tools about email and need a fake score to demo.

Why only ~40 rules? Isn’t that… thin?

On purpose. A wall of 400 undated “best practices” is how you look busy and still get burned. Every page needs a primary source we actually read. Thin and checkable beats fat and folklore. Europe, bulk inbox rules, measurement honesty, and protocol topics like BIMI/DMARC policy are on the shelf when we can cite them — not every Member State and not every vendor myth. Coverage map lists what we still refuse to invent.

Is this legal advice?

No. If it were, you’d have a billable hour and a longer PDF. This is a dated operator reference written by an email geek. Confirm anything high-stakes with counsel who knows your facts. Same for “will this make me compliant?” — no tool does that. Lawyers and judges do. We say what the sources say and what to do first on Monday.

Why no trust score out of 100?

Because we refuse to invent a number you can’t audit. Fake scores sell seed tests and panic. You get findings, dates, and links. If that feels less exciting than a red dial, good — you’re not the red-dial customer.

Why should I trust you more than my ESP’s blog?

ESPs sell seats. Seed-score vendors sell fear. AI invents citations when nobody watches. We sell nothing today — no pixels, no placement scores, no affiliate — so we can say when a tool is the problem. A human verifies, dates, and corrects in public. Tools may help draft; they do not ship unsourced claims. Check the primary links. Fail that test and leave.

Do I need an account?

No. Filters live in this browser and the URL. Share the link. That’s it. Accounts come later only if they earn it — not so we can nurture you about email.

I’m an agency. Where’s multi-client mode?

We tried a client-name CRM on the setup card. It made the product feel like work before it felt useful. Role filters + copy link + one-page brief (optional PDF title) is enough for now. Complexity comes back when the free shelf is habit, not before.

Is the quiet changelog a bug?

No. Quiet means nothing material moved. We don’t invent urgency so the homepage looks “alive.” Sticky risks still show what usually needs a person when the market is still.