[pfx] Re: Potential bug in milter interface, can't change first header field

Taco de Wolff via Postfix-users: > Thanks Wietse and Steffen, I forgot to mention that I'm using Postfix > 3.5.8, but it appears the bug is thus still present in the latest version. > Looking forward to the fix :-) Another solution is to adopt Postfix 3.9 (the development release) where this was

[pfx] Re: Potential bug in milter interface, can't change first header field

Taco de Wolff via Postfix-users wrote in : |Thanks Wietse and Steffen, I forgot to mention that I'm using Postfix |3.5.8, but it appears the bug is thus still present in the latest version. |Looking forward to the fix :-) | |@Steffen, that is genius and hadn't thought of it. I can confirm

[pfx] Re: Potential bug in milter interface, can't change first header field

Thanks Wietse and Steffen, I forgot to mention that I'm using Postfix 3.5.8, but it appears the bug is thus still present in the latest version. Looking forward to the fix :-) @Steffen, that is genius and hadn't thought of it. I can confirm that issuing two modifications works as expected. The

[pfx] Re: Potential bug in milter interface, can't change first header field

Taco de Wolff via Postfix-users wrote in : |While writing a milter for use with Postfix, I was unable to change the |first header field and instead of changing it, Postfix appends it to the |end of the header. Incidentally, as I believed this was a bug with the insheader with index 0 worked

[pfx] Re: Potential bug in milter interface, can't change first header field

The Postfix Milter implementation is sometimes inconsistent about the "first" header so that it can sometimes not be updated. The fix below was in the queue for Postfix 3.5 - 3.8 a few days before the SMTP smuggling shitshow happened. The last SMTP smuggling patch was released on January 21. For

[pfx] Potential bug in milter interface, can't change first header field

Hi, While writing a milter for use with Postfix, I was unable to change the first header field and instead of changing it, Postfix appends it to the end of the header. Incidentally, as I believed this was a bug with the milter library, I rewrote the milter server implementation from scratch and

[pfx] Re: Postconf.5 smtp_tls_loglevel 2

Viktor Dukhovni via Postfix-users: > On Wed, Feb 21, 2024 at 08:32:49AM +, Rune Philosof via Postfix-users > wrote: > > It seems a bit unclearly phrased > > > 2 Also log levels during TLS negotiation. > > Indeed this is not very helpful. See the description of the "-L" option > in

[pfx] Re: Postconf.5 smtp_tls_loglevel 2

On Wed, Feb 21, 2024 at 08:32:49AM +, Rune Philosof via Postfix-users wrote: > It seems a bit unclearly phrased > > 2 Also log levels during TLS negotiation. Indeed this is not very helpful. See the description of the "-L" option in . > Should

[pfx] Postconf.5 smtp_tls_loglevel 2

It seems a bit unclearly phrased > 2 Also log levels during TLS negotiation. Should it be > 2 Also log certificate trust\-chain verification errors even if server > certificate verification is not required ___ Postfix-users mailing list --