tagg...@riseup.net wrote:
Hi SA users,
In the past (3.2.5 or so) I used to be able to use local.cf to override
rule settings like this,
header __RCVD_IN_ZEN eval:check_rbl('zen', 'zen.dnsbl.')
header RCVD_IN_XBL eval:check_rbl('zen-lastexternal',
'zen.dnsbl.', '127.0.0.[45678]')
header RCVD_IN_PBL eval:check_rbl('zen-lastexternal',
'zen.dnsbl.', '127.0.0.1[01]')
uridnsbl URIBL_SBL` sbl.dnsbl. TXT
(I am changing the host used for lookups to a local host)
but now (3.3.1) those seem to be ignored in favor of the default settings.
Did this behavior change?
Not that I know of - in fact I do exactly this for Spamhaus here as
well. I also put the local IP and URI blacklists under .dnsbl in the
same rbldnsd instances.
Try a simple rule in local.cf:
body TESTME /./
that should hit on everything. If that doesn't hit, you're looking at
the wrong copy of local.cf.
spamassassin -D should show you the directories SA is reading for your
channel and local rules.
I started working on a different solution (proposed by Kevin Olson @
mxtools) of cloning the rules with a different name, changing those, and
disabling the main rules. But the problem with that is that there are lots
of rules that depend on these particular rule names which break. I could
close those as well, but likely there are things that depend on them as
well and the end result is a complete mess that's hard to maintain.
If your cloned rules work with the alternate zone name, but the altered
stock rule doesn't, you've probably got a typo somewhere.
(I actually override the Spamhaus rules in a local rules channel, which
I set up because I was distributing the rules to 6 machines at the time.
I named starting with zzz to make sure it loaded *after* the stock
rules. The Spamhaus rules have been working for two years like this now.)
-kgd
