On 2023-12-10 at 16:16:27 UTC-0500 (Sun, 10 Dec 2023 22:16:27 +0100)
Carlos Velasco via Postfix-users <carlos.vela...@nimastelecom.com>
is rumored to have said:
Wietse Venema via Postfix-users escribió el 10/12/2023 a las 21:53:
2. the "own Received" header not being passed to milter. I
understand
it works as expected, but could be great to be able to decide this
with a configuration parameter.
That is because every Milter in the real world gets the client info
from the smfi_connect() callback function and from Milter macros,
instead of parsing Received: headers.
That statement is absolutely false.
Quite a bold choice there...
Many milters, like amavisd, use other filters for mail content
inspection, like SpamAssassin. Spamassassin uses the "Received"
headers for some tasks, like this:
https://cwiki.apache.org/confluence/display/spamassassin/TrustPath#
As a contributor & PMC member for both SpamAssassin (definitely not a
milter) and MIMEDefang (definitely a milter, which uses SpamAssassin) I
assure you that the Received header which notionally reflects the
current transaction DOES NOT exist when the milter gets the message
data, and for SA to do its "trust path" audit of Received headers, the
MIMEDefang milter MUST construct one for SA to use.
Amavis is slightly different because it can be used as a SMTP proxy
(between 2 Postfix smtpd processes) or a milter. When used as a proxy,
it sees the whole message with the locally-added Received headers. When
used as a milter, it works with what Postfix provides it (the relevant
macros) to construct a Received header for SA.
All of this is documented accurately.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
