Thinking about deliverability

I was chatting with folks over on one of the email slack channels today. The discussion was about an ESP not wanting to implement a particular change as it would hurt deliverability. It led me down a path of thinking about how we think of deliverability and how that informs how we approach email.
The biggest problem I see is the black and white thinking.
There’s an underlying belief in the deliverability, receiving, and filtering communities  that the only way to affect sending behavior is to block (or threaten to block) mail.

This was true back in the ancient times (the late 90’s). We didn’t have sophisticated tools and fast CPUs. There weren’t a lot of ways to handle bad mail other than to block. Now the landscape is different. We have many more tools and the computing capacity to quickly sort large streams of data.
At most places these days, blocking is an escalation, not a warning shot. Many places rate limit and bulk folder questionable mail as a first strike against problem mail. Sometimes the mail is bad enough to result in a block. Other times, it’s not bad enough to block, so it disappears into the bulk folder.
There’s a corresponding belief in the sending community that if their behavior doesn’t result in blocking then they’re acting acceptably. This isn’t true either. There are a lot of things you can do (or not do) that don’t help delivery, but will actively harm delivery. Likewise, there are things you can do that don’t actively harm delivery, but will help. All of these things add up to reaching the inbox.

It’s all shades of grey

Things don’t happen on a short timeline. Bad email behavior might take days, weeks or even months to affect things.
Take the situation where a company buys a list and starts sending spam. On one side we have anti-spammers on the other we have marketers.
Anti-spammers often react to the spam to a purchased list with bluster and threats. This behavior is illegal! It’s against CAN SPAM! All your mail will be blocked! Your ESP will throw you off! Yeah, no. That’s not how it works back here in the real world. Purchasing lists is not illegal under CAN SPAM. Blocking might happen, but unless it’s a filthy list it’s not likely to happen the first time. Many ESPs will work with senders, requiring them to remove the purchased list but allowing them to continue mailing their regular lists. Eventually, people start ignoring the boy who cried spam.
It’s not like senders are all honest about the effects of purchased lists, either. Talk to a few marketers and they will swear blind purchased lists are great. They’re kinda right, in the short term under very specific conditions. If the sender starts out with a good reputation, makes smart purchases, and pays attention they’ll often get away with purchasing lists for a while. Eventually, though, delivery problems show up. But because the problems take so long to show up, they refuse to believe purchasing lists led to their mail going to bulk.
In both cases we have folks who aren’t looking at the whole picture. Thus, you end up with delivery folks who simplify their message to “it will hurt deliverability” when the reality is a lot more complex. Sometimes senders have a bad ideas that shouldn’t be done, even though they won’t hurt deliverability. But they won’t listen to any advice containing more realistic consequences.
 
 

Related Posts

Changing deliverability thinking

Almost every email marketing program, at least those sending millions of emails per campaign, have delivery problems at one time or another. The problems seem random and unpredictable. Thus most marketers think that they can only address delivery problems, they can’t prepare or prevent them.
On the delivery side, though, we know deliverability problems are predictable. There are situations and events in a company’s marketing program that increase deliverability risks.
I talked a little bit about this with Derek Harding at a recent conference. I started talking about my ideas that deliverability is not random and that companies need to stop treating it as unpredictable.  He pulled together a great article from our discussions. Head over to ClickZ to read about it: Take control of your email deliverability.
1540530
The predictability of deliverability is something I’m going to be writing more about in the coming months. This is, I think, the next challenge for email marketers. Figuring out how to incorporate deliverability into their overall marketing strategy. Successful programs need to take ownership of getting to the inbox. Deliverability isn’t an emergency, because it’s been planned for and managed throughout a program.

Read More

Delivery and engagement

Tomorrow is the webinar Mythbusters: Deliverability vs. Engagement. This webinar brings together the ISP speakers from EEC15, plus Matt from Comcast, to expand on their comments. There’s been some confusion about the impact of engagement on delivery and whether or not senders should care about recipient engagement.
My opinion on the matter is well known: recipient engagement drives delivery to the inbox at some providers. I expect tomorrow we’ll hear a couple things from the ISPs.

Read More

August 2017: The month in email

Hello! Hope all are keeping safe through Harvey, Irma, Katia and the aftermath. I know many people that have been affected and are currently out of their homes. I am proud to see so many of my fellow deliverability folks are helping our displaced colleagues with resources, places to stay and money to replace damaged property.
Here’s a mid-month late wrapup of our August blog posts. Our favorite part of August? The total eclipse, which was absolutely amazing. Let me show you some pictures.





Ok, back to email.
We’re proud of the enormous milestone we marked this month: ten years of near-daily posts to our Word to the Wise blog. Thanks for all of your attention and feedback over the past decade!
In other industry news, I pointed to some interesting findings from the Litmus report on the State of Email Deliverability, which is always a terrific resource.
I also wrote about the evolution of filters at web-based email providers, and noted that Gmail’s different approach may well be because it entered the market later than other providers.
In spam, spoofing, and other abuse-related news, I posted about how easy it is for someone to spoof a sender’s identity, even without any technical hacks. This recent incident with several members of the US presidential administration should remind us all to be more careful with making sure we pay attention to where messages come from. How else can you tell that someone might not be wholly legitimate and above-board? I talked about some of what I look at when I get a call from a prospective customer as well as some of the delightful conversations I’ve had with spammers over the years.
In the security arena, Steve noted the ongoing shift to TLS and Google’s announcement that they will label text and email form fields on pages without TLS as “NOT SECURE”. What is TLS, you ask? Steve answers all your questions in a comprehensive post about Transport Layer Security and Certificate Authority Authorization records.
Also worth reading, and not just for the picture of Paddington Bear: Steve’s extremely detailed post about local-part semantics, the chunk of information before the at sign in an email address. How do you choose your email addresses (assuming they are not assigned to you at work or school…)? An email address is an identity, both culturally and for security purposes.
In subscription best practices — or the lack thereof — Steve talked about what happens when someone doesn’t quite complete a user registration. Should you send them a reminder to finish their registration? Of course! Should you keep sending those reminders for 16 months after they’ve stopped engaging with you? THE SURPRISING ANSWER! (Ok, you know us. It wasn’t that surprising.)

Read More