ANNOUNCE: The 6.5.0.beta2 snapshot of fetchmail is available

Matthias Andree <[email protected]> Sun, 3 Jan 2021 15:25:57 +0100
Newsgroups gmane.mail.fetchmail.announce
Message-ID <X/HT9b/[email protected]>
--===============6424432776025795328==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="z3mn6UKEP57u8taM"
Content-Disposition: inline


--z3mn6UKEP57u8taM
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings,

The 6.5.0.beta2 release of fetchmail is now available at the usual location=
s,
including <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/>.

The source archive is available at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6=
=2E5.0.beta2.tar.xz/download>

This is a deep link to the GnuPG signature:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6=
=2E5.0.beta2.tar.xz.asc/download>

Here are the release notes:

---------------------------------------------------------------------------=
-----
fetchmail-6.5.0 (not yet released):

## REMOVED FEATURES
* fetchmail no longer supports using an MDA as SMTP fallback. This is requi=
red=20
  to make deliveries consistent.
  The --enable-fallback configure option is gone.
* fetchmail no longer supports SSLv3. --sslproto ssl3 and ssl3+ options have
  been removed and behave as though "--sslproto auto" had been given.

## INCOMPATIBLE CHANGES
* fetchmail by default only negotiates TLS v1.2 or higher. (RFC-7525)
* fetchmail can auto-negotiate TLS v1.1 through the --sslproto tls1.1+ opti=
on.
* fetchmail can auto-negotiate TLS v1.0 through the --sslproto tls1+ option.
* fetchmailconf now requires Python 3.7.0 or newer.
* fetchmail, with --logfile, now logs time stamps into the file, in localti=
me
  and in the format "Jun 20 23:45:01 fetchmail: ". It will be localized thr=
ough
  the environment variables LC_TIME (or LC_ALL) and TZ.
  Contributed by Holger Hoffst=E4tte.
* fetchmail sets the OPENSSL security level to 2 by default.
  Override is possible from an environment variable,
  see EXPERIMENTAL CHANGES below.

## CHANGED REQUIREMENTS
* fetchmail 6.5.0 is written in C99 and requires a SUSv3 (Single Unix
  Specification v3, a superset of POSIX.1-2001 aka. IEEE Std 1003.1-2001 wi=
th
  XSI extension) compliant system.

  In particular, older fetchmail versions had workarounds or replacement co=
de
  for several functions standardized in the Single Unix Specification v3, t=
hese=20
  have been removed. Hence:
  - The trio/ library has been removed from the distribution.
  - The libesmtp/getaddrinfo.? library has been removed from the distributi=
on.
  - The KAME/getnameinfo.c file has been removed from the distribution.

* fetchmail 6.5.0 requires a TLSv1.3-capable version of OpenSSL,
  at a minimum OpenSSL v1.1.1.

## BUG FIXES
* fetchmail can now report mailbox sizes of 2^31 octets and beyond.
  This required C99 support (for the long long type).
  Fixes Debian Bug#873668, reported by Andreas Schmidt.
* fetchmail now defines its OpenSSL API level (1.1.1, or 10101) so
  as to compile with OpenSSL 3.0.0. (fetchmail was requesting to hide
  deprecated APIs.)

## CHANGES
* When fetchmail attempts to log out from an IMAP4 server and the server me=
sses
  up its responses (it is supposed to send an untagged * BYE and a tagged
  A4711 OK) and sends a tagged A4711 BYE response, tolerate that, rather th=
an
  reporting a protocol error. We don't intend to chat any more so the proto=
col
  violation is harmless, and we know the server cannot send more untagged
  status responses.
  Analysis and fix courtesy of Maciej S. Szmigiero, GitLab merge request !2=
0.
* The configure script now spends more effort for getting --with-ssl right,=
 by=20
  running pkg-config in the right environment, and using the AC_LIB_LINKFLA=
GS=20
  macro to obtain run-time library path setting flags.

## EXPERIMENTAL CHANGES - these are not documented anywhere else, only here:
* fetchmail supports a FETCHMAIL_SSL_SECLEVEL environment variable that
  can be used to override the OpenSSL security level. Fetchmail by default
  raises the security level to 2 if lower. This variable can be used to low=
er it.
  Use with extreme caution. Note that levels 3 or higher will frequently ca=
use
  incompabilities with servers because server-side data sizes are often too=
 low.
  Valid range: 0 to 5 for OpenSSL 1.1.1 and 3.0.0-alpha4.
* fetchmail supports a FETCHMAIL_SSL_CIPHERS environment variable that
  sets the cipher string (through two different OpenSSL functions) for SSL =
and
  TLS versions up to TLSv1.2.
  If setting the ciphers fails, fetchmail will not connect.
  If not given, defaults to Postfix's "medium" list,=20
  "aNULL:-aNULL:HIGH:MEDIUM:+RC4:@STRENGTH".
* fetchmail supports a FETCHMAIL_TLS13_CIPHERSUITES environment variable
  that sets the ciphersuites (a colon-separated list, without + ! -) for
  TLSv1.3. If not given, defaults to OpenSSL's built-in list. If setting th=
e=20
  ciphersuites fails, fetchmail refuses to connect.
* NOTE the features above are simplistic. For instance, even though you=20
  configure --sslproto tls1.3, a failure to set tls1.2 ciphers could cause
  a connection abort.

# KNOWN BUGS AND WORKAROUNDS
  (This section usually floats upwards through the NEWS file so it stays wi=
th=20
  the current release information)
* Fetchmail does not handle messages without Message-ID header well
* Fetchmail currently uses 31-bit signed integers in several places
  where unsigned and/or wider types should have been used.
* 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 circumstance=
s 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.
---------------------------------------------------------------------------=
-----

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

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

iQIzBAEBCgAdFiEE3EplW9mTzUhx+oIQ5BKxVu/zhVoFAl/x0/UACgkQ5BKxVu/z
hVrb9RAAm9J/ap7i5NCnWuNMF1GpdZnAv/09UFZXy8iovoX2lDdLVXE+Amf43uEL
thMjbUnOoemrakQkgJlYwhRo4DDD0BR111EmwTVN+AudqG7GGcrDK15euT8umnxe
nQIgnXHOBvDqOeH7oWArO/NI5AEw2FaIVJNpa8eT7KgVDudDMldNRj/tu+erjL2J
Ge5NjZpiy5Lht7+feTsziBGR5c9WMU2QKSePENZzfPfeSgdwvXZSNXu+Xld+RLpa
bu4K22iaAtGWAWB+JnOpiVD5ZlDFmCxW0Uk6+Ju91Y+F/9a9zXbN3wV/IUP7KVIH
9UHXGoIxoLZ2fruG+k/zKf8XvwHV7eCgrejSa+436O/Uzf+BfGvFDlnPelBmbVxE
VzNgnhEm+8Qf+U53x8761pS3t5+fmv5jE4lil++/ASw3/SmcTJX7TGLCfhJXDuxz
ogUrj/e5+j4ythq26c1hQN/LjD8VmhqCHAYkSpTVPBb+BE0HamnM5+kdconep5iy
X6nFG9gMPTTG9utp7VMo8XKGSyOX4boDiL74B7+DCwKRI7rCcK5tYds7Kh0PDGyj
91nv6GZ0PpUbheuKgTdEVPPL/LHhfSGLAAOvfT9yRWofNVgSoCp/SWsHlKPWpuAu
Mnkuu1p25egsxIFEqQ2LWAdcCkAzYQf99aMrnCmxnyp3+ju1wEg=
=VnAH
-----END PGP SIGNATURE-----

--z3mn6UKEP57u8taM--


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


--===============6424432776025795328==
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

--===============6424432776025795328==--