1 # NEWS - Release notes for nmh 1.7
4 Welcome to nmh, the new version of the classic MH mail handling system.
5 It's been over three years since the last release of nmh, and there have
6 been a number of significant changes since the last release. Long-time
7 MH and nmh uses should read careful the NOTEABLE CHANGES section, as there
8 are some significant changes to nmh behavior. Otherwise, please see the
9 README and INSTALL files for help on getting started with nmh.
11 For news of future releases, subscribe to the low-volume
12 https://lists.nongnu.org/mailman/listinfo/nmh-announce
18 The largest notable changes in the 1.7 release are:
20 - Complete unification of network security support. All network protocols
21 (currently, POP and SMTP) have been refactored to use a common set of
22 security routines. This means all protocols support all SASL mechanisms
23 (via the Cyrus-SASL library) and TLS. TLS support has been strengthened
24 to perform certificate name validation and to require TLS 1.1 as a
25 minimum protocol. Also, all protocols can make use of the OAuth2/XOAUTH
26 SASL mechanism, which is supported by Gmail.
27 - send(1) now supports adding switches to post(8) based on the address or
28 domain of the email address in the From: header; this more easily allows
29 users to support multiple identities.
30 - A generic facility for passing arguments to filter programs in repl(1)
31 by use of the -convertargs switch.
32 - Native support for the manipulation of iCalendar requests; see mhical(1)
39 The following are new features for the 1.7 release of nmh:
41 - When building from source, configure will derive ${prefix} from an existing
42 nmh installation if it finds one in your $PATH.
43 - Added welcome message when nmh detects that its version changed.
44 - The default locations for configuration files and support binaries
45 have been changed. Configuration files now install into ${sysconfdir}/nmh,
46 and support binaries are placed in ${libexecdir}/nmh. If you are upgrading
47 an existing installation you should look for old configuration files in
48 ${sysconfdir} and merge any local customizations into the new files in
49 ${sysconfdir}/nmh, then remove the old files. ${libdir} will also contain
50 obsolete support programs that should be removed.
51 - All TLS connections now perform certificate validation (including hostname
52 matching) by default; can be disabled on a per-application basis.
53 - post now defaults to port 587 on 'smtp' message submission.
54 - A value of 0 for the width switch of scan(1), inc(1), ap(1), dp(1),
55 fmttest(1), and mhl(1) now means as many characters as the format
56 engine can produce [Bug #15274]. That amount is limited by internal
58 - If a component has trailing whitespace, e.g., body:component="> ",
59 mhl now trims that whitespace off when filtering blank text lines.
60 - An "rtrim" flag has been added to mhl to remove any trailing
61 whitespace from filtered text lines. A corresponding "nortrim" flag
63 - Added getmymbox and getmyaddr mh-format(5) function escapes.
64 - New -[no]changecur, -fixtype, -decodetypes, and -[no]crlflinebreaks switches
65 have been added to mhfixmsg(1).
66 - mhfixmsg now removes an extraneous trailing semicolon from header
68 - Added -convertargs switch to repl(1), to pass arguments to programs
69 specified in the user's profile or mhn.defaults to convert message
71 - Added mhical(1), to display, reply to, and cancel iCalendar (RFC 5545)
73 - Added multiply mh-format(5) function.
74 - "mhparam bindir" prints the path to the directory containing the public
75 executables (${bindir}).
76 - New "-prefer" switch for mhshow (and mhlist and mhshow), to allow specifying
77 the preferred content types to show, if present in a multipart alternative.
78 - mh-format now has %(kilo) and %(kibi) functions, to allow printing
79 numbers with SI or IEC quantities, e.g. "10K", "2.3Mi".
80 - Support for the -sendmail flag to send/post to change the sendmail
81 binary when using the sendmail/pipe MTS.
82 - Added support to send(1) to specify switches to post(1) based on address or
83 domain name in From: header line in message draft.
84 - post(8) -snoop now attempts to decode base64-encoded SMTP traffic.
85 - folder(1) -nocreate now prints a warning message for a non-existent folder.
86 - mhfixmsg(1) now allows -decodetext binary, though 8bit is still the default.
87 - inc(1) and msgchk(1) now support TLS encryption natively.
88 - All network protocols support the XOAUTH authentication mechanism.
89 - Support for SMTPUTF8 (RFC 6531) has been added. mhshow(1) already supported
90 RFC 6532, assuming all 8-bit message header field bodies are UTF-8 and use
92 - mhfixmsg now replaces RFC 2047 encoding with RFC 2231 encoding of name and
93 filename parameters in Content-Type and Content-Disposition headers,
95 - If a message body contains 8-bit bytes, post(8) uses SMTP 8BITMIME if the
96 server supports it. If not, post fails with a message to the user to
97 encode the message for 7-bit transport.
98 - Fewer lseek(2)s will be used when reading headers in the common case.
99 - ./configure's --enable-debug has been removed; it did nothing.
100 - configure now defaults to enabling each of TLS and Cyrus SASL if the
101 necessary headers and libraries are found.
102 - Moved build_nmh to top-level directory.
103 - Better error reporting for connections to network services.
109 - The format scanner no longer subtracts 1 from the width. This has the
110 effect of no longer counting the trailing newline in the output of
111 scan(1), inc(1), and the other programs that rely on the format scanner.
112 - The first character of some very short (less than 4 characters) message
113 bodies is no longer dropped.
114 - Single-character headers can be reliably formatted, etc., instead of
115 apparently being missing.
116 - mhfixmsg now adds a Content-Transfer-Encoding header at the message level,
117 if needed after decoding text parts.
118 - mhbuild now checks whether all text parts need a Content-Transfer-Encoding
119 header, not just those with a character set not specified.
120 - mhbuild no longer parses lines that start with # as directives with
122 - repl now makes sure that any Fcc header in a replied-to message is not
123 copied into the outgoing draft by default, and that the -fcc switch
124 actually works in the absence of a Fcc header in the replied-to message.
125 - A Content-ID is generated for message/external-body entities as required
126 by RFC 2045, even if -nocontentid is supplied to mhbuild.
127 - post will now expand aliases on a "From" line when doing a BCC [Bug #51098].
128 - scan can now handle empty files without violating an assert [Bug #51693].
129 - An error when writing an error message, e.g. EPIPE, no longer causes
130 recursion until the stack is exhausted.
136 - Support for the MHPDEBUG environment variable is deprecated and will be
137 removed from a future nmh release. Instead, use the -debug switch to pick.
138 - With the move of support binaries from ${libdir} to ${libexecdir}/nmh, the
139 mostly undocumented 'libdir' mhparam(1) component has been replaced by a
140 new 'libexecdir' component. 'libdir' will be removed in a future release.
146 - The undocumented -queue switch to post was deprecated in nmh 1.6, and was
147 removed in this release.
148 - conflict(8) was deprecated in nmh 1.6, and was removed in this release.
149 - mhtest(8) was deprecated in nmh 1.6, and was removed in this release.
150 - msh(1) was deprecated in nmh 1.6, and was removed in this release.
151 - Support in alias files for the the "*" address-group (everyone) was
152 deprecated in nmh 1.6, and was removed in this release.
153 - Support for multiple hostnames in the "servers" entry of mts.conf has
155 - Support in alias files for expanding aliases based on group membership
156 (=) and primary group (+) has been removed.
158 As always, feedback is welcome.
162 nmh-workers@nongnu.org
164 ----------------------------------------------------------------------------
167 # NEWS - Release notes for nmh 1.6
170 Welcome to nmh, the new version of the classic MH mail handling system.
171 It's been nearly two years since the last release of nmh, and there have
172 been a number of significant changes since the last release. Long-time
173 MH and nmh uses should read careful the NOTEABLE CHANGES section, as there
174 are some significant changes to nmh behavior. Otherwise, please see the
175 README and INSTALL files for help on getting started with nmh.
181 The following are new features for the 1.6 release of nmh:
183 - All nmh programs will now warn about multiple profile entries for
184 the same non-null, non-comment component. In previous versions, all
185 but the first were silently ignored.
186 - mhmail now supports all post(8) options, or optionally can use
187 send(1) with all of its options. Its formerly undocumented -resent
188 switch has been documented. And it has new -attach, -headerfield,
189 and -send/-nosend switches.
190 - Default to flock() locking on OpenBSD and Darwin.
191 - Added -directives support to mhbuild(1) to control whether or not
192 mhbuild will honor MIME directives by default. And added support
193 for special #on/#off/#pop directives to control the MIME directive
195 - Added -messageid switch to send(1) and post(8). This allows
196 selection of the style to use for generated Message-ID and
197 Content-ID header fields. The default localname style is
198 pid.time@localname, where time is in seconds, and matches previous
199 behavior. The random style replaces the localname with some
200 (pseudo)random bytes and uses microsecond-resolution time.
201 - Added -clobber switch to mhstore(1) to control overwriting of
203 - Added -outfile switch to mhstore(1).
204 - Added -noall/-all switches to sortm(1). sortm -noall requires
206 - $PAGER overrides the compiled-in default pager command.
207 - Added etc/scan.highlighted format file, as an example of how to
208 highlight/colorize the output of scan(1).
209 - inc(1) now supports a -port switch to specify the port used by the
211 - pick(1) now decodes MIME-encoded header fields before searching.
212 - The VISUAL and EDITOR environment variables are now supported as fallbacks
213 if the user does not configure an editor entry in their profile.
214 - The format engine (mh_format(5)) now properly accounts for multibyte
215 characters when accounting for column widths.
216 - burst(1) now can burst MIME-formatted digests (messages that contain
217 message/rfc822 parts instead of messages formatted with RFC 934).
218 - All proc entries (showproc, moreproc, etc) can now accept entries that
219 contain spaces and shell metacharacters. If found, such entries will
220 either be space-split or processed by /bin/sh.
221 - A new program, fmttest(1) is included to help debug format files. See
222 NOTABLE CHANGES below.
223 - mhshow/mhstore now have support for RFC-2017 (access-type=url) for
224 external message bodies.
225 - Added -retainsequences switch to refile(1).
226 - A new program, mhfixmsg(1), is included to rewrite MIME messages with
227 various transformations. See NOTABLE CHANGES below.
228 - Added -[no]rmmproc switches to rmm(1).
229 - Added support for Content-Disposition header (RFC 2183) to mhstore(1)
230 and mhn(1) when used with -auto.
231 - All nmh commands now support transactional locking for sequence files.
232 See NOTABLE CHANGES below.
233 - There is no longer a per-folder maximum number of sequences.
234 - For the SMTP MTA TLS can now be negotiated at the beginning of the
235 connection with the -initialtls switch.
236 - Messages can now be selected using a relative offset from some other
237 message, or from the start or end of a sequence. See mh-sequence(5).
238 - The -changecur and -nochangecur switches have been added to mhlist(1).
239 - mhbuild(1) can now encode 8-bit message headers using RFC-2047 encoding
240 rules. See NOTABLE CHANGES below.
241 - The whatnow(1) attach feature will determine the content type of an
242 attachment using a program such as file --mime-type, if available at
243 configuration time. If not, it will use mhshow-suffix- entries as
244 before. The -v switch to attach causes it to display the mhbuild
245 directive that send(1) will use.
246 - mhbuild(1) now supports the -auto/-noauto flags (to be used by send(1)
247 when invoking mhbuild automatically).
248 - mhbuild(1) now is automatically run by send, to insure that all outgoing
249 messages have proper MIME formatting. See NOTABLE CHANGES below.
250 - A new header, "Attach", is supported by mhbuild; it is used to replace
251 previous functionality (which by default used a header named
252 Nmh-Attachment). See NOTABLE CHANGES below.
253 - The default Content-Transfer-Encoding for text parts is now 8bit.
254 - mhbuild(1) now supports a selectable Content-Transfer-Encoding
255 - If nmh was configured with iconv(3) support, mhshow will convert, if
256 necessary, the charset of text/plain content to match the user's
257 locale setting. See NOTABLE CHANGES below.
258 - Added support for %{charset} display string escape to mhshow(1).
259 - The MIME parsing and generating routines now support RFC 2231 extended
260 parameter information.
261 - mh-mime(7) now provides an introduction to nmh's MIME handling.
262 - mhshow(1) will now by default display all text content under one pager,
263 and display markers for non-text and non-inline content. The content
264 markers are changeable via mh-format(5). See NOTABLE CHANGES below.
269 - Changed exit status of each nmh command's -version and -help
270 switches from 1 to 0.
271 - The following environment variables were deprecated in nmh 1.5
272 and removed from this release:
273 MHPOPDEBUG (use -snoop command line switch instead)
274 MM_NOASK (use -nolist and -nopause command line switches instead)
275 NOMHNPROC (use -nocheckmime command line switch instead)
276 FACEPROC (undocumented faceproc feature removed)
277 - Changed repl and dist default to -noatfile. The default of -atfile
278 was deprecated in nmh 1.5. If there are no requests to maintain
279 -atfile, it will be removed in the future.
280 - The undocumented -queue switch to mhmail has been removed.
281 - spost(8) has been merged into post(8). Its functionality is enabled
282 by selecting the sendmail/pipe mail transport method, described in
283 the mh-tailor(5) man page. The spost -noalias, -backup/-nobackup,
284 -push/-nopush, and -remove/-noremove switches are not supported by
285 post. Note that spost did not support -whom or Dcc, and neither
286 does post when using sendmail/pipe. And spost would expand blind
287 aliases and send them in the message; post with sendmail/pipe
288 refuses to do that. For backward compatibility, spost has been
289 replaced by a simple shell script that exec's post -mts
290 sendmail/pipe. See NOTABLE CHANGES below.
291 - Support for the undocumented and deprecated --enable-nmh-debug configure
292 flag has been removed.
293 - Support for encoding some characters designated as EBCDIC-unsafe
294 via the -ebcdicsafe and -noebcdicsafe switches to mhbuild has
296 - The configure flag --with-pager has been removed; the default pager
297 is now hardcoded as "more". Users are still free to override the
298 default using the PAGER environment variable or entries in .mh_profile.
299 - The configure flag --with-editor has been removed; the fallback editor
300 if none is configured is "vi".
301 - The support for the undocumented NOPUBLICSEQ preprocessor definition
302 to disable public sequence support has been removed.
303 - Support for the -normalize and -nonormalize switches to the ali(1) and
304 ap(8) commands has been removed.
305 - "make install" no longer strips executables. Use "make install-strip"
307 - The environment variable MM_CHARSET to indicate the native character
308 set is no longer supported. The native character set will be solely
309 determined by the locale settings.
310 - Temporary files are stored in the first non-null location of
311 {MHTMPDIR environment variable, TMPDIR environment variable, MH Path}.
312 They are no longer be stored in the location specified by the TMP
313 environment variable.
314 - Instead of printing PostScript attachments, by default, from mhshow,
315 try to find a suitable viewer.
316 - Support for parallel display of multipart/parallel content has been
317 removed from mhshow; all multipart content will be displayed in
319 - Support for -pause/-nopause switches on mhshow has been removed.
324 - The undocumented -queue switch to post is deprecated/obsolete
325 and will be removed in the next release. It supports the
326 SMTP XQUE verb, which is obsolete according to
327 http://smtpfilter.sourceforge.net/esmtp.html
328 - conflict(8) is deprecated and will be removed from the next release.
329 - mhtest(8) is deprecated and will be removed from the next release.
330 - msh(1) is deprecated and will be removed from the next release.
331 - Support in alias files for the the "*" address-group is obsolescent
332 and will be removed in a future release.
338 - Replaced utilities that operate on pbm files with those that operate
339 on pnm files in etc/mhn.defaults [Bug #15152].
340 - Removed obsolete BUGS section at end of rcvstore(1) man page [Bug #4361].
341 - Fixed -nocc me doesn't account for Alternate-Mailboxes [Bug #36635].
342 - Propagate Mail-Followup-To [Bug #5571].
343 - "mark -sequence cur -delete all" now works for cur as well as any
344 other sequence, to allow clearing of the current message indication.
345 - The first alias contained in a blind list is now expanded. The
346 mh-alias(5) man page was updated to show that blind lists must not
347 be terminated with, or contain, a trailing semicolon [Bug #15604].
348 - Fixed sendfiles(1) to always provide a From: address. Also, updated
350 - Fixed pick(1) to properly unfold multiple-line header fields by
351 removing newlines instead of replacing them with spaces [Bug #15215].
352 - Removed the artificial limit of 1000 messages at a time for rmmproc.
353 - Fixed decoding of header fields when they contain a character that
355 - post(8) -sasl now honours username in .netrc [Bug #23168]. whom(1),
356 send(1), inc(1), and msgchk(1) also benefit from this fix. And, nmh
357 now supports specification of any valid filename in place of
359 - Added quoting of local part of invalid address in message being
360 replied to [Bug #26780].
361 - Fix segmentation faults for %(putlit) and %(zputlit) format escapes when
362 the "str" register was NULL.
363 - Encode and decode text MIME types with canonical line breaks properly.
364 - mhstore(1) now obeys its -noverbose switch.
365 - Properly report the input filename when mhbuild encounters errors.
366 - Set the content-transfer-encoding properly when attaching message/rfc822
373 The biggest changes in this release are in the arena of MIME handling.
374 Specifically relating to MIME composition and display. On the
375 composition front, mhbuild(1) will now automatically be run by send(1)
376 for all drafts. Specifically, mhbuild is now run with the new -auto
377 flag, which will suppress the processing of mhbuild directives and cause
378 mhbuild to silently exit if the draft is already MIME-formatted. When
379 invoking mhbuild manually via the "mime" command at the WhatNow? prompt,
380 mhbuild will behave as before and process mhbuild directives.
382 In both cases (automatic and manual invocation) mhbuild will encode email
383 headers according to RFC-2047 rules. Mhbuild also will use RFC 2231
384 encoding rules for MIME parameters when appropriate. In addition, the
385 attach system has been substantially reworked; the new header name is
386 now "Attach" (to better align with other MUA behavior) and cannot be
387 changed by the end-user. The existing "attach" command simply adds
388 the filename(s) to the draft in new Attach: headers, and the actual
389 file processing is done by mhbuild; this attachment processing will
390 take place in either automatic or manual mode.
392 On the display front, mhshow(1) will now automatically convert text
393 into the user's native character set using iconv, if nmh was built
394 with iconv support. Also, mhshow will now by default only display
395 text content that was not marked as an attachment. By default all
396 displayed content wll be run under one pager, as opposed to individual
397 pagers for each part as was in the past. Non-displayed parts will be
398 indicated using a marker string, which can be customized by a new
401 All nmh utilities now understand RFC 2231-encoded MIME parameters and
402 will automatically convert the encoded parameters into the native
403 character set, when appropriate (again, assuming nmh was built with
406 In other changes, sequence files are now locked using transactional
407 locks: locks that are held across sequence file reading, modification,
408 and writing. The locking algorithm used for spool files and nmh data
409 files is now runtime configurable.
411 For people that struggle with mh-format(5) files, a new utility for testing
412 them has been developed: fmttest(1). It includes the ability to trace the
413 execution of format instructions.
415 For users that wish to use Unix utilities on their mail, a new utility
416 to transform MIME messages to more easily-digestable format is now
417 available: mhfixmsg(1). It supports a number of options to control
418 the message transformation.
420 For users of spost(8), the support for spost has been rolled into post(8)
421 under a new sendmail/pipe MTS. A shell script emulating the old behavior
422 of spost has been provided.
424 As always, feedback is welcome.
428 nmh-workers@nongnu.org
430 ----------------------------------------------------------------------------
433 # NEWS - Release notes for nmh 1.5
436 Welcome to nmh, the new version of the classic MH mail handling
437 system. Long-time MH and nmh users should read carefully the NOTABLE
438 CHANGES section, as there are some subtle but significant changes
439 to the way nmh now behaves. Otherwise, please see the README and INSTALL
440 files for help on getting started with nmh.
446 The following are new features for the 1.5 release of nmh.
448 - Improved performance for TLS encryption of the SMTP protocol.
449 - MH-E and POP support are now always compiled in.
450 - The selection of a locking directory for dot-locking files is now
451 controllable via configure.
452 - fileproc and mhlproc mh-profile are now obeyed by send, rcvdist,
454 - New mh-format instructions have been implemented: %(putlit),
455 %(concataddr), %(myhost), %(myname), %(localmbox). See mh-format(5)
457 - Nmh's idea of the local mailbox is now configurable via a new profile
458 entry, Local-Mailbox. See mh-profile(5) for more details.
459 - comp, forw, and dist now process all component templates through
460 mh-format(5), and now all support new command line arguments -from,
461 -to, -cc, -fcc, and -subject.
462 - burst(1) now supports any valid message delimiter according to RFC 934.
463 - post(8) now requires a From: header in all drafts that it processes;
464 see NOTABLE CHANGES below for more details.
465 - post(8) can now explicitly control the SMTP envelope address either via
466 the Sender: header or the new Envelope-From: header.
467 - The -attach option is now the default for send (using the header
468 Nmh-Attachment) and -attachformat 1 is the default attachment type.
469 - repl and dist now support new switches -atfile and -noatfile to control
470 the creation of the ./@ link to the message being replied or
471 redistributed. The current default is -atfile.
472 - Support (if available) for readline editing and filename completion at
474 - Support for using an external command to filter the body of a message
475 through in mhl. See mhl(1) for more details, specifically, the
476 "format" keyword, the "formatproc" entry in mh-profile(5), and the
477 -fmtproc switch for mhl and repl.
478 - Preliminary support for improved MIME handling when replying to messages!
479 Yes, a long requested feature has a solution. A perl script
480 called replyfilter is available; it is designed to act as a mhl
481 external filter to process MIME messages in a more logical way.
482 It is available in $(srcdir)/docs/contrib/replyfilter or is
483 typically installed as $(prefix)/share/doc/nmh/contrib/replyfilter.
484 See the comments at the top of replyfilter for usage information;
485 it will likely require some adjustment for your site. replyfilter
486 requires the MIME-Tools and MailTools perl modules.
488 ----------------------------
489 OBSOLETE/DEPRECATED FEATURES
490 ----------------------------
492 The following features have either been removed completely or marked
493 as officially deprecated for removal in a future release of nmh.
495 - The creation of the ./@ link to the message being replied or
496 redistributed is deprecated; -noatfile will be the default in the
497 next release. If there are no requests to maintain -atfile it
498 will be removed in a future release.
499 - Old code enabled by the UCI preprocessor definition has been removed.
500 - All configuration options that were formerly only adjustable by editing
501 config.h have either been moved into configure or removed completely.
502 - Support for the built-in ftp client (used when dealing with external-body
503 message parts in MIME messages) has been removed.
504 - The following environment variables are marked as obsolete/deprecated.
505 Support for them will be removed from the next nmh release:
506 MHPOPDEBUG (use -snoop command line switch instead)
507 MM_NOASK (use -nolist and -nopause command line switches instead)
508 NOMHNPROC (use -nocheckmime command line switch instead)
509 FACEPROC (undocumented faceproc feature to be removed)
510 - The hostable option of mts.conf is no longer needed and has been removed.
516 The largest change is that post(8) now requires a From: header in all drafts
519 The impetus for this change has been the evolution of email and client
520 systems. When MH was first developed the norm was to have tightly managed
521 clients that were part of the same domain as a user's email address. This
522 is no longer a valid assumption, and the algorithm used by nmh to determine
523 the user's local mailbox is no longer a reasonable default.
525 Unfortunately, the way that nmh uses the user's local mailbox used to happen
526 very late in the message process; it was handled by post during message
527 submission. If no From: header exists in the current draft post would
528 insert one based on it's idea of the local mailbox, which was frequently
531 After a long discussion within the nmh development community, it was
532 decided that the only reasonable way forward was to move the local mailbox
533 handling up a level and place it under more direct control of the end
534 user. post(8) no longer will try to determine the local mailbox name;
535 it will take that information from the draft message. Thus a From: header
536 is now required in all drafts.
538 As part of these changes, all message composition utilities now process
539 their component files using mh-format. All of the default component
540 files have been modified to include a From: header in them; this will
541 give the user a chance to see nmh's idea of the local mailbox and modify
542 it if desired. The new mh-profile(5) entry Local-Mailbox can be used
543 to adjust the local mailbox name if the system default is not appropriate.
545 So how should end-users adapt to these changes? Here are some suggestions:
547 1) If you use the default component files, everything should basically work
548 the same for you. You should see a From: header in the drafts of your
549 messages. If the address you see in the From: header is incorrect
550 you can change it via the Local-Mailbox profile entry. You can also
551 use the -from switch to change it on a per-command basis.
553 2) If you have custom component files that include a From: header or
554 you perform custom processing on drafts that end up placing a From:
555 header in the draft message, everything should work as before.
557 3) If you have custom component files that do NOT include a From: header
558 then you will have to adapt then to include a From: header. You
559 can either simply hard-code the correct From: header or use the
560 default component files as a guide (see mh-format(5) for more
561 details, specifically the %(localmbox) function).
563 The other significant change is the support for filters in mhl. Included
564 in the distribution is replyfilter, a filter designed for sane processing
565 of MIME messages during replies. Since this isn't as integrated into
566 nmh as we would prefer, it's included in the contrib directory as an
567 optional component. Please try it out and give us feedback.
571 nmh-workers@nongnu.org
573 ----------------------------------------------------------------------------
576 # NEWS - Release notes for nmh 1.4
579 This releases contains numerous bugfixes and a number of new features.
580 The new features include:
582 - SASL security layers (encryption) are now supported for the SMTP MTA.
583 - TLS is now supported for the SMTP MTA.
584 - inc can now incorporate mail from Maildir drops.
585 - You can now select the SMTP server and port from either "send" or a
586 user's mh_profile (you could always select the server; that option is
587 now documented). These are available via the -server and -port
589 - All networking code has been modified to use the new networking APIs
590 (getaddrinfo and friends). All networking code (with the exception of
591 the built-in ftp client) now supports IPv6.
592 - New commands 'new', 'fnext', 'fprev', and 'unseen' for showing folders
593 with unseen mail (or mail in any specified sequence), changing to next
594 such folder, changing to previous such folder, and scanning all such
595 folders, respectively. This is based on Luke Mewburn's 'new':
596 http://www.mewburn.net/luke/src/new
597 - nmh will no longer attempt to install a mhn.defaults file that causes
598 mhshow to open its own xterms.
600 A large chunk of old code has been garbage collected. Specifically,
601 support for APOP, RPOP, NNTP (including bboards) and MPOP is now gone.
602 Also gone is support for prefixing a \01 in the "servers" entry in
603 mts.conf to iterate over all servers on a named network.
605 ----------------------------------------------------------------------------
608 # NEWS - Release notes for nmh 1.3
611 It's been over two years since the 1.2 release; but the changes here are
612 mostly minor; largely bugfixes.
614 You should note that we have changed the default configuration to allow
615 all supported forms of address masquerading. For more details please see
616 the --enable-masquerade option to configure, and the mh-tailor and post
projects / nmh / blob