Yahoo puts your emails in spam when it can't confirm they come from your domain, or when too many Yahoo users mark them as spam. Since February 2024, Yahoo has required every sender to pass SPF or DKIM and keep complaints below 0.3%, and bulk senders must also pass DMARC with an aligned From address and offer one-click unsubscribe.
Most problems are technical and can be fixed in your DNS settings. Here is what Yahoo checks, and how to find out which rule you're failing.
What Yahoo requires from every sender
Yahoo's Sender Hub lists four rules for everyone who sends to Yahoo Mail, however small:
- Authenticate with SPF or DKIM. SPF is a DNS record that lists the servers allowed to send email for your domain. DKIM is a digital signature that proves an email came from your domain and wasn't changed on the way.
- Keep spam complaints below 0.3%. That's fewer than 3 complaints for every 1,000 emails that reach the inbox.
- Send from a server with valid forward and reverse DNS. The sending server's name and address must point to each other. Your email service handles this for you.
- Follow the email standards (RFC 5321 and RFC 5322), which most email services and apps do by default.
The extra rules for bulk senders
Yahoo doesn't say how many emails make you a bulk sender. It only says a bulk sender sends a significant volume of mail. If you send newsletters, promotions or other email to a list, treat these rules as applying to you:
- SPF and DKIM must both pass, not just one.
- Publish a DMARC record. DMARC is a DNS record that tells receivers what to do with email that fails SPF and DKIM, and sends you reports. A policy of p=none is enough to meet the rule.
- Align your From address. The domain in your From address must match the domain that passed SPF or DKIM. If your email service signs with its own domain, this rule fails even though DKIM "passes".
- Offer one-click unsubscribe. Marketing and subscribed email needs a List-Unsubscribe header that supports one-click unsubscribe (RFC 8058), plus a visible unsubscribe link. Yahoo asks you to honor unsubscribes within 2 days.
- Keep complaints below 0.3%.
What happens when you fail a rule
Yahoo says mail that doesn't meet its requirements may go to the Spam folder or be rejected. If Yahoo rejects it, you get a bounce with an error code that explains why.
A separate rule applies to everyone: if your domain's own DMARC policy is p=quarantine or p=reject and your email fails DMARC, Yahoo follows your policy. That can send your own genuine email to spam, or bounce it, when a sending service isn't set up correctly.
Sending from a @yahoo.com address through another service
Yahoo publishes a DMARC policy of p=reject for its own domain. That tells Yahoo, Gmail and other mailboxes to reject email that uses a Yahoo address but wasn't sent by Yahoo's servers.
So if you use yourname@yahoo.com as the From address in a newsletter tool, a shop or a website form, the email can't pass DMARC. Some services rewrite the address to get around this. Either way, use an address at your own domain, such as hello@yourbusiness.com.
Complaints: what a test can't see
Every time a Yahoo user clicks "Spam" on your email, it counts against you. Yahoo calculates the complaint rate on email that reached the inbox.
A test email checks the technical side, but it can't measure complaints. For that, Yahoo offers a Complaint Feedback Loop through Yahoo Sender Hub. It sends you a report each time a Yahoo user marks your email as spam. To sign up, your email must be DKIM-signed by your own domain, which is one more reason to get DKIM right.
To keep complaints low:
- only email people who asked to hear from you
- remove people who unsubscribe quickly
- send what people signed up for, at the pace they expect
How to find which rule you're failing
Send one email from your usual address and service to your private test address. The report checks SPF, DKIM, DMARC, alignment and reverse DNS, and gives a verdict for Yahoo alongside Gmail, Google Workspace, Outlook.com and Microsoft 365. Each failed check comes with the exact fix.
Common fixes:
No DMARC record. Add this TXT record at _dmarc.yourbusiness.com. It starts in monitoring mode (p=none), so nothing changes for your email yet. Change the rua address to a mailbox you read; once reports show all your genuine email passing, move to p=quarantine.
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourbusiness.comDKIM signed by your email service, not by you. Turn on domain authentication in the service that sends your email, and add the DNS records it gives you. In Mailchimp, for example, that means adding two CNAME records (k2._domainkey and k3._domainkey) under Account & billing → Domains.
No SPF record, or one that doesn't list your sender. Add your email service to your SPF record using the include: value from its help pages. Keep only one SPF record for your domain.
After changing DNS, give it a little time, then send a fresh test. When the Yahoo verdict shows a pass, the technical side is done, and anything left is about complaints and list quality.
Checked against: Yahoo Sender Hub, Sender Best Practices · Yahoo Sender Hub, FAQs.