Peter via Postfix-users:
> The download link on 
> http://ftp.porcupine.org/mirrors/postfix-release/index.html for the 
> signature file is bad.  You have 
> http://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.11.3.tar.gz.gpg3
>  
> but the link should be 
> http://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.11.3.tar.gz.gpg2

Sorry about that. I have updated both the link and the link text,
so that future mistakes will be easier to spot before uploading.

        Wietse

> Peter
> 
> 
> On 18/05/2026 02:02, Wietse Venema via Postfix-users wrote:
> > [An on-line version of this announcement will be available at
> > https://www.postfix.org/announcements/postfix-3.11.3.html]
> > 
> > Fixed in Postfix 3.8-3.11:
> > 
> >    * Bitrot: builds with musl libc broke, because they were using an
> >      obsolete NO_SNPRINTF code path that had not been updated for Claude
> >      Code findings.
> > 
> >    * Two fixes for a signed integer overshift condition (a left shift into
> >      the sign bit). This "works" on contemporary CPUs, but may break in
> >      the future. One reported by Kamil Frankowicz, and one by Robert Sayre.
> > 
> >    * Viktor Dukhovni fixed an 'uninitialized value' error in the
> >      'collate.pl' script.
> > 
> > Fixed in Postfix 3.11:
> > 
> >    * Test code fixes by Viktor Dukhovni for a deprecation warning with
> >      OpenSSL 4.0, and for a race condition that caused a test script
> >      to fail.
> > 
> > You can find the updated Postfix source code at the mirrors listed at
> > https://www.postfix.org/.
> > 
> >          Wietse
> > _______________________________________________
> > Postfix-users mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> 
> _______________________________________________
> Postfix-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to