Spam Cannibal DNSBL spews false positives. Why Spam Cannibal Sucks.

If you are a system administrator thinking of adding Spam Cannibal's DNSBL to your arsenal, think again.  This list is the equivalent of using a chain saw to remove a small mole.  They block entire ranges of IP addresses. You will have to nurse this black list and constantly check for false positives.

Don't believe me. Read this thread from administrators discussing why spam cannibal sucks.

Then read this one.

And this one.

If you are on the receiving end of Spam Cannibal's bullshit, where important emails are lost just because someone you are not even associated with who is a few IP addresses away from you may have once sent a spam message, it just really sucks.

Spam Cannibal lies when they say, "The ONLY way you can get into SpamCannibal's database is by sending spam or virus ladened email to our mail servers!"

But then in their next sentence, they contradict this by saying that they block "IP addresses and ranges that have sent or relayed what we believe to be spam or other unsolicited email directly to our email servers."  So in fact, you don't have to send spam... you only have to have the misfortune of having been assigned an IP address near a spammer.

Spam Cannibal lacks the attention to detail that better lists have.  They really don't care who they hurt. They don't respect the importance of your user's communications.  They even don't provide a way to remove your IP address from this list, which is a huge failure of this DNSBL.  Clearly, they just don't give a rats ass.

If you value your time as a system administrator and your user's ability to receive email, then dump Spam Cannibal. Their approach is too random, too sporadic and unpredictable to be consistently useful. Sure Spam Cannibal keeps spam at bay, but so does just shutting off email.

There are better solutions than to use this DNSBL's careless nuclear approach to fighting email spam.