On 2025-10-04 at 12:34:01 UTC-0400 (Sat, 4 Oct 2025 12:34:01 -0400)
Jim Seymour via Postfix-users <[email protected]>
is rumored to have said:
Hi All,
I'm confused by this one.
First of all: It's a pretty old version of postfix, 3.1.0, but I
don't think that should matter?
You will be surprised. Bad news. Read on.
Had a pflogsumm report rejected by the local mailserver this morning.
The guilty line was one of the following two in the message reject
detail:
message reject detail
---------------------
cleanup
body (369)
...
1 <a href='http://iworklog.ru'>iworklog.ru</a>!
1 На сайте
<ahref='http://iworklog.ru'>iworklog.ru</a> ва<D0>...
(I've trimmed some of the leading whitespace.)
That's... unhelpful...
Are you entirely 100% certain that all that leading whitespace was
spaces with no tabs?
Surely you understand why I ask. But it is in fact an academic
rhetorical question.
/etc/postfix/body_checks contains:
..
# Skip pflogsumm report lines
/^ {6,11}\d{1,6}[ km] / OK
From `man body_checks`:
DUNNO Pretend that the input line did not match any pattern,
and
inspect the next input line. This action can be used to
shorten the table search.
For backwards compatibility reasons, Postfix also accepts
OK
but it is (and always has been) treated as DUNNO.
I know, shocking. I was surprised the first time I saw it too.
HOWEVER, in the same man page:
PASS optional text...
Log a "pass:" record with the optional text... (or log a
generic text), and turn off header, body, and Milter
inspection for the remainder of this message.
Note: this feature relies on trust in information that is
easy
to forge.
This feature is available in Postfix 3.2 and later.
This feature is not supported with smtp header/body
checks.
See what I mean about bad news?
--
Bill Cole
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]