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 to increase it
to 64k when using TCP. Therefore, the syslog aspect can handle larger messages
effectively.
The issue I've been grappling with is more centered around the 200-character
limit in the %.200s format, rather than any limitations imposed by syslog.
I already use long queue IDs for unique identification of Mail transactions,
and that's totally fine, its just about to have the ability to log custom
headers without a small size limit. The current limit is also missing in the
header_checks documentation (i totally agree that there _must be_ a limit)
I hope this provides a clearer perspective.
Best regards,
Matthias Schneider
----- Ursprüngliche Mail -----
Von: "Wietse Venema via Postfix-users" <postfix-users@postfix.org>
An: "Postfix users" <postfix-users@postfix.org>
Gesendet: Mittwoch, 24. Januar 2024 14:37:34
Betreff: [pfx] Re: Feature Request: Adjustable Header Log Size Limit in
INFO/WARN/REJECT Header_Check
1) You can log full headers with a Milter. You will run into the
length limit of the syslog() client (historically, 2 kBytes) before
the Milter protocol limit (64 kBytes) which is less than the Postfix
header_size_limit (default: 102400).
2) You can uniqely identify all Postfix transactions with a long
Postfix queue ID. There is no need to log the same large header
upon entry and exit.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
