From: W Sanders (no email)
Date: Mon Sep 01 2003 - 16:12:48 EDT
Far from me to presume anything (having launched this thread myself),
but another way to think about the multiline thing is, "Postfix DOES
match multi-line message headers. Postfix DOES NOT join continued
lines. Postfix DOES treat the entire header WITHOUT stripping out
newlines, etc, as a single string". (We define the act of "joining
continued lines" as "stripping out newlines". Postfix does not do
that.)
So /foo.*bar/ matches
foo bar
as well as
foo
bar
It's just that simple!
As far as /m being a toggle - a lot of times one "inherits" already
built versions of SW. Some people (or "bozos") like to compile program
with lots of non-default options for no reason. However, under 99% of
circumstances, /m is not used, because Postfix has been compiled by a
reasonable person.
Me, I inherited a Postfix that was built by who knows who, and in
addition the header_check file had /m after all the regexps. It took a
few minutes of trial and error to figure out that Postfix had been
compiled with default options, and that the /m's in the header_checks
file were actually broken. Now my Postfix is merrily bit-bucketing a
Sobig-infested email message about every 6 seconds =:-0
-w
|
|
|