Regarding that loop termination condition, you wrote up a long
explanation, which means this code will need to be simplified or
else there will be mistakes (if not now, then in the future). Postfix
is about not writing clever code.
I took a little time to fix the delivered_hdr.c code, so now I
Hi,
FYI I wrote the same thing ages ago, and eventually backed it out.
It did make it simpler to correlate the error message with the original
message, even for myself, and I like to think I'm good at dealing with
mail.
But unfortunately it also made it simpler to accidentally delete the
Hello Wietse,
On 21/09/2020 17:12, Wietse Venema wrote:
> I am not opposed to making bounces thread-friendly, but I wonder,
> Postfix includes a copy of the undelivered message, why is it
> difficult to find out what message was not delivered? Are mail
> systems routinely deleting that
I am not opposed to making bounces thread-friendly, but I wonder,
Postfix includes a copy of the undelivered message, why is it
difficult to find out what message was not delivered? Are mail
systems routinely deleting that information, because spam?
The code is not bad for a rusty C programmer.
Hi,
I had a few users explain that the bounces they sometimes get are so
hard to understand...
To make life easier for them I added some messages to the templates so
that they can read their errors in their native language. That helped,
but users were still not always clear, which specific
