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

DNSBLs, wildcards and domain expiration

Last week the megarbl.net domain name expired. Normally this would have no affect on anyone, but their domain registrar put in a wildcard DNS entry. Because of how DNSBLs work, this had the effect of causing every IP to be listed on the blocklist. The domain is now active and the listings due to the DNS wildcard are removed.

Read More

Fake DNSBLs

Spamhaus recently announced a few years ago that they have discovered a company that is pirating various blocklists, relabeling them and selling access to them. Not only is the company distributing the zones, they’re also running a “pay to delist” scheme whereby senders are told if they pay money, they’ll be removed from the lists.
The fake company does remove the listing from the fake zones, but does nothing to remove the IP from the original sender. This company has been caught in the past and was blocked from downloading Spamhaus hosted zones in the past, but have apparently worked around the blocks and are continuing to pirate the zone data.
It’s not clear how many customers the blocklist has, although one ESP rep told me they were seeing bounces referencing nszones.com at some typo domains.
No legitimate DNSBL charges for delisting. While I, and other people, do consult for senders listed on the major blocklists, this is not a pay for removal. What I do is act as a mediator and translator, helping senders understand what they need to do to get delisted and communicating that back to the blocklist. I work with senders to identify good, clean addresses, bad address segments and then suggest appropriate ways to comply with the blocklist requirements.

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