X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/66576f625749ee3cbd168604996d97cb33a58367..2b677bfbc0ece2abfb27fa5ff7827ebe2e4609a0:/docs/pending-release-notes?ds=inline diff --git a/docs/pending-release-notes b/docs/pending-release-notes index 7de2628a..350710a4 100644 --- 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. -- 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 @@ -68,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. +- Better error reporting for connections to network services ----------------- OBSOLETE FEATURES @@ -80,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. +- 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 @@ -106,7 +111,7 @@ BUG FIXES 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 +- 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