ANNOUNCE: The 6.5.0.beta3 snapshot of fetchmail is available

Matthias Andree <[email protected]> Sat, 24 Apr 2021 15:26:22 +0200

Newsgroups	gmane.mail.fetchmail.user
Message-ID	<YIQcfs9pAICBbzCH__37033.8850699895$1619349867$gmane$org@ryzen.an3e.de>

Greetings,

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

The source archive is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.5/fetchmail-6.5.0.beta3.tar.xz/download>

This is a deep link to the GnuPG signature:
<https://sourceforge.net/projects/fetchmail/files/branch_6.5/fetchmail-6.5.0.beta3.tar.xz.asc/download>

This is mostly merging of the recent 6.4 releases, with these additional changes:

* 13d7eab8 2021-04-24 | INSTALL: Spell-check [Matthias Andree]
* deb5e66f 2021-03-29 | Add basic test framework to source from other tests. [Matthias Andree]
* 9c9d47c9 2021-03-29 | fetchmail.man: Add QUICKSTART section. [Matthias Andree]
* 3aafc8bd 2021-03-23 | Reduce 15 different translatable "Query status" messages into 2. [Lauri Nurmi]
* c4ba1d68 2021-03-13 | po/de.po: Update. [Matthias Andree]
* 13c9a52c 2021-03-13 | INSTALL: mention Python 3 optional, and suggest make check [Matthias Andree]
* 6161c8c2 2021-03-13 | OpenSSL: Prepare for removal of TLS_MAX_VERSION declaration. [Matthias Andree]
* 1b374b5f 2021-03-13 | tests: import Ubuntu's POP3 mock server operation test [Bryce Harrington]
* da6eb347 2021-03-13 | sanity check well-known POP3/IMAP ports vs. SSL [Matthias Andree]
* 58cd8002 2021-01-30 | tls-aux.h: Remove unneeded 1.0.2 compatibility code. [Matthias Andree]

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 required
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+ option.
* 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 localtime
and in the format "Jun 20 23:45:01 fetchmail: ". It will be localized through
the environment variables LC_TIME (or LC_ALL) and TZ.
Contributed by Holger Hoffstätte.
* 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 with
XSI extension) compliant system.

In particular, older fetchmail versions had workarounds or replacement code
for several functions standardized in the Single Unix Specification v3, these
have been removed. Hence:
- The trio/ library has been removed from the distribution.
- The libesmtp/getaddrinfo.? library has been removed from the distribution.
- 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 messes
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 than
reporting a protocol error. We don't intend to chat any more so the protocol
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 !20.
* The configure script now spends more effort for getting --with-ssl right, by
running pkg-config in the right environment, and using the AC_LIB_LINKFLAGS
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 lower it.
Use with extreme caution. Note that levels 3 or higher will frequently cause
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,
"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 the
ciphersuites fails, fetchmail refuses to connect.
* NOTE the features above are simplistic. For instance, even though you
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 with
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 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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fetchmail-users

signature.asc (application/pgp-signature, 833 B)