Fixed strip_crs() in mhfixmsg to work even if it's the

[nmh] / docs / pending-release-notes

diff --git a/docs/pending-release-notes b/docs/pending-release-notes
index 1192e7e31cad2e37ebb594a3872054d69784cb1f..64b1d71cedcfd332166b6cff2316e0b883fa9742 100644 (file)
--- a/docs/pending-release-notes
+++ b/docs/pending-release-notes
@@ -24,6 +24,7 @@ NEW FEATURES
   (pseudo)random bytes and uses microsecond-resolution time.
 - Added -clobber switch to mhstore(1) to control overwriting of
   existing files.
+- Added -outfile switch to mhstore(1).
 - Added -noall/-all switches to sortm(1).  sortm -noall requires
   a messages argument.
 - $PAGER overrides the compiled-in default pager command.
@@ -45,6 +46,17 @@ NEW FEATURES
 - mhshow/mhstore now have support for RFC-2017 (access-type=url) for
   external message bodies.
 - Added -retainsequences switch to refile(1).
+- A new program, mhfixmsg(1), is included to rewrite MIME messages with
+  various transformations.
+- Added -[no]rmmproc switches to rmm(1).
+- Added support for Content-Disposition header (RFC 2183) to mhstore(1)
+  and mhn(1) when used with -auto.
+- All nmh commands now support transactional locking for sequence files.
+- There is no longer a per-folder maximum number of sequences.
+- For the SMTP MTA TLS can now be negotiated at the beginning of the
+  connection with the -initialtls switch.
+- Messages can now be selected using a relative offset from some other
+  message, or from the start or end of a sequence.  See mh-sequences(5).
 
 ----------------------------
 OBSOLETE/DEPRECATED FEATURES
@@ -111,3 +123,9 @@ BUG FIXES
 - Removed the artificial limit of 1000 messages at a time for rmmproc.
 - Fixed decoding of header fields when they contain a character that
   can't be converted.
+- post(8) -sasl now honours username in .netrc [Bug #23168].  whom(1),
+  send(1), inc(1), and msgchk(1) also benefit from this fix.  And, nmh
+  now supports specification of any valid filename in place of
+  $HOME/.netrc.
+- Added quoting of local part of invalid address in message being
+  replied to [Bug #26780].