TagYahoo

3 months ago

Effects of the Yahoo and Google Changes

By laura

2 Min read

Add comment

23January

In October 2023, Yahoo and Google announced new standards for sending bulk mail to their systems. For bulk senders these changes included requiring aligned authentication and publishing a DMARC record and complying with the List-Unsubscribe RFC. The ISPs also formally announced complaints must stay below a threshold of 0.3%. At the time of the announcement, they said enforcement would start in...

January 5, 2024

Are you a grown-up sender?

By steve

2 Min read

Add comment

05January

Yes, it’s another yahoogle best practices post. Google divide their requirements for senders into those sending more than 5,000 messages a day, and those sending less. Yahoo divide their requirements into “All Senders” and “Bulk Senders”, and explicitly don’t define that via a volume threshold: “A bulk sender is classified as an email sender sending a...

January 4, 2024

Yahoogle FAQs

By steve

1 Min read

Add comment

04January

Just a very, very short post with links to the Yahoo and Google requirements FAQs. Given I can’t ever remember them I’m guessing lots of y’all can’t either.

Yahoo: and :

January 3, 2024

Answers to your questions about the new Yahoo and Google technical requirements

By laura

1 Min read

Add comment

03January

On January 9th at 6pm GMT, 1pm EST and 10am PST I’ll be speaking with Nout Boctor-Smith of Nine Lives Digital about the new Yahoo and Google technical requirements. In this webinar you’ll: Learn more about what these new email sender guidelines entail and how they differ from the status quo  Understand why you’re being asked to do things that were previously handled by your...

January 2, 2024

About My Email

By steve

2 Min read

3 comments

02January

Happy 2024, everyone! We’ve released a shiny new tool to let folks self-check a lot of common questions we see about email requirements. Go to AboutMy.email and send an email to the email address it gives you. Once it receives that email it will go through it and do many of the basic checks we’d usually do to check the technical health of a client’s email1AboutMy.email is a...

November 9, 2023

Yahoogle Requirements Update

By steve

1 Min read

Add comment

09November

Since I wrote about it last month the requirements for bulk senders to Yahoo and Google have changed a little.

The big change is that bulk senders need to authenticate with both SPF and DKIM, rather than SPF or DKIM. Only one of those has to align with the 822 From: header.

October 18, 2023

Wildcards and DKIM and DMARC, oh my!

By steve

5 Min read

1 comment

18October

If you’re an ESP with small customers you may have looked at the recent Google / Yahoo requirements around DMARC-style alignment for authentication and panicked a bit. Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy, and impersonating Gmail From: headers might impact your email delivery.…For direct mail, the domain in the...

October 3, 2023

New Requirements for Bulk Senders

By steve

3 Min read

8 comments

03October

UPDATE: You need to authenticate with both DKIM and SPF. Google are circulating a new set of requirements for bulk senders on their blog. So are Yahoo. It’s almost like postmasters talk to each other or something. If you dig through the links in the Gmail blog post you can find this summary of what they’ll be requiring from bulk senders by February: Set up SPF or DKIM email...

May 30, 2023

Unresolvable RFC.5321 domain at Yahoo

By steve

5 Min read

1 comment

30May

Seen this recently? 451 Message temporarily deferred due to unresolvable RFC.5321 from domain; see This is Yahoo doing some extra work to identify that the 5321.From domain1The return-path, aka the 821.From, 5321.From, or bounce address is the email address you send from at the protocol level, not the email address in the From: header, and it’s the address any bounces will be sent to. of...

May 30, 2022

Message not compliant with the RFCs

By laura

3 Min read

1 comment

30May

Every once in a while we’ll see a rejection from Yahoo that says RFCs 554 5.0.0 Message not accepted due to failed RFC compliance. What does that mean and what can we do about it? It really does mean exactly what it says on the label: there’s something about the message that is not in compliance with any number of RFCs and are not going to accept the message in its current state. When...