Documentation updates.

1 files changed, 19 insertions, 10 deletions

diff --git a/NEWS b/NEWS
index 7ecb0bf8..a36bc39e 100644
--- a/NEWS
+++ b/NEWS
@@ -11,6 +11,13 @@ change.  MA = Matthias Andree, ESR = Eric S. Raymond, RF = Rob Funk.)
 # ADVANCE WARNING OF FEATURES TO BE REMOVED OR CHANGED IN FUTURE VERSIONS
 (There are no plans to remove features from a 6.3.X release, but they may be
 removed from a 6.4.0 or newer release.)
+* Future fetchmail releases may require compilers and operating systems
+  that adhere to standards issued 2011 or later.
+  (Currently, C89 and Single Unix Specification V2 should suffice.)
+* Future fetchmail releases may tighten up security and lean towards
+  it a bit more by, for instance, implementing recommendations from
+  RFC-7817 or RFC-8314. This may, for instance, require that TLS v1.1
+  or newer be used.
 * The MX and host alias DNS lookups that fetchmail performs in multidrop mode
   are based on assumptions that are rarely met in practice, somewhat defective,
   deprecated and may be removed from a future fetchmail version.
@@ -22,7 +29,6 @@ removed from a 6.4.0 or newer release.)
 * IMAP2 and IMAP4 (not IMAP4r1) are obsolete, support may be removed from a
   future fetchmail version.
 * RPOP is obsolete, support will be removed from a future fetchmail release.
-* --sslcertck will become a default setting in a future fetchmail version.
 * The multidrop To/Cc guessing code along with the fragile duplicate suppressor
   is deprecated and may be removed from a future release.
 * The "envelope Received" option may be removed from a future release, because
@@ -96,8 +102,6 @@ fetchmail-6.4.0 (not yet released):
 * fetchmail 6.3.X is unsupported.
 * fetchmail now configures OpenSSL support by default.
 * fetchmail now requires OpenSSL v1.0.2 or newer.
-* fetchmail now supports a pure OpenSSL v1.1.0 API with deprecated functions
-  disabled.
 * Fetchmail now supports --sslproto auto and --sslproto tls1+ (same as ssl23).
 * --sslproto tls1.1+, tls1.2+, and tls1.3+ are now supported for
   auto-negotiation with a minimum specified TLS protocol version, and --sslproto
@@ -111,7 +115,8 @@ fetchmail-6.4.0 (not yet released):
 * fetchmail now handles POP3 --keep UID lists more efficiently, by using Rainer
   Weikusat's P-Tree implementation. This reduces the complexity for handling
   a large UIDL from O(n^2) to O(n log n) and becomes noticably faster with
-  thousands of kept messages. (IMAP does not track UIDs and is unaffected.)
+  thousands of kept messages.
+  (IMAP does not currently track UIDs and is unaffected.)
   At the same time, the UIDL emulation code for deficient servers has been
   removed. It never worked really well.  Servers that do not implement the
   optional UIDL command only work with --fetchall option set, which in itself is
@@ -119,11 +124,11 @@ fetchmail-6.4.0 (not yet released):
 * fetchmail, when setting up TLS connections, now uses SSL_set_tlsext_host_name()
   to set up the SNI (Server Name Indication). Some servers (for instance
   googlemail) require SNI when using newer SSL protocols.
-* fetchmail will drop the connection when fetching with IMAP and receiving an
-  unexpected untagged "* BYE" response, to work around certain faulty servers.
 * Fetchmail now sets the expected hostname through OpenSSL 1.0.2's new 
   X509_VERIFY_PARAM_set1_host() function to enable OpenSSL's native certificate
   verification features.
+* fetchmail will drop the connection when fetching with IMAP and receiving an
+  unexpected untagged "* BYE" response, to work around certain faulty servers.
 * The FETCHMAIL_POP3_FORCE_RETR environment variable is now documented,
   it forces fetchmail, when talking POP3, to always use the RETR command,
   even if it would otherwise use the TOP command.
@@ -150,14 +155,15 @@ fetchmail-6.4.0 (not yet released):
   This was reported to break Kerberos-based authentication with Microsoft
   Exchange 2013 by Greg Hudson.
 * Set umask properly before writing the .fetchids file, to avoid failing the
-  security check on the next run.  Reported by Fabian Raab, Debian Bug#831611.
+  security check on the next run.  Reported by Fabian Raab,
+  Fixes Debian Bug#831611.
 * When forwarding by LMTP, also check antispam response code when collecting
   the responses after the CR LF . CR LF sequence at the end of the DATA phase.
   (Contributed by Evil.2000, GitLab merge request !12.)
 * fetchmail will not try other protocols after a socket error. This avoids
   mismatches of how different prococols see messages as "seen" and re-fetches
   of known mail.  (Fix contributed by Lauri Nurmi, GitLab Merge Request !10.)
-* fetchmail no longer reports System error during SSL_connect(): Success.
+* fetchmail no longer reports "System error during SSL_connect(): Success."
   Fixes Debian Bug#928916, reported by Paul Kimoto.
 
 ## UPDATED TRANSLATIONS - THANKS TO:
@@ -173,11 +179,14 @@ fetchmail-6.4.0 (not yet released):
   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.
 * Sun Workshop 6 (SPARC) is known to miscompile the configuration file lexer in
   64-bit mode.  Either compile 32-bit code or use GCC to compile 64-bit
-  fetchmail.  Note that fetchmail doesn't take advantage of 64-bit code,
-  so compiling 32-bit SPARC code should not cause any difficulties.
+  fetchmail.
 * 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.