Word to the Wise helps email marketers create more effective email messages, programs and infrastructures. We advise you how to skillfully navigate the constant business, technology, and policy challenges so your messages reach your customers.
We can help you with your email strategy, deliverability challenges and many other email issues.
Six years ago today I wrote here “Spam isn’t going away“, talking about systemic problems at Google, Cloudflare and Amazon and in India. If I were writing it today I might mention Microsoft, Salesforce and ExactTarget as well as Google, and might stress Amazon less (mostly because all the Amazon spam sites tend to be hidden behind Cloudflare, so you don’t know...
TXT Records DKIM public keys live in DNS TXT records. A DNS TXT record contains strings of text, and each string is limited to be no more than 255 characters long. Recommended practice for DKIM at the moment is to use 2048 bit keys (1024 bit keys aren’t insecure, but they’re looking a bit weak and 2048 is where folks have mostly decided to move to). But a 2048 bit DKIM key is going to...
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...
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...
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...
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 :
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...
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...
Meanwhile…
I apparently gave chess.com an email address in 2007 – probably due to a client engagement? I don’t know. I unsubscribed from their mail at some point as there has only been one email from them between 2010 and 2021. Maybe this time they’ll actually unsubscribe me.
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.
RSS - Posts