You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(73) |
Jul
(22) |
Aug
(42) |
Sep
(11) |
Oct
(23) |
Nov
(40) |
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
(17) |
Apr
(26) |
May
(6) |
Jun
(21) |
Jul
(133) |
Aug
(25) |
Sep
(40) |
Oct
(12) |
Nov
(71) |
Dec
(57) |
2006 |
Jan
(23) |
Feb
(22) |
Mar
(43) |
Apr
(27) |
May
(13) |
Jun
(7) |
Jul
(3) |
Aug
(20) |
Sep
(16) |
Oct
(17) |
Nov
(31) |
Dec
(10) |
2007 |
Jan
(12) |
Feb
(17) |
Mar
(26) |
Apr
(13) |
May
(4) |
Jun
(1) |
Jul
(1) |
Aug
(21) |
Sep
(3) |
Oct
(8) |
Nov
(8) |
Dec
(5) |
2008 |
Jan
(5) |
Feb
(1) |
Mar
(3) |
Apr
(10) |
May
(3) |
Jun
(11) |
Jul
(5) |
Aug
(1) |
Sep
(6) |
Oct
|
Nov
(10) |
Dec
(2) |
2009 |
Jan
(17) |
Feb
(2) |
Mar
(1) |
Apr
(9) |
May
(23) |
Jun
(22) |
Jul
(32) |
Aug
(30) |
Sep
(11) |
Oct
(24) |
Nov
(4) |
Dec
|
2010 |
Jan
(12) |
Feb
(56) |
Mar
(32) |
Apr
(41) |
May
(36) |
Jun
(14) |
Jul
(7) |
Aug
(10) |
Sep
(13) |
Oct
(16) |
Nov
|
Dec
(14) |
2011 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(16) |
May
(36) |
Jun
(2) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(1) |
Nov
(8) |
Dec
(3) |
2012 |
Jan
(1) |
Feb
(5) |
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(7) |
Sep
(9) |
Oct
(2) |
Nov
(8) |
Dec
(9) |
2013 |
Jan
(11) |
Feb
(6) |
Mar
(14) |
Apr
(10) |
May
|
Jun
(12) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(7) |
Dec
(4) |
2014 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
(7) |
Jul
|
Aug
(8) |
Sep
(8) |
Oct
|
Nov
|
Dec
(2) |
2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
(2) |
Feb
(3) |
Mar
(5) |
Apr
(2) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(2) |
Sep
(3) |
Oct
(4) |
Nov
(3) |
Dec
|
2021 |
Jan
(5) |
Feb
(2) |
Mar
(3) |
Apr
(3) |
May
|
Jun
|
Jul
(2) |
Aug
(14) |
Sep
(3) |
Oct
(4) |
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
(2) |
Oct
(1) |
Nov
|
Dec
|
From: Matthias A. <mat...@gm...> - 2024-10-29 22:10:59
|
The 6.5.0 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.tar.xz/download> The detached GnuPG signature is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.tar.xz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.5.0.tar.xz)= 42611aea4861a5311e5116843f01c203dceadf440bf2eb1b4a43a445f2977668 Note that the Sourceforge Git view is quirky, the preferred Git repository is at https://gitlab.com/fetchmail/fetchmail and mirrored at https://sourceforge.net/p/fetchmail/git/ci/legacy_6x/tree/ But it seems that SourceForge's Git web interface isn't fully recognizing the latest changes on the "legacy_6x" branch that the 6.5.0 release was made from, you need to click the 6.5.0 tag on the left to see the update version. Fetchmail 6.4.X and older releases are now unsupported. DISTRIBUTORS BEWARE: OpenSSL changed license, so you may need to change your license tags and possibly the license which you invoke to redistribute fetchmail. As an alternative, wolfSSL could be used to maintain GPL v2 compatibility, but it lacks some features OpenSSL offers. Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.5.0 (released 2024-10-29, 31200 LoC): ## SECURITY FIX: * .netrc now may not have more than 0700 permission if it contains passwords, else fetchmail will warn and ignore the file. ## 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. * 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 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 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ón Martínez Vera [Spanish] * fr: Frédéric Marchal [French] * ja: Takeshi Hamasaki [Japanese] * ro: Remus-Gabriel Chelu [Romanian] * sv: Göran 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 locally, and if the selected translation would require the Subject: line to wrap inside an RFC-2047 encoded word (=?UTF-8?Q?...?=), the wrapped encoded-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 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. * 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 than 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 advertised 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 debugging. * 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 report 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 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. * 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. ================================================================================ |
From: Matthias A. <mat...@gm...> - 2024-09-28 00:22:48
|
The 6.5.0.rc2 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/>. It adds seven new translations and fixes a PATH_MAX related mis-merge that might break compilation on arcane operating systems. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.rc2.tar.xz/download> The detached GnuPG signature is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.rc2.tar.xz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.5.0.rc2.tar.xz)= 577b4f32b81be2c5ccd4a2ea18131a758f159497b13aba71d8e3a490952914ac Here are the release notes changes since rc1: -------------------------------------------------------------------------------- * 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ón Martínez Vera [Spanish] * fr: Frédéric Marchal [French] * ja: Takeshi Hamasaki [Japanese] * ro: Remus-Gabriel Chelu [Romanian] * sv: Göran Uddeborg [Swedish] * fetchmail now defines its OpenSSL API level to 3.0.0 so as to expose the 3.0.0 APIs from OpenSSL. * 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. * 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. ================================================================================ |
From: Matthias A. <mat...@gm...> - 2024-09-24 15:47:41
|
The 6.5.0.rc1 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.rc1.tar.xz/download> The detached GnuPG signature is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.rc1.tar.xz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.5.0.rc1.tar.xz)= f4c8317bf95477d975c945a5624275729385904a7a2d4931f8098cfd9dddf5d0 Please test this thorougly, report bugs, issues in documentation, everything, through issues on <https://gitlab.com/fetchmail/fetchmail>, and send praise -- and if your translation isn't up to date, consider joining the <https://translationproject.org> and helping out. Thank you very much in advance! Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.5.0 (not yet released): ## SECURITY FIX: * .netrc now may not have more than 0700 permission if it contains passwords, else fetchmail will warn and ignore the file. ## 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. * 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 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 or wolfSSL, at a minimum OpenSSL v1.1.1 or wolfSSL v5.5.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. (fetchmail was requesting to hide deprecated APIs.) * 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 locally, and if the selected translation would require the Subject: line to wrap inside an RFC-2047 encoded word (=?UTF-8?Q?...?=), the wrapped encoded-word was not indented, thus not marked as a continuation line. ## 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. * 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 than 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 advertised 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 debugging. * 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 report 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 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. * 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 0.60 or newer <https://mesonbuild.com/>. fetchmail is not currently written in a way that supports unity (amalgamated) builds. ================================================================================ |
From: Matthias A. <mat...@gm...> - 2024-07-20 09:42:16
|
The 6.4.39 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.39.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.39.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.39.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.39.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.39.tar.xz)= 75109a1f307b538155fa05f5ef298e8298cb4deae95aed24c16b38d36ff0a186 SHA2-256(fetchmail-6.4.39.tar.lz)= 657ff8655860e649c0863eb942eda1668d4f20f72263129622829e60c018854b Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.39 (released 2024-07-20, 31729 LoC): # BUG FIXES: * When a server offers STARTTLS although the connection is already wrapped in TLS, fetchmail would issue a bogus "WARNING: server offered STARTTLS but sslproto '' given." (or STLS for POP3). In situations where we wrap the connection in TLS, suppress the warning. Reported by Mike Pope. * If fetchmail was running localized, generate an error e-mail message locally, and if the selected translation would require the Subject: line to wrap inside an RFC-2047 encoded word (=?UTF-8?Q?...?=), the wrapped encoded-word was not indented, thus not marked as a continuation line. -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2024-05-14 23:12:04
|
The 6.5.0.beta10 release of fetchmail is now available at the usual location, <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/>. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.5/fetchmail-6.5.0.beta10.tar.xz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.5/fetchmail-6.5.0.beta10.tar.xz.asc/download> The SHA256 hash for the tarball is: SHA2-256(fetchmail-6.5.0.beta10.tar.xz)= 1c818b87ccd6cde10b18e55bb30e2ce9dca9c4cc28be699fd436c4eab87ac636 ============================================================================ |
From: Matthias A. <mat...@gm...> - 2024-01-31 21:05:15
|
Note that the shipped NEWS file in the tarball and this release message claim fetchmail-6.4.38 were "not yet released", but I have released iti today intentionally, not by accident. That line should have read instead: "fetchmail-6.4.38 (released 2024-01-31, 31720 LoC)" and has been pushed with a GnuPG-signed tag to the Git repos, https://gitlab.com/fetchmail/fetchmail and https://sourceforge.net/p/fetchmail/git/ci/legacy_64/tree/ Am Wed, Jan 31, 2024 at 10:00:33PM +0100 schrieb Matthias Andree: > The 6.4.38 release of fetchmail is now available at the usual locations, > including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. > > The source archive is available at: > <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.xz/download> > <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.lz/download> > > The detached GnuPG signature is available at: > <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.xz.asc/download> > <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.lz.asc/download> > > The SHA256 hashes for the tarballs are: > SHA2-256(fetchmail-6.4.38.tar.xz)= a6cb4ea863ac61d242ffb2db564a39123761578d3e40d71ce7b6f2905be609d9 > SHA2-256(fetchmail-6.4.38.tar.lz)= be82b520d9698c1378c3a9a4dbab4d392c8c90d457af11a97ce9b85a3fedc70a > > > Here are the release notes: > -------------------------------------------------------------------------------- > fetchmail-6.4.38 (not yet released): > > # BREAKING CHANGES: > * Tighten OpenSSL and wolfSSL version requirements again. See README.SSL. > Distributors providing older versions that they backport security fixes for > may want to patch socket.c but remember to redirect support to your > distribution's support channels. > The fetchmail maintainer only supports functionally unmodified builds with > publicly available SSL/TLS library versions. > fetchmail will refuse to build against OpenSSL 1.0.2 older than 1.0.2u, > or wolfSSL older than 5.6.2. It will warn about OpenSSL older than 3.0.9, > or between 3.1.0 and 3.1.4, or wolfSSL older than 5.6.6. > > # TRANSLATIONS: language translations were updated by these fine people: > (in reverse alphabetical order of language codes): > * ru: Kirill Isakov [Russian] > * eo: Keith Bowes [Esperanto] > > -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2024-01-31 21:00:50
|
The 6.4.38 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.38.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.38.tar.xz)= a6cb4ea863ac61d242ffb2db564a39123761578d3e40d71ce7b6f2905be609d9 SHA2-256(fetchmail-6.4.38.tar.lz)= be82b520d9698c1378c3a9a4dbab4d392c8c90d457af11a97ce9b85a3fedc70a Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.38 (not yet released): # BREAKING CHANGES: * Tighten OpenSSL and wolfSSL version requirements again. See README.SSL. Distributors providing older versions that they backport security fixes for may want to patch socket.c but remember to redirect support to your distribution's support channels. The fetchmail maintainer only supports functionally unmodified builds with publicly available SSL/TLS library versions. fetchmail will refuse to build against OpenSSL 1.0.2 older than 1.0.2u, or wolfSSL older than 5.6.2. It will warn about OpenSSL older than 3.0.9, or between 3.1.0 and 3.1.4, or wolfSSL older than 5.6.6. # TRANSLATIONS: language translations were updated by these fine people: (in reverse alphabetical order of language codes): * ru: Kirill Isakov [Russian] * eo: Keith Bowes [Esperanto] -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2023-02-26 10:28:17
|
The 6.4.37 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.37.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.37.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.37.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.37.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.37.tar.xz)= 4a182e5d893e9abe6ac37ae71e542651fce6d606234fc735c2aaae18657e69ea SHA2-256(fetchmail-6.4.37.tar.lz)= 2bc3c602bb967a8d7a7348a6e7bdffc54ab93c61187301431c63914372ec3c1b Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.37 (released 2023-02-26, 31710 LoC): # TRANSLATIONS: language translations were updated by this fine person: * sr: Мирослав Николић (Miroslav Nikolić) [Serbian] -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2023-01-28 09:52:47
|
The 6.4.36 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.36.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.36.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.36.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.36.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.36.tar.xz)= 700d433838d3e29e304452aec56b21874f538ec24113fdcbb25139c5f2edc23a SHA2-256(fetchmail-6.4.36.tar.lz)= 5554fd033b461f255f83301985fe12b5bbf964d8fdcead87a339b7e0c726cd65 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.36 (released 2023-01-28, 31710 LoC): # TRANSLATIONS: language translations were updated by these fine people: (in alphabetical order of language codes): * cs: Petr Pisar [Czech] * es: Cristian Othón Martínez Vera [Spanish] * fr: Frédéric Marchal [French] * ja: Takeshi Hamasaki [Japanese] * pl: Jakub Bogusz [Polish] * ro: Remus-Gabriel Chelu [Romanian] * sq: Besnik Bleta [Albanian] * sv: Göran Uddeborg [Swedish] -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2023-01-06 21:09:45
|
The 6.5.0.beta9 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.beta9.tar.xz/download> The detached GnuPG signature is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.beta9.tar.xz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.5.0.beta9.tar.xz)= ee6212d2aad80507f9128a0969ae1a2a8dbd3407c8bf8e5f9ec4fc3a6754b093 Here are the additions to the release notes since beta8: +--------------------------------------------------------------------------- KNOWN ISSUES: * Using ccache may trigger "implicit fallthrough" warnings because the comments that, for instance, GCC understands, are removed by ccache's separate preprocessing. Fixing this portably requires C++17. INCOMPATIBLE CHANGES: * 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 requires a TLSv1.3-capable version of OpenSSL or wolfSSL, at a minimum OpenSSL v1.1.1 or wolfSSL v5.5.1. ## BUG FIXES * Received: lines now return GMT time if the tzoffset cannot be represented as whole minutes. Reported by @rriddicc via Gitlab #49. ## CHANGES * 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. * fetchmail can be built with meson 0.60 or newer <https://mesonbuild.com/>. fetchmail is not currently written in a way that supports unity (amalgamated) builds. ============================================================================ |
From: Matthias A. <mat...@gm...> - 2023-01-04 11:34:23
|
The 6.4.35 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.35.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.35.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.35.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.35.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.35.tar.xz)= 7b0b56cbc0fca854504f167795fab532d5a54d5a7d3b6e3e36a33f34a0960a01 SHA2-256(fetchmail-6.4.35.tar.lz)= 8c8675b4655344d6d14143c4a16fa0ebcf5754c9e707d413dab9fec68d1826cd Here are the release notes: >------------------------------------------------------------------------------- fetchmail-6.4.35 (released 2023-01-04, 31707 LoC): # BREAKING CHANGES: * Fetchmail now warns about OpenSSL before 1.1.1s or 3.0.7, and rejects wolfSSL older than 5.5.0. # TRANSLATIONS: language translations were updated by these fine people: (in reverse alphabetical order of language codes so as not to prefer people): * sv: Göran Uddeborg [Swedish] * eo: Keith Bowes [Esperanto] >------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2022-10-16 11:49:27
|
The 6.5.0.beta8 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.beta8.tar.xz/download> The detached GnuPG signature is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.beta8.tar.xz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.5.0.beta8.tar.xz)= 2d984fcd03a26629efdb9126c33db5d03c63b59c35b3924f86f0ec8700fbfcd9 Here are the release notes since beta7, but also review the NEWS file for all changes since 6.4.28..6.4.34 which are also part of this release but not shown here for brevity. See <https://gitlab.com/fetchmail/fetchmail/-/blob/6.5.0.beta8/NEWS> -------------------------------------------------------------------------------- * --auth ssh may be removed from future fetchmail versions. Use --auth implicit. * Future fetchmail releases (even minor ones) may change undocumented parts of the .netrc parser in incompatible ways to enhance compatibility with typical ftp(1) .netrc parsers. * Apparently OPIE is dying. I only have this support on FreeBSD, and FreeBSD 14 (slated for release in 2023) is about to remove it. -------------------------------------------------------------------------------- * FreeBSD's OPIE implementation cannot be found when using a C++ compiler. This should not affect the normal build, which uses a C compiler. * .netrc now may not have more than 0700 permission if it contains * passwords, else fetchmail will warn and ignore the file. * 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. * 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 report it as implicit. * fetchmail can be built with meson <https://mesonbuild.com/>. ================================================================================ |
From: Matthias A. <mat...@gm...> - 2022-10-15 14:04:16
|
The 6.4.34 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It fixes a situation where a permanent SMTP refusal could cause loss of messages (by deletion from the upstream server) even though softbounce was set. Bug report and patch courtesy of Horváth Zsolt. Translation update for Serbian courtesy of Miroslav Nikolić. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.34.tar.xz)= c3bdded1b5ce236960bd1ceeee3f3257220ed99c3eec84a5d76bb5618e3258d4 SHA2-256(fetchmail-6.4.34.tar.lz)= 920b9b488471d1c76a2e7060344eec347b409ef954a86a200549cf6c2adf40fe Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.34 (released 2022-10-15, 31701 LoC): # CRITICAL BUG FIXES: * When an SMTP receiver refuses delivery, a message would be deleted from the mail store in spite of a softbounce option that is enabled. Bug report, analysis and patch by Horváth Zsolt. Gitlab, fixes #50. # BUILD NOTE: * If you are reusing config.cache from prior builds, this may cause issues with finding Python or some libraries. In case of trouble, remove config.cache and retry. # TRANSLATIONS: language translations were updated by this fine person: * sr: Мирослав Николић (Miroslav Nikolić) [Serbian] -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2022-08-27 07:11:57
|
The 6.4.33 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. Turns out the snapd version of HTMLDOC 1.9.16 is broken, so I have added a wrapper script that uses the flatpak version of HTMLDOC, for the benefit of rebuilding on distros that do not ship HTMLDOC natively. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.33.tar.xz)= 82954ebd26c77906463ce20adca45cbcf8068957441e17941bd3052a5c15432e SHA2-256(fetchmail-6.4.33.tar.lz)= 80fe73c709e8390deabe7e7db979fca4c161d35056331397a4b783c4aacb5911 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.33 (released 2022-08-27, 31696 LoC): # TRANSLATIONS: language translations were updated by this fine person: * fr: Frédéric Marchal [French] # CONTRIBUTED SCRIPT CHANGES: * contrib/fetchsetup improvements by Matěj Cepl * contrib/runfetchmail improvements by Matěj Cepl -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2022-07-30 10:57:56
|
The 6.4.32 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It updates translations and makes maintainer-build fixes. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.32.tar.xz)= 3ee7444665606ad06fb5f7b15f91e3173b845bc98b646b1a4514a46aa48b7228 SHA2-256(fetchmail-6.4.32.tar.lz)= fea53fc9088207c65bcc3692d66ad91958fbff2e65aef74ca34094f4361e8169 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.32 (released 2022-07-30, 31696 LoC): # FIXES: * Use configure to find rst2html, some systems install it only with .py suffix, others only without, and some install both. * Update README.maintainer # TRANSLATIONS: language translations were updated by these fine people: (in alphabetical order of language codes so as not to prefer people): * cs: Petr Pisar [Czech] * es: Cristian Othón Martínez Vera [Spanish] * ja: Takeshi Hamasaki [Japanese] * pl: Jakub Bogusz [Polish] * ro: Remus-Gabriel Chelu [Romanian] * sq: Besnik Bleta [Albanian] * sv: Göran Uddeborg [Swedish] -------------------------------------------------------------------------------- |
From: Matthias A. <mat...@gm...> - 2022-07-16 12:31:33
|
Note that fetchmail 6.4.31's tarball contains the wrong date and version in the manual page, it will identify as 6.4.30 from February this year, not as up to date 6.4.31. If you find that confusing, apply the following one-line patch (also attached in Git e-mail patch format): --- a/fetchmail.man +++ b/fetchmail.man @@ -10,7 +10,7 @@ .\" Load www macros to process .URL requests, this requires groff: .mso www.tmac .\" -.TH fetchmail 1 2022-02-18 "fetchmail 6.4.30" "fetchmail reference manual" +.TH fetchmail 1 2022-07-16 "fetchmail 6.4.31" "fetchmail reference manual" .SH NAME fetchmail \- fetch mail from a POP, IMAP, ETRN, or ODMR-capable server -- Matthias Andree |
From: Matthias A. <mat...@gm...> - 2022-07-16 12:12:07
|
The 6.4.31 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It should make the build a bit more robust and the manpage more portable, and adds some error checking to the .netrc file parser. Further .netrc parser updates and documentation of expected input formats are postponed to fetchmail 6.5 because they might break existing setups, so should not change in a patchlevel release. Note that OpenSSL and wolfSSL both had security updates, OpenSSL for c_rehash, and wolfSSL had fixes for side channel attacks. Upgrade those before you upgrade fetchmail. Versions are at least OpenSSL 1.1.1q or 3.0.5, or wolfSSL 5.4.0. The documentation has been updated accordingly, but fetchmail does not enforce these, leaving it up to distributors. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA2-256(fetchmail-6.4.31.tar.xz)= 904bf9247054df8e91b47b1a9fe15a31dda8478c25b5291da0424653744a28f7 SHA2-256(fetchmail-6.4.31.tar.lz)= db7bf0af57f5a5b41ef5cb4c8d62e3f20b3513fc5b964fd2ea84cf1b7814a53c Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.31 (released 2022-07-16, 31694 LoC): # BUG FIXES: * Try to fix ./configure --with-ssl=... for systems that have multiple OpenSSL versions installed. Issues reported by Dennis Putnam. * The netrc parser now reports its errors to syslog or logfile when appropriate, previously it would always log to stderr. * Add error checking to .netrc parser. # CHANGES: * manpage: use .UR/.UE macros instead of .URL for URIs. * manpage: fix contractions. Found with FreeBSD's igor tool. * manpage: HTML now built with pandoc -> python-docutils (manServer.pl was dropped) -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2022-04-26 19:24:15
|
The 6.4.30 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It updates the Romanian-language translations and tightens up SSL/TLS library version requirements a tiny bit and might fix cross-compilation. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.30.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.30.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.30.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.30.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA256(fetchmail-6.4.30.tar.xz)= 35824c20aa1d8d97e3f1611fef49b9f7f68396f7cbc4d3a807fed27ae9ea445a SHA256(fetchmail-6.4.30.tar.lz)= 2a5feabd20379401664f8fdd99c1e2506aa6acaef6daa4a678ef365be7972303 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.30 (released 2022-04-26, 31666 LoC): # BREAKING CHANGES: * Bump wolfSSL minimum required version to 5.2.0 to pull in security fix. # CHANGES: * Using OpenSSL 1.* before 1.1.1n elicits a compile-time warning. * Using OpenSSL 3.* before 3.0.2 elicits a compile-time warning. * configure.ac was tweaked in order to hopefully fix cross-compilation issues report, and different patch suggested, by Fabrice Fontaine, https://gitlab.com/fetchmail/fetchmail/-/merge_requests/42 # TRANSLATIONS: language translations were updated by this fine person: * ro: Remus-Gabriel Chelu [Romanian] -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2022-03-20 11:27:57
|
The 6.4.29 release of fetchmail is now available at <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It updates the Vietnamese-language translations. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.29.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.29.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.29.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.29.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA256(fetchmail-6.4.29.tar.xz)= 397df984082abae51edec6831700d68636f0e117cfaffcbdd3eed66d04b97321 SHA256(fetchmail-6.4.29.tar.lz)= 7f465b1959197f0510309986da02ba5fa813b6e2fd863bbb5994798b83a1ff85 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.29 (released 2022-03-20, 31661 LoC): # TRANSLATIONS: language translations were updated by this fine person: * vi: Trần Ngọc Quân [Vietnamese] -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2022-03-05 16:26:47
|
The 6.4.28 release of fetchmail is now available from <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It updates the Spanish translation, courtesy of Cristian Othón Martínez Vera. DISTRIBUTORS please note OpenSSL's licensing change for OpenSSL 3, and you may want to review COPYING. NOTE that LibreSSL licensing is incompatible with fetchmail's, as there is no GPL clause 2(b) exception for LibreSSL, so LibreSSL can only be used where it is part of the operating system (one of the very few examples is OpenBSD). The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.28.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.28.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.28.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.28.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA256(fetchmail-6.4.28.tar.xz)= a003f9ac88bf083a232c9451ef5f3f88473fad2c7f2822d3f7455a6d32bc3a97 SHA256(fetchmail-6.4.28.tar.lz)= 5ba7ea053772b8eafa65cd410656225ec5ced8b51e47296fb11c31a7940ad423 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.28 (released 2022-03-05, 31661 LoC): # TRANSLATIONS: language translations were updated by this fine person: * es: Cristian Othón Martínez Vera [Spanish] -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2022-02-28 01:51:00
|
The 6.4.27 release of fetchmail has been available for a month <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. I seem not to have mailed out the announcement... ...and upgrading is not really essential from 6.4.26. Do note that when using with wolfSSL that you pull in its security fix, and unless you've linked wolfSSL dynamically, rebuild fetchmail. DISTRIBUTORS please note OpenSSL's licensing change for OpenSSL 3, and you may want to review COPYING. NOTE that LibreSSL licensing is incompatible with fetchmail's, as there is no GPL clause 2(b) exception for LibreSSL, so LibreSSL can only be used where it is part of the operating system (one of the very few examples is OpenBSD). The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.27.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.27.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.27.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.27.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA256(fetchmail-6.4.27.tar.xz)= 9e64f9e71f798cf1fe2278b84e2f5880b806527c0c0206925c086ccd179113dc SHA256(fetchmail-6.4.27.tar.lz)= 09e3818043c40d0eeb53565ff0d9aca657ff3de3950a378f699aec984f28a335 Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.27 (released 2022-01-26, 31661 LoC): # BREAKING CHANGES: * Bump wolfSSL minimum required version to 5.1.1 to pull in security fix. # TRANSLATIONS: language translations were updated by this fine person: * ro: Remus-Gabriel Chelu [Romanian] -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2022-02-28 01:44:54
|
Greetings, The 6.5.0.beta7 release of fetchmail is now available at <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.beta7.tar.xz/download> The detached GnuPG signature is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.beta7.tar.xz.asc/download> The SHA256 hash for the tarball is: SHA256(fetchmail-6.5.0.beta7.tar.xz)= ec7c7b1af74e6cf8b4011bbe4f270796775e9db672a731bc68980124b91d0133 Here are the release notes: =------------------------------------------------------------------------------- fetchmail-6.5.0.beta7: (since .beta6): # ADDITIONS: * There is now a --forceidle feature to force idle mode even if not advertised in the server capabilities. This is a dangerous option, use it carefully. Courtesy of Eric Durand, GitLab merge request !39. * 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 debugging. =------------------------------------------------------------------------------- fetchmail-6.4.22...27 were merged into .beta7, highlights: # BREAKING CHANGES: * Since distributions continue patching for LibreSSL use, which cannot be linked legally, block out LibreSSL in configure.ac and socket.c, and refer to COPYING, unless on OpenBSD (which ships it in the base system). OpenSSL and wolfSSL 5 can be used. SSL-related documentation was updated, do re-read COPYING, INSTALL, README, README.packaging, README.SSL. Note that distribution of packages linked with LibreSSL is not feasible due to a missing GPLv2 clause 2(b) exception. fetchmail can now be used with wolfSSL 5.1.1's OpenSSL compatibility layer, see INSTALL and README.SSL. This is considered experimental. Feedback solicited. # OPENSSL AND LICENSING NOTE: * fetchmail 6.5.0 is compatible with OpenSSL 1.1.1 and 3.0.0. OpenSSL's licensing changed between these releases from dual OpenSSL/SSLeay license to Apache License v2.0, which is considered incompatible with GPL v2 by the FSF. For implications and details, see the file COPYING. # ADDITIONS: * Added an example systemd unit file and instructions to contrib/systemd/ which runs fetchmail as a daemon with 5-minute poll intervals. Courteously contributed by Barak A. Pearlmutter, Debian Bug#981464. # CHANGES: * ./configure --with-ssl now supports pkg-config module names, too. See INSTALL. * IMAP: When fetchmail is in not-authenticated state and the server volunteers CAPABILITY information, use it and do not re-probe. (After STARTTLS, fetchmail must and will re-probe explicitly.) * fetchmail.man and README.SSL were updated in line with RFC-8314/8996/8997 recommendations to prefer Implicit TLS (--ssl/ssl) and TLS v1.2 or newer, placing --sslproto tls1.2+ more prominently. # SECURITY FIXES: * CVE-2021-39272: fetchmail-SA-2021-02: On IMAP connections, without --ssl and with nonempty --sslproto, meaning that fetchmail is to enforce TLS, and when the server or an attacker sends a PREAUTH greeting, fetchmail used to continue an unencrypted connection. Now, log the error and abort the connection. --Recommendation for servers that support SSL/TLS-wrapped or "implicit" mode on a dedicated port (default 993): use --ssl, or the ssl user option in an rcfile. --Reported by: Andrew C. Aitchison, based on the USENIX Security 21 paper "Why TLS is better without STARTTLS - A Security Analysis of STARTTLS in the Email Context" by Damian Poddebniak, Fabian Ising, Hanno Böck, and Sebastian Schinzel. The paper did not mention fetchmail. * This allows STARTTLS in more scenarios, but also hardens against bypassing. # BUG FIXES: * Fetchmail no longer crashes when attempting a connection with --plugin "" or --plugout "". * Fetchmail no longer leaks memory when processing the arguments of --plugin or --plugout on connections. * On POP3 connections, the CAPAbilities parser is now caseblind. * Fix segfault on configurations with "defaults ... no envelope". Reported by Bjørn Mork. Fixes Debian Bug#992400. This is a regression in fetchmail 6.4.3 and happened when plugging memory leaks, which did not account for that the envelope parameter is special when set as "no envelope". The segfault happens in a constant strlen(-1), triggered by trusted local input => no vulnerability. * Fix program abort (SIGABRT) with "internal error" when invalid sslproto is given with OpenSSL 1.1.0 API compatible SSL implementations. ================================================================================ |
From: Matthias A. <mat...@gm...> - 2021-12-26 21:56:25
|
The 6.4.26 release of fetchmail is now available at the usual locations, including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. DISTRIBUTORS please note OpenSSL's licensing change for OpenSSL 3, and you may want to review COPYING. NOTE that LibreSSL licensing is incompatible with fetchmail's, as there is no GPL clause 2(b) exception for LibreSSL, so LibreSSL can only be used where it is part of the operating system (one of the very few examples is OpenBSD). The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.26.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.26.tar.lz/download> The detached GnuPG signature is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.26.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.26.tar.lz.asc/download> The SHA256 hashes for the tarballs are: SHA256(fetchmail-6.4.26.tar.xz)= 2cc8a94bfaaf794687b2b2147786508f30da598d1ab035c345d731928ac40c9a SHA256(fetchmail-6.4.26.tar.lz)= 18060c9a3aa4b0eb31fdf3543503313a136aac5b979d5a8fcba8e886fbd188ab Here are the release notes: -------------------------------------------------------------------------------- fetchmail-6.4.26 (released 2021-12-26, 31661 LoC): # FIXES: * When using wolfSSL 5.0.0, work around a bug that appears to hit wolfSSL when receiving handshake records while still in SSL_peek(). Workaround is to read 1 byte and cache it, then call SSL_peek() again. This affects only some servers. https://github.com/wolfSSL/wolfssl/issues/4593 # TRANSLATIONS: language translations were updated by this fine person: * sr: Мирослав Николић (Miroslav Nikolić) [Serbian] -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2021-12-10 19:24:57
|
Greetings, The 6.4.25 release of fetchmail is now available at <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. DISTRIBUTORS please note OpenSSL's licensing change for OpenSSL 3, and you may want to review COPYING. NOTE that LibreSSL licensing is incompatible with fetchmail's, as there is no GPL clause 2(b) exception for LibreSSL, so LibreSSL can only be used where it is part of the operating system (one of the very few examples is OpenBSD). There have been several tweaks to improve the stability of the configure script and build again. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.25.tar.xz/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.25.tar.lz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.25.tar.xz.asc/download> <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.25.tar.lz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.25.tar.lz)= ba94f3d9ea3e9dd55e59b7a08ca71edfdbc3e3ca1413a285aa8b08aaac923b05 SHA256(fetchmail-6.4.25.tar.xz)= 7ebefbe89172fd59f0fd8317d8743a8436f375ccdcab3900e4c3ec06a8fbf27f Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.25 (released 2021-12-10, 31653 LoC): # BREAKING CHANGES: * Since distributions continue patching for LibreSSL use, which cannot be linked legally, block out LibreSSL in configure.ac and socket.c, and refer to COPYING, unless on OpenBSD (which ships it in the base system). OpenSSL and wolfSSL 5 can be used. SSL-related documentation was updated, do re-read COPYING, INSTALL, README, README.packaging, README.SSL. * Bump OpenSSL version requirement to 1.0.2f in order to safely remove the obsolete OpenSSL flag SSL_OP_SINGLE_DH_USE. This blocks out 1.0.2e and older 1.0.2 versions. 1.0.2f was a security fix release, and 1.0.2u is publicly available from https://www.openssl.org/source/old/1.0.2/ * Some of the configure.ac fiddling MIGHT have broken cross-compilation again. The maintainer does not test cross-compiling fetchmail; if you have difficulties, try setting PKG_CONFIG_LIBDIR to the pkg-config path containing your target/host libraries, or see if --with-ssl-prefix or --with-wolfssl-prefix, or overriding LDFLAGS/LIBS/CPPFLAGS, can help. Feedback solicited on compliant systems that are before end-of-life. # BUG FIXES: * 6.4.24's workaround for OpenSSL 1.0.2's X509_V_FLAG_TRUSTED_FIRST flag contained a typo and would not kick in properly. * Library and/or rpath setting from configure.ac was fixed. # ADDITIONS: * Added an example systemd unit file and instructions to contrib/systemd/ which runs fetchmail as a daemon with 5-minute poll intervals. Courteously contributed by Barak A. Pearlmutter, Debian Bug#981464. * fetchmail can now be used with wolfSSL 5's OpenSSL compatibility layer, see INSTALL and README.SSL. This is considered experimental. Feedback solicited. # CHANGES: * The getstats.py dist-tool now counts lines of .ac and .am files. * ./configure --with-ssl now supports pkg-config module names, too. See INSTALL. # TRANSLATIONS: language translations were updated by these fine people: (in reverse alphabetical order of language codes so as not to prefer people): * sv: Göran Uddeborg [Swedish] * sq: Besnik Bleta [Albanian] * pl: Jakub Bogusz [Polish] * ja: Takeshi Hamasaki [Japanese] * fr: Frédéric Marchal [French] * eo: Keith Bowes [Esperanto] * cs: Petr Pisar [Czech] # CREDITS: * Thanks to Corey Halpin for testing release candidates. -------------------------------------------------------------------------------- Happy fetches, Matthias |
From: Matthias A. <mat...@gm...> - 2021-12-03 00:15:54
|
Greetings, The 6.4.25 release CANDIDATE #4 of fetchmail is now available at <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>. It fixes up the OpenSSL 1.0.2 workaround for Let's Encrypt Sites. It contains support for wolfSSL 5.0, blocks out LibreSSL due to licensing issues, and overhauls the configure script for OpenSSL. release candidate #2 adds contrib/systemd (which see) and makes some fixes to configure.ac. It updated some translations. release candidate #3 makes more fixes to configure.ac and updates some translations. release candidate #4 fixes compilation with wolfSSL on 32-bit systems, for instance, FreeBSD i386, and mentions that wolfSSL support requires a C99 compiler. See COPYING, INSTALL, README.SSL, README.packaging for more details on the news. Please test this thoroughly and report your findings so we can be sure that 6.4.25 will be a good release. It has been mailed out to the translation project to solicit translation updates. The source archive is available at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.25.rc4.tar.xz/download> Detached GnuPG signatures for the respective tarballs are at: <https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.25.rc4.tar.xz.asc/download> SHA256 hash values for the tarballs: SHA256(fetchmail-6.4.25.rc4.tar.xz)= d1ea78ea27245631908cf8fe4e821a9a534cb97e9ce68a4afd4302903df054d5 Thanks to Corey Halpin for the suggestion about license clarification with gnu.org links (submitted through FreeBSD's Bugzilla). Here are the release notes: --------------------------------------------------------------------------------- fetchmail-6.4.25.rc4 (release candidate issued 2021-12-03, 31641 LoC): # BREAKING CHANGES: * Since distributions continue patching for LibreSSL use, which cannot be linked legally, block out LibreSSL in configure.ac and socket.c, and refer to COPYING. OpenSSL and wolfSSL 5 can be used. SSL-related documentation was updated, do re-read COPYING, INSTALL, README, README.packaging, README.SSL. * Bump OpenSSL version requirement to 1.0.2f in order to safely remove the obsolete OpenSSL flag SSL_OP_SINGLE_DH_USE. This blocks out 1.0.2e and older 1.0.2 versions. 1.0.2f was a security fix release, and 1.0.2u is publicly available from https://www.openssl.org/source/old/1.0.2/ * Some of the configure.ac fiddling MIGHT have broken cross-compilation again. The maintainer does not test cross-compiling fetchmail; if you have difficulties, try setting PKG_CONFIG_LIBDIR to the pkg-config path containing your target/host libraries, or see if --with-ssl-prefix or --with-wolfssl-prefix, or overriding LDFLAGS/LIBS/CPPFLAGS, can help. Feedback solicited on compliant systems that are before end-of-life. # BUG FIXES: * 6.4.24's workaround for OpenSSL 1.0.2's X509_V_FLAG_TRUSTED_FIRST flag contained a typo and would not kick in properly. * Library and/or rpath setting from configure.ac was fixed. # ADDITIONS: * Added an example systemd unit file and instructions to contrib/systemd/ which runs fetchmail as a daemon with 5-minute poll intervals. Courteously contributed by Barak A. Pearlmutter, Debian Bug#981464. # CHANGES: * fetchmail can now be used with wolfSSL 5's OpenSSL compatibility layer, see INSTALL and README.SSL. This is considered experimental. Feedback solicited. * The getstats.py dist-tool now counts lines of .ac and .am files. * ./configure --with-ssl now supports pkg-config module names, too. See INSTALL. # TRANSLATIONS: language translations were updated by these fine people: (in reverse alphabetical order of language codes so as not to prefer people): * sv: Göran Uddeborg [Swedish] * sq: Besnik Bleta [Albanian] * pl: Jakub Bogusz [Polish] * ja: Takeshi Hamasaki [Japanese] * fr: Frédéric Marchal [French] * eo: Keith Bowes [Esperanto] * cs: Petr Pisar [Czech] # CREDITS: * Thanks to Corey Halpin for testing release candidates. -------------------------------------------------------------------------------- Happy fetches, Matthias |