SORBS is way too restrictive

RBLs enable mail admins to automatically block incoming mail based on DNS lookups. But I noticed that my MTA was again blocking Google and Hotmail completely, again due to the overly restrictive SORBS blacklist. This is inacceptable collateral damage, so I suggest you don’t use SORBS if you intend to receive mail from large-scaled customer sites. SpamAssassin still gives scores for that blacklist, but not enough to trigger a blocking by only that single list.

Posted by Stephan Paukner in Information Technology at 05:30 | Comments (2) | Trackbacks (0)

Defined tags for this entry: anti-spam

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

Martin Leyrer on :

I have quite good results with dnsbl.sorbs.net list.dsbl.org No false positives so far. Any further RBLs you could recommend?

Stephan on :

Well, my Postfix log summary (pflogsumm) says that dnsbl.sorbs.net blocked hotmail.com and google.com. I was also using dul.dnsbl.sorbs.net. Anyway, that list wasn’t blocking much at all recently, within 5 days about 60-90 connections. list.dsbl.org even only ~3. Much more hits gain bl.spamcop.net (~1700) and zen.spamhaus.org (~1000), but I can’t promise that these aren’t too restrictive as well. I also use blackholes.mail-abuse.org dialups.mail-abuse.org pbl.spamhaus.org for DUL blocking, but I don’t know whether they trigger at all.

Add Comment

Name

Homepage

Comment

In reply to

Phone*

What is one plus eight?

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.

Standard emoticons like :-) and ;-) are converted to images.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA