Bill Cole via Postfix-users:
> > Absolutely. If you specify
> >
> > reject_rbl_client string-with-complex-syntax
> >
> > Then the rbl_reply_maps seach key will be that
> > string-with-complex-syntax.
>
> OK. Right now I have multiple items like this in
> smtpd_recipient_retrictions
>
> reject_rbl_client KEY.zen.dq.spamhaus.net=127.0.0.2
> reject_rbl_client KEY.zen.dq.spamhaus.net=127.0.0.3
> [... etc.]
In that case you need two table entries like
KEY.zen.dq.spamhaus.net=127.0.0.2 reply text...
KEY.zen.dq.spamhaus.net=127.0.0.3 reply text...
Or a pcre: table with a pattern that matches both.
/^\QKEY.(zen.dq.spamhaus.net)\E(=.*)/ 554 $rbl_class $rbl_what Blocked by
$1...
But no-one should be doing that.
> So the string being searched is 'KEY.zen.dq.spamhaus.net=127.0.0.2', but
> if I consolidated those into a single restriction:
>
> reject_rbl_client KEY.zen.dq.spamhaus.net=127.0.0.[2..11]
>
> that would then search for 'KEY.zen.dq.spamhaus.net=127.0.0.[2..11]',
> matching the existing map entry.
Indeed. Mind you, I had to do some digging myself because address
filters were added 10+ years ago, and their impact on then 10-year
old existing features was not fully documented.
Unlike rbl_reply_maps, postscreen strips the filter (and weight)
before searching the reply table. There are merits to both approaches.
Zen is a combination of XBL, PBL, and other lists. In some cases
one might want to handle XBL, PBL, etc. differently.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
