Good morning,
out of curiosity, does it possibly -if implemented- break ARC signature
creation of e.g. rspamd, which seems to use auth-info?
ARC-Authentication-Results: i=1;
ORIGINATING;
auth=pass smtp.auth=u...@doma.in smtp.mailfrom=u...@doma.in
Or is this transferred via MILTER protocol instead?
Florian
Am 04.02.2025 um 23:09 schrieb Wietse Venema via Postfix-users:
ellie via Postfix-users:
I sent a test mail to a throwaway account now, and found the according
log entry! The one you wanted was gone since I happened to have reboot
with wiped logs since then. I hope it shows something helpful :-o sorry
again for the effort.
OK, so I have forgotten how Postfix works. The header_checks parameter
is not used in the SMTP daemon (smtpd). It is used in the cleanup
daemon, which is a different service that handles mail from inside
and outside of Postfix.
Technically, it is still possible with header_checks but it becomes
absolutely non-trivial which is not good. Postfix was supposed to
be easier to use than the alternatives at the time that Postfix
was created.
I will implement Ellie's request, and move the Postfix 3.10 code
freeze up by a few days.
smtpd_hide_session_info (default: no)
Hide SMTP session info from the Received: message header. Do not
record the SMTP client name or IP address, SASL login name, or TLS
session details. This reduces the Received: header from:
Received: from <client name/address, SASL login, TLS details>
by servername (Postfix) with XXXX id yyy; server-date-stamp
to:
Received: by servername (Postfix) with XXXX id yyy; server-date-stamp
This means that if an account is compromised the message will have no
trace to the evil-doer. Only the server logs will have that. So don't
wipe the logs on reboot.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
