Am 17.02.2015 um 19:14 schrieb Wietse Venema:
li...@rhsoft.net:
Am 17.02.2015 um 18:46 schrieb Wietse Venema:
li...@rhsoft.net:
is it intentional that if a message hits more than one Regex that it
creates also more than once BCC like below? it's little bit surprising
Of course. If more than one header line matches the table, then
more than one action will execute(*).
Why is that surprising?
[bcc]
header_checks works as documented. If you want a different BCC
action then it will have to have a different name.
agreed, something like BCC-FINAL to express clear the desired result
(*) The exceptions are REJECT and DISCARD which terminate further
table lookups because the decision is obviously final.
and DUNNO
Nope. As the documentation says:
DUNNO Pretend that the input line did not match any pattern, and
INSPECT THE NEXT INPUT LINE.
This is basic stuff.
well, yes, i compared the behavior with access tables like hundrets of
PTR rules with DUNNO rules on top for known false positives
