ANNOUNCE: The 6.4.18 release of fetchmail is available (translation update and minor fixes)
Matthias Andree <[email protected]>
| Newsgroups | gmane.mail.fetchmail.user |
|---|---|
| Message-ID | <YF+1SqXtjEbiUO+L__1479.05019564263$1616885121$gmane$org@ryzen.an3e.de> |
Greetings, The 6.4.18 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It contains a few bug fixes and an updated Finnish translation. NOTE that the tarball contains an outdated NEWS file that does not mention the release date or lines-of-code. I will not re-roll the tarballs. The fixed NEWS file shall be committed to Git shortly. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.18.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.18.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.18.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.18.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.18.tar.lz)= abf0d6c63f1863af92d2129b1bd4c7e80ab4a511aaf8354eeefceaa072bd9a54 SHA256(fetchmail-6.4.18.tar.xz)= 302dc9bcdc6927dedf375d2baaead2347557faa70d98b1da83f2409fa6fb259f Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.18 (released 2021-03-27, 30011 LoC): # REGRESSION FIX: * fetchmailconf: fetchmail 6.4.16 added --sslcertfile to the configuration dump, but fetchmailconf support was incomplete in Git 7349f124 and it could not parse sslcertfile, thus the user settings editor came up empty with console errors printed. Fix configuration parser in fetchmailconf. # ROBUSTNESS FIXES: * fetchmailconf: do not require fetchmail for -V. do not require Tk (Tkinter) for -d option. This is to fail more gracefully on incomplete installs. * TLS code: remove OPENSSL_NO_DEPRECATED macros to avoid portability issues with OpenSSL v3 - these are for development purposes, not production. * TLS futureproofing: use SSL_use_PrivateKey_file instead of SSL_use_RSAPrivateKey_file, the latter will be deprecated with OpenSSL v3, and the user's key file might be something else than RSA. # TRANSLATION UPDATE: This fine person has contributed an updated translation: * fi: Lauri Nurmi [Finnish] --------------------------------------------------------------------------------- Happy fetches, Matthias _______________________________________________ Fetchmail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fetchmail-users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE3EplW9mTzUhx+oIQ5BKxVu/zhVoFAmBftUoACgkQ5BKxVu/z hVrW1g//dtUiCupTa0WbaF+wknhh0yvWuRZGmhCiXjuAORImackO1Kksdv9ZX6MR 6D5O+RjWuB0JFPc7eTJBW4A9D+g1UUu8WJSJaQ79YmhUjnyYeNxuDeBqexM6A9Nh nXa0JJdPHIyB7Pk+2gPVVK15SDpHAlwf+RyZJ93nProLNn4YMmwFgddOU5JzJ8tI EoxGr894KfEbRfvSAfD1H7w44/wvQ3h7BazhasEG5fQ6ZsvzXVgR9YIx261MydGj oD8cLxAjvQkg57kG4ohe1wknK0g6npg0pBUj1RBMwMHGtAPteMRwpK4tG8u3bF3R j3OEL9Vz+snSr9NaCErYAHryjMcO9Ul7iJGW6IXNxCQERFasv9Fps9waf9U8ebyp C5duuQgVD/JsDQngDIeK5Hu3neSdA1HNhFK914f9vqGxnmorh3ggkGKTbK035vCG mdpXQ/dhjTY10fE69cF4ifdGts2eUmbX/oWc3oClJXvfkq4nse+K5hwmJraKNIBR 59nXGd8a5jelcR2bL+6nxzVDcQNgZTh+Gfxsgebwqo/7hS2/f3EDYKp1C1aNAdZH kzh1b1DLfDlRjWL0mwy40fwCZO15s1DTnDutP/1kECESWZKKQ6JcIuK3VlMK52tj VXNE+8D4DC2fbakYGvV3mX+MMYW46N0ZbMmoMOzktxzQH8wFQ7w= =hRmD -----END PGP SIGNATURE-----