yahoo
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: https://senders.yahooinc.com/best-practices/ Google: https://support.google.com/a/answer/14229414
On January 9th at 6pm GMT, 1pm EST and 9am 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 ESP (email service provider) Discover what adjustments you can make now to ensure your emails reach their intended inboxes in 2024 We know folks have a lot of questions about these changes and how to comply with them, so we’ve made sure to leave time for them. I’m so looking forward to this opportunity and I hope you can join us! Reserve Your Space!
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 email1 and displays a detailed report of what it finds. Details it reports on include SPF DKIM DMARC BIMI, including details about the certificate and image What IP address it was sent from, and whether it has valid DNS The size of the mail as sent (no more arguments about Gmail clipping size) The SMTP session as it was delivered The raw payload of the mail as delivered Checks for line length, non-ascii characters, non-CRLF line endings Headers, both pretty (including RFC 2047 decoded) and
On April 4, 2022, the Certified Senders Alliance invited Yahoo’s Marcel Becker and yours truly (Al Iverson) of Spam Resource to “embark upon a discussion of domain reputation” where we also talk in length about open tracking, how it wasn’t that accurate to begin with (bots mostly talking to bots) but now, with Apple’s Mail Privacy Protection (MPP), it’s even less accurate than before. That doesn’t mean you should never rely on open data to make an informed decision about an audience segment — but it does mean that you should never trust an “open” even tracked at the subscriber level, when making any sort of decision on what to do with an individual subscriber. Meaning, don’t use opens as part of your drip campaign logic to decide who gets what email — it won’t be accurate. But, for myself, I’ll continue to say that there’s a place for open
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
By Clea Moore, Principal Product Manager As we have shared in the past, our mission is to deliver messages that our users want to receive and filter out the messages they don’t. We have received a lot of questions and listened to a lot of feedback. So today we released some updates to our documentation on the Sender Hub regarding the upcoming changes in 2024. Check out our updated “Sender Requirements & Recommendations” and “FAQs” pages for more information. As a reminder, beginning in February 2024, we will be enforcing certain standards for all senders, including: Properly authenticating your mail Keeping complaint rates low The requirements for “bulk” senders will be more strict, including: Enabling easy, one-click unsubscribe (starting June 2024) Authenticating with both SPF and DKIM Publishing a DMARC policy Please make sure you are following these new guidelines, which are designed to improve the experience of our users
Did you know? You can sign up for a free att.net email account right this very second! And it’ll cost you nothing at all! I signed up for one myself, and it was a perfectly fine and easy process. Why would you want to do this? AT&T makes note of, the mailbox comes “in partnership” with Yahoo Mail, making it easy to assume that this is just a Yahoo Mail account with the att.net domain. But, those of us deliverability nerds out there remember that AT&T has some extra filtering here and there, before passing messages off to Yahoo. Or they used to. Do they still? The MX record for the various AT&T domains points to a different mail gateway — not the normal Yahoo Mail one. So the infrastructure configuration certainly implies that there could be some filtering happening a bit differently for an att.net mailbox versus a “regular”
There’s no two ways about it — it truly is getting trickier to deliver email to Gmail lately. There’s a lot going on here — from the recent past, to what’s happening today, through to the very near future. Let me jump right into it, starting with changes that are more likely to affect ESP/CRM customers, marketing senders and newsletter publishers. Get ready: the bounce apocalypse is coming. Google warned us in mid-2023 that they will now begin to disable and delete Google accounts (including Gmail accounts) after two years of inactivity. This starts December 1, 2023. Your bounce rates are likely to go up. Don’t fret — these truly are invalid, abandoned addresses. Suppressing these addresses when they bounce helps you reduce useless sending effort. There truly was nobody home. Learn more on this “digital wake up call” from fellow deliverability expert Matthew Vernhout here. “Over quota” and “out
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.
Starting February, 2024, long established email authentication best practices will become a requirement. It’s as simple as that, folks. This news may be alarming to you for a variety of reasons; you may have previously interpreted these guidelines as being optional or didn’t understand the related technical complexities. Or maybe you trusted that your email service provider, or IT Department was taking care of this for you. Whichever camp you may be in, the responsibility is yours to ensure you are compliant and have the proper visibility to maintain that favorable status from that point forward. As abuse continues to mature, so must the controls that have been implemented to secure the email channel. We applaud Google and Yahoo for ushering this new reality in much of the same way that dmarcian has always taken a standards and best practices approach. Our mission has been to spread DMARC across the