Where to get deliverability help

There are lots of places to get deliverability help, I thought I’d list some of them here so I have a post to point people to.

Of course, we provide deliverability consulting services and have done since 2001. Our customers are mostly large companies sending millions of emails a month. I focus mostly on complex problems that other deliverability folks haven’t solved. Overall I focus on understanding client programs and business needs as well as current deliverability situation. Once I have a picture of a client’s program, I craft solutions that work with their business processes and get mail to the inbox. We don’t sell tools or certification. Instead, we work with our clients to help them fix delivery and teach them how to analyze the data they already have.
The nature of the work I do is intensive and I limit the number of clients I have in order to provide personalized service. But that’s OK! We have 2000+ blog posts to answer questions. And, there are lots of other companies that provide deliverability help. Here’s a partial list of places to look for resources.

Your Service Provider

Many (most?) ESPs and MTAs provide deliverability help for customers. In some cases, this is primarily self serve through their website support pages, blog posts, and knowledge bases. Other ESPs have dedicated deliverability support staff to answer questions and help customers answer questions. MTA vendors and SaaS SMTP providers also provide deliverability support.

ISPs and Filtering Companies

Many ISPs and commercial filtering companies also provide deliverability advice in their blogs. Sometimes the information on these sites is not presented in as sender friendly a way as the third parties and the ESPs. I know some of my clients have visited these websites and bristled at the tone. Nevertheless, the information is good and it’s written by the people who block mail. It’s worth looking past the tone and seeing the content.

Email Associations

Most email adjacent organizations provide deliverability resources. The EEC, M3AAWG, and the ESPC are organizations we belong to that provide free deliverability resources, many of them developed through member collaboration. Other organizations, too, have deliverability sections, I’m sure.

Governments

Many governments provide information about local laws. Not necessarily deliverability advice, but vital for successful businesses.

Third Party Tools

Gone are the days when Return Path was really the only game in town for monitoring inbox delivery. There are multiple players in the market including 250OK, GreenArrow, Postmastery and eDataSource. But not everything in email is about monitoring inbox delivery. Many other companies have email focused products and provide information on delivery and email issues including (in no particular order) places like InboxPros, Litmus, Sendforensics, dmarcian, ValiMail, Agari.
I know I’ve missed some resources, this wasn’t intended to be a comprehensive list. Just some information about where to look for deliverability help besides yours truly.

List-Unsub header
More on AOL transition to Oath Infrastructure

Related Posts

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

Filters evolving

I started writing this blog post while sitting on a conference call with a bunch of senders discussing some industry wide problems folks are having with delivery. Of course the issue of Microsoft comes up. A lot of senders are struggling with reaching the inbox there and no one has any real, clear guidance on how to resolve it. And the MS employees who regularly answer questions and help folks have been quiet during this time.

In some ways the current situation with Microsoft reminds me of what most deliverability was like a decade ago. Receivers were consistently making changes and they weren’t interacting with senders. There weren’t FBLs really. There weren’t postmaster pages. The reason knowing someone at an ISP was so important was because there was no other way to get information about blocking.
These days, we have a lot more institutional knowledge in the industry. The ISPs realized it was better to invest in infrastructure so senders could resolve issues without having to know the right person. Thus we ended up with postmaster pages and a proliferation of FBLs and best practices and collaboration between senders and receivers and the whole industry benefited.
It is challenging to attempt to troubleshoot deliverability without the benefit of having a contact inside ISPs. But it is absolutely possible. Many ISP folks have moved on over the years; in many cases due to layoffs or having their positions eliminated. The result is ISPs where there often isn’t anyone to talk to about filters.
The lack of contacts doesn’t mean there’s no one there and working. For instance, in the conference call one person asked if we thought Microsoft was going to fix their systems or if this is the new normal. I think both things are actually true. I think Microsoft is discovering all sorts of interesting things about their mail system code now that it’s under full load. I think they’re addressing issues as they come up and as fast as they can. I also think this is some level of a new normal. These are modern filters that implement the lessons learned over the past 20 years of spam filtering without the corresponding cruft.
Overall, I do think we’re in a period of accelerating filter evolution. Address filtering problems has always been a moving target, but we’ve usually been building on known information. Now, we’re kinda starting over. I don’t have a crystal ball and I don’t know exactly what the future will bring. But I think the world of deliverability is going to get challenging again.
 

Read More

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.

Read More