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 |