| | | quote | Originally posted by Cliff Pennock:
I checked today's and yesterday's mail log and found that SORBS is indeed utterly useless and the only mails it blocked where all legit emails. So I have removed SORBS from my list of blacklist databases.
|
|
I have long since removed SORBS filtering from my mail server, for the same reason. Two other reasons not to support or use SORBS:
1) Rather than just blacklist a single offending IP address or host, SORBS often blacklists the whole IP address range containing it (usually a class C, but I have seen them block an entire class A or B range). That may be what is happening with the Hotmail IPs being blacklisted. Sometimes they will blacklist an ISP's entire address block, spanning multiple class B or C ranges. See #2 below for a possible reason.
2) Apparently SORBS' business model is based on extorting a $50 "fine" for each IP address to have it removed from their blacklist, even if there was no legitimate reason for them to blacklist it in the first place. I refuse to support extortionists.
Send an e-mail from an SMTP server behind a dynamic IP address and that IP is likely to end up on the SORBS blacklist. To be fair, e-mail originating from behind dynamically-allocated IPs probably
should be subjected to more scrutiny than e-mail coming from behind static IPs, but that doesn't justify automatically blacklisting dynamic IPs. All my (legitimate) e-mail has to be relayed through one of RoadRunner's "smart forwarders" for just this reason, to prevent it from being rejected solely because my server is behind a dynamic IP.
[This message has been edited by Marvin McInnis (edited 09-02-2010).]
