Menu
▾
▴
fetchmail-devel — Development related discussion
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
(1) |
Dec
(1) |
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
|
From: Matthias A. <mat...@gm...> - 2020-11-13 00:04:56
|
Am 11.11.20 um 03:22 schrieb Geoff Bailey:
> G'day all,
>
> I'm trying to use fetchmail with Office 365 and XOAUTH2 enabled. So far
> unsuccessfully, alas. Anyway, this section in lines 650 to 662 of pop3.c
> is not helping:
>
> if (ctl->server.authenticate == A_OAUTHBEARER)
> {
> if (has_oauthbearer || !has_xoauth2)
> {
> ok = do_oauthbearer(sock, ctl, FALSE); /* OAUTHBEARER */
> }
> if (ok != PS_SUCCESS && has_xoauth2)
> {
> ok = do_oauthbearer(sock, ctl, TRUE); /* XOAUTH2 */
> }
> break;
> }
>
> As you can see, if has_xoauth2 is true and has_oauthbearer is false, as it
> is in this case, then a very old value of ok is incorrectly used and the
> XOAUTH2 branch is skipped.
>
> The simplest adjustment would be to insert
>
> ok = PS_AUTHFAIL; /* anything other than PS_SUCCESS */
>
> or similar before the has_oauthbearer check.
>
Hi Geoff,
thanks for the report. Does it help to rewrite the code as:
if (ctl->server.authenticate == A_OAUTHBEARER)
{
if (has_oauthbearer || !has_xoauth2)
{
ok = do_oauthbearer(sock, ctl, FALSE); /* OAUTHBEARER */
}
else
{
ok = do_oauthbearer(sock, ctl, TRUE); /* XOAUTH2 */
}
if (ok == PS_SUCCESS)
break;
}
This will change behaviour however, in that there is no fall-through
from OAUTHBEARER if it fails to XOAUTH2.
Cheers,
Matthias
|
|
From: Geoff B. <ft...@gm...> - 2020-11-11 02:23:15
|
G'day all,
I'm trying to use fetchmail with Office 365 and XOAUTH2 enabled. So far
unsuccessfully, alas. Anyway, this section in lines 650 to 662 of pop3.c
is not helping:
if (ctl->server.authenticate == A_OAUTHBEARER)
{
if (has_oauthbearer || !has_xoauth2)
{
ok = do_oauthbearer(sock, ctl, FALSE); /* OAUTHBEARER */
}
if (ok != PS_SUCCESS && has_xoauth2)
{
ok = do_oauthbearer(sock, ctl, TRUE); /* XOAUTH2 */
}
break;
}
As you can see, if has_xoauth2 is true and has_oauthbearer is false, as it
is in this case, then a very old value of ok is incorrectly used and the
XOAUTH2 branch is skipped.
The simplest adjustment would be to insert
ok = PS_AUTHFAIL; /* anything other than PS_SUCCESS */
or similar before the has_oauthbearer check.
(This is not nearly sufficient to fix my problems, of course, but it at
least addresses a manifest error.)
Cheers,
Geoff.
|
|
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-30 15:08:37
|
Am 30.09.20 um 07:29 schrieb haomiao: > Hi > > I am using fetchmail for long time and stored my > passwoed in .netrc file, this file is also used by > my mail sender program (msmtp). > > Recently, I decide to move all my password to a > password store. So I need fetchmail to get password > from external program. > > I modified fetchmail by adding a `password_from` > option and it's worked fine for me. > > How can I contribute my code to fetchmail project? > > Hello haomiao, the best and easiest approach is to migrate that feature code to the "next" branch here: https://gitlab.com/fetchmail/fetchmail/-/tree/next and file a merge request. Existing changes on that branch can be reviewed here: https://gitlab.com/fetchmail/fetchmail/-/blob/next/NEWS#L76 Patches should also be created against the "next" branch in Git. Looking forward to your submission. Regards, Matthias |
|
From: haomiao <mia...@us...> - 2020-09-30 05:33:47
|
Hi I am using fetchmail for long time and stored my passwoed in .netrc file, this file is also used by my mail sender program (msmtp). Recently, I decide to move all my password to a password store. So I need fetchmail to get password from external program. I modified fetchmail by adding a `password_from` option and it's worked fine for me. How can I contribute my code to fetchmail project? -- haomiao |
|
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-21 11:35:03
|
Greetings,
the fetchmail 7.x branch is now called "next". It replaces the prior "master" branch,
which was renamed. (The prior "next" branch was really old and is called old-next.)
Note the Git branches:
legacy_63 (discontinued, unsupported old branch for 6.3.x releases)
legacy_64 (stable 6.4.x releases),
legacy_6x (near-future 6.5.x development),
next (mid-term future 7.x.x development)
Happy fetching,
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:02
|
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] -------------------------------------------------------------------------------- |
|
From: Matthias A. <mat...@gm...> - 2020-03-30 20:29:00
|
Greetings, The 6.4.3-rc2 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. | I found that one bug fix caused double-free errors with asan, and | the TLS1_3 warning rigging wasn't working properly, and that some | HAVE_DECL_ checks were broken. | | Please test if you use the plugin option, or if you are using a more complex configuration | with defaults, or where command line overrides rcfile. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.3-rc2.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.3-rc2.tar.lz> Here are the release notes: fetchmail-6.4.3 (WIP) ## 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. And this is the Git history since -rc1: * aa38c490 2020-03-30 | Record po for 6.4.3-rc2. * 6f7a83c0 2020-03-30 | Make fetchmail -V print SSL/TLS library warnings... * 0e590bf4 2020-03-30 | Fix -SSL/+SSL reporting in fetchmail -V output. * 43b557d5 2020-03-30 | Fix HAVE_DECL_ users to check value, not definition. * 66a35bd6 2020-03-30 | Remove broken AC_CHECK_DECLS(getenv). * c9fb6180 2020-03-30 | Properly report if the defaults entry is not the first. * 5af21c95 2020-03-30 | Bump version, we'll need -rc2. * 85e5a019 2020-03-30 | fetchmail.c Avoid double-free in optmerge()'s STRING_MERGE macro. Happy fetches, Matthias |
|
From: Matthias A. <mat...@gm...> - 2020-03-30 13:10:10
|
The 6.4.3-rc1 release of fetchmail is now available at the usual locations, including <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/>. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.3-rc1.tar.xz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4//fetchmail-6.4.3-rc1.tar.lz> Please test if you use the plugin option, or if you are using a more complex configuration with defaults, or where command line overrides rcfile. Here are the release notes: fetchmail-6.4.3 (WIP) ## 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. ## 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. By popular demand, diffs from the previous release have been omitted. |
|
From: Matthias A. <mat...@gm...> - 2020-03-29 00:04:43
|
The 6.4.3-beta1 release of fetchmail is now available at the usual locations, including <http://sourceforge.net/projects/fetchmail>. The source archive is available at: <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.3-beta1.tar.lz> <https://downloads.sourceforge.net/project/fetchmail/branch_6.4/fetchmail-6.4.2-3-beta1ar.xz> Please test if you use the plugin option, or if you are using a more complex configuration with defaults, or where command line overrides rcfile. ## 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. |
147 messages has been excluded from this view by a project administrator.
