ANNOUNCE: fetchmail 6.4.26 is available (Serbian translation updates, workaround added for some servers when wolfSSL 5.0.0 is used)

Matthias Andree <[email protected]> Sun, 26 Dec 2021 22:56:12 +0100
Newsgroups gmane.mail.fetchmail.announce
Message-ID <Ycjk/O4Y1TWp8q/[email protected]>
--===============9209774978370367015==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="c62aoxun7T5Hye4H"
Content-Disposition: inline


--c62aoxun7T5Hye4H
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

The 6.4.26 release of fetchmail is now available at the usual locations,
including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>.

DISTRIBUTORS please note OpenSSL's licensing change for OpenSSL 3,
and you may want to review COPYING. NOTE that LibreSSL licensing
is incompatible with fetchmail's, as there is no GPL clause 2(b)=20
exception for LibreSSL, so LibreSSL can only be used where it is
part of the operating system (one of the very few examples is OpenBSD).

The source archive is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.=
26.tar.xz/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.=
26.tar.lz/download>

The detached GnuPG signature is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.=
26.tar.xz.asc/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.=
26.tar.lz.asc/download>

The SHA256 hashes for the tarballs are:
SHA256(fetchmail-6.4.26.tar.xz)=3D 2cc8a94bfaaf794687b2b2147786508f30da598d=
1ab035c345d731928ac40c9a
SHA256(fetchmail-6.4.26.tar.lz)=3D 18060c9a3aa4b0eb31fdf3543503313a136aac5b=
979d5a8fcba8e886fbd188ab

Here are the release notes:
---------------------------------------------------------------------------=
-----
fetchmail-6.4.26 (released 2021-12-26, 31661 LoC):

# FIXES:
* When using wolfSSL 5.0.0, work around a bug that appears to hit wolfSSL w=
hen
  receiving handshake records while still in SSL_peek(). Workaround is to r=
ead
  1 byte and cache it, then call SSL_peek() again.
  This affects only some servers. https://github.com/wolfSSL/wolfssl/issues=
/4593

# TRANSLATIONS: language translations were updated by this fine person:
* sr:    =D0=9C=D0=B8=D1=80=D0=BE=D1=81=D0=BB=D0=B0=D0=B2 =D0=9D=D0=B8=D0=
=BA=D0=BE=D0=BB=D0=B8=D1=9B (Miroslav Nikoli=C4=87) [Serbian]
---------------------------------------------------------------------------=
-----

Happy fetches,
Matthias

--c62aoxun7T5Hye4H
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3EplW9mTzUhx+oIQ5BKxVu/zhVoFAmHI5PwACgkQ5BKxVu/z
hVrbKRAApOjIepVBnpGnwSz+o8BGw3QJS4bHft7p1jRDqU4/A+4lpeWyCA3p1Mv+
La1VE9GAsxxacm3rN8C3ZuOdCRIYcoEqIdmO3UEHrBrNbSKsR3HeMS0sK77L3ahw
KJNZ+48TC8zrtSw/nIUeuGRcln6Q0leRdDEF3a2xqyTwyRz0FQrSHxhFOrEIPWX2
1lW99N0XNkbq/P1RUfsrI+Ua7PW3u2CsKlWG3roJSIAyKDWuAegC0ktUH3R1fBjp
8lHdbofLrZOfHTjIcDkDfOdBDJJ75m7qmfeBGfmUId2A5vPsHvftyOyOhYn3WBwS
Jqvx0KEnzhJa0noRmVUHVGteqfNYTBxM8ZsOMUM+opxlJY0VUHPOyp5OunHPX+Ze
piEyXb/jpPQkOdRbsPZU/io53kFUBBCJtEF13g/9M2OaUEY5hAyBU9jn1HrIbUmD
3GekRqzaXZqlVMuPJNdWAfYX5/fu+nUQLcj0RRoIs77txhb85mXWmYEXHQIW2jHv
K2devwDPjtkQuZJqkw5PRDz1cdWSBlNeF8Rx37WzfIAuoalW6i1n5yayWsjyE8W7
9q4XJXEyZflVEcpws2NcShqVkL0PYZhs8zshD+/fpSr/TmKzIAgNf9ManSylW3M/
tukQFpYODWBaUAYb7KaUzrht1xcm/NyxL+zWmrLDFe/1Ak0/0j4=
=x7VG
-----END PGP SIGNATURE-----

--c62aoxun7T5Hye4H--


--===============9209774978370367015==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============9209774978370367015==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Fetchmail-announce mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fetchmail-announce

--===============9209774978370367015==--