bulk sender guidelines
Here is everything you need to know (I think? I hope?) about how to comply with the new sender requirements announced by Google and Yahoo, applying to Gmail and Yahoo mail, coming into force in early 2024. You can read more about it all here (and over at Yahoo or Google), but it boils down to a handful of things that were previously best practice recommendations for deliverability excellence, which are now requirements that these two mailbox providers are saying that senders must implement. Those that don’t implement these requirements risk being blocked and unable to send mail to Yahoo Mail and Gmail subscribers. Here are the ten steps you need to take, that if you follow these all the way through, you’ll be fully compliant with the new requirements. Stop sending newsletter/marketing/bulk mail as Gmail or Yahoo. For your 1:1 email messaging where you respond to emails from your
I’ve got some important info for you today (and a reminder of two free webinars; one recorded, one upcoming and live) related to all of this. First, Yahoo and Google are both indicating that the compliance deadlines for their upcoming new sender requirements are changing. Yahoo is indicating that authentication requirements and low complaint rates must be met by February 2024, but that one-click unsub now has an implementation deadline of June, 2024. Publishing a DMARC policy and authenticating with both DKIM and SPF seems to be required as of February 2024. (More info here.) Google is indicating that “enforcement for bulk senders that don’t meet our email sender guidelines will be gradual and progressive. Starting in February 2024, senders out of compliance are likely to see light and intermittent temporary deferrals. Starting in April, that’ll change to rejections instead of deferrals, and they’ll increase the percentage of non-compliant mail
If you dig into the newly published upcoming sender requirements from Google, you’ll unearth three points that relate to DMARC. These are important enough that I wanted to highlight them specifically.First, note that Gmail is moving to a “p=quarantine” policy for gmail.com. That means it is no longer safe to send mail as (anything)@gmail.com except when doing so via Gmail’s infrastructure. This new policy update is Google telling the world to spam filter mail that says it’s from a gmail.com email address, but doesn’t pass email authentication tests. This is a big deal. Gmail, Yahoo, and many other mailbox providers are going to filter unauthenticated messages much more harshly as a result.My memory’s a little fuzzy, but I remember a freemium SMB-focused ESP that had a free “newsletter service” that I think they’ve long since shut down. The platform let you send as yourself, so they served up an awful
On Tuesday, October 3, Google and Yahoo announced updated sender requirements for those who wish to send mail to Gmail or Yahoo Mail successfully and in volume. Marcel Becker from Yahoo and Neil Kumaran from Google explain in detail what senders will have to do if they don’t want to find their mail blocked at either mailbox provider. They warn that failure to comply will result in rejected mail in early 2024.Any changes here really are evolutionary more than revolutionary. These have been solid “best practice” recommendations for a good long while; so I think of this as both “documenting what everybody knows” and laying the groundwork for reasoned, documented policy-based blocking of non-conforming mail. Those requirements boil down to this:Authenticate email. We were moving to a point where you basically already had to authenticate your email messages if you wanted inbox placement success; now it’s fair to say that it
