On Tue, Feb 17, 2015 at 06:52:59PM +0100, li...@rhsoft.net wrote:
> >>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 because in
> >>all known cases the first rule hit's and the evaluation of the file is
> >>stopped
Message don't hit header check rules, individual header lines do.
> >On a per-header line basis. Postfix header checks are *simple*
> >---------------------------
>
> not sure how the word simple is meant in the context
> "it's intentional" or "it's not intentional" would be clearer
Simple means "naive", "minimal", ..., stateless machine looks
at each header-line in isolation.
> simple in the from all are proceeded or simple in the form stop after the
> first one hits like OK / DUNNO which is not the case
for each header line {
for each rule in table {
if rule matches {
perform-action
break
}
}
}
Table matches short-circuit remaining rules for the *current* header
only.
> fact is that both fire:
> /^X\-Spam\-Flag: Yes/ BCC spamfil...@rhsoft.net
> /^X\-Spam\-Report:.*(BAYES_50)/ BCC spamfilter+inbox...@rhsoft.net
One for the first header, and one for the second.
--
Viktor.
