Asking for help with a blocklist

There are often questions arising about how to go about getting off a particular blocklist. A few years ago I led the MAAWG effort to document what to if if you were On a Blocklist (pdf link). That document was aimed primarily at MAAWG members and deliverability experts with working knowledge of blocklists. I think, even now, it’s a good background on how to deal with a listing and mail being blocked.
stop_at
There have been discussions on multiple mailing lists over the last week or so about how to deal with listings at different blocklists. Many folks on these lists have extensive experience, so these are good places to ask. With that being said, a lot of the requests lack sufficient details to help.
So, if you’re ever on a blocklist and want some help from a mailing list about the problem, here’s a short guide for how to ask for help.

DO:

  • Keep the request short and concise. We don’t need 14 paragraphs about a business or how long a poster has been doing mail. Focus instead on details that people are going to need to answer the question.
  • Tell them which blocklist. “Listed by Spamhaus” isn’t a useful statement. Spamhaus runs almost half a dozen lists, all with different listing criteria. “A domain blocklist” isn’t helpful, there are dozens of lists, all with different criteria. Getting delisted on the DBL is different from getting delisted by URIBL. State the specific list involved.
  • Include the IP address. Most people people try and hide their IP address, limiting the amount of help anyone, including the blocklist folks, can give. Those folks who finally admit the IP often find very helpful answers from list members. On some lists, folks run spamtraps and are happy to share data from those feeds, even if they’re not involved in the listings.
  • Include full bounce messages, if you have them.  The messages sent during a rejected SMTP transaction are full of information about why a message was rejected. “Blocked with 554 at AOL” doesn’t tell anyone that much. “Blocked with 554 RLY:B1” at AOL tells us a lot more. Including the full message will save a lot of time in tracking down the information.
  • Include how long this has been going on. A listing that’s been up for a few weeks is different than a listing that’s been up for months. Likewise, if the listing goes away and comes back, say that.
  • Include what you’ve done to resolve it. Stating the steps already means new ideas, not the stuff already tried.

DON’T:

  • Challenge the legality of blocklists. IP based blocking using public sources of data is 2 decades old at this point. They are a part of the email ecosystem. What few cases have been brought against blocklists have reinforced their legality.
  • Get personal. This isn’t about a particular individual. All the lists used by the large mail providers are run by teams. Sometimes they are small teams, but they are teams.
  • Argue the mail isn’t spam. It may or may not be, but these arguments can go on and on and only delay actual help in the delisting process. Also, some blocklists don’t list for spam, so the argument becomes even more pointless.

If a blocklist is in wide enough use that a listing is causing delivery problems, there are a couple things this says about the list.

  1. It blocks enough bad mail to be useful
  2. It doesn’t block much good mail.
  3. The policies for listing and delisting are supported by the receivers using the list.
  4. True listing errors are corrected quickly.

There are, maybe, a dozen lists that are used widely enough to significantly affect delivery of email. There are hundreds of other lists that are less widely used. I tell clients to not worry about being on a list unless it’s actively causing delivery problems. Yes, I use some of the online tools that check hundreds of lists. But just being listed doesn’t mean there’s a problem. Likewise, folks who are on no blocklist can still have delivery problems at major providers across the net.
 

Word to the Wise provides delisting assistance as part of our consulting program. If you’re having problems with a blocklist and need advice, feel free to contact us. 

Related Posts

Thoughts on filters

One of the questions we received during the EEC16 closing keynote panel was why isn’t there a single blocklist that everyone uses and why don’t ISPs share data more. It would be so much easier for senders if every ISP handled mail the same as every other. But the world isn’t that simple, and it’s not always clear which mail stream is spam and which is good mail.

Read More

December 2014: The month in email

2014 has been a busy and exciting year at Word to the Wise (look for more on that in a year-end wrap-up post next week!) and this month was particularly thrilling for us as we officially doubled our size with the addition of Josh and Meri on our client services team.
If you’re a regular reader of our blog, you’ve probably spotted Josh’s byline on a few posts: Google’s Inbox Team answers questions on Reddit, which looks at what this new email client portends for both consumers and email marketers, and M3AAWG Recommends TLS, which reviews M3AAWG’s recommendation that mailbox providers phase out SSL encryption in favor of TLS. Look for more smart insights from Josh in 2015.
Steve contributed a post on the proper syntax for displaying a friendly email address, and a very helpful guide for generating useful test data that doesn’t compromise personally identifiable information from your actual customer data. He also detailed the brief DBL false positive from Spamhaus’ new “Abused-Legit” sub-zone and best practices for handling unrecognized responses.
I wrote about some of the subtleties inherent in how brands decide to “converse” with customers in email and other channels. We’ll just keep saying it: companies need to respect the inbox as personal space. I want to thank both Steve and Josh for picking up my slack on blogging. 7+ years is a long time to try and say new things on the blog and I needed a bit of a break.

Read More

Some email related news

A couple links to relevant things that are happening in email.
M3AAWG released the Help! I’m on a Blocklist! (PDF link) doc this week. This is the result of 4 years worth of work by a whole lot of people at M3AAWG. I was a part of the working group (“doc champion” in M3AAWG parlance) and want to thank everyone who was involved and contributed to the process. I am very excited this was approved and published so people can take advantage of the collective wisdom of M3AAWG participants.
In other announcements, Gmail announced today on their Google+ page that that they were putting a new “unsubscribe” link next to the sender name when mail is delivered to the Promotions, Social or Forums tab. This appears to be the official announcement of the functionality they announced at the SF M3AAWG last February. It likely means that all users are currently getting the “unsubscribe” link. What Gmail doesn’t mention in that blog post is that this functionality uses the “List-Unsubscribe” header, not the link in the email, but I don’t think anyone except bulk mailers really care about how it’s being done, just that it is.
Also today Gmail announced they were going to recognize usernames with non-Latin or accented characters in the name. Eventually, they claim, they’ll also allow people to get Gmail addresses with accented characters.

Read More