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
First, there are format string limits all over Postfix. As a matter
of principle I would not make a special case for headers.
Second, the existing 200 byte limit should be plenty sufficient to
uniqiely identify every past, present, and future email message in
this universe and in several other
Barbara M. via Postfix-users:
> Jan 23 00:11:34 auth postfix/smtpd[188544]: NOQUEUE: reject: RCPT from
> wp-host1.xyz.com[4.3.2.1]: 554 5.7.1 : Relay
> access denied; from= to=
> proto=ESMTP helo=
It this is this an INTERNAL DESTINATION, add it to main.cf:relay_domains.
relay_domains =
Dear Viktor,
Thank you for the quick reply with a solution.
Am 21.01.24 um 16:55 schrieb Viktor Dukhovni via Postfix-users:
On Sun, Jan 21, 2024 at 09:39:06AM +0100, Paul Menzel wrote:
pg.de is currently a parked domain, so our users will not going to
email there, and I would like to
Hi Wietse,
I appreciate your suggestion to use a collate script. However, the collate
script, too, relies on the logfile as a reliable source. In my case, I'm keen
on receiving the state directly from syslog, bypassing the disk.
I understand there may be some potential data loss with this
