Tales from Tech Support – SORBS Escalated Listings

We have been contacted by a few people last week about a small peak in the number of legitimate emails blacklisted by SORBS, which I believe was caused by escalated listings (see the blog post of SORBS for details). Though we discourage using the escalated zone of SORBS because of the higher chance for false positives (we removed response from the DNSBL definition shipped with ORF a long time ago), some folks still have it enabled.

In short, ISPs do not care much if a paying customers is spamming until the whole IP block gets blacklisted by a DNSBL and other (innocent) customers start to complain. I do not think it’s the ideal way of doing things (i.e. to force the ISPs to get rid of spammers by blacklisting innocent people), on the other hand, I totally understand SORBS and other DNSBLs: they simply have no other choice if the ISP ignores their reports of abuse.

What do you think?

1 thought on “Tales from Tech Support – SORBS Escalated Listings

  1. CCPD

    I’ve removed SORBS escalated lists from all of my clients ORF deployments. SORBS is way over the top and causes far too many false positives. If they keep doing what they are doing, they will become impotent, because IT administrators are going to get tired of all the “So-and-so can’t email me!” complaints from their clients.

Leave a Reply

Your email address will not be published. Required fields are marked *

AlphaOmega Captcha Classica  –  Enter Security Code