Document bug fix

[nmh] / docs / pending-release-notes

diff --git a/docs/pending-release-notes b/docs/pending-release-notes
index 5c2560463c3399a21f133b4eb0a96df2bc30d4b3..572484a64949450477579834de6f09477bcf1f78 100644 (file)
--- a/docs/pending-release-notes
+++ b/docs/pending-release-notes
@@ -15,7 +15,7 @@ NEW FEATURES
 - 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.
 - 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 suppoooort binaries
+- 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
   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


@@ -49,6 +49,8 @@ NEW FEATURES
 - 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.
 - 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.

 - 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
   of a UTF-8 locale.
 - 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
   of a UTF-8 locale.


@@ -66,6 +68,7 @@ NEW FEATURES
 - 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 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

 
 -----------------
 OBSOLETE FEATURES
 
 -----------------
 OBSOLETE FEATURES


@@ -78,6 +81,10 @@ OBSOLETE FEATURES
 - msh(1) was deprecated in nmh 1.6, and was removed in this release.
 - Support in alias files for the the "*" address-group (everyone) was
   deprecated in nmh 1.6, and was removed in this release.
 - msh(1) was deprecated in nmh 1.6, and was removed in this release.
 - Support in alias files for the the "*" address-group (everyone) was
   deprecated in nmh 1.6, and was removed in this release.

+- Support for multiple hostnames in the "servers" entry of mts.conf has
+  been removed.
+- Support in alias files for expanding aliases based on group membership
+  (=) and primary group (+) has been removed.

 
 -------------------
 DEPRECATED FEATURES
 
 -------------------
 DEPRECATED FEATURES


@@ -102,3 +109,11 @@ BUG FIXES
   if needed after decoding text parts.
 - mhbuild now checks whether all text parts need a Content-Transfer-Encoding
   header, not just those with a character set not specified.
   if needed after decoding text parts.
 - mhbuild now checks whether all text parts need a Content-Transfer-Encoding
   header, not just those with a character set not specified.

+- mhbuild no longer parses lines that start with # as directives with
+  -nodirectives.
+- repl now makes sure that any Fcc header in a replied-to message is not
+  copied into the outgoing draft by default, and that the -fcc switch
+  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)