I think that I’ve now fixed this in my domain, so I thought I’d just note the
route to finding it, more as a comment on the complexity of working out what’s
going on.
After making a simple robot to send emails with long headers and demonstrating
how they broke in my production environment, I re
On 02.05.24 12:53, Tim Coote via Postfix-users wrote:
I think that I’ve now fixed this in my domain, so I thought I’d just note
the route to finding it, more as a comment on the complexity of working
out what’s going on.
After making a simple robot to send emails with long headers and
demonst
On 2024-05-02 at 07:53:15 UTC-0400 (Thu, 2 May 2024 12:53:15 +0100)
Tim Coote via Postfix-users
is rumored to have said:
What would have helped - and I’ve no idea how feasible this is -
would be some tooling to pull out different versions of the message as
they flow through the queues.
This
Wietse Venema via Postfix-users:
> Looks like there is sufficient basis to make SMTPD_QUIT_NC rerquests
> thts from Postfix. Just need to figure out how to enable/disable
> this particular command based on the Postfix and Milter protocol
> versions. There is already some 'set' intersection code for
Wietse Venema via Postfix-users wrote in
<4vvgyx1yynzj...@spike.porcupine.org>:
|Wietse Venema via Postfix-users:
|> Looks like there is sufficient basis to make SMTPD_QUIT_NC rerquests
|> thts from Postfix. Just need to figure out how to enable/disable
|> this particular command based on the
