You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(4) |
Oct
(3) |
Nov
(4) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(6) |
Feb
|
Mar
(4) |
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
(3) |
Dec
(1) |
2007 |
Jan
(4) |
Feb
(2) |
Mar
(4) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
(4) |
Mar
(2) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(2) |
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
2013 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
(2) |
Feb
(3) |
Mar
(3) |
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
(3) |
Aug
(2) |
Sep
(1) |
Oct
(4) |
Nov
(1) |
Dec
|
2021 |
Jan
(4) |
Feb
(2) |
Mar
(3) |
Apr
(3) |
May
|
Jun
|
Jul
(2) |
Aug
(11) |
Sep
(3) |
Oct
(3) |
Nov
(4) |
Dec
(3) |
2022 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2023 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Matthias A. <mat...@gm...> - 2021-03-07 14:25:22
|
Greetings, The 6.4.17 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 is more willing to give information on the trust store paths it is using (with -V or --version). The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.17.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.17.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.17.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.17.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.17.tar.lz)= 1f4aa30f4d62a3e786af01c7dd128611027ef92af85a351368f9dcc97fa50b02 SHA256(fetchmail-6.4.17.tar.xz)= a41bcdf11b41aa0682b259aee4717c617c15dadd43fa008b2ed38b770f4d50c6 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.17 (released 2021-03-07, 29998 LoC): # BUG FIXES * IMAP client: it used to leak memory for username and password when trying the LOGIN (password-based) authentication and encountered a timeout situation. * dist-tools/getstats.py: also counts lines in *.py files, shown above. # CHANGES * fetchmail.man: now mentions that you may need to add --ssl when specifying a TLS-wrapped port. * fetchmailconf: --version (-V) now prints the Python version in use. # TRANSLATION UPDATES This fine person has contributed updated translations for fetchmail: * ja: Takeshi Hamasaki [Japanese] --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2021-02-10 19:02:18
|
[re-send with corrected download URLs] Greetings, The 6.4.16 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/branch_6.4/>. It contains a few bug fixes and is more willing to give information on the trust store paths it is using (with -V or --version). The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.16.tar.lz)= 0cc50212d62a7c9912e0c7fdf795ba205db554195d05a45e36c94671ec54c089 SHA256(fetchmail-6.4.16.tar.xz)= 044b9a0ac03afbae7744979defe3e2e32e39141bca68fd0c8deda2ed40884fb9 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.16 (released 2021-02-08, 27707 LoC): # BUG FIXES * fetchmail's --configdump, and fetchmailconf, lacked support for the sslcertfile option. --configdump support added by Earl Chew, Gitlab issue #25, merge request !28. * fetchmail's manual page was never updated to reflect 6.2.5's change about the duplicate-killer code for multidrop mode, which read "* Dup-killer code now keys on an MD5 hash of the raw headers." ...instead of just the Message-ID. [commit 9dd8400, 2003-10-10 by esr] The manual page was now updated accordingly and documents historic behaviour: start to 5.0.7 no duplicate suppression; 5.0.8 to 6.2.4 duplicate suppression only by Message-ID; 6.2.5 to 6.4.X duplicate suppression by entire raw header. Manpage bug found by Julian Bane debugging "duplicate message" behaviour. * ./configure no longer runs AC_LIB_LINKFLAGS (how to link) checks when called --without-ssl # FEATURES * fetchmail --version [fetchmail -V] now queries and prints the SSL/TLS library's "SSL default trusted certificate" file or directory (mind the word "default"), where the OpenSSL-compatible TLS implementation will look for trusted root, meaning certification authority (CA), certificates. NOTE 1: watch the output carefully if the line prints the defaults or the configured path (without "default"). NOTE 2: SSL_CERT_DIR and SSL_CERT_FILE are documented environment variables for OpenSSL 1.1.1 to override the *default* locations (those compiled into OpenSSL or possibly in its configuration file). This was added when Gene Heskett was debugging his setup and the information "where does OpenSSL look" was missing. * fetchmail --version now prints version of the OpenSSL library that it was compiled against, and that it is using at runtime, and also the OPENSSL_DIR and OPENSSL_ENGINES_DIR (if available). # TRANSLATION UPDATES These fine people have contributed updated translations for fetchmail, in no particular order: * sq: Besnik Bleta [Albanian] * eo: Keith Bowes [Esperanto] * cs: Petr Pisar [Czech] * pl: Jakub Bogusz [Polish] * sv: Göran Uddeborg [Swedish] * fr: Frédéric Marchal [French] # 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. --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2021-02-08 18:21:18
|
Greetings, The 6.4.16 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/branch_6.4/>. It contains a few bug fixes and is more willing to give information on the trust store paths it is using (with -V or --version). The source archive is available at: <https://sourceforge.net/projects/fetchmail/branch_6.4/fetchmail-6.4.16.tar.xz/download> <https://sourceforge.net/projects/fetchmail/branch_6.4/fetchmail-6.4.16.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.16.tar.lz)= 0cc50212d62a7c9912e0c7fdf795ba205db554195d05a45e36c94671ec54c089 SHA256(fetchmail-6.4.16.tar.xz)= 044b9a0ac03afbae7744979defe3e2e32e39141bca68fd0c8deda2ed40884fb9 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.16 (released 2021-02-08, 27707 LoC): # BUG FIXES * fetchmail's --configdump, and fetchmailconf, lacked support for the sslcertfile option. --configdump support added by Earl Chew, Gitlab issue #25, merge request !28. * fetchmail's manual page was never updated to reflect 6.2.5's change about the duplicate-killer code for multidrop mode, which read "* Dup-killer code now keys on an MD5 hash of the raw headers." ...instead of just the Message-ID. [commit 9dd8400, 2003-10-10 by esr] The manual page was now updated accordingly and documents historic behaviour: start to 5.0.7 no duplicate suppression; 5.0.8 to 6.2.4 duplicate suppression only by Message-ID; 6.2.5 to 6.4.X duplicate suppression by entire raw header. Manpage bug found by Julian Bane debugging "duplicate message" behaviour. * ./configure no longer runs AC_LIB_LINKFLAGS (how to link) checks when called --without-ssl # FEATURES * fetchmail --version [fetchmail -V] now queries and prints the SSL/TLS library's "SSL default trusted certificate" file or directory (mind the word "default"), where the OpenSSL-compatible TLS implementation will look for trusted root, meaning certification authority (CA), certificates. NOTE 1: watch the output carefully if the line prints the defaults or the configured path (without "default"). NOTE 2: SSL_CERT_DIR and SSL_CERT_FILE are documented environment variables for OpenSSL 1.1.1 to override the *default* locations (those compiled into OpenSSL or possibly in its configuration file). This was added when Gene Heskett was debugging his setup and the information "where does OpenSSL look" was missing. * fetchmail --version now prints version of the OpenSSL library that it was compiled against, and that it is using at runtime, and also the OPENSSL_DIR and OPENSSL_ENGINES_DIR (if available). # TRANSLATION UPDATES These fine people have contributed updated translations for fetchmail, in no particular order: * sq: Besnik Bleta [Albanian] * eo: Keith Bowes [Esperanto] * cs: Petr Pisar [Czech] * pl: Jakub Bogusz [Polish] * sv: Göran Uddeborg [Swedish] * fr: Frédéric Marchal [French] # 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. --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2021-01-30 15:20:04
|
Greetings, The 6.4.16-rc1 release candidate of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/branch_6.4/>. It contains a few bug fixes that were contributed via Gitlab. The source archive is available at: <https://sourceforge.net/projects/fetchmail/branch_6.4/fetchmail-6.4.16-rc1.tar.xz/download> <https://sourceforge.net/projects/fetchmail/branch_6.4/fetchmail-6.4.16-rc1.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16-rc1.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.16-rc1.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.16-rc1.tar.lz)= 48ca15ba5d87b564050b7642732ffc0b2faf82b83a9eb630032e4ae7c760c866 SHA256(fetchmail-6.4.16-rc1.tar.xz)= 2ac20bb2858b9cad575b1d4b95855d02561a57f65dbd5abf20868234977a73aa Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.16 (not yet released): # BUG FIXES * fetchmail's --configdump, and fetchmailconf, lacked support for the sslcertfile option. --configdump support added by Earl Chew, Gitlab issue #25, merge request !28. * fetchmail's manual page was never updated to reflect 6.2.5's change about the duplicate-killer code for multidrop mode, which read "* Dup-killer code now keys on an MD5 hash of the raw headers." ...instead of just the Message-ID. [commit 9dd8400, 2003-10-10 by esr] The manual page was now updated accordingly and documents historic behaviour: start to 5.0.7 no duplicate suppression; 5.0.8 to 6.2.4 duplicate suppression only by Message-ID; 6.2.5 to 6.4.X duplicate suppression by entire raw header. Manpage bug found by Julian Bane debugging "duplicate message" behaviour. * ./configure no longer runs AC_LIB_LINKFLAGS (how to link) checks when called --without-ssl # FEATURE * fetchmail --version [fetchmail -V] now queries and prints the SSL/TLS library's "SSL default trusted certificate" file or directory (mind the word "default"), where the OpenSSL-compatible TLS implementation will look for trusted root, meaning certification authority (CA), certificates. NOTE 1: watch the output carefully if the line prints the defaults or the configured path (without "default"). NOTE 2: SSL_CERT_DIR and SSL_CERT_FILE are documented environment variables for OpenSSL 1.1.1 to override the *default* locations (those compiled into OpenSSL or possibly in its configuration file). This was added when Gene Heskett was debugging his setup and the information "where does OpenSSL look" was missing. * fetchmail --version now prints version of the OpenSSL library that it was compiled against, and that it is using at runtime, and also the OPENSSL_DIR and OPENSSL_ENGINES_DIR (if available). # 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. --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2021-01-03 21:10:13
|
Greetings, The 7.0.0-alpha7 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_7-alpha/>. This is to have a tarball-based reference point, alpha6 had, well, aged quite a bit. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_7-alpha/fetchmail-7.0.0-alpha7.tar.xz/download> Here are the release notes: fetchmail-7.0.0 (not yet released): NOTE THIS IS AN ALPHA RELEASE THAT HAS NOT BEEN THOROUGHLY TESTED! XXX and FIXME - see the big merge of 2019-08-25, and 2021-01-03 # INCOMPATIBLE CHANGES * The SSL/TLS options were massively changed and disentangled, to be clearer. * --sslmode starttls=must is now the default as a consequence of the previous sslcertck default. If you need an unencrypted connection, use --sslmode none. If you need an SSL-wrapped connection that starts immediately on a separate port, use --sslmode wrapped. * See the REMOVED FEATURES section below for further incompatibilities. # MAJOR CHANGES * The POP3 code now always uses UIDL, except if "fetchall" is in effect. Fixes BerliOS Bug #16172. Fixes Debian Bug#345788. The --uidl option is now gone. # FEATURES ADDED * fetchmail has initial support for OAUTH2, courtesy of Matthew M. Ogilvie. This requires a helper script (in Python) that ships in the contrib/ section. * Fetchmail can now retrieve credentials from PWMD. This needs to be enabled at compile-time and requires run-time configuration. See README.PWMD for details. Contributed by Ben Kibbey, author of libpwmd and pwmd. * Fetchmail can now run an external command to retrieve credentials (passwords), see the fetchmail man page for passwordeval. * Fetchmail now supports a retrieve-error command line or rcfile option that takes exactly one argument, abort (default), continue or markseen. This specifies the policy used by fetchmail to handle messages whose bodies fail to be retrieved due to server errors. Both the continue and markseen options will skip the message with errors and allow the session to continue so that subsequent messages can be retrieved. The markseen option will also mark the message with errors as seen. The default policy is to abort the session whenever a server error occurs. Contributed by Craig Brown. * Fetchmailconf offers CRAM-MD5 and APOP authentication. XXX FIXME: check * The SSL/TLS/STARTTLS operation mode is now selected through a new --sslmode option, which cleans up the incomprehensible --ssl and --sslproto mess of fetchmail versions before v7.0.0. * The SSL/TLS/STARTTLS protocol version can now be selected through a new --sslprotocolversion switch. * The SSL/TLS cipher in used is now reported in verbose mode. * FIXME: The SHA1 fingerprint is now printed along with the MD5 digest of the server's certificate; however, this can not yet be matched - matches are still against MD5 only. # REMOVED FEATURES * IMAP2 and POP2 protocol support were removed. * RPOP support (not actually a protocol, but a variant of POP3) was removed. * POP3: the (--)uidl option has been removed. It is always on. * POP3: LAST is no longer used. It was removed from POP3 in the year 1994, and it could cause mail loss when the connection was interrupted or if clients besides fetchmail polled the mailbox. * The MX and host alias DNS lookups that fetchmail performs in multidrop mode have been removed. They were based on the mistaken assumption that the IMAP/POP3 server was also the MX server, which is rarely the case. They have never supported IPv6 (including IPv6-mapped IPv4) either. Non-DNS based alias keywords such as "aka" remain. * Kerberos IV support was removed. * The --ssl option is obsolescent and triggers a warning that users should use --sslmode wrapped instead. It is understood as an alias for --sslmode wrapped. * The --sslproto option was removed. Two new options were added in its place, --sslmode and --sslprotocolversion. * A lot of outdated and/or unsafe-to-use material got dropped from contrib/. # CHANGES * APOP is no longer a protocol, but an authentication method. In order to use it, use protocol POP3 auth APOP, or on the commandline, -p pop3 --auth apop. If no authentication method is specified, APOP is automatically tried if offered by the server before we resort to sending the password as clear text. -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2021-01-03 14:26:17
|
Greetings, The 6.5.0.beta2 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.5.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.5.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 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. -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2021-01-03 13:38:55
|
Greetings, and a happy new year 2021! The 6.4.15 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/branch_6.4/>. It contains a few bug fixes that were contributed via Gitlab. The source archive is available at: <https://sourceforge.net/projects/fetchmail/branch_6.4/fetchmail-6.4.15.tar.xz/download> <https://sourceforge.net/projects/fetchmail/branch_6.4/fetchmail-6.4.15.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.15.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.15.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.15.tar.lz)= 6f56d0c08278f190de840ae4d1affa767a2545b056e1993b8d3f80294bbf7ad3 SHA256(fetchmail-6.4.15.tar.xz)= 735b217474937e13cfcdea2d42a346bf68487e0d61efebe4d0d9eddcb3a26b96 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.15 (released 2021-01-03, 27614 LoC): # BUG FIXES * Fix a typo in the manual page reported by David McKelvie. * Fix cross-compilation with openssl, by Fabrice Fontaine. Merge request !23. * Fix truncation of SMTP PLAIN AUTH with ^ in credentials, by Earl Chew. Gitlab issue #23, merge request !25. # 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. --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-11-26 10:35:08
|
Greetings, The 6.4.14 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/branch_6.4/>. It updates the Serbian translation and also the FAQ. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.14.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.14.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.14.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.14.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.14.tar.lz)= b84dba26e64b526515256a8ae705eb2bc5338b7fa1455c4c08410df20cc28ae6 SHA256(fetchmail-6.4.14.tar.xz)= 424707390f7cdc6d16db4887931117f2242873846b28cc1d0ae1c0ecf158bdcb Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.14 (released 2020-11-26): # TRANSLATION UPDATES were made by these fine people: * sr: Мирослав Николић (Miroslav Nikolić) [Serbian] # 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. --------------------------------------------------------------------------------- By popular demand, diffs from the previous release have been omitted. Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-10-25 14:00:25
|
Greetings, Fetchmail 6.4.13 has been released and is now available at the usual location, <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. Please test it and report back. I'll send it off to the translation project in parallel. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.13.tar.lz)= 326dcea5b001ef11e1bf0e3e53da9a4dcb4069120772480fc16b8fa7683672b6 SHA256(fetchmail-6.4.13.tar.xz)= 7d28cf060b06b9c8ec72267be7edc9a99b70f61d7d32d8b609458dcedfa74be1 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.13 (released 2020-10-25, 27608 LoC): # BUG FIXES: * Errors about lock file (= pidfile) creation could be lost in daemon configurations (-d option, or set daemon) when using syslog. Now they are also logged to syslog. Found verifying a pidfile creation issue on 6.4.12 that was previously reported by Alex Hall of Automatic Distributors. * If the lock file cannot be removed (no write permission on directory), try to truncate it, and if that fails, report error. * If the pidfile was non-default, fetchmail -q or --quit would malfunction and claim no other fetchmail were running, because it did not read the configuration files or merge the command line options, thus it would look for the PID in the wrong file. # CHANGES: * Lockfile (= pidfile) creation errors are now logged with filename and reason. # TRANSLATION UPDATES were made by these fine people: * cs: Petr Pisar [Czech] * ja: Takeshi Hamasaki [Japanese] * sq: Besnik Bleta [Albanian] * zh_CN: Boyuan Yang [Chinese (simplified)] * sv: Göran Uddeborg [Swedish] * pl: Jakub Bogusz [Polish] * fr: Frédéric Marchal [French] * eo: Keith Bowes [Esperanto] * de: [German - by current maintainer] --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-10-15 21:40:31
|
[URLs corrected for downloads and GnuPG signatures] Greetings, Fetchmail's 6.4.13 release CANDIDATE #2 is now available at the usual location, <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. Please test it and report back. I'll send it off to the translation project in parallel. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13-rc2.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13-rc2.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13-rc2.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.13-rc2.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.13-rc2.tar.lz)= 045b6ce950423e7b76c8797555ccb8e0fa6ccf513aefeb2ddbbea98843487a97 SHA256(fetchmail-6.4.13-rc2.tar.xz)= 54f582b5b6034e681ca602120b2c865f8efb00768f0672998f3e6bcbe4a988d9 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.13 (work in progress): # BUG FIXES: * Errors about lock file (= pidfile) creation could be lost in daemon configurations (-d option, or set daemon) when using syslog. Now they are also logged to syslog. Found verifying a pidfile creation issue on 6.4.12 that was previously reported by Alex Hall of Automatic Distributors. * If the lock file cannot be removed (no write permission on directory), try to truncate it, and if that fails, report error. * If the pidfile was non-default, fetchmail -q or --quit would malfunction and claim no other fetchmail were running, because it did not read the configuration files or merge the command line options, thus it would look for the PID in the wrong file. # CHANGES: * Lockfile (= pidfile) creation errors are now logged with filename and reason. # TRANSLATION UPDATES were made by these fine people (German was also updated): * cs: Petr Pisar [Czech] * ja: Takeshi Hamasaki [Japanese] * sq: Besnik Bleta [Albanian] * zh_CN: Boyuan Yang [Chinese (simplified)] * sv: Göran Uddeborg [Swedish] * pl: Jakub Bogusz [Polish] * de: [German - by current maintainer] --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-10-15 18:15:44
|
Greetings, Fetchmail's 6.4.13 release CANDIDATE #2 is now available at the usual location, <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. Please test it and report back. I'll send it off to the translation project in parallel. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc2.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc2.tar.lz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc2.tar.xz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc2.tar.lz.asc> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.13-rc2.tar.lz)= 045b6ce950423e7b76c8797555ccb8e0fa6ccf513aefeb2ddbbea98843487a97 SHA256(fetchmail-6.4.13-rc2.tar.xz)= 54f582b5b6034e681ca602120b2c865f8efb00768f0672998f3e6bcbe4a988d9 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.13 (work in progress): # BUG FIXES: * Errors about lock file (= pidfile) creation could be lost in daemon configurations (-d option, or set daemon) when using syslog. Now they are also logged to syslog. Found verifying a pidfile creation issue on 6.4.12 that was previously reported by Alex Hall of Automatic Distributors. * If the lock file cannot be removed (no write permission on directory), try to truncate it, and if that fails, report error. * If the pidfile was non-default, fetchmail -q or --quit would malfunction and claim no other fetchmail were running, because it did not read the configuration files or merge the command line options, thus it would look for the PID in the wrong file. # CHANGES: * Lockfile (= pidfile) creation errors are now logged with filename and reason. # TRANSLATION UPDATES were made by these fine people (German was also updated): * cs: Petr Pisar [Czech] * ja: Takeshi Hamasaki [Japanese] * sq: Besnik Bleta [Albanian] * zh_CN: Boyuan Yang [Chinese (simplified)] * sv: Göran Uddeborg [Swedish] * pl: Jakub Bogusz [Polish] * de: [German - by current maintainer] --------------------------------------------------------------------------------- By popular demand, diffs from the previous release have been omitted. --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-10-13 22:50:11
|
Greetings, Fetchmail's 6.4.13 release CANDIDATE is now available at the usual location, <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. Please test it and report back. I'll send it off to the translation project in parallel. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc1.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc1.tar.lz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc1.tar.xz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.13.rc1.tar.lz.asc> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.13.rc1.tar.lz)= ff9c11c806570ae0f21f78c6e33a9ef434b277454eb1b24043f73b774d579a35 SHA256(fetchmail-6.4.13.rc1.tar.xz)= fc74e83b71c2ad7129db288fe511d4e4f6de94cfcda189705cf61402cd811389 Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.13 (work in progress): # BUG FIXES: * Errors about lock file (= pidfile) creation could be lost in daemon configurations (-d option, or set daemon) when using syslog. Now they are also logged to syslog. Found verifying a pidfile creation issue on 6.4.12 that was previously reported by Alex Hall of Automatic Distributors. * If the lock file cannot be removed (no write permission on directory), try to truncate it, and if that fails, report error. * If the pidfile was non-default, fetchmail -q or --quit would malfunction and claim no other fetchmail were running, because it did not read the configuration files or merge the command line options, thus it would look for the PID in the wrong file. # CHANGES: * Lockfile (= pidfile) creation errors are now logged with filename and reason. --------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-09-04 09:04:52
|
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 |
From: Matthias A. <mat...@gm...> - 2020-08-28 16:51:33
|
Greetings, The 6.4.11 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. == NOTE == I intend this to be the last 6.4.x version with 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.11.tar.lz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.11.tar.xz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.11.tar.lz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.11.tar.xz.asc> SHA256 hash values: SHA256(fetchmail-6.4.11.tar.lz)= cc7ca0899e93b77a2c248dd2f2ac84d5451b73a393b1d601699bcad8ef5e79cb SHA256(fetchmail-6.4.11.tar.xz)= 3e481dd869907c3786b486fd8a7bb4b24e60889b1ac449b786ec0a059b39e29c Here are the release notes: --------------------------------------------------------------------------------- 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 |
From: Matthias A. <mat...@gm...> - 2020-08-27 17:53:33
|
Greetings, The 6.4.10 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. == NOTE == I intend this to be the last 6.4.x version with 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.10.tar.xz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.10.tar.xz.asc> SHA256 hash values: SHA256(fetchmail-6.4.10.tar.lz)= 702d815684c1899b586e6d2549b8fcc23c372ae57537e15cd81e5c2ff5059c37 SHA256(fetchmail-6.4.10.tar.xz)= dbbefd43b8a8ac0517b817fdb63629d321e53fd63143b92d117bbd7d91d7b25e Here are the release notes: --------------------------------------------------------------------------------- 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 |
From: Matthias A. <mat...@gm...> - 2020-07-11 15:25:17
|
The 6.5.0.beta1 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.5.0.beta1.tar.lz> And its GnuPG signature at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5//fetchmail-6.5.0.beta1.tar.lz.asc> You will need lzip to decompress the tarballs, if your OS does not ship it, get it from https://www.nongnu.org/lzip/ The earlier development snapshots released today messed up the TLS cipher list (<= 1.2) or ciphersuite (TLS >= 1.3) setting a bit, and also the error checking. Let's just move forward to a -beta1. Please guide feedback to the fetchmail-devel@ mailing list. Here are the release notes - note the EXPERIMENTAL CHANGES section, which has the most recent updates throughout today. -------------------------------------------------------------------------------- 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. This can only be changed in socket.c, look for SSL_min_security_level = 2. ## 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, for instance, for mailbox sizes, and misreports sizes of 2 GibiB and beyond. * 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. -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2020-07-11 13:59:10
|
Note the final letter of the version: A vs. B. The 6.5.0.dev20200711b release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/>. NOTE: replies with your findings should go to the fetchmail-devel@ mailing list, not -users@. I've made some configure changes that should assist with finding and linking against OpenSSL outside the typical paths, and also set the run-time linker path (rpath) properly. Let me know if/where this regresses and then provide me details (config.log, config.h and make logs) if it fails. It also tightens up OpenSSL to security level 2, so if you know your mail server is pretty old, let me know if it still works for you. This is supposed to become a 6.5.0 in several months' time. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.dev20200711b.tar.lz> GnuPG signature file: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.dev20200711b.tar.lz.asc> Here are the release notes: -------------------------------------------------------------------------------- ## 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 all TLS versions. If setting the ciphers fails, fetchmail will not connect. If not given, defaults to Postfix's "medium" list, "aNULL:-aNULL:HIGH:MEDIUM:+RC4:@STRENGTH". -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2020-07-11 12:39:30
|
The 6.5.0.dev20200711a release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/>. NOTE: replies with your findings should go to the fetchmail-devel@ mailing list, not -users@. I've made some configure changes that should assist with finding and linking against OpenSSL outside the typical paths, and also set the run-time linker path (rpath) properly. Let me know if/where this regresses and then provide me details (config.log, config.h and make logs) if it fails. It also tightens up OpenSSL to security level 2, so if you know your mail server is pretty old, let me know if it still works for you. This is supposed to become a 6.5.0 in several months' time. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.dev20200711a.tar.lz> There's also a GnuPG signature file (with .asc appended) available. 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. This can only be changed in socket.c, look for SSL_min_security_level = 2. ## 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. # 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. -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-06-14 18:20:21
|
Greetings, The 6.4.8 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. == NOTE == I intend this to be the last 6.4.x version with 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.8.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.8.tar.lz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.8.tar.lz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.8.tar.xz.asc> SHA256 hash values: SHA256(fetchmail-6.4.8.tar.lz)= d8e03112a4067e0bf930cba7da20de82d970ad657efa1aeb7fe4e35229cb0ce1 SHA256(fetchmail-6.4.8.tar.xz)= 26cd936ece146e056cdf79a676a33738b4eab0a5ae2edf3fce5ba034721b09bd Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.8 (released 2020-06-14, 27596 LoC): ## NEW TRANSLATION, with thanks to the translator: * sr: Мирослав Николић (Miroslav Nikolić) [Serbian] - Sorry, this was missed earlier because my translation scripts did not properly report new translations. -------------------------------------------------------------------------------- # 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. -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-06-14 17:26:25
|
Greetings, The 6.4.7 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. == NOTE == I intend this to be the last 6.4.x version with 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 in two compressed formats at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.7.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.7.tar.lz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.7.tar.lz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.7.tar.xz.asc> SHA256 hash values: SHA256(fetchmail-6.4.7.tar.lz)= d6e9918240f2ddc07aa91a478f8a6359279d41de287eb5b27e1fe6ee28b1b81e SHA256(fetchmail-6.4.7.tar.xz)= c4c8d1b7356f82f2ec62e55abe1f266acaa808a7398ad79a9211644a7a905c62 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.7 (released 2020-06-14, 27596 LoC): ## TRANSLATION UPDATE, with thanks to the translator: * sv: Göran Uddeborg [Swedish] # 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. -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-05-29 10:39:30
|
Greetings, The 6.4.6 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. This fixes a regression on older operating systems that can print this error: fetchmail: Cannot find absolute path for user's home directory == NOTE == I intend this to be the last 6.4.x version with 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 in two formats at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.6.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.6.tar.lz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.6.tar.lz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.6.tar.xz.asc> SHA256 hash values: SHA256(fetchmail-6.4.6.tar.lz)= 7bc1e126d159e0a2e977104ab262935ff6c1e5d341d271fd07a2d669ed475aff SHA256(fetchmail-6.4.6.tar.xz)= 16efec4b6019b4d2b6e43ed1d4f523dee019ac86754de856d0cf34d503d66011 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.6 (released 2020-05-29, 27596 LoC): ## TRANSLATION UPDATE, with thanks to the translator: * eo: Felipe Castro [Esperanto] -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-05-07 18:16:25
|
Greetings, The 6.4.5 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. This fixes a regression on older operating systems that can print this error: fetchmail: Cannot find absolute path for user's home directory == NOTE == I intend this to be the last 6.4.x version with 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 in two formats at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.5.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.5.tar.lz> Detached GnuPG signatures for the respective tarballs are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.5.tar.lz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.5.tar.xz.asc> SHA256 hash values: SHA256(fetchmail-6.4.5.tar.lz)= 3325f468b821377069cd92089a559aa3a4a240621b01bf470646512d15440d88 SHA256(fetchmail-6.4.5.tar.xz)= d30f06920294490141ddcd4a66583bf16a0c88c1d7b4f58a3b9cef8511946b1c Here are the release notes: fetchmail-6.4.5 (released 2020-05-07, 27596 LoC): ## REGRESSION FIX: * fetchmail 6.4.0 and 6.4.1 changed the resolution of the home directory in a way that requires SUSv4 semantics of realpath(), which leads to 'Cannot find absolute path for... directory' error messages followed by aborts on systems where realpath() follows strict SUSv2 semantics and returns EINVAL if the 2nd argument is NULL. On such systems, for instance, Solaris 10, fetchmail requires PATH_MAX to be defined, and will then work again. Regression reported by David Hough. On systems that neither provide auto-allocation semantics for realpath(), nor PATH_MAX, fetchmail will print this error and abort. Such systems are unsupported, see README. ## CHANGES: * Add a test program fm_realpath, and a t.realpath script, neither to be installed. These will test resolution of the current working directory. ## TRANSLATION UPDATES in reverse alphabetical order of language codes, ## with my thanks to the translators: * zh_CN: Boyuan Yang [Chinese (simplified)] * sv: Göran Uddeborg [Swedish] * sq: Besnik Bleta [Albanian] * pl: Jakub Bogusz [Polish] * ja: Takeshi Hamasaki [Japanese] * fr: Frédéric Marchal [French] * cs: Petr Pisar [Czech] # 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. -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-05-04 10:45:00
|
Greetings, The 6.4.5-rc2 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. It has been mailed out to the translation project so as to collect the one new translation, and possibly updated translations for other languages. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.5-rc2.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.5-rc2.tar.lz> Here are the release notes: fetchmail-6.4.5 (unreleased): ## REGRESSION FIX: * fetchmail 6.4.0 and 6.4.1 changed the resolution of the home directory in a way that requires SUSv4 semantics of realpath(), which leads to 'Cannot find absolute path for... directory' error messages followed by aborts on systems where realpath() follows strict SUSv2 semantics and returns EINVAL if the 2nd argument is NULL. On such systems, for instance, Solaris 10, fetchmail requires PATH_MAX to be defined, and will then work again. Regression reported by David Hough. On systems that neither provide auto-allocation semantics for realpath(), nor PATH_MAX, fetchmail will print this error and abort. Such systems are unsupported, see README. ## CHANGES: * Add a test program fm_realpath, and a t.realpath script, neither to be installed. These will test resolution of the current working directory. Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2020-04-26 10:59:01
|
Greetings, The 6.4.4 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. NOTE: I intend this to be the last 6.4.x version with 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.4.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.4.tar.lz> Detached GnuPG signatures are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.4.tar.lz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.4.tar.xz.asc> Digests (obtained from openssl dgst -sha256): SHA256(fetchmail-6.4.4.tar.lz)= 06bead00aacec86b44edcbcdaf3937f667f7962003ab38784563fb9704d6b4bc SHA256(fetchmail-6.4.4.tar.xz)= 511b60daabf7543a01de06af07c8772290c6807cd53c42a8504960e978f3abea Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.4 (released 2020-04-26, 27530 LoC): ## UPDATED TRANSLATION - WITH THANKS TO THE TRANSLATOR: * ja: Takeshi Hamasaki [Japanese] -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2020-04-05 10:14:57
|
Greetings, The 6.4.3 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. NOTE: I intend this to be the last 6.4.x version with 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 with the same content but different compression format at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.3.tar.lz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.3.tar.xz> Detached GnuPG signatures are at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.3.tar.lz.asc> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.3.tar.xz.asc> Digests (obtained from openssl dgst -sha256): SHA256(fetchmail-6.4.3.tar.lz)= b22217beb0a1545a84a111baada2008f00887afe395a8514805e5297366385d0 SHA256(fetchmail-6.4.3.tar.xz)= b0360e14b9aa5d065eef8ff99ad0347ef6cbbfc934c8114908295a402a09d3e4 Here are the release notes: fetchmail-6.4.3 (released 2020-04-05, 27530 LoC): ## BUGFIXES: * Plug memory leaks when parts of the configuration (defaults, rcfile, command line) override one another. * fetchmail terminated the placeholder command string too late and included garbage from the heap at the end of the string. Workaround: don't use place- holders %h or %p in the --plugin string. Bug added in 6.4.0 when merging Gitlab merge request !5 in order to fix an input buffer overrun. Faulty commit 418cda65f752e367fa663fd13884a45fcbc39ddd. Reported by Stefan Thurner, Gitlab issue #16. * Fetchmail now checks for errors when trying to read the .idfile, Gitlab issue #3. * Fetchmail's error messages that reports that the defaults entry isn't the first was made more precise. It could be misleading if there was a poll or skip statement before the defaults. ## CHANGES: * Fetchmail documentation was updated to require OpenSSL 1.1.1. OpenSSL 1.0.2 reached End Of Life status at the end of the year 2019. Fetchmail will tolerate, but warn about, 1.0.2 for now on the assumption that distributors backport security fixes as the need arises. Fetchmail will also warn if another SSL library that is API-compatible with OpenSSL lacks TLS v1.3 support. * If the trust anchor is missing, fetchmail refers the user to README.SSL. ## INTERNAL CHANGES: * The AC_DECLS(getenv) check was removed, its only user was broken and not accounting for that AC_DECLS always defines HAVE_DECL_... to 0 or 1, so fetchmail never declared a missing getenv() symbol (it was testing with #ifdef). Remove the backup declaration. getenv is mandated by SUSv2 anyways. ## UPDATED TRANSLATION - WITH THANKS TO THE TRANSLATORS: * sq: Besnik Bleta [Albanian] * zh_CN: Boyuan Yang [Chinese (simplified)] * pl: Jakub Bogusz [Polish] * cs: Petr Pisar [Czech] * fr: Frédéric Marchal [French] * sv: Göran Uddeborg [Swedish] * eo: Felipe Castro [Esperanto] -------------------------------------------------------------------------------- |