ANNOUNCE: fetchmail 6.5.1 is available (minor polishing)

Matthias Andree via Fetchmail-announce <[email protected]> Wed, 13 Nov 2024 00:48:09 +0100
Newsgroups gmane.mail.fetchmail.announce
Message-ID <ZzPpOZeKCfVFo6XK__7821.83832941286$1731455341$gmane$org@ryzen.an3e.de>
--===============2900314392955126599==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="rheOfRe8m/Cbo5mX"
Content-Disposition: inline


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

The 6.5.1 release of fetchmail is now available at the usual locations,
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.1.tar.xz/download>

The detached GnuPG signature is available at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6=
=2E5.1.tar.xz.asc/download>

The SHA256 hashes for the tarballs are:
SHA2-256(fetchmail-6.5.1.tar.xz)=3D ca3fdb95141c277aca109be77f4d45b47e03ee0=
10043058dd90bc182db518d4a


Here are the release notes:
---------------------------------------------------------------------------=
-----
fetchmail-6.5.1 (released 2024-11-13):

## BUG AND PORTABILITY FIXES:
* Drop two wolfSSL compile-time checks that were for older 6.4 or for future
  7.0 releases and broke compilation with wolfSSL 5.7.4.=20
  Fixes https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282413#c4
* Use %p instead of non-portable %#p for one wolfSSL-related diagnostic mes=
sage
  (FreeBSD defines %#p to be %p, on many other platforms it's undefined=20
  behavior).
* Add regex_helper.c to list of files that contain translatable strings,
  which contains two strings we missed to translate.

## CHANGES:
* Simplify EVP_MD_fetch API detection ("like OpenSSL 3" vs. "like OpenSSL 1=
")=20
  for version switch and base it on the claimed OpenSSL version of the cryp=
to=20
  SSL, which works for LibreSSL (claims OpenSSL 2) and wolfSSL alike.

## TRANSLATIONS: fetchmail's messages were translated by these fine people:
* sq:    Besnik Bleta [Albanian]
* es:    Cristian Oth=F3n Mart=EDnez Vera [Spanish]
* ro:    Remus-Gabriel Chelu [Romanian]
* fr:    Fr=E9d=E9ric Marchal [French]
* pl:    Jakub Bogusz [Polish]
* sv:    G=F6ran Uddeborg [Swedish]
* ja:    Takeshi Hamasaki [Japanese]
* eo:    Keith Bowes [Esperanto]

---------------------------------------------------------------------------=
----
fetchmail-6.5.0 (released 2024-10-29, 31200 LoC):

## SECURITY FIX:
* .netrc now may not have more than 0700 permission if it contains password=
s,
  else fetchmail will warn and ignore the file.

## 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.
* The ca, da, en_GB, id, it, nl, ru, zh_CN translations have been disabled,
  they are too far behind.

## 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
  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 or wolfSSL,
  at a minimum OpenSSL v3.0.9 or wolfSSL v5.7.2.

## TRANSLATIONS: fetchmail's messages were translated by these fine people:
* cs:    Petr Pisar [Czech]
* eo:    Keith Bowes [Esperanto]
* es:    Cristian Oth=F3n Mart=EDnez Vera [Spanish]
* fr:    Fr=E9d=E9ric Marchal [French]
* ja:    Takeshi Hamasaki [Japanese]
* ro:    Remus-Gabriel Chelu [Romanian]
* sv:    G=F6ran Uddeborg [Swedish]
* sq:    Besnik Bleta [Albanian]
* pl:    Jakub Bogusz [Polish]

## BUG FIXES
* fetchmail can now report mailbox sizes of 2^31 octets and beyond (2 GibiB=
).
  This required C99 support (for the long long type).
  Fixes Debian Bug#873668, reported by Andreas Schmidt.
* fetchmail now defines its OpenSSL API level to 3.0.0 so as to expose the
  3.0.0 APIs from OpenSSL.
* The .netrc parser no longer permits "machine" after "default".
* Add manpage info on the .netrc syntax, as ftp(1) is not standardized and
  may not be installed. Fixes Launchpad Bug #1976361 reported by Bill Yikes.
* Received: lines now return GMT time if the tzoffset cannot be represented
  as whole minutes. Reported by @rriddicc via Gitlab #49.
* If fetchmail was running localized, generated an error e-mail message loc=
ally,
  and if the selected translation would require the Subject: line to wrap
  inside an RFC-2047 encoded word (=3D?UTF-8?Q?...?=3D), the wrapped encode=
d-word
  was not indented, thus not marked as a continuation line.
* SSL error handling was improved, fetchmail now consistently clears the
  thread/SSL error queue before SSL I/O operations and checks SSL_get_error
  afterwards.  The SSL_connect() error handling has been revised to log more
  consistently.

## 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
  running pkg-config in the right environment, and using the AC_LIB_LINKFLA=
GS
  macro to obtain run-time library path setting flags.
* For typical POP3/IMAP ports 110, 143, 993, 995, if port and --ssl option
  do not match, emit a warning and continue. Closes Gitlab #31.
* There is now a --idletimeout feature contributed by Eric Durand, to
  permit setting a shorter timeout for the --idle option, because many
  servers violate the protocol (requiring 30 minutes) and hang up sooner th=
an
  the 28 minutes fetchmail waits before refreshing IDLE.
  GitLab merge request !35.
* There is now a --forceidle feature to force idle mode even if not adverti=
sed
  in the server capabilities. This is a dangerous option, use it carefully.
  Courtesy of Eric Durand, GitLab merge request !39.
* There is now a --moveto feature (only feasible in IMAP) that, instead of
  flushing mail, moves it to a user-specified folder. This is to assist with
  archiving, or when providers (G...) break the IMAP model.
  Courteously provided by Damjan Jovanovic.
* rcfile parsing errors are now reported in more detail, and with -vv mode,
  also lead to a non-importable Python dump of what was obtained, for debug=
ging.
* fetchmail's --auth option ssh was renamed to implicit, to make clear that=
 it
  does *NOT* imply any particular type or features of the --plugin.  --auth=
 ssh
  will be understood for a while for compatibility but fetchmail will repor=
t it
  as implicit.
* fetchmail no longer warns about port/service mismatches with/without ssl
  option when a "plugin" is in use because fetchmail cannot know whether the
  plugin talks SSL or STARTTLS/STLS. Fixes Debian Bug#1076604.
* fetchmail re-executes itself if the .netrc file's modification change
  is found to be newer at the beginning of a new run.
* fetchmail can now use other digest algorithms than MD5 for the
  --sslfingerprint option. To use, specify the algorithm's name in
  curly braces as prefix in the finger print, say,
  --sslfingerprint '{SHA256}00:01:[...]:1F'. This will also switch the
  algorithm for printing. All algorithms supported by the TLS/SSL library
  can be specified. Fixes Gitlab issue #19, Debian Bug#700266.

## 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.
* 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.
* fetchmail can be built with meson 1.30 or newer <https://mesonbuild.com/>.
  fetchmail is not currently written in a way that supports unity
  (amalgamated) builds.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

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

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

iQIzBAEBCgAdFiEE3EplW9mTzUhx+oIQ5BKxVu/zhVoFAmcz6TkACgkQ5BKxVu/z
hVof4hAApueVUmh4HXpX7VtgvglEbjA0AbFHz7CKktGuRgtGXT8QlSTasDIh+c6s
OdFxi7LYKSeP07vtogy0v+FkCLKSxVzkZ8WhnpdAoxMKMgOyj76D3QYGw7aX0iS2
/yk7W0UfQeZ36fCAk4tuOBg86UU9AAJcj5h2oh/32VxJGDnskxi/aGMmOEMWmhCP
WYh0MkSx1Nor6Skz7BEiFEDWMieuFxDy10l7a3Dw0HmRMlH4sslmoJFtBaPNxfkE
ZOQ0VBifaUXbjiGjRPd2jaFXctSIqGUbXDJHb1lalY7cl9SJDaDi1NGP56LCOOpy
0sTUR8A6ThqqGd297X+eIf7O/W4pZgwUfyA1S/zs9hRbw0vyrbWC7E2lJvpizZ+z
P9GL3YJPQ2RvKxNXW3zSKYlQfJABhW/GEliiZArYnfiECEZtR8QuFJnqvWQ1fknh
OUYW4AeY0MkOzz0WfUe4RYqt2sFOlz6S3dcaPWJM6D+4HN4G65JzWJE1QkVA4KWq
uChgaAG4uTXSg43aLtmrqu2/ilUtErglClnXtSvTvNQ/LY4xSXacJCX7naXi4tBY
BdqF8UM7hwMCfsHj9KxvOfLazupuy6KtOKRG36etvjBGhqhZ6jQo7eXp8o4FMZdq
JfNZDYr7gbChMqBtgWmTHuxmjsZY9xuVx5EPOfa89/ADHndi4DI=
=p9xo
-----END PGP SIGNATURE-----

--rheOfRe8m/Cbo5mX--


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


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

--===============2900314392955126599==--