Richard Frovarp writes:
> I am trying to go through and remove some of the DNSBL lookups that are
> being performed. I have found previous posts that state just set the
> meta rule to a score of 0 to disable. I have also found previous posts
> that state only these evals are performing lookups: check_rbl,
> check_rbl_txt and check_rbl_envfrom. And that check_rbl_sub do not
> perform a lookup, but use previous rules. What about check_rbl_accreditor?
>
> Furthermore, looking in 20_dnsbl_tests.cf I see this:
>
> header __RCVD_IN_NJABL eval:check_rbl('njabl',
> 'combined.njabl.org.')
> header RCVD_IN_NJABL_DUL eval:check_rbl('njabl-lastexternal',
> 'combined.njabl.org.', '127.0.0.3')
> header __RCVD_IN_SORBS eval:check_rbl('sorbs',
> 'dnsbl.sorbs.net.')
> header RCVD_IN_SORBS_DUL eval:check_rbl('sorbs-lastexternal',
> 'dnsbl.sorbs.net.', '127.0.0.10')
> header __RCVD_IN_SBL_XBL eval:check_rbl('sblxbl',
> 'sbl-xbl.spamhaus.org.')
> header RCVD_IN_XBL eval:check_rbl('sblxbl-lastexternal',
> 'sbl-xbl.spamhaus.org.', '127.0.0.[456]')
>
> Am I missing something? It seems to me that all of the -lastexternal
> lines will perform duplicate DNS lookups from the previous line, perhaps
> just a little bit later. I of course run a caching name server, but it
> does seem to be an extra query and those lines could be changed into
> check_rbl_sub.
if I recall correctly, or at least this is the case in 3.2.0, the shared
lookups will be performed once and the result shared between *both*
RCVD_IN_XBL and __RCVD_IN_SBL_XBL.
--j.
