yahoogle
The worst thing about the yahoogle requirements has been their use of the term “one-click unsubscribe”. It’s an overloaded term that’s being used here to mean RFC 8058 in-app unsubscription. That’s a completely different thing to what one-click unsubscription has been used to mean for decades, often in the context of complying with legal requirements around unsubscription. It’s confusing. So here’s the simple explanation. To comply with everyone’s unsubscription requirements you need to do two things. First thing You need to have a clear link visible in the body of your message that allows users to unsubscribe. It’s the link you already have in the footer of your message: When the user clicks on it they should go to a web page. That web page must have a clear, conspicuous button that the user can click to unsubscribe. It cannot require them to provide any other information. That page can
With over nine years experience at Google, Neil Kumaran has worked across multiple teams, but always focused on things close to my heart – risk mitigation, security, safety and anti-abuse. It is thus timely that he was willing to sit down and chat with me about the upcoming new Gmail sender requirements, the initial phase of which is set to begin in February. I think it’s easy for most (good) email senders to comply. I do grant, though, that there are some number of email senders who may not be technically savvy enough to know how to implement technologies like DKIM and DMARC on their own, and that work remains to be done to help educate the world about these new requirements. Hopefully discussions like this will help. And keep an eye on Spam Resource for more help and guidance. And with no further ado, on to the interview. Hey
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
Here’s a directory of many different email service provider (ESP) links to their various guides explaining what their clients have to do to be fully compliant with the new 2024 Yahoo / Google sender requirements. Wondering how different platforms are guiding their customers? Or are you a customer of a given platform and you’re looking to find their guidance? Here you go. AWeber Beehiiv BenchmarkEmail Braze Brevo Constant Contact ConvertKit GetResponse HubSpot Klaviyo Mailchimp MailerLite MessageBird Sender Sendgrid Socketlabs There are lots more ESP/CRM platforms out there. Did I miss yours? Drop me a line via the usual means or leave a comment below with details, and I’ll update this list as I’m able.
It’s not always easy to know what the actual headers and body of an email as sent look like. For a long time accepted wisdom was that you could send a copy to your gmail account, and use the Show Original menu option to, well, see the original message as raw text. It turns out that’s not actually something you can trust. I used swaks to send a test message with an extra header to my gmail account. swaks –to wttwsteve@gmail.com –from steve@blighty.com –add-header “List-Unsubscribe: =?us-ascii?Q?=3Cmailto=3Asteve=40blighty.com=3e?=” Code language: JavaScript ( javascript ) We can see swaks sending it: -> DATA Date: Wed, 17 Jan 2024 08:49 :59 -0800 -> To: wttwsteve @gmail.com -> From: steve@blighty.com -> Subject: test Wed, 17 Jan 2024 08:49:59 -0800 -> X-Mailer: swaks v20130209.0 jetmore.org/john/code/swaks/ -> List-Unsubscribe: =?us-ascii?Q?=3Cmailto=3Asteve=40blighty.com=3e?= -> Code language: CSS ( css ) But when we then go to gmail and click on Show
Hey there! In my new role as Director of Deliverability for AWeber, I’m going to dive right in! I’m putting together a new webinar AS WE SPEAK, that covers everybody’s favorite topic — DKIM, DMARC, YAHOO, GMAIL & YOU! Also known as: what you need to do to comply with Yahoo and Google’s new sender requirements. Because this is focused on AWeber customers, I’ll cover everything from where and how to buy a domain name for your email messages (and why you have to), how to link that up to your AWeber account to correctly authenticate your email sends, how to configure and implement a DMARC record, and more! And I’ll take your questions, too! I hope you’ll join me alongside Jesse Kennedy to learn more about these very important bits for email sending success! The fun happens Wednesday, January 17th at 12:00 eastern. Click here to register.
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 significant volume of mail. We will not specify a volume threshold.”. So … do you need to count how many messages you send, to see if Google thinks you’re a bulk sender or not? No. Definitely not. Google state a threshold just so they don’t have to argue about the definition of “bulk sender”, I’m sure. In practice they’ll be using the same definition as bulk sender as Yahoo – we know it when we see it. But the real distinction isn’t volume – it’s whether you’re professional, grown-up sender or a hobbyist. If
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 significant volume of mail. We will not specify a volume threshold.”. So … do you need to count how many messages you send, to see if Google thinks you’re a bulk sender or not? No. Definitely not. Google state a threshold just so they don’t have to argue about the definition of “bulk sender”, I’m sure. In practice they’ll be using the same definition as bulk sender as Yahoo – we know it when we see it. But the real distinction isn’t volume – it’s whether you’re professional, grown-up sender or a hobbyist. If
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
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