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.
131 - rcvdist(1) now passes switch arguments to post(8).
137 - Support for the MHPDEBUG environment variable is deprecated and will be
138 removed from a future nmh release. Instead, use the -debug switch to pick.
139 - With the move of support binaries from ${libdir} to ${libexecdir}/nmh, the
140 mostly undocumented 'libdir' mhparam(1) component has been replaced by a
141 new 'libexecdir' component. 'libdir' will be removed in a future release.
147 - The undocumented -queue switch to post was deprecated in nmh 1.6, and was
148 removed in this release.
149 - conflict(8) was deprecated in nmh 1.6, and was removed in this release.
150 - mhtest(8) was deprecated in nmh 1.6, and was removed in this release.
151 - msh(1) was deprecated in nmh 1.6, and was removed in this release.
152 - Support in alias files for the the "*" address-group (everyone) was
153 deprecated in nmh 1.6, and was removed in this release.
154 - Support for multiple hostnames in the "servers" entry of mts.conf has
156 - Support in alias files for expanding aliases based on group membership
157 (=) and primary group (+) has been removed.
159 As always, feedback is welcome.
163 nmh-workers@nongnu.org
165 ----------------------------------------------------------------------------
168 # NEWS - Release notes for nmh 1.6
171 Welcome to nmh, the new version of the classic MH mail handling system.
172 It's been nearly two years since the last release of nmh, and there have
173 been a number of significant changes since the last release. Long-time
174 MH and nmh uses should read careful the NOTEABLE CHANGES section, as there
175 are some significant changes to nmh behavior. Otherwise, please see the
176 README and INSTALL files for help on getting started with nmh.
182 The following are new features for the 1.6 release of nmh:
184 - All nmh programs will now warn about multiple profile entries for
185 the same non-null, non-comment component. In previous versions, all
186 but the first were silently ignored.
187 - mhmail now supports all post(8) options, or optionally can use
188 send(1) with all of its options. Its formerly undocumented -resent
189 switch has been documented. And it has new -attach, -headerfield,
190 and -send/-nosend switches.
191 - Default to flock() locking on OpenBSD and Darwin.
192 - Added -directives support to mhbuild(1) to control whether or not
193 mhbuild will honor MIME directives by default. And added support
194 for special #on/#off/#pop directives to control the MIME directive
196 - Added -messageid switch to send(1) and post(8). This allows
197 selection of the style to use for generated Message-ID and
198 Content-ID header fields. The default localname style is
199 pid.time@localname, where time is in seconds, and matches previous
200 behavior. The random style replaces the localname with some
201 (pseudo)random bytes and uses microsecond-resolution time.
202 - Added -clobber switch to mhstore(1) to control overwriting of
204 - Added -outfile switch to mhstore(1).
205 - Added -noall/-all switches to sortm(1). sortm -noall requires
207 - $PAGER overrides the compiled-in default pager command.
208 - Added etc/scan.highlighted format file, as an example of how to
209 highlight/colorize the output of scan(1).
210 - inc(1) now supports a -port switch to specify the port used by the
212 - pick(1) now decodes MIME-encoded header fields before searching.
213 - The VISUAL and EDITOR environment variables are now supported as fallbacks
214 if the user does not configure an editor entry in their profile.
215 - The format engine (mh_format(5)) now properly accounts for multibyte
216 characters when accounting for column widths.
217 - burst(1) now can burst MIME-formatted digests (messages that contain
218 message/rfc822 parts instead of messages formatted with RFC 934).
219 - All proc entries (showproc, moreproc, etc) can now accept entries that
220 contain spaces and shell metacharacters. If found, such entries will
221 either be space-split or processed by /bin/sh.
222 - A new program, fmttest(1) is included to help debug format files. See
223 NOTABLE CHANGES below.
224 - mhshow/mhstore now have support for RFC-2017 (access-type=url) for
225 external message bodies.
226 - Added -retainsequences switch to refile(1).
227 - A new program, mhfixmsg(1), is included to rewrite MIME messages with
228 various transformations. See NOTABLE CHANGES below.
229 - Added -[no]rmmproc switches to rmm(1).
230 - Added support for Content-Disposition header (RFC 2183) to mhstore(1)
231 and mhn(1) when used with -auto.
232 - All nmh commands now support transactional locking for sequence files.
233 See NOTABLE CHANGES below.
234 - There is no longer a per-folder maximum number of sequences.
235 - For the SMTP MTA TLS can now be negotiated at the beginning of the
236 connection with the -initialtls switch.
237 - Messages can now be selected using a relative offset from some other
238 message, or from the start or end of a sequence. See mh-sequence(5).
239 - The -changecur and -nochangecur switches have been added to mhlist(1).
240 - mhbuild(1) can now encode 8-bit message headers using RFC-2047 encoding
241 rules. See NOTABLE CHANGES below.
242 - The whatnow(1) attach feature will determine the content type of an
243 attachment using a program such as file --mime-type, if available at
244 configuration time. If not, it will use mhshow-suffix- entries as
245 before. The -v switch to attach causes it to display the mhbuild
246 directive that send(1) will use.
247 - mhbuild(1) now supports the -auto/-noauto flags (to be used by send(1)
248 when invoking mhbuild automatically).
249 - mhbuild(1) now is automatically run by send, to insure that all outgoing
250 messages have proper MIME formatting. See NOTABLE CHANGES below.
251 - A new header, "Attach", is supported by mhbuild; it is used to replace
252 previous functionality (which by default used a header named
253 Nmh-Attachment). See NOTABLE CHANGES below.
254 - The default Content-Transfer-Encoding for text parts is now 8bit.
255 - mhbuild(1) now supports a selectable Content-Transfer-Encoding
256 - If nmh was configured with iconv(3) support, mhshow will convert, if
257 necessary, the charset of text/plain content to match the user's
258 locale setting. See NOTABLE CHANGES below.
259 - Added support for %{charset} display string escape to mhshow(1).
260 - The MIME parsing and generating routines now support RFC 2231 extended
261 parameter information.
262 - mh-mime(7) now provides an introduction to nmh's MIME handling.
263 - mhshow(1) will now by default display all text content under one pager,
264 and display markers for non-text and non-inline content. The content
265 markers are changeable via mh-format(5). See NOTABLE CHANGES below.
270 - Changed exit status of each nmh command's -version and -help
271 switches from 1 to 0.
272 - The following environment variables were deprecated in nmh 1.5
273 and removed from this release:
274 MHPOPDEBUG (use -snoop command line switch instead)
275 MM_NOASK (use -nolist and -nopause command line switches instead)
276 NOMHNPROC (use -nocheckmime command line switch instead)
277 FACEPROC (undocumented faceproc feature removed)
278 - Changed repl and dist default to -noatfile. The default of -atfile
279 was deprecated in nmh 1.5. If there are no requests to maintain
280 -atfile, it will be removed in the future.
281 - The undocumented -queue switch to mhmail has been removed.
282 - spost(8) has been merged into post(8). Its functionality is enabled
283 by selecting the sendmail/pipe mail transport method, described in
284 the mh-tailor(5) man page. The spost -noalias, -backup/-nobackup,
285 -push/-nopush, and -remove/-noremove switches are not supported by
286 post. Note that spost did not support -whom or Dcc, and neither
287 does post when using sendmail/pipe. And spost would expand blind
288 aliases and send them in the message; post with sendmail/pipe
289 refuses to do that. For backward compatibility, spost has been
290 replaced by a simple shell script that exec's post -mts
291 sendmail/pipe. See NOTABLE CHANGES below.
292 - Support for the undocumented and deprecated --enable-nmh-debug configure
293 flag has been removed.
294 - Support for encoding some characters designated as EBCDIC-unsafe
295 via the -ebcdicsafe and -noebcdicsafe switches to mhbuild has
297 - The configure flag --with-pager has been removed; the default pager
298 is now hardcoded as "more". Users are still free to override the
299 default using the PAGER environment variable or entries in .mh_profile.
300 - The configure flag --with-editor has been removed; the fallback editor
301 if none is configured is "vi".
302 - The support for the undocumented NOPUBLICSEQ preprocessor definition
303 to disable public sequence support has been removed.
304 - Support for the -normalize and -nonormalize switches to the ali(1) and
305 ap(8) commands has been removed.
306 - "make install" no longer strips executables. Use "make install-strip"
308 - The environment variable MM_CHARSET to indicate the native character
309 set is no longer supported. The native character set will be solely
310 determined by the locale settings.
311 - Temporary files are stored in the first non-null location of
312 {MHTMPDIR environment variable, TMPDIR environment variable, MH Path}.
313 They are no longer be stored in the location specified by the TMP
314 environment variable.
315 - Instead of printing PostScript attachments, by default, from mhshow,
316 try to find a suitable viewer.
317 - Support for parallel display of multipart/parallel content has been
318 removed from mhshow; all multipart content will be displayed in
320 - Support for -pause/-nopause switches on mhshow has been removed.
325 - The undocumented -queue switch to post is deprecated/obsolete
326 and will be removed in the next release. It supports the
327 SMTP XQUE verb, which is obsolete according to
328 http://smtpfilter.sourceforge.net/esmtp.html
329 - conflict(8) is deprecated and will be removed from the next release.
330 - mhtest(8) is deprecated and will be removed from the next release.
331 - msh(1) is deprecated and will be removed from the next release.
332 - Support in alias files for the the "*" address-group is obsolescent
333 and will be removed in a future release.
339 - Replaced utilities that operate on pbm files with those that operate
340 on pnm files in etc/mhn.defaults [Bug #15152].
341 - Removed obsolete BUGS section at end of rcvstore(1) man page [Bug #4361].
342 - Fixed -nocc me doesn't account for Alternate-Mailboxes [Bug #36635].
343 - Propagate Mail-Followup-To [Bug #5571].
344 - "mark -sequence cur -delete all" now works for cur as well as any
345 other sequence, to allow clearing of the current message indication.
346 - The first alias contained in a blind list is now expanded. The
347 mh-alias(5) man page was updated to show that blind lists must not
348 be terminated with, or contain, a trailing semicolon [Bug #15604].
349 - Fixed sendfiles(1) to always provide a From: address. Also, updated
351 - Fixed pick(1) to properly unfold multiple-line header fields by
352 removing newlines instead of replacing them with spaces [Bug #15215].
353 - Removed the artificial limit of 1000 messages at a time for rmmproc.
354 - Fixed decoding of header fields when they contain a character that
356 - post(8) -sasl now honours username in .netrc [Bug #23168]. whom(1),
357 send(1), inc(1), and msgchk(1) also benefit from this fix. And, nmh
358 now supports specification of any valid filename in place of
360 - Added quoting of local part of invalid address in message being
361 replied to [Bug #26780].
362 - Fix segmentation faults for %(putlit) and %(zputlit) format escapes when
363 the "str" register was NULL.
364 - Encode and decode text MIME types with canonical line breaks properly.
365 - mhstore(1) now obeys its -noverbose switch.
366 - Properly report the input filename when mhbuild encounters errors.
367 - Set the content-transfer-encoding properly when attaching message/rfc822
374 The biggest changes in this release are in the arena of MIME handling.
375 Specifically relating to MIME composition and display. On the
376 composition front, mhbuild(1) will now automatically be run by send(1)
377 for all drafts. Specifically, mhbuild is now run with the new -auto
378 flag, which will suppress the processing of mhbuild directives and cause
379 mhbuild to silently exit if the draft is already MIME-formatted. When
380 invoking mhbuild manually via the "mime" command at the WhatNow? prompt,
381 mhbuild will behave as before and process mhbuild directives.
383 In both cases (automatic and manual invocation) mhbuild will encode email
384 headers according to RFC-2047 rules. Mhbuild also will use RFC 2231
385 encoding rules for MIME parameters when appropriate. In addition, the
386 attach system has been substantially reworked; the new header name is
387 now "Attach" (to better align with other MUA behavior) and cannot be
388 changed by the end-user. The existing "attach" command simply adds
389 the filename(s) to the draft in new Attach: headers, and the actual
390 file processing is done by mhbuild; this attachment processing will
391 take place in either automatic or manual mode.
393 On the display front, mhshow(1) will now automatically convert text
394 into the user's native character set using iconv, if nmh was built
395 with iconv support. Also, mhshow will now by default only display
396 text content that was not marked as an attachment. By default all
397 displayed content wll be run under one pager, as opposed to individual
398 pagers for each part as was in the past. Non-displayed parts will be
399 indicated using a marker string, which can be customized by a new
402 All nmh utilities now understand RFC 2231-encoded MIME parameters and
403 will automatically convert the encoded parameters into the native
404 character set, when appropriate (again, assuming nmh was built with
407 In other changes, sequence files are now locked using transactional
408 locks: locks that are held across sequence file reading, modification,
409 and writing. The locking algorithm used for spool files and nmh data
410 files is now runtime configurable.
412 For people that struggle with mh-format(5) files, a new utility for testing
413 them has been developed: fmttest(1). It includes the ability to trace the
414 execution of format instructions.
416 For users that wish to use Unix utilities on their mail, a new utility
417 to transform MIME messages to more easily-digestable format is now
418 available: mhfixmsg(1). It supports a number of options to control
419 the message transformation.
421 For users of spost(8), the support for spost has been rolled into post(8)
422 under a new sendmail/pipe MTS. A shell script emulating the old behavior
423 of spost has been provided.
425 As always, feedback is welcome.
429 nmh-workers@nongnu.org
431 ----------------------------------------------------------------------------
434 # NEWS - Release notes for nmh 1.5
437 Welcome to nmh, the new version of the classic MH mail handling
438 system. Long-time MH and nmh users should read carefully the NOTABLE
439 CHANGES section, as there are some subtle but significant changes
440 to the way nmh now behaves. Otherwise, please see the README and INSTALL
441 files for help on getting started with nmh.
447 The following are new features for the 1.5 release of nmh.
449 - Improved performance for TLS encryption of the SMTP protocol.
450 - MH-E and POP support are now always compiled in.
451 - The selection of a locking directory for dot-locking files is now
452 controllable via configure.
453 - fileproc and mhlproc mh-profile are now obeyed by send, rcvdist,
455 - New mh-format instructions have been implemented: %(putlit),
456 %(concataddr), %(myhost), %(myname), %(localmbox). See mh-format(5)
458 - Nmh's idea of the local mailbox is now configurable via a new profile
459 entry, Local-Mailbox. See mh-profile(5) for more details.
460 - comp, forw, and dist now process all component templates through
461 mh-format(5), and now all support new command line arguments -from,
462 -to, -cc, -fcc, and -subject.
463 - burst(1) now supports any valid message delimiter according to RFC 934.
464 - post(8) now requires a From: header in all drafts that it processes;
465 see NOTABLE CHANGES below for more details.
466 - post(8) can now explicitly control the SMTP envelope address either via
467 the Sender: header or the new Envelope-From: header.
468 - The -attach option is now the default for send (using the header
469 Nmh-Attachment) and -attachformat 1 is the default attachment type.
470 - repl and dist now support new switches -atfile and -noatfile to control
471 the creation of the ./@ link to the message being replied or
472 redistributed. The current default is -atfile.
473 - Support (if available) for readline editing and filename completion at
475 - Support for using an external command to filter the body of a message
476 through in mhl. See mhl(1) for more details, specifically, the
477 "format" keyword, the "formatproc" entry in mh-profile(5), and the
478 -fmtproc switch for mhl and repl.
479 - Preliminary support for improved MIME handling when replying to messages!
480 Yes, a long requested feature has a solution. A perl script
481 called replyfilter is available; it is designed to act as a mhl
482 external filter to process MIME messages in a more logical way.
483 It is available in $(srcdir)/docs/contrib/replyfilter or is
484 typically installed as $(prefix)/share/doc/nmh/contrib/replyfilter.
485 See the comments at the top of replyfilter for usage information;
486 it will likely require some adjustment for your site. replyfilter
487 requires the MIME-Tools and MailTools perl modules.
489 ----------------------------
490 OBSOLETE/DEPRECATED FEATURES
491 ----------------------------
493 The following features have either been removed completely or marked
494 as officially deprecated for removal in a future release of nmh.
496 - The creation of the ./@ link to the message being replied or
497 redistributed is deprecated; -noatfile will be the default in the
498 next release. If there are no requests to maintain -atfile it
499 will be removed in a future release.
500 - Old code enabled by the UCI preprocessor definition has been removed.
501 - All configuration options that were formerly only adjustable by editing
502 config.h have either been moved into configure or removed completely.
503 - Support for the built-in ftp client (used when dealing with external-body
504 message parts in MIME messages) has been removed.
505 - The following environment variables are marked as obsolete/deprecated.
506 Support for them will be removed from the next nmh release:
507 MHPOPDEBUG (use -snoop command line switch instead)
508 MM_NOASK (use -nolist and -nopause command line switches instead)
509 NOMHNPROC (use -nocheckmime command line switch instead)
510 FACEPROC (undocumented faceproc feature to be removed)
511 - The hostable option of mts.conf is no longer needed and has been removed.
517 The largest change is that post(8) now requires a From: header in all drafts
520 The impetus for this change has been the evolution of email and client
521 systems. When MH was first developed the norm was to have tightly managed
522 clients that were part of the same domain as a user's email address. This
523 is no longer a valid assumption, and the algorithm used by nmh to determine
524 the user's local mailbox is no longer a reasonable default.
526 Unfortunately, the way that nmh uses the user's local mailbox used to happen
527 very late in the message process; it was handled by post during message
528 submission. If no From: header exists in the current draft post would
529 insert one based on it's idea of the local mailbox, which was frequently
532 After a long discussion within the nmh development community, it was
533 decided that the only reasonable way forward was to move the local mailbox
534 handling up a level and place it under more direct control of the end
535 user. post(8) no longer will try to determine the local mailbox name;
536 it will take that information from the draft message. Thus a From: header
537 is now required in all drafts.
539 As part of these changes, all message composition utilities now process
540 their component files using mh-format. All of the default component
541 files have been modified to include a From: header in them; this will
542 give the user a chance to see nmh's idea of the local mailbox and modify
543 it if desired. The new mh-profile(5) entry Local-Mailbox can be used
544 to adjust the local mailbox name if the system default is not appropriate.
546 So how should end-users adapt to these changes? Here are some suggestions:
548 1) If you use the default component files, everything should basically work
549 the same for you. You should see a From: header in the drafts of your
550 messages. If the address you see in the From: header is incorrect
551 you can change it via the Local-Mailbox profile entry. You can also
552 use the -from switch to change it on a per-command basis.
554 2) If you have custom component files that include a From: header or
555 you perform custom processing on drafts that end up placing a From:
556 header in the draft message, everything should work as before.
558 3) If you have custom component files that do NOT include a From: header
559 then you will have to adapt then to include a From: header. You
560 can either simply hard-code the correct From: header or use the
561 default component files as a guide (see mh-format(5) for more
562 details, specifically the %(localmbox) function).
564 The other significant change is the support for filters in mhl. Included
565 in the distribution is replyfilter, a filter designed for sane processing
566 of MIME messages during replies. Since this isn't as integrated into
567 nmh as we would prefer, it's included in the contrib directory as an
568 optional component. Please try it out and give us feedback.
572 nmh-workers@nongnu.org
574 ----------------------------------------------------------------------------
577 # NEWS - Release notes for nmh 1.4
580 This releases contains numerous bugfixes and a number of new features.
581 The new features include:
583 - SASL security layers (encryption) are now supported for the SMTP MTA.
584 - TLS is now supported for the SMTP MTA.
585 - inc can now incorporate mail from Maildir drops.
586 - You can now select the SMTP server and port from either "send" or a
587 user's mh_profile (you could always select the server; that option is
588 now documented). These are available via the -server and -port
590 - All networking code has been modified to use the new networking APIs
591 (getaddrinfo and friends). All networking code (with the exception of
592 the built-in ftp client) now supports IPv6.
593 - New commands 'new', 'fnext', 'fprev', and 'unseen' for showing folders
594 with unseen mail (or mail in any specified sequence), changing to next
595 such folder, changing to previous such folder, and scanning all such
596 folders, respectively. This is based on Luke Mewburn's 'new':
597 http://www.mewburn.net/luke/src/new
598 - nmh will no longer attempt to install a mhn.defaults file that causes
599 mhshow to open its own xterms.
601 A large chunk of old code has been garbage collected. Specifically,
602 support for APOP, RPOP, NNTP (including bboards) and MPOP is now gone.
603 Also gone is support for prefixing a \01 in the "servers" entry in
604 mts.conf to iterate over all servers on a named network.
606 ----------------------------------------------------------------------------
609 # NEWS - Release notes for nmh 1.3
612 It's been over two years since the 1.2 release; but the changes here are
613 mostly minor; largely bugfixes.
615 You should note that we have changed the default configuration to allow
616 all supported forms of address masquerading. For more details please see
617 the --enable-masquerade option to configure, and the mh-tailor and post
projects / nmh / blob