new.c: Order two return statements to match comment.

[nmh] / NEWS

diff --git a/NEWS b/NEWS
index a59252aff2307d81cfd2a9a71ca7c87149e4c9f8..2727362991d567c579e8f90e03fffc570aaff45e 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -68,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.
   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}).
 - "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
   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
 - 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


@@ -94,13 +94,11 @@ The following are new features for the 1.7 release of nmh:
   server supports it.  If not, post fails with a message to the user to
   encode the message for 7-bit transport.
 - Fewer lseek(2)s will be used when reading headers in the common case.
   server supports it.  If not, post fails with a message to the user to
   encode the message for 7-bit transport.
 - 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.
 - ./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
 
 ---------
 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.
   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
 - 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.
   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
 
 -------------------
 DEPRECATED FEATURES