Zane C.B. | 14 May 22:16

Re: whitelisting

On Wed, 14 May 2008 17:05:18 -0300
Leonardo Rodrigues Magalhães <leolistas <at> solutti.com.br> wrote:

> 
> 
> Zane C.B. escreveu:
> > I have tried below, but I keep finding that it does not work and I
> > keep having to comment out the last two RBLs.
> >
> > smtpd_sender_restrictions = 
> >     check_recipient_access
> > hash:/usr/local/etc/postfix/access.smtpd_sender_restrictions,
> > reject_rbl_client bl.spamcop.net, reject_rhsbl_sender
> > rhsbl.sorbs.net, reject_rbl_client sbl-xbl.spamhaus.org,
> >     reject_rbl_client smtp.dnsbl.sorbs.net,
> >     reject_rbl_client virbl.dnsbl.bit.nl,
> >     reject_rbl_client virus.rbl.msrbl.net,
> >     reject_rbl_client web.dnsbl.sorbs.net,
> >     reject_rbl_client spam.dnsbl.sorbs.net,
> >     reject_rbl_client dnsbl-2.uceprotect.net,
> >     reject_rbl_client dnsbl-3.uceprotect.net
> >
> >   
> 
>     i had bad experiences with uceprotect.net .... their RBLs seems
> to have high false positive rates, which makes me stop using them.
> Anyway, sometimes some of my customers get flagged on their RBL,
> which causes me some problems with not sending message to some
> servers who use them.
> 
>     i would recommend you to definitely stop using them or any
> other RBL that lists network blocks instead of individual addresses.
> 
>     and change sbl-xbl.spamhaus.org by zen.spamhaus.org, which is 
> sbl-xbl plus pbl.
> 
> http://www.spamhaus.org/ZEN/


Cool. I will look into that.

I have found the cause of the problem. It turned out
check_recipient_access was being used instead of check_sender_access.

Gmane