https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7783
Bug ID: 7783
Summary: check_rbl and rule redefinition
Product: Spamassassin
Version: 3.4.3
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Rules
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: Undefined
Hello,
I have two different SA installations, 3.4.2 and 3.4.3 . Both have this rule
redefinition:
header __RCVD_IN_ZEN eval:check_rbl('zen','<key>.zen.dq.spamhaus.net.')
header __RCVD_IN_ZEN_LASTEXTERNAL eval:check_rbl('zen-lastexternal',
'<key>.zen.dq.spamhaus.net.', '^127\.0\.0\.([2-9]|10|11)$')
What happens is that in 3.4.3 the rule __RCVD_IN_ZEN still uses
zen.spamhaus.org despite being redefined, while in 3.4.2 it works as expected.
I found this workaround for 3.4.3:
header __RCVD_IN_ZEN eval:check_rbl('zendqs','<key>.zen.dq.spamhaus.net.')
header __RCVD_IN_ZEN_LASTEXTERNAL eval:check_rbl('zendqs-lastexternal',
'<key>.zen.dq.spamhaus.net.', '^127\.0\.0\.([2-9]|10|11)$')
that is, using another name for the 'set' parameter in check_rbl. Doing this
the rule __RCVD_IN_ZEN is being correctly redefined and does the lookups only
on the .dq.spamhaus.net zone.
Looks like if that I use the same 'set' name as a rule loaded before my custom
redefinition, that earlier 'set' takes precedence.
Is that an expected behaviour or am I doing something fundamentally wrong?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
