Many organizations use deliverability as a data point when selecting an email service provider. Unfortunately there are a number of myths about deliverability and especially about the role of deliverability staff at ESPs.<\/p>\n\n\n\n
Some are out of date, some are misconceptions and some are untruths spread by competitive ESPs. But all of them really deserve to be dispelled.<\/p>\n\n\n\n\n\n\n\n
I want to be clear that I am not knocking deliverability staff or the ESPs they work for. I know many of them very well and they\u2019re fine folks doing sterling work for great organizations. When selecting an ESP though, companies should clearly understand what they are and are not getting.<\/p>\n\n\n\n
As with all these myths there is some truth to this, but there\u2019s far more to the situation. It varies a little from ESP to ESP but historically deliverability was an internal, behind the scenes role. Many deliverability people were systems engineers, email postmasters or anti-spam activists before they got into deliverability. Deliverability staff were mostly hired to protect the ESP from its own customers.<\/p>\n\n\n\n
Job #1 was to keep bad customers off the ESP\u2019s network. Bad actors can damage an ESP\u2019s reputation and that of their other customers. For most customers if there\u2019s one thing worse than being blocked for your own activity it\u2019s being blocked for someone elses. So identifying and preventing bad actors and bad behaviors is still the primary job for deliverability teams.<\/p>\n\n\n\n
Bad delivery has a tendency to upset customers and so assisting customers with delivery has become job #2 for deliverability staff. However there is often a disconnect between what customers think \u201cdeliverability troubleshooting and issue resolution\u201d means and what deliverability staff think it means.<\/p>\n\n\n\n
Deliverability troubleshooting means using email deliverability testing tools<\/a>, figuring out what went wrong, everyone agrees on that, though there is often some misunderstanding about how that should be done and how quickly it can be achieved (see Myth #3). The major disconnect though is on resolution.<\/p>\n\n\n\n Companies tend to think resolution is about the ESP changing things \u2013 ISP whitelisting, blocklist delisting etc.. Deliverability people know that resolution is primarily about education and subsequent behavior modification. For sure, a good deliverability person can help you get an SBL (Spamhaus Blocklist) entry removed.<\/p>\n\n\n\n But first they\u2019ll want to ensure that the underlying cause of the listing has been fixed because they know that\u2019s what Spamhaus requires and because they know the listing will simply return if it\u2019s not done. If you\u2019re thinking that resolution means fixing messes without you changing your practices, it\u2019s time to think again.<\/p>\n\n\n\n Though this may have been true once upon a time, today it\u2019s most definitely what you know not who you know. Spam filtering systems are complex and automated. The days when an individual postmaster would personally blacklist your IPs or personally whitelist them are long gone.<\/p>\n\n\n\n Once upon a time knowing the right people at the major ISPs, and more importantly being respected in the industry mattered. It could get you the benefit of the doubt or enable cutting the queue when trying to resolve issues. Today those right people have been replaced at the ISPs by algorithms so you\u2019ll just have to hang on to that box of meat<\/a>.<\/p>\n\n\n\n The deliverability staff at an ESP do matter, but if your ESP evaluation<\/a> has a checkbox that asks for personal relationships with ISPs you\u2019re asking the wrong questions.<\/p>\n\n\n\n This myth sadly was cultivated in large part by the ESPs themselves. Once upon a time there were so many ESPs that didn\u2019t really know what they were doing that deliverability could be a competitive differentiator and it was used as such.<\/p>\n\n\n\n The reality though is that there are no secret handshakes or deliverability tricks known only to insiders and there never were. There are still ESPs that don\u2019t get the basics right of email authentication<\/a> and platform management and whose deliverability is worse for it, but if you\u2019re looking for a deliverability edge you\u2019re looking in vain.<\/p>\n\n\n\n<\/span>Myth #3: Deliverability is about relationships<\/span><\/h2>\n\n\n\n
<\/span>Myth #4: Some ESPs have a secret sauce<\/span><\/h2>\n\n\n\n
<\/span>What is the ESP with the best deliverability?<\/span><\/h2>\n\n\n\n