Hi Jaroslaw,
In this context, it's not about the ability to recognize the message, as unique
IDs and postfix long queue IDs can handle that effectively within the
200-character limit. The primary concern is having the capability to log full
header values. As Gerald illustrated with the example
;
An: "postfix-users"
Gesendet: Mittwoch, 24. Januar 2024 23:21:10
Betreff: [pfx] Re: Feature Request: Adjustable Header Log Size Limit in
INFO/WARN/REJECT Header_Check
> Viktor Dukhovni via Postfix-users :
>
> On Wed, Jan 24, 2024 at 08:27:53PM +0100, Matthias Schneider via
&g
Request: Adjustable Header Log Size Limit in
INFO/WARN/REJECT Header_Check
On Wed, Jan 24, 2024 at 03:10:03PM +0100, Matthias Schneider via Postfix-users
wrote:
> Initially, I experimented with a Milter for logging the required
> headers, but I found that employing a larger %s printf value
Initially, I experimented with a Milter for logging the required headers, but I
found that employing a larger %s printf value proved to be a more efficient
solution. However, I'd like to point out that the default configuration for
MaxMessageSize in rsyslog is often set to 8k, with the potential
Gesendet: Mittwoch, 24. Januar 2024 12:18:54
Betreff: [pfx] Re: Feature Request: Adjustable Header Log Size Limit in
INFO/WARN/REJECT Header_Check
Dnia 24.01.2024 o godz. 08:20:33 Matthias Schneider via Postfix-users pisze:
>
> Upon reviewing the code, it appears there are only one li
Hi Wietse,
I understand your perspective on format string limits throughout Postfix. I'd
like to clarify that my concern is specific to the 200-byte limit imposed on
the logging of header key/values in INFO header_check lines.
Upon reviewing the code, it appears there are only one limit on
vst
Venema via Postfix-users"
An: "Postfix users"
Gesendet: Montag, 22. Januar 2024 16:49:10
Betreff: [pfx] Re: Feature Request: Adjustable Header Log Size Limit in
INFO/WARN/REJECT Header_Check
Matthias Schneider via Postfix-users:
> Thanks for getting back to me quickly.
>
>
Thanks for getting back to me quickly.
While I understand your concerns about logging reliability, it's important to
highlight that, for some users, the log serves as the sole source of truth to
confirm whether an email was relayed or rejected in the SMTP process.
The challenge we face is the n
Hi,
i think this has something todo with smtpd_tls_fingerprint_digest:
smtpd_tls_fingerprint_digest = ${{$compatibility_level}
An: "postfix-users"
Gesendet: Montag, 22. Januar 2024 15:44:40
Betreff: [pfx] Enabling TLS1.3 and allow sending over SMTPS/465
Hi,
Two questions really, one is
Dear Postfix Developers,
I hope this message finds you well. I'm reaching out to address a concern
related to the limit for the header key/value string in the "info", "warn" and
"reject" header_check log message during the cleanup process.
The current 200-character limit, introduced in 2002 (
10 matches
Mail list logo
