X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/4c877c13ff3c608388e6cc4005d15f24f3350ca3..94187a80bd60baab4b9c4b949ad820d730578123:/NEWS

diff --git a/NEWS b/NEWS
index 3c32e019..27273629 100644
--- a/NEWS
+++ b/NEWS
@@ -36,6 +36,18 @@ NEW FEATURES
 
 The following are new features for the 1.7 release of nmh:
 
+- When building from source, configure will derive ${prefix} from an existing
+  nmh installation if it finds one in your $PATH.
+- Added welcome message when nmh detects that its version changed.
+- The default locations for configuration files and support binaries
+  have been changed.  Configuration files now install into ${sysconfdir}/nmh,
+  and support binaries are placed in ${libexecdir}/nmh.  If you are upgrading
+  an existing installation you should look for old configuration files in
+  ${sysconfdir} and merge any local customizations into the new files in
+  ${sysconfdir}/nmh, then remove the old files.  ${libdir} will also contain
+  obsolete support programs that should be removed.
+- All TLS connections now perform certificate validation (including hostname
+  matching) by default; can be disabled on a per-application basis.
 - post now defaults to port 587 on 'smtp' message submission.
 - A value of 0 for the width switch of scan(1), inc(1), ap(1), dp(1),
   fmttest(1), and mhl(1) now means as many characters as the format
@@ -46,15 +58,6 @@ The following are new features for the 1.7 release of nmh:
 - An "rtrim" flag has been added to mhl to remove any trailing
   whitespace from filtered text lines.  A corresponding "nortrim" flag
   has also been added.
-- The default locations for configuration files and support binaries
-  have been changed.  Configuration files now install into ${sysconfdir}/nmh,
-  and support binaries are placed in ${libexecdir}/nmh.  If you are upgrading
-  an existing installation you should look for old configuration files in
-  ${sysconfdir} and merge any local customizations into the new files in
-  ${sysconfdir}/nmh, then remove the old files.  ${libdir} will also contain
-  obsolete support programs that should be removed.
-- When building from source, configure will derive ${prefix} from an existing
-  nmh installation if it finds one in your $PATH.
 - Added getmymbox and getmyaddr mh-format(5) function escapes.
 - New -[no]changecur, -fixtype, -decodetypes, and -[no]crlflinebreaks switches
   have been added to mhfixmsg(1).
@@ -65,13 +68,13 @@ The following are new features for the 1.7 release of nmh:
   content.
 - Added mhical(1), to display, reply to, and cancel iCalendar (RFC 5545)
   event requests.
-- added multiply format function
+- Added multiply mh-format(5) function.
 - "mhparam bindir" prints the path to the directory containing the public
   executables (${bindir}).
-- new "-prefer" switch for mhshow (and mhlist and mhshow), to allow specifying
+- New "-prefer" switch for mhshow (and mhlist and mhshow), to allow specifying
   the preferred content types to show, if present in a multipart alternative.
 - mh-format now has %(kilo) and %(kibi) functions, to allow printing
-  numbers as, for example, "10K", or "2.3Mi"
+  numbers with SI or IEC quantities, e.g. "10K", "2.3Mi".
 - Support for the -sendmail flag to send/post to change the sendmail
   binary when using the sendmail/pipe MTS.
 - Added support to send(1) to specify switches to post(1) based on address or
@@ -80,8 +83,6 @@ The following are new features for the 1.7 release of nmh:
 - folder(1) -nocreate now prints a warning message for a non-existent folder.
 - mhfixmsg(1) now allows -decodetext binary, though 8bit is still the default.
 - inc(1) and msgchk(1) now support TLS encryption natively.
-- All TLS connections now perform certificate validation (including hostname
-  matching) by default; can be disabled on a per-application basis.
 - All network protocols support the XOAUTH authentication mechanism.
 - Support for SMTPUTF8 (RFC 6531) has been added.  mhshow(1) already supported
   RFC 6532, assuming all 8-bit message header field bodies are UTF-8 and use
@@ -92,15 +93,12 @@ The following are new features for the 1.7 release of nmh:
 - If a message body contains 8-bit bytes, post(8) uses SMTP 8BITMIME if the
   server supports it.  If not, post fails with a message to the user to
   encode the message for 7-bit transport.
-- Added welcome message when nmh detects that its version changed.
 - Fewer lseek(2)s will be used when reading headers in the common case.
-- Single-character headers can be reliably formatted, etc., instead of
-  apparently being missing.
 - ./configure's --enable-debug has been removed;  it did nothing.
 - configure now defaults to enabling each of TLS and Cyrus SASL if the
   necessary headers and libraries are found.
 - Moved build_nmh to top-level directory.
-- Better error reporting for connections to network services
+- Better error reporting for connections to network services.
 
 ---------
 BUG FIXES
@@ -111,6 +109,8 @@ BUG FIXES
   scan(1), inc(1), and the other programs that rely on the format scanner.
 - The first character of some very short (less than 4 characters) message
   bodies is no longer dropped.
+- Single-character headers can be reliably formatted, etc., instead of
+  apparently being missing.
 - mhfixmsg now adds a Content-Transfer-Encoding header at the message level,
   if needed after decoding text parts.
 - mhbuild now checks whether all text parts need a Content-Transfer-Encoding
@@ -122,7 +122,10 @@ BUG FIXES
   actually works in the absence of a Fcc header in the replied-to message.
 - A Content-ID is generated for message/external-body entities as required
   by RFC 2045, even if -nocontentid is supplied to mhbuild.
-- Post will now expand aliases on a "From" line when doing a BCC (bug #51098)
+- post will now expand aliases on a "From" line when doing a BCC [Bug #51098].
+- scan can now handle empty files without violating an assert [Bug #51693].
+- An error when writing an error message, e.g. EPIPE, no longer causes
+  recursion until the stack is exhausted.
 
 -------------------
 DEPRECATED FEATURES