X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/8eacff500716cab8256b032c0f4dd29bc2dc16bb..9322ba2854211794c27fae9468768b80b767c211:/docs/pending-release-notes

diff --git a/docs/pending-release-notes b/docs/pending-release-notes
index 8e1aa0d7..23cc77c0 100644
--- a/docs/pending-release-notes
+++ b/docs/pending-release-notes
@@ -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.
+- 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.
@@ -63,6 +65,10 @@ NEW FEATURES
 - 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
 
 -----------------
 OBSOLETE FEATURES
@@ -75,6 +81,8 @@ 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.
+- Support for multiple hostnames in the "servers" entry of mts.conf has
+  been removed.
 
 -------------------
 DEPRECATED FEATURES
@@ -99,3 +107,10 @@ 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.
+- mhbuild no longer parses lines that start with # as directives with
+  -nodirectives.
+- repl now make 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.