#14629: fetchmail-6.4.16
-------------------------+------------------------------
 Reporter:  renodr       |       Owner:  pierre.labastie
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  10.1
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+------------------------------

Comment (by pierre.labastie):

 {{{
 fetchmail-6.4.16 (released 2021-02-08, 27707 LoC):

 # BUG FIXES
 * fetchmail's --configdump, and fetchmailconf, lacked support for the
   sslcertfile option. --configdump support added by Earl Chew,
   Gitlab issue #25, merge request !28.
 * fetchmail's manual page was never updated to reflect 6.2.5's change
 about the
   duplicate-killer code for multidrop mode, which read
   "* Dup-killer code now keys on an MD5 hash of the raw headers."
   ...instead of just the Message-ID. [commit 9dd8400, 2003-10-10 by esr]
   The manual page was now updated accordingly and documents
   historic behaviour:
   start to 5.0.7 no duplicate suppression;
   5.0.8 to 6.2.4 duplicate suppression only by Message-ID;
   6.2.5 to 6.4.X duplicate suppression by entire raw header.
   Manpage bug found by Julian Bane debugging "duplicate message"
 behaviour.
 * ./configure no longer runs AC_LIB_LINKFLAGS (how to link) checks
   when called --without-ssl

 # FEATURES
 * fetchmail --version [fetchmail -V] now queries and prints the SSL/TLS
   library's "SSL default trusted certificate" file or directory (mind the
 word
   "default"), where the OpenSSL-compatible TLS implementation will look
 for
   trusted root, meaning certification authority (CA), certificates.
   NOTE 1: watch the output carefully if the line prints the defaults
   or the configured path (without "default").
   NOTE 2: SSL_CERT_DIR and SSL_CERT_FILE are documented environment
 variables
   for OpenSSL 1.1.1 to override the *default* locations (those compiled
 into
   OpenSSL or possibly in its configuration file).
   This was added when Gene Heskett was debugging his setup and the
   information "where does OpenSSL look" was missing.
 * fetchmail --version now prints version of the OpenSSL library that
   it was compiled against, and that it is using at runtime, and also
   the OPENSSL_DIR and OPENSSL_ENGINES_DIR (if available).

 # TRANSLATION UPDATES
   These fine people have contributed updated translations for fetchmail,
   in no particular order:
 * sq:    Besnik Bleta [Albanian]
 * eo:    Keith Bowes [Esperanto]
 * cs:    Petr Pisar [Czech]
 * pl:    Jakub Bogusz [Polish]
 * sv:    Göran Uddeborg [Swedish]
 * fr:    Frédéric Marchal [French]

 # KNOWN BUGS AND WORKAROUNDS
   (This section floats upwards through the NEWS file so it stays with the
   current release information)
 * Fetchmail does not handle messages without Message-ID header well
   (See sourceforge.net bug #780933)
 * Fetchmail currently uses 31-bit signed integers in several places
   where unsigned and/or wider types should have been used, for instance,
   for mailbox sizes, and misreports sizes of 2 GibiB and beyond.
   Fixing this requires C89 compatibility to be relinquished.
 * BSMTP is mostly untested and errors can cause corrupt output.
 * Fetchmail does not track pending deletes across crashes.
 * The command line interface is sometimes a bit stubborn, for instance,
   fetchmail -s doesn't work with a daemon running.
 * Linux systems may return duplicates of an IP address in some
 circumstances if
   no or no global IPv6 addresses are configured.
   (No workaround. Ubuntu Bug#582585, Novell Bug#606980.)
 * Kerberos 5 may be broken, particularly on Heimdal, and provide bogus
 error
   messages. This will not be fixed, because the maintainer has no Kerberos
 5
   server to test against. Use GSSAPI.
 }}}

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/14629#comment:2>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to