[Fetchmail-devel] ANNOUNCE: fetchmail 6.4.12 is now available (regression fixes + README, + new translation for Romanian by Florentina Mușat)

[Matthias A. <mat...@gm...>]

Greetings,

The 6.4.12 release of fetchmail is now available at the usual locations,
including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>.

Reviewing remarks of the FreeBSD packager WRT 6.4.11, I have found a bug in
the makerelease.pl script that caused corruption the README file. It
did contain a NEWS fragment in the past few releases instead of
the README file from the repository. (FreeBSD Bugzilla #249009 comment #2)

This bug might have affected release tarballs back to 6.4.2
(failure inducing change c82cca7831bd8e9bc65f860b38a847bb5056b5f6).

6.4.12 was built with a fixed script and now has the right README file.

Sorry about the quick release sequence.

== NOTE ==
Fetchmail 6.4.x does not receive functional changes, and new
6.4.x are not planned, except if regressions, critical fixes, or new
translations or important documentation fixes appear and 6.5.0 is too far out.

Fetchmail 6.4.x is the last branch that will tolerate OpenSSL 1.0.2 and C89
compilers, and support Python 2.7.x (for newer x) for fetchmailconf.

== EXCURSION ---------
The direction for the near future is to do some bugfixing and possibly minor
features on the Git branch 'legacy_6x', for now called 6.5.0.dev*, it is a
branch that will require newer operating systems, toolchains, library, for
instance, OpenSSL 1.1.1 with TLSv1.3 support, C99 (for long long support) or
possibly C11 (TBD) and possibly newer IEEE Std 1003.1 compliance.
== END EXCURSION -----


The source archive is available at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.12.tar.lz>
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.12.tar.xz>

Detached GnuPG signatures for the respective tarballs are at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.12.tar.lz.asc>
<https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.12.tar.xz.asc>

SHA256 hash values:
SHA256(fetchmail-6.4.12.tar.lz)= 9bf4d6cd8ff3d0b3d48fb639645d674ffac3d9d9337cfb8bda35e14f67431758
SHA256(fetchmail-6.4.12.tar.xz)= 2b84e0971dbf683ec7edd313f9218adbc7dc51c1de9825b3b549bf619c1a4887

Here are the release notes:

---------------------------------------------------------------------------------
fetchmail-6.4.12 (released 2020-09-04, 27596 LoC):

# BUG FIXES:
* The README file is now the one from Git again. The makerelease.pl script
  used to roll and upload the tarball sometimes clobbered the README file and
  replaced its contents by a part of the NEWS file.

# KNOWN BUGS AND WORKAROUNDS
  (This section floats upwards through the NEWS file so it stays with the
  current release information)
* Fetchmail does not handle messages without Message-ID header well
  (See sourceforge.net bug #780933)
* Fetchmail currently uses 31-bit signed integers in several places
  where unsigned and/or wider types should have been used, for instance,
  for mailbox sizes, and misreports sizes of 2 GibiB and beyond. 
  Fixing this requires C89 compatibility to be relinquished.
* BSMTP is mostly untested and errors can cause corrupt output.
* Fetchmail does not track pending deletes across crashes.
* The command line interface is sometimes a bit stubborn, for instance,
  fetchmail -s doesn't work with a daemon running.
* Linux systems may return duplicates of an IP address in some circumstances if
  no or no global IPv6 addresses are configured.
  (No workaround. Ubuntu Bug#582585, Novell Bug#606980.)
* Kerberos 5 may be broken, particularly on Heimdal, and provide bogus error
  messages. This will not be fixed, because the maintainer has no Kerberos 5
  server to test against. Use GSSAPI.

---------------------------------------------------------------------------------
fetchmail-6.4.11 (released 2020-08-28, 27596 LoC):

# REGRESSION FIX:
* configure: fetchmail 6.4.9 and 6.4.10 would miss checking for TLS v1.2 and
  TLS v1.3 support if AC_LIB_LINKFLAGS came up with something such as
  /path/to/libssl.so, rather than -lssl. (For instance on FreeBSD)

---------------------------------------------------------------------------------
fetchmail-6.4.10 (released 2020-08-27, 27596 LoC):

# REGRESSION FIX:
* configure: fetchmail 6.4.9's configure was unable to pick up OpenSSL
  if it wasn't announced by pkg-config, for instance, on FreeBSD.

---------------------------------------------------------------------------------
fetchmail-6.4.9: (not announced by e-mail, withdrawn)

## DOCUMENTATION UPDATE:
* manpage: mention that the SSL/TLS certificate fingerprint uses an MD5 hash.

## CHANGES:
* configure: try to use AC_LIB_LINKFLAGS to obtain proper link flags for 
  libcrypto and libssl if pkg-config failed.
  This is an attempt to fix borderline issues when users building on systems 
  with obsolete OpenSSL try to use a local newer OpenSSL from a separate 
  directory.

## NEW TRANSLATION, with thanks to the translator:
* ro:    Florentina Mușat [Romanian]

---------------------------------------------------------------------------------

Happy fetches,
Matthias