Purchased lists and ESPs: 9 months later

It was about 8 months ago I published a list of ESPs that prohibit the use of purchased lists. There have been a number of interesting responses to that post.
thumbsup
ESPs wanted to be added to the list
The first iteration of the list was crowdsourced from different ESP representatives. They shared the info they had with each other. With their permission, I put it together into a post and published it here. Since then, I’ve had a trickle of ESPs asking to be added to the list. I’m happy to add any ESP. The only requirement is a privacy policy (or AUP) that states no purchased lists.
People reference the list regularly
I’ve had a lot of ESP deliverability folks send thanks for writing this post. They tell me they reference it regularly when dealing with clients. It’s also been listed as “one of the best blog posts of 2015” by Pardot.
Some 2016 predictions build on the post
I’ve read multiple future predictions that talk about how the era of purchased lists is over. I don’t think they’re wrong. I think that purchased lists are going to be deliverability nightmares on an internet where users wanting a mail is a prime factor in inbox deliverability. They’re already difficult to deliver, but it’s going to get worse.
Thumbsdown
Not everyone thinks this is a good post. In fact, I just recently got an comment about how wrong I was, and… well, I’ll just share it because I don’t think my summary of it will do it any justice.

Laura,
It seems as though you are just disguising your real intention, by giving the reader a misguided title, that allows your sponsors to be noticed, and you to make money from their advertising dollars. Let’s be clear that the attack on purchased lists is an attack on small business. Not all companies have the resources to build a list in the “proper” way, one way to cost effectively jump start their business is through starting with said “improper” methods.
Your article’s title is misleading and directed to the politically correct business environment ruining this country. It would be nice to publish an article about ESP’s that allow purchased lists, as your title implies.
I will bet we never see that article, considering that you will lose sponsors and the intent of yours or any business, making money.
It is equivalent that if our Lady Liberty had a marketing message “give me your well, rich and privileged marketeers, the rest of you wretched refuse, need not apply”
Do the right thing! Write the intended article!

I do know there are ESPs who allow purchased lists. Most of the time I know of them because they, or their customers, come to me to fix deliverability issues. There is a limit to what I can do. ISPs expect opt-in mail. Business filters expect opt-in mail. Purchased lists are not opt-in. Some filters and ISPs specifically state that senders should not use purchased lists when sending to those ISPs.
I do my best for clients, and for one or two I’ve helped them create programs that get to the inbox at least some of the time. Our rare successes are in very specific, small, niche markets where our forensic approach to deliverability creates a mailing program that works for the senders and doesn’t annoy recipients enough to cause delivery problems.  More often, though, there isn’t a fix. Clients aren’t willing to stop buying addresses or even undertake the hard work to transition to an opt-in program.
downwardSpiral
For ESPs the it’s even a more difficult business model transition. Some ESPs discover early on that purchased lists are a problem and stop allowing them. Others end up relying on the revenue and can’t disconnect customers using purchased lists. The result is predictable, and I’ve watched multiple ESPs go through this.

  • ISPs start filtering or blocking mail from the ESP IP addresses or mentioning the ESP anywhere in the email.
  • Good customers start looking for new solutions, as their deliverability is suffering. Revenues start dropping.
  • Spamhaus lists some or all of the ESP IP ranges on the SBL.
  • More customers leave for better ESPs.
  • Customers who are purchasing lists can’t move, so the bulk of revenue now comes from companies using purchased lists.
  • ESP notices the significant downturn in revenue and hires outside help (me!) to fix the problem.
  • I work with ESP to try and maintain revenues enough to keep the business running while getting rid of the bad customers.

At this point there are basically two places the ESP can go.

  1. Bite the bullet, go into debt, clean up and start attracting back good customers.
  2. Decide they can’t manage the change and continue mailing purchased lists and accepting their poor deliverability.

The reality is purchased lists are hard to deliver. They cost more than just the initial purchase price. They’re problematic for most ESPs. Some ISPs specifically call out purchased lists as no-nos for inbox delivery. The best managed purchased list programs get to the inbox some of the time. But it’s only going to get harder and harder to reach that purchased inbox moving forward.

Related Posts

This is why the ISPs throw up their hands at senders

I recently saw a question from an ESP rep asking if anyone had a personal contact at a particular ISP. The problem was that they had a rejection from the ISP saying: 571 5.7.1 too many recipients this session. The ESP was looking for someone at the ISP in order to ask what the problem was.
This is exactly the kind of behaviour that drives ISPs bonkers about senders. The ISP has sent a perfectly understandable rejection: “5.7.1: too many recipients this session.” And instead of spending some time and energy on the sender side troubleshooting, instead of spending some of their own money to work out what’s going on, they fall back on asking the ISPs to explain what they should do differently.
What, exactly, should you do differently? Stop sending so many recipients in a single session. This is not rocket science. The ISP tells you exactly what you need to do differently, and your first reaction is to attempt to mail postmaster@ the ISP and then, when that bounces, your next step is to look for a personal contact?
No. No. No.
Look, connections and addresses per connections is one of the absolute easiest things to troubleshoot. Fire up a shell, telnet to port 25 on the recipient server, and do a hand SMTP session, count the number of receipts. Sure, in some corporate situations it can be a PITA to do, sometimes you’re going to need to get it done from a particular IP which may be an interface on an appliance and doesn’t have telnet or whatever. But, y’know what? That Is Your Job.  If your company isn’t able to do it, well, please tell me so I can stop recommending that as an ESP. Companies have to be able to test and troubleshoot their own networks.
Senders have been begging ISPs for years “just tell us what you want and we’ll bother you less.” In this case the ISP was extremely clear about what they want: they want fewer recipients per connection. But the ESP delivery person is still looking for a contact so they can talk to the ISP to understand it better.
This is why the ISPs get so annoyed with senders. They’re tired of having to do the sender’s job.

Read More

Abuse it and lose it

Last week I blogged about the changes at ISPs that make “ISP Relations” harder for many senders. But it’s not just ISPs that are making it a little more difficult to get answers to questions, some spam filtering companies are pulling back on offering support to senders.
For instance, Cloudmark sent out an email to some ESPs late last week informing them that Cloudmark was changing their sender support policies. It’s not that they’re overwhelmed with delisting requests, but rather that many ESPs are asking for specific data about why the mail was blocked. In December, Spamcop informed some ESPs that they would stop providing data to those ESPs about specific blocks and spam trap hits.
These decisions make it harder for ESPs to identify specific customers and lists causing them to get blocked. But I understand why the filtering companies have had to take such a radical step.
Support for senders by filtering companies is a side issue. Their customers are the users of the filtering service and support teams are there to help paying customers. Many of the folks at the filtering companies are good people, though, and they’re willing to help blocked senders and ESPs to figure out the problem.
For them, providing information that helps a company clean up is a win. If an ESP has a spamming customer and the information from the filtering company is helping the ESP force the customer to stop spamming that’s a win and that’s why the filtering companies started providing that data to ESPs.
Unfortunately, there are people who take advantage of the filtering companies. I have dozens of stories about how people are taking advantage of the filtering companies. I won’t share specifics, but the summary is that some people and ESPs ask for the same data over and over and over again. The filtering company rep, in an effort to be helpful and improve the overall email ecosystem, answers their questions and sends the data. In some cases, the ESP acts on the data, the mail stream improves and everyone is happy (except maybe the spammer). In other cases, though, the filtering company sees no change in the mail stream. All the filtering company person gets is yet another request for the same data they sent yesterday.
Repetition is tedious. Repetition is frustrating. Repetition is disheartening. Repetition is annoying.
What we’re seeing from both Spamcop and Cloudmark is the logical result from their reps being tired of dealing with ESPs that aren’t visibly fixing their customer spam problems. Both companies are sending some ESPs to the back of the line when it comes to handling information requests, whether or not those ESPs have actually been part of the problem previously.
The Cloudmark letter makes it clear what they’re frustrated about.

Read More

Email filters

What makes the best email filter? There isn’t really a single answer to that question. Different people and different organizations have different tolerances for how false positives versus false negatives. For instance, we’re quite sensitive to false positives here, so we run extremely conservative filtering and don’t block very much at the MTA level. Other people I know are very sensitive to false negatives and run more aggressive filtering and block quite a bit of mail at the MTA level.
For the major ISPs, the people who plan, approve, design and monitor the filters usually want to maximize customer happiness. They want to deliver as much real mail as possible while blocking as much bad mail. Blocking real mail and letting through bad mail both result in unhappy customers and increase the ISP’s costs, either through customer churn or through support calls. And this is a process, filters are not static. ISPs roll out new filters all the time, sometimes they are an improvement and sometimes they’re not. When they’re not, they’re pulled out of production. This works both for positive filters like Return Path and negative filters like blocklists.
Then there is mail filtering that doesn’t have to do with spam. Business filters, for instance, often block non-business mail. Permission of the recipient often isn’t even a factor. Companies don’t often go out of their way to block personal mail, but if personal mail gets blocked (say the vacation plane ticket or the amazon receipt) they don’t often unblock it. But when you think about why a business provides email, it makes perfect sense. The business provides email to further its own business goals. Some personal usage is usually OK, but if someone notices and blocks personal email then it’s unlikely the business will unblock it, even if the employee opted in.
In the case of email filters, the free market does work. Different ISPs filter mail differently. Some people love Gmail’s filters. Other people think Hotmail has the best filtering. There are different standards for filtering, and that makes email stronger and more robust. Consumers have choices in their mail provider and spamfiltering.

Read More