I'm using in my main.cf:
reject_rbl_client zombie.dnsbl.sorbs.net,
reject_rbl_client relays.ordb.org,
reject_rbl_client opm.blitzed.org,
reject_rbl_client list.dsbl.org,
reject_rbl_client sbl.spamhaus.org,
Please do not use spamcop.net it has many many false positives.
Regards,
Leon Kolchinsky
-----Original Message-----
From: Quinn Comendant [mailto:[EMAIL PROTECTED]
Sent: Monday, November 27, 2006 11:07 PM
To: SpamAssassin Users
Subject: Re: rbl insight and wisdom please
I'm using the following with qmail's rblsmtpd:
-r zen.spamhaus.org
-r bl.spamcop.net
-r relays.ordb.org
-r cbl.abuseat.org
I do find it very hard to determine if a list is "malfunctioning" and honest
emails are blocked until clients start complaining. It has happened before with
me using other blocklists.
One idea just popped into my head: you can grep your logs for all IP addresses
you trust (mail from the IPs of trusted users and their recipients) and run
that list of IPs against an DNSRBL you are considering using.
You can test a DNSRBL by reversing an IP and appending the RBL domain, so for
111.122.133.144, you might execute:
dig 144.133.122.111.zen.spamhaus.org A | grep -v '^;'
And if there is anything returned, the IP is on the list.
Quinn
On Mon, 27 Nov 2006 12:42:40 -0800, R Lists06 wrote:
> Hopefully this hasn't been rehashed to death on this list yet has there ever
> been a general consensus as to which rbl's and similar lists are best to use
> if you are going to engineer your mail systems with such?
>
> Anyone care to share their implementations as well as current best and worst
> practices please?
>
> Thanks
>
> - rh
>
> --
> Robert - Abba Communications
> Computer & Internet Services
> (509) 624-7159 - www.abbacomm.net
>
>
>
