4 The complete changelog of commits in between two versions can be
5 inspected by using the git(1) `log' command as shown below, where `OLD'
6 and `NEW' are the two versions to be compared, e.g., v14.5.2 and v14.6.1:
9 $ git log --reverse --topo-order OLD..NEW
10 # Only topic branch headers:
11 $ git log --oneline --merges --reverse OLD..NEW
12 # Same, but truly accessible:
13 $ git log --oneline --parents --merges --reverse OLD..NEW |
14 while read c1 c2 c3 c4 c5 c6; do
15 printf "%-24s: \$ git log --oneline --no-merges ${c1} ^${c2}\n" "${c6}";
21 Thanks to Andy Switala (andy DOT switala AT gmail DOT com).
22 And thanks to all package maintainers for their stamina.
24 At the first workday after the release i've run into a bug that was
25 caused by an oversight, a double-Fclose() that would be harmless if we
26 wouldn't forcefully panic() when we encounter it!
28 So i've spent another week on a review, and despite fixing many
29 additional notational oversights i haven't found more oversights of
30 newly introduced problems. On the other hand i've found and fixed some
31 old problems during the review, and tweaked some other things:
33 - The INSTALL file now has a `Current codebase state' section.
35 - Commands invoked via `!' should now be interruptable.
36 I'm afraid the exit status of such a command will not be reflected by
37 the return value of the `!' command yet, but hey, at least `!sleep 10'
38 can now be interrupted -- try this with another Berkeley Mail!
41 - All credential prompts should now be interruptable.
42 (Inspired from Andy Switala) [c3bb2a2]
44 - 'make test' will now test a silly S/MIME case when WANT_DEBUG (or
45 'make devel') was used. [8cff17f]
47 - *batch-exit-on-error* should now look at the exit status of *every*
48 command when the command loop ticks. [c7e7d53]
50 - The new `[?name-list]?search-pattern' search expression has been
51 changed to `[@name-list]@search-pattern' -- like this it doesn't clash
52 with the `?' help command and can thus be used on a line by itself,
53 causing the default command (`next') to be invoked on its' result,
54 shall there be one. Ok, yes, that was surely also an oversight.
60 + With this release the S-nail codebase has been converted to my usual
61 style of function-code-flow and notation.
63 ?0[]$ git diff --shortstat v14.5.2..HEAD
64 55 files changed, 28065 insertions(+), 25356 deletions(-)
65 ?0[]$ git diff --ignore-all-space --shortstat v14.5.2..HEAD
66 55 files changed, 14664 insertions(+), 11955 deletions(-)
68 Maildir and S/MIME support have been restored, and a MIME bug that
69 could have led to missing data in header display+ has been fixed.
70 Ah, and users of compressed boxes should now feel luckier, too --
71 at least once they've realized that the compress extension is no
72 longer appended automatically, but must be given explicitly.
74 Thus: i hope that all those i-am-new-to-the-codebase bugs i've
75 introduced over a year ago have been found and fixed, and that
76 v14.6 is the true "sweet sixteen" (months of maintainership).
78 ChangeLog (packager-affine)
79 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
81 - If WANT_AMALGAMATION is set, `-pipe' will be added to our CFLAGS
82 (which are only honoured with WANT_AUTOCC, of course). [1330411]
84 - New configuration option: WANT_IMAP_SEARCH, enabled by default.
86 The regular expression support for IMAP-style search expressions has
87 been removed again: it changed the IMAP search semantic in that it
88 couldn't be executed on the server, but only local, and the syntax
89 sucked, too. (And we have a new `?' search expression.) [402b7c6]
91 - CONFIG=MEDIUM and CONFIG=NETSEND now both WANT_REGEX. [dee954e]
93 - The `make test' target should *really* work gracefully, now that usage
94 of the `-#' command line option also sets the folder to be opened to
95 `/dev/null'. (Still no `void' box in sight.) [0119d514]
97 - All published patches may also be found in a new [patches] branch.
102 - Several fixes that saw published patches (with equivalent
103 functionality), and are thus described in NEWS, are included:
105 . s-nail-14.5.2-sort-alt.patch
106 Fixes a hasty commit that introduced string relaxation in a faulty
109 . s-nail-14_5_2-mimeheader.patch
110 Fixes data loss if multiple MIME encoded-words follow each other in
111 header bodies. [c81afce]
113 . s-nail-14_5_2-maildir.patch
114 Effectively restores proper maildir support. [1c2563b, 13f325f]
116 . s-nail-14_5_2-smime.patch
117 Fixes an off-by-one error and, in effect, restores S/MIME sign and
118 encryption etc. support. [e759f75]
120 - The `screen' terminal type is by default recognized as being
121 colour-capable. [e759f75]
123 - With the NCL command line editor and WANT_TABEXPAND hitting <TAB>
124 should now act as if an "implicit asterisk" had been given in case
125 there was no expansion of the original user input; e.g., '? ls <TAB>'
126 may exceed your line limit now ;). [0910a8f]
128 - The S/MIME cipher list was outdated, RFC 5751 requires AES-128 as
129 the default, the RC2 ones are long obsoleted (etc.). Also we now
130 should handle that OpenSSL may not support individual algorithms.
132 Note: we use the option value `des3' for `DES EDE3' from now on!
133 (Maybe see *smime-cipher-user@host* manual entry.)
135 *ssl-method* may now also be assigned the new (default) method `auto'
139 - Messages will now be stored in a set *record* even if only file or
140 pipe addressees were given. [a11935b]
142 - Support for xz(1) compressed mailboxes has been added.
143 (The `Can't canonicalize' warning for compressed boxes had the same
144 cause that made maildir usage impossible, but i don't feel _too_ bad
145 because looking into the code a bit revealed that the *newmail*
146 mechanism never worked for such boxes anyway. And will for a while.)
149 - S-nail now supports nested if..else..endif conditionals. [3c22c04]
151 - The NCL command line editor now locks its' history file when it reads
152 and writes it, so as to protect against concurrent usage. [c3a39ce]
154 - You can now say 'fi%', 'fi&', 'p&10' and `ghost ps '!ps axu'' followed
155 by 'ps|grep nail'. [c3266c6]
157 - Invocation cleanup: usage of -f and -u is mutual, -H and -u is ok, -u
158 in send mode not. [fa0a0aa]
160 - New message specification: `[?name-list]?search-string' will search
161 in locally available messages. If the optional `?name-list' part is
162 given, that specifies the (comma-separated list of) header fields to
163 search in. The special names `body' and `text' can be used to search
164 in message bodies alone and bodies including the headers fields,
165 respectively. Note that "message bodies" unfortunately still means
166 "including headers of attachments and attachments themselves", and
167 until some later time. [61bb460]
169 - The new command line option `-L spec-list' prints a header summary of
170 only those messages that comply to the specification list `spec-list'.
171 If -L and -H are used in combination, no summary is printed at all,
172 but the exit status reports wether `spec-list' would have matched some
173 messages or not. [934e12c]
175 ChangeLog (purely technical)
176 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
178 - Most of the work was changing the code-flow of the entire codebase to
179 my usual style of programming, with a single function entry and
180 a single function exit, including the addition of N(ot) Y(et) D(ead)
181 points of interest, which finally enabled me to get rid of (sic!)
182 using a debugger for S-nail development. Just compile via 'make
183 devel', and in case of a crash you should get a nice backtrace
184 listing. (You use IMAP, do you?)
186 However, because practically every line of code has been touched, this
187 caused some other changes along the way, e.g., the handling of
188 temporary files was changed completely (the formerly used Ftemp()
189 function has been replaced with a new Ftmp(), which handles unlinking
190 itself as necessary etc.), it was detected that the S/MIME support was
191 no longer compliant to any RFC, some resource leaks have been
192 eliminated... It is likely that a change so large introduced some
193 other flees and flaws, however. But it looks good so far.
199 + No official release, only exists as git(1) tag.
201 v14.5.2: fix 4: 2014-02-15 (2014-02-14)
202 ---------------------------------------
204 - s-nail-14_5_2-smime.patch
205 Fix a very stupid off-by-one error that i've introduced
206 in [7bdf330] (OpenBSD 5.3: sigh, address strcpy(),strcat()
208 Until we've changed the used data from string to something
209 line-wise, use strcat(3) again.
211 v14.5.2: fix 3: 2014-02-10
212 --------------------------
214 - s-nail-14_5_2-maildir.patch
215 maildir folders would have caused problems in environments which
216 provide the realpath(3) function: beside a "cannot canonicalize PATH"
217 warning the finally used path would be wrong (`test3' would end up as
218 `test3/test3'), so that any further access would try to use the wrong
219 path. Please read the description of this patch and/or the commit
220 logs of the commits [1c2563b] and [13f325f].
222 v14.5.2: fix 2: 2014-02-05
223 --------------------------
225 - s-nail-14_5_2-mimeheader.patch
228 Subject: ehm, .getElementById("blink") needs <span
229 =?US-ASCII?Q?id=3D"blink">,?= not =?US-ASCII?Q?class=3D"id"?=
231 would yet be displayed without the " not " in between the two encoded
232 words because of faulty "encoded-word-continuation" detection (note
233 the quotation marks). The error path could also have been seen in
234 mail forwarding and in faulty searching etc.
235 This patch is in a row of fixes for my hasty [0f9ad93] from 2013-03-12
236 that already caused the v14.2 minor release (because of [b608c6b] from
237 2013-03-14). Those with mercy may read the commit message of [c81afce].
239 v14.5.2: fix 1: 2014-01-30
240 --------------------------
242 - s-nail-14_5_2-sort.patch
243 Reverses (sort(),thread(): use srelax()!, 2014-01-18, [a9b67e9]),
244 which was a hasty commit of an untested diff that i've added few
247 As a rather careless last-minute change i've added string relaxation
248 to threaded and sorted display, but it's really one more step towards
249 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
251 An alternative, forward-heading patch that keeps string relaxation has
252 been pushed to [master] as [5e75529] and is also available as
253 s-nail-14_5_2-sort-alt.patch.
258 Thanks to Ypnose, Sunil Nimmagadda and Gavin Troy.
259 Gavin Troy *really* deserves special thanks for facing [next]!
260 And i want to dedicate the new coloured message display functionality
261 to John Dodson and Ypnose. Thank you.
262 (And best wishes to beautiful Australia!)
264 ChangeLog (packager-affine)
265 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
267 - All utilities can now be overwritten during configuration so that
268 their values are fixated in the generated makefile (`mk.mk').
269 I.e., talking about MAKE=, STRIP=, awk=, cat=, chmod=, cp=, cmp=,
270 grep=, mkdir=, mv=, tee=.
271 rm= and sed= have to be overwritten from the command line, they're
272 needed before `conf.rc' is read.
273 [5c03347, 072ec65, 39a00ab, 23a1245, ?]
276 - The release tarball is now also available in a xz(1) version.
278 - New configuration option: WANT_COLOUR, by default enabled.
280 - 'make test' should now really work, even if the running user has
281 a mailbox with content. [f223a91]
283 - WANT_AUTOCC is now by default enabled, so as for normal users which
284 don't have the need to embed into a defined packaging environment.
287 - Installation no longer strip(1)s away debug symbols if WANT_DEBUG was
294 - Fixes to some bugs that are present since the first cvs(1) commit of
295 Heirloom mailx(1); includes that *ssl-key-user@host* should now work.
296 [4405a2cc, 9770c26f, 692976b9]
298 - Some off-by-XY fixes, thanks to the debug memory canaries.
299 [19b2b0d, 202506e, 43df6e4]
301 - Fixes for (other) stupidisms (of mine): [1c2161f]
303 This includes true implementation of in-memory history limit for the
304 NCL, which was the final and real solution to a segmentation fault
305 that Gavin Troy had to deal with on [next]. [1089f2b]
308 - For completeness: new command `var-inspect' shows information about
309 all given options. Mostly ment for implementing future tests.
312 - The `pipe' command no longer embeds message information into the
313 data passed through to the command (when *piperaw* is set).
314 [ef5ecc6 (part of topic/colour)]
316 - Simple coloured message (header) display is now possible. Please
317 read the new manual section "Coloured message display", use
318 *colour-disable* to turn it off. (It is enabled by default if it
319 knows the terminal is capable and, if used, the pager can, too. Note
320 we now set LESS=FRXi when starting PAGER and no LESS= is in the
323 Dedicated to John Dodson and Ypnose.
324 [topic/colour, c6e84c7]
326 - The `if', `else', `endif' syntax has been extended.
327 You can now "if 0" (never), "if 1" (always), "if $OPTION" (boolean
328 check for OPTION) and "if $OPTION == 'VALUE'" as well as "if $OPTION
329 != 'VALUE'". Unfortunately it is still not possible to use
330 conditionals inside conditionals. [0fb2ae7]
332 - -# now also sets MBOX=/dev/null. [4be2f1e]
334 - The NCL command line editor now supports cursor keys when the terminal
335 produces xterm(1)-compatible keycodes ('ESC' + '[' + [DACB] for left,
336 up, right and down, respectively). What a thrill, yay!!! [0cbf672]
338 - New (optional) command: `history': show or clear command line history,
339 or select a specific command line from in there.
340 History works a bit different now, and should no longer include
341 command lines which include specific message numbers; more to come.
342 [59c6195, topic/hist2]
344 I plan to join all the history management and use only the one that is
345 part of NCL now, hooking it into editline(3) and readline(3). That
346 would shrink tty.c a bit and also introduce duplicate elimination for
349 - The new ~u and ~U tilde escapes work like ~f and ~m, respectively, but
350 don't include any header lines. Inspired by a patch from
351 Sunil Nimmagadda on openbsd-tech@. [c37b8b3]
353 - The `|' command should work again -- it has stopped working on
354 2013-09-09 when i've accidentally changed the command name from `|' to
358 - As a rather careless last-minute change i've added string relaxation
359 to threaded and sorted display, but it's really one more step towards
360 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
361 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
362 Buffer allocs ever/max simultan. : 14/14
363 Overall alloc count/bytes : 17165/881088
364 Cycle maximums: alloc count/bytes: 16906/876984+0
365 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
366 Buffer allocs ever/max simultan. : 0/0
367 Overall alloc count/bytes : 16515/841816
368 Cycle maximums: alloc count/bytes: 16256/837712+829560
370 ChangeLog (purely technical)
371 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
373 - We now have debug canaries for all memory sources now that [8419d44]
374 added them to the "string dope".
376 - The most work has been done on our value system, which manages the
377 binary and value options, like *folder* etc.
378 It is now based on enumerations, i.e., constant integers, not on
379 strings. This of course only relates to non-dynamic options.
380 Anyway, this saves us key hashing and allows more compact data
381 representation in general (see the new header `okeys.h' for more).
387 ChangeLog (packager-affine)
388 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
390 - The build system *only* uses the automatically detected $CFLAGS and
391 $LDFLAGS if WANT_AUTOCC=1. I.e., even unset or empty $CFLAGS and
392 $LDFLAGS are not touched until then.
393 (We do however still set $CC if that is unset or empty or set to the
394 plain string "cc".) [856625f6]
399 - Fixed segmentation faults / bus errors when setting *nofolder*
400 / *line-editor-cursor-right* to the null string (only with WANT_NCL),
401 respectively. [d1f1a19b, 21e5c285, 9f6ff25d]
403 - *prompt* handling is now really POSIX compliant (thus no prompting
404 occurs not only for 'set noprompt', but also for setting *prompt* to
407 This was indeed a rather large changeset that also introduced the new
408 *prompt* escape character \&, which expands to `?' by default and to
409 `&' if *bsdcompat* is set.
411 Like that we now can simply assign "\& " to *prompt* at program
412 startup, which (a) allows to do 'set noprompt' without error (once)
413 and (b) allows for POSIX compliance in respect to prompt handling
414 without any complicated conditional code, but (c) gives us the
415 opportunity to continue to support BSD prompts.
418 - For completeness: new command: `features'. (Rather useful for being
419 able to implement more tests in the future, and act according to what
420 is really compiled into the tested binary.
422 - The `-#' command line option now also sets *quiet* by itself.
425 - nail.1: a newly introduced empty line in the manual produced error
426 messages on some systems. Fixed.
428 - The return value of the `mimetypes' command has been reversed and
429 should now be fixed. [acf56ac52]
431 - In threaded display the Subject: followup suppression no longer
432 takes into account invisible messages.
433 Also, rudely hack in a messages-already-written-in-this-round counter,
434 so that the followup suppression knows when "the top of the screen" is
435 reached, which (seems to) help(s) against missing subjects up there as
436 well as after a `newmail'. [topic/subject]
438 - Added a WANT_REGEX=1 toggle in `conf.rc'.
439 When we find regular expressions then a new regex-enabled IMAP-style
440 search is available (see the manual for more) [1ec8fe68]
442 ? f (/or subject ^\[S-nail (subject ^\[nail-devel))
443 ? f (/subject ^\[S-nail) (/subject ^\[nail-devel)
444 ? f (/subject "^\\[(S-nail|nail-devel)")
446 I'm looking forward for being able to add another, simplified, syntax.
448 ChangeLog (purely technical)
449 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
451 - The cc-test.sh has seen some tweaks, for easier future extension, and
452 for adding a test for [d1f1a19]. [several, mentioned: 21e5c285]
454 - On systems without a real wordexp(3) implementations deadlocks could
455 occur because we sometimes hold_all_sigs() to avoid longjmp(3)s away
456 (and will do so for quite some time, still), and that resulted in the
457 SIGCHLD that reported the exit of the started subshell to be blocked,
458 too (e.g., after '? *.h<Tab>': endless hang). Fixed.
463 Many thanks: Gaetan Bisson, William Yodlowsky, Gavin Troy,
464 Thomas (wasd AT gmx DOT net), Ypnose.
465 And Gavin Troy definetely deserves a very special credit.
466 But thank you all, and very much indeed!
468 ChangeLog (packager-affine)
469 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
471 - The `test' make target has been fixed. [f0991e14]
474 - It is possible to gain a different kind of make(1) verbosity by
475 using a VERBOSE=1 command line argument (this knob is not taken into
476 account when deciding wether a rebuild is needed). [498e4ad0]
479 - On Crux 3 Linux and OpenBSD the readline(3) and editline(3),
480 respectively, libraries will now be found when desired. [a7d1aa78]
483 - WANT_LINE_EDITOR has been renamed to WANT_NCL, *plus*.
484 So now there are WANT_READLINE, WANT_EDITLINE and WANT_NLC, each of
485 them can be set individually, and they are tested in the shown order.
486 Also, WANT_TABEXPAND and WANT_HISTORY have been introduced and can be
487 used to fine-tune functionality. [ae4e01e1, b2635feb, 9742bf40]
489 (While here, i've fixed WANT_TABEXPAND code so that it is more
490 sensitive to line excess; on Linux etc., where MAX_INPUT is 255,
491 strange behaviour could be seen because we didn't take into account
492 the length of the prompt at all. The NCL is assumed to have only
493 one remaining, but unfixable problem: backspace often is incapable
494 to cross visual line boundaries; use ^A/^E + ^L, then. [e832c04a]
496 Also, cursor (now ^B and ^F) and history movement (now ^P and ^N) of
497 the NCL have been changed. [d7d928da])
499 - WANT_QUOTE_FOLD is now enabled by default. And WANT_ASSERTS has been
500 renamed to WANT_DEBUG. [1e10da1f]
502 - The build system has seen yet another overhaul in general. CC, CFLAGS
503 and LDFLAGS plus are now tracked and changes will force rebuilds.
504 The new WANT_AUTOCC option can be used to let the build system figure
505 out a compiler and choose known-to-work flags. Use the new ADDCFLAGS=
506 and ADDLDFLAGS= command line arguments to add your specific flags on
507 top of those -- the final CFLAGS etc. are what is change-tracked.
509 This rather massive internal rework revealed that old Bourne shells
510 were yet not supported by the new build system, and so did testing
511 that UnixWare installation was yet impossible due to tool
512 incompatibility. [75c4b74e]
514 - The new WANT_AMALGAMATION option will force compilation of all the
515 sources in a single compilation unit. This requires a rather large
516 amount of memory, but may produce a more compact, maybe more optimized
517 binary. (Implementing this revealed quite some bugs which could
518 therefore be fixed.) [topic/amalgam]
520 - `nail.rc' has been pimped a bit (mostly comments, but
521 *mime-counter-evidence* is now always set). [e3094ba7]
523 That changeset was however buggy. [f3dcb46]
526 - We no longer use install(1) for `install'ation make rules. [80b02cd9]
531 - Even '$ s-nail & fg $!' will now work with the NCL. [2a8b5c55]
533 - Several off-by-one (off-by-two) fixes. [32ce9836, 71e6d013, f139dc36]
536 - Setting *noprompt* now prevents prompting, as per POSIX. [ecefaf63]
538 - *prompt*: new \$ (exit status of last command) and \@ (name of
539 currently active mailbox) escape sequences. [6f652046]
541 - One may now omit the space in '? unc' ('?unc') [05fcb383]
543 - New commands: `ghost' and `unghost' define command aliases (since
544 `alias' is taken for a different purpose) [topic/commands]
549 - There is now a pseudo account `null' (case-insensitive).
550 Also a new `localopts' command exists; when used from within an
551 `account' block, options changed will be reverted back to its former
552 value when the account is left (e.g. by switching to `null'):
555 alternates sdaoden@users.sf.net sdaoden@users.sourceforge.net \
556 sdaoden@googlemail.com sdaoden@gmail.com
557 set Sign="\n--steffen\nForza Figa!" sign="\n--steffen"
558 set smtp=smtp.gmail.com smtp-auth=plain smtp-use-starttls
564 set from="Steffen \"Daode\" Nurpmeso <sdaoden@gmail.com>"
569 set from="Steffen \"Daode\" Nurpmeso <sdaoden@users.sf.net>"
577 neither of *Sign*, *sign*, *smtp** nor *from* should be set.
578 Please see the manual for more.
579 TODO - neither command-ghosts nor alternates etc. are yet tracked
580 TODO - we should have a boolify() so as to say 'localopts yes' etc.
583 - New command: `cwd' (print current working directory).
584 Also fixing the `chdir' return value. [eff4397c]
586 - The *ssl-method* now allows explicit setting of 'tls.1.1' and
587 'tls1.2' values. [c66b4196]
589 - When sending to display, be aware that filenames in MIME parts may of
590 course be MIME-encoded! [1454be03]
592 - *hostname* is now honoured even if *smtp* is not set. (We always
593 supported *from*, so why not *hostname*?)
595 - The `-u user' option now acts identically to setting the $USER
596 environment variable and both now tend to mean something like
597 "impersonate as user in some aspects". Note that we have always used
598 the latter in one or the other way, and `-u user' always ment more
599 than just "open mailbox of user", so i think this change sharpens the
600 edge in the right direction. [09632731]
602 - Filename argument quoting has been tweaked for (some) function(s which
603 take a filename argument last). The following snippet as reported by
604 Gavin Troy should work now: [2bb9b80e]
606 ? mv +inbox.Junk\ Mail
608 - The GNU implementation of wordexp(3) is also (i've added a workaround
609 for the very same bug for Mac OS X in S-nail v14.3 [63273772]) buggy,
610 which causes segmentation faults when expansions failed (`fi &VOID').
614 - The `fi' command no longer uses the (possibly truncated) display
615 version of a filename, but the full path. [5cd85b07]
617 ChangeLog (purely technical)
618 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
620 - Large rework of internal structure: bundle inclusion of most of the
621 external and the content of most of the internal #include files in the
622 new nail.h. If that would have been done very first bugs like the
623 infamous MAXPATHLEN bug as reported by Paul Vojta (see v14.4.2) would
624 never have occurred. [21f3155b]
626 - Support for -fstrict-overflow cc(1) flags. [topic/strict-overflow]
628 - Fixed the quotation filter which yet allocated memory even if not
631 - String relaxation reduces memory pressure rather drastically when
632 working with many (especially MIME) mails at a time, e.g., when
633 writing a modified mailbox. Before all messages of a mailbox had to
634 be worked without releasing any memory in between, now we give back
635 memory (to our pool, not the system) after each and every message.
638 - The other memory source now uses bound canaries, which also found some
641 - We now use the EL_PROMPT_ESC editline(3) mode for prompting, which
642 should offer the possibility to use coloured prompts etc. with
643 (even those) editline(3) (versions which do offer it -- older versions
644 should just do fine by themselves).
645 S-nail uses the special trigger control character \1. [ea30d818]
648 Note however that all tested editline(3) versions are buggy and
649 either don't get it right (`\1COLOR-ON\1stuff\1COLOR-OFF\1') or are
650 incapable of proper repainting (`\1COLOR-ONstuffCOLOR-OFF\1').
652 - We now use the MD5 digest code from the OpenSSL library if that is
658 Many thanks: Gaetan Bisson, Stephen Isard, Jérémie Courrèges-Anglas,
659 William Yodlowsky, and Adam Sjøgren from GMANE.org!
661 ChangeLog (packager-affine)
662 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
664 - The packager-install: target has been fixed. [a8c1b0b]
665 (Gaetan Bisson and William Yodlowsky)
667 - As suggested by Gaetan Bisson the several build system tasks are now
668 individually addressable, i.e., 'make [OPTIONS] config', 'make build',
669 'make test', 'make packager-install'); nothing changes unless you want
670 to, in which case: please see INSTALL. [4d3b799]
672 The new target 'test' will call cc-test.sh with its new --check-only
673 option which will only perform the (too few) function tests on the
675 And cc-test.sh will no longer create output files, but simply echoes
676 to STDOUT and STDERR. [629e1ee, 786f219]
679 - The default configuration file now sets *bsdannounce* and *bsdflags*,
680 all in one line, as suggested by William Yodlowsky.
681 (If *header* is disabled, *bsdannounce* is ignored, but *header* must
682 be enabled by default according to POSIX, and *bsdannounce* is just
683 the same as *header*, but for the folder-switched event. Thus setting
684 *bsdannounce* is the more sane default, imho.) [6161f10]
687 - Announcement messages are now tagged '[ANNOUNCE]'. [26e1b35]
688 (Tagging suggested by Stephen Isard and Jérémie Courrèges-Anglas)
690 - The manual NAME now includes the version (but it's somewhat ugly).
696 - When switching folders when in compose mode, message attachments
697 become invalid. For v14.4.5, at least warn when this happens.
700 - When reading multipart/alternative messages which do not contain
701 a text/plain part, the (most likely HTML) part is not displayed (even
702 if S-nail is configured to display HTML). The reason is a bug i've
703 introduced with [0d43a999] (Change "Part X:" display message..,
704 2012-12-20). (Note that the committed fix i've posted to the list was
705 not correct either and has been fixed itself.) [225c02b, ecfa149]
710 Thanked, Gavin Troy, Gaetan Bisson.
712 - Fix output buffer confusion that would have occurred when parts of
713 a multipart mail had a pipe command set. Longer story in [e75d16dd].
716 - The makefile now supports a `packager-install' target that bypasses
717 the reevaluation of the configuration (after checking that there is
718 one) and directly steps ahead to the install process.
721 - Notes in INSTALL that CFLAGS and LDFLAGS need to be overwritten from
722 within (conf.rc or) the command line.
728 I convey special thanks to Karol Błażewicz and Gaetan Bisson.
730 - The new build system didn't allow to overwrite CFLAGS= when used in
731 conjunction with GNU make(1). To make a long story short, removing
732 a `.POSIX:' directive from the makefile fixed the problem. Luckily.
735 - More INSTALL notes for UnixWare 7.1.4, which suffers from the same
736 problem: here the fix is to use the -e option of make(1).
738 - Karol Błażewicz reported a segmentation violation he got when using an
739 Arch Linux S-nail test package, and Gaetan Bisson informed me about
740 that. The problem was that we didn't assign the resulting default
741 address (which gets used when *from* is not set) to the result which
742 gets used, effectively resulting in a NULL dereference. [cfd60479]
747 Many thanks to Paul Vojta.
749 - On GNU/Linux there is no MAXPATHLEN constant defined by default, as
750 this is a non-standard legacy constant. Mozilla ran into this some
751 time ago, though a bit different [1]. It made it easier for S-nail.
753 [1] <https://bugzilla.mozilla.org/show_bug.cgi?id=412610>
755 We could include `sys/limits.h' to get at MAXPATHLEN, there it is
756 defined to be PATH_MAX, but let's just include the standard `limits.h'
757 and ensure MAXPATHLEN ends up >= PATH_MAX. With this condition being
758 true even FORTIFYd sources won't bail with reported buffer overflows
759 because realpath(3) expects a buffer of PATH_MAX bytes. [bee5e57c]
762 - With the builtin LINE_EDITOR, ensure proper interaction with GNU
763 rlogind(8), which is alone in its quest to set the ISTRIP termios(4)
766 - Bugfix a codepath that would have prevented compilation when
767 HAVE_ICONV is not set.
768 While there, allow to unselect message attachments when using the `~@'
769 tilde command interactively, which i mysteriously had forgotten when
770 allowing selection of 'em. (oops?) [4f58ffea]
772 - It's now easier for packagers to get at debug-enabled CFLAGS; simply
773 use WANT_ASSERTS=1 (should not be enabled in shipouts, please).
776 - Fixed a terrible bug that i've introduced in november 2012, that would
777 have corrupted MBOX files when using the `resend' command. (The
778 so-called "From_ line" would have been quoted to ">From_ line" instead
779 of simply being stripped.) [19d449e2]
781 - Fixed a SIGSEGV for the builtin LINE_EDITOR, that would have occurred
782 if a history traversal (^B or ^F) would have been continued by
783 a reverse history completion (^R).
784 While there, avoid some multiple-beeps-in-a-row that yet occurred due
785 to code reuse, and document that ^G etc. reset the multibyte state
788 Also, the expand-on-tab code could have excessed line input maximums,
789 e.g., after `? /usr/bin/*<Tab>'. This was of course known, but
790 i wanted to keep it because all tested (modern) terminals "mess up but
791 won't break", and thus made it possible to use the data, even if it's
792 visual representation was messed up. The real solution will be much,
793 *much* more complicated, i.e., show possible *completions*, page-wise,
794 etc., i.e., just like is known by tab *completion*. This will need
795 far more time because it doesn't make sense to embed such complicated
796 code into the current bed.
797 Now i've chosen to simply don't display excess, but replace the
798 content with a message that says that there was excess. It simply
799 looks better. [0320c8ba]
801 - I've changed the use of `[?]' as a replacement sequence for invalid
802 / non-displayable characters to `?' (again). There are still code
803 paths (from the original codebase) which use the real Unicode
804 replacement character instead, so our display is still not unique.
805 On the long term the codepath can anticipate in all levels wether
806 use of Unicode is possible, so that, then, we will be unique again,
807 using either only `?' or the Unicode replacement character. [faf6380]
809 - I've anticipated in v15.0 and implemented *quote-fold* as a stream
810 filter. It is now multibyte safe and takes into account the visual
811 width of characters, i.e., ideographs etc. It is working almost as
812 good as an algorithm can work that looks at data linewise, but is yet
813 experimental and incomplete in that it will break lines even if only
814 whitespace or a backslash escape follows. It is code that is only
815 a few hours old, which is why it is not enabled by default. [
822 - Fix some harmless stylos and typos in the manual and `conf.rc'.
825 - Ensure *complete* proper cleanup on signal-caused configuration run
828 - Bugfix: reenable empty configuration variable overrides, as in
830 $ make install SID= NAIL=mailx ...
833 - Bugfix: rename the `conf.rc' variables SHELL, LISTER and PAGER because
834 they clash with the POSIX standard variables of the same names, which
835 hurts now that the configuration is run through the shell itself.
836 The configuration names are now XSHELL, XLISTER and XPAGER (ouch).
839 - nail.rc: comment out some non-portable S-nail(1) specifics, for those
840 who install this file as mailx.rc or so, somewhere. [3f14b01]
842 - From now on S-nail will use simple version tags, as, e.g., `14.4.1',
843 i.e., no more `s-nail-14.4.1'. [a75437d, 183d59c] (Jürgen Daubert)
845 Also move UAGENT out of `version.h' [f7be5be]
847 Uh! v14.4 must have originated in a bad dream; good it's vanished.
852 Thanks to the entire vivid and virile S-nail(1) user community is
853 proper, especially Stephen Isard, Gavin Troy, Martin Neitzel.
854 Not to forget Ryan Kavanagh and Ayan George.
856 Note this time the changes are in reverse order, i.e., oldest first.
861 15fbe09 ^bf9173f 'topic/varmac-unite'
862 Simplification and unification of variable and macro handling
863 40f6f58 ^15fbe09 'topic/cledit1'
864 Command line editor; new manual section `Line editor'
865 ad28a32 ^40f6f58 'topic/termsize'
866 Honour POSIX mailx(1) and respect $COLUMNS and $LINES on startup
867 dc3cd49 ^a446fd8 'topic/qf'
869 b8738f7 ^0651fd0 'topic/spam1'
870 Interaction with SpamAssassin; new manual section `Handling spam'
871 5419d6f ^b8738f7 'topic/make1'
872 Reworked build system; please read `INSTALL' and `conf.rc'
873 9ab4d6b ^5419d6f 'topic/list1'
874 Slightly tweaked message thread display, fix `:u :r' to mean it
879 - The default PAGER is now more(1). (But read on.)
881 - The `echo' command is now compliant, and fully supports XSI.
883 - The `group' and `ungroup' command aliases have been removed, they are
884 `alias' and `unalias'.
886 - We now have the capability of line editing and history.
887 One may choose from not less than three different implementations:
888 a builtin editor as well as possible linkage against BSD editline(3)
889 and also a GNU readline(3) compatible layer.
890 Please read the new manual section `Line editor'.
892 Input is now compliant in that an interactive line may be continued
893 after escaping the newline character with a backslash.
894 [topic/cledit1] (all of them)
896 The *prompt* variable may now contain shell escapes, just like the
897 `echo' command. [0938d8a]
898 As a special extension the new \? escape, when used within *prompt*,
899 will expand to the exit status of the last command. [41076d2]
901 - The POSIX standard environment variables $COLUMNS and $LINES are now
902 honoured upon startup. [topic/termsize]
904 - The `help' / `?' commands now support abbreviation, i.e.,
905 ``$ ? unc'' should now find `uncollapse'. [7b86195]
907 - The `~' abbreviation that has been introduced as an alias for `call'
908 is now a real command, not a magic shortcut. [9987289]
910 - The new variable *quote-as-attachment* can be used to additionally
911 embed the quoted message as a `message/rfc822' MIME attachment.
914 - The compose-mode command `~@' will now attach messages from the
915 current mailbox if given a filename of the style `#NUMBER'.
916 Please read the corresponding manual section `Tilde escapes', though.
918 - The `WANT_JUNK' and `WANT_SCORE', as well as Gunnar Ritters junk mail
919 management have been removed.
921 Instead S-nail(1) can now support interaction with SpamAssassin, but
922 sofar only via the spamc(1) / spamd(1) client / server pair of
923 programs that ships as part of SpamAssassin. The new configuration
924 directive `WANT_SPAM' controls wether this feature is desired.
926 Please read the new manual section `Handling spam'.
927 [topic/spam1] (Martin Neitzel)
929 (S-nail(1) is now *definitely* floating-point free.)
931 - The configuration and make system have been overhauled / reorganized.
932 The configuration is now in `conf.rc', also contains directives like
933 `PREFIX' etc, and is always read in. However, only those directives
934 which are not yet set (via environment or command line overwrites) are
935 incorporated into the set of configuration options. Therefore
940 will now build S-nail(1) twice, because of the changed configuration.
942 Note that `WANT_GSSAPI' is now by default disabled, which shrunk
943 a freshly started s-nail image by more than 30 percent.
945 We're not finished yet in that there is no dependency graph etc.
946 Please do read `INSTALL' and `conf.rc'.
949 - Message selection has been slightly bugfixed in that `:u :r' really
950 means `:u' AND `:r'. Compared to NetBSD Mail(1) it's still a shame.
952 Threaded message display has been slightly changed in that within
953 a thread identical Subject: lines are not repeated. It may not be
954 perfect yet due to the general list / thread state. [topic/list1]
956 - If, upon startup, the environment variable `NAIL_NO_SYSTEM_RC' is set,
957 then the system wide initialization file isn't read, just as if the
958 `-n' option had been given. [1b31535]
960 - It is now possible to use CTRL-C during connection hangs. (But in
961 general error recovery capabilities of the socket related
962 infrastructure is non-existent, practically speaking.) [45a9f36]
964 - *quote-fold* has been temporarily disabled, as it is not multibyte
967 No review for v14.4. And today is Friday, the 13th. Ouuuh!
972 I should *maybe* should have and want to give prominence to
973 Martin Neitzel for this, i maybe have misunderstood.
975 - Bugfix *synchronous* *pipe-** execution..
977 Well, unfortunately yet another newly introduced bug slept in
978 S-nail v14.3[.1] -- [a8d724b3, Add @ and @& shell command prefixes
979 for pipe-MIMETYPE, 2013-05-03] falsely changed the waiting state
980 for subprocesses, as has shown up by a HTML-only mail on the
982 'Seems i'm collecting one line fixes in this codebase; this needs
983 to change in the future.
988 I want to give prominence to Juergen Daubert (jue AT jue DOT li), who
989 reported that i've broken plain-old unfancy send mode in 14.3.
991 + Ok, i'll hope we're out of new errors for the v14.3 series with that.
993 - New variable: *batch-exit-on-error*.
994 Only works if the new -# command line option has been given, and will
995 check the "current" exit status whenever one operation completes
996 (S-nail returns to the command prompt).
997 If the exit status implies error (e.g., sending the last message
998 failed) then we exit forcefully with that error status. (The normal
999 behaviour is that the status is reset when the command loop ticks.)
1002 - While here again, i've added the new -# command line option.
1003 This is the first step to implement a reliable batch mode;
1004 unfortunately it still selects the users system mailbox on startup,
1005 because we simply cannot go to "no" mailbox for quite some time -- at
1006 some future time we will be able to go to some VOID thing, and then
1007 this will end up as a rather efficient batch mode.
1008 For now it sets *dot*, *emptystart*, *noheader* and *sendwait*, and
1009 also implies the -~ command line option. [7549569]
1012 printf "m ${MBOX}\n~s subject1\nE-Mail Körper 1\n.\n" &&
1013 printf "m ${MBOX}\n~s subject2\nEmail body 2\n.\n" &&
1015 ) | MAILRC=/dev/null "${NAIL}" -n -#
1017 - Also, -N set *header* instead of *noheader*. [7b4a13f6]
1020 - Plain old unfancy invocations like
1023 $ echo bla|s-nail ./FILE1
1025 had been broken (by [522cb3ec]). [260e19d]
1031 Thanks to Gavin Troy (gavtroy AT gmail DOT com) who inspired the @ and
1032 @& pipe-command prefixes.
1037 - S-nail has been registered at Coverity Scan, and the third build
1038 (after topic branches *coverity-444* and *coverity-444.2*) produced no
1039 more errors. (<http://scan2.coverity.com/projects/444>.)
1040 (Then i used POP3 and IMAP and fixed some SIGSEGV. ;) Still didn't
1041 look at S/MIME, Maildir, caches etc... o()
1043 - S-nail v14.3 doesn't produce any spurious linker warnings on
1044 OpenBSD 5.3; all (correct!) use cases of strcpy() and strcat() have
1045 been replaced. [7bdf330, 2c8d7cb]
1047 - This is the first release with a (though very short) review -- i'm
1048 slowly getting comfortable with the code. (But i'm too stupid to
1049 perform reviews on patches, 'always did reviews on C++/Perl/xy
1050 classes. Aaah, how beautiful ... objects.)
1055 - It is now possible to "call" macros without using the `call' command
1056 by prefixing them with a tilde, as in
1065 - Added the *pop3-bulk-load* option.
1066 Yes, there are mailing lists etc. which use plain text email, and,
1067 there, headers are often more data than the body, so it doesn't make
1068 sense to download the headers twice (unfortunately POP3 doesn't
1069 support a BODY command; if only it would support a RETRDELE command..)
1072 And yep, from this changeset on i personally use S-nail even over the
1073 network, no longer my stale and incomplete S-Postman. And i can tell
1074 you, this damn thing is so silent, i always set *verbose* not to go
1075 grazy ... but .. i hate to say it .. the healing will take time.
1077 - POP3 will now try to use APOP authentication automatically; thus the
1078 *use-apop* stuff has been replaced by *pop3-no-apop* options (just in
1079 case there are POP3 servers which advertise they support APOP but in
1080 fact fail to do so; anyone?) [6c3c5575]
1082 - Some IMAP segmentation violations have been fixed:
1084 ? fi imaps://user1@localhost
1085 Password:Interrupt <- CNTRL-C
1086 ? set imap-auth=cram-md5 <- hey, 'forgot to set correct auth
1087 ? fi imaps://user1@localhost
1088 IMAP write error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown
1091 And also, when *folder* was set to an IMAP account but hasn't been
1092 opened yet, and no IMAP account ever has been opened, a string
1093 comparison against a NULL pointer yet caused a SIGSEGV, too.
1096 - `set folder=' now tolerates `%:' and expands PROTOs stuff etc.:
1098 ? short xp %:imaps://user1@localhost
1101 Pure convenience so that it doesn't need to be typed twice (still no
1102 completion in sight...). Note that setting *folder* to a POP3 box
1103 will now be actively rejected. [b12b17f5]
1105 NOTE: while implementing this i've detected another dead-end
1106 miscondition in S-nail -- you really should ensure that your target
1107 folder/box is connected before you leave your current POP3/network
1108 based folder, if there is data to be moved to the target (i.e.,
1109 mbox). This problem will persist for a long time due to the way the
1110 entire codebase functions; i hope i can find a short/mid-term
1111 solution, but the real healing will take years. The mentioned
1112 solution would at least make S-nail interruptable, currently we get
1113 stuck and interrupts are blocked...
1115 - If you're using S-nail on Mac OS X and have seen some segmentation
1116 faults when expanding shell stuff then you may be pleased to hear that
1117 S-nail now works around an Apple bug. [63273772]
1119 - The builtin mime.types have been corrected and a lot of new ones have
1120 been added. New data from
1121 <http://svn.apache.org/viewvc/tika/trunk/tika-core/src/main/resources/\
1122 org/apache/tika/mime/tika-mimetypes.xml>, thanks! [8072fcb6]
1124 - BEWARE: handling of command line arguments has changed a bit!
1126 1. The -D, -d, -E, -i, -N and -v command line options are now
1127 implemented by means of setting the respective option, as via -S.
1128 (This means that from now on resource files can only *temporarily*
1129 overwrite command line arguments.)
1131 2. The -I and -T command line arguments have been dropped.
1132 It seems Gunnar Ritter stopped developing nail/Heirloom mailx once he
1133 started implementing Newsreader functionality. It'll take a long time
1134 until we get there, so for now drop all the Newsreader stuff.
1136 3. Handling of -r has been changed. E.g.:
1138 s-nail -A test -Snoeditalong -r 'La mort est <fem@me>' -d
1139 ? set from=bummer@m1.com
1143 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t1"
1144 ? set from=bummer@m2.com
1147 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t2"
1151 s-nail -A test -Snoeditalong -r '' -d
1152 ? set from=bummer@m1.com
1156 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m1.com" "t1"
1157 ? set from=bummer@m2.com
1160 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m2.com" "t2"
1162 [*main-fun-cleanup* topic branch]
1164 - *smime-sign-include-certs-** stuff works again, oops.. [9a8597c6]
1166 - A whole lot of smallest and small fixes due to registration at
1167 Coverity Scan, as project 444. Error handling in S-nail is ridiculous.
1168 [*coverity-444* and *coverity-444.2* topic branches. The sheer number
1169 of fixes was the reason to sit down and go for unplanned S-nail v14.3]
1171 - *idna-strict-checks* has been dropped. It's silly to have in a MUA,
1172 especially given that GNU LibIDN doesn't ship with a lot of rules.
1173 We were able to drop quite some code (and a use-after-free, too :().
1176 - The ~p tilde command displays attachments more verbose.
1177 Until the big big MIME and send layer rewrite :) this is intermediate
1178 since until then we do not really know neither MIME type nor charset
1179 of an attachment at the time this is displayed (for sure). Yet
1180 i think it's nicer to show what we have than keep it the way it was.
1183 - @ and @& shell command prefixes have been added for the pipe-MIMETYPE
1184 mechanism. The former suppresses filters if multiple messages are
1185 displayed at once, the latter adds asynchronous program execution on
1186 top of that. E.g., to display PDF documents, but only if you
1187 *explicitly* address the message *alone and by itself*, and without
1188 blocking S-nail and the $PAGER, do:
1190 set pipe-application/pdf="@&cat >"${TMPDIR}"/s-nail${$}.pdf;\
1191 mupdf "${TMPDIR}"/s-nail${$}.pdf; rm "${TMPDIR}"/s-nail${$}.pdf"
1193 (Inspired by Gavin Troy.) [a8d724b3]
1195 Note: most of that had been posted to nail-devel@ already, but it was
1196 tweaked ([251b636]) so that you now *really* have to say `p MSGNO' to
1199 - The NETLESS CONFIG= has been removed; it is almost identical to
1200 MINIMAL now (i.e., without WANT_JUNK and WANT_SCORE).
1202 - WANT_JUNK and WANT_SCORE have been disabled by default.
1203 They don't seem to be too useful; i hope i can implement
1204 a SpamAssassin hook for (downloaded) mail messages for v14.4.
1205 If so, expect these two "modules" to become removed completely.
1210 Another unplanned (minor) bugfix release after Gavin Troy (gavtroy AT
1211 gmail DOT com) pointed out that MIME CTE decoding was broken, who
1212 i therefore want to give a lot of prominence right here.
1214 - Fix MIME content decoding which has been broken by [01c0e135].
1221 An unplanned (minor) bugfix release after i've found two bugs today and
1222 heard from Jérémie Courrèges-Anglas (jca+nail AT wxcvbn DOT org) that
1223 there exists a S-nail OpenBSD package.
1225 I want to give prominence to the following people that helped to
1226 improve S-nail(1) during this development cycle, in order of
1227 appearance: Dirk Peters (peters AT schwertfisch DOT de).
1229 Thank you very much, and best from Germany!
1231 - Some warnings of newer clang(1) versions were silenced, including yet
1232 another alloca(3) problem (see *memtracer* topic branch in v14.0
1235 - Tweaking the MIME boundary detection left a little hole that could
1236 cause boundaries not to be detected, as has been shown by a Microsoft
1237 Word generated mail on the ICU list. [11e5fb5b]
1239 - A format string could overflow bounds if unrealistic
1240 (18446744073709551615) line numbers or message sizes would have been
1241 produced. [faa65c40]
1243 - An algorithmic error could cause overlong lines which wrapped around
1244 to the next display line. [ade52660]
1247 v14.2, 2013-03-15 [v14.1, 2013-03-12]
1248 -------------------------------------
1250 I want to give prominence to the following people that helped to
1251 improve S-nail(1) during this development cycle, in order of
1252 appearance: Martin Neitzel, Christos Zoulas, Stephen Isard, jgw@txo.org
1255 Thank you very much, and best from Germany!
1257 + v14.2 differs from v14.1 only by one commit, one that fixes
1258 (mime_fromhdr(): partial rewrite using n_iconv_str(), 2013-03-12),
1259 which i hastily implemented just hours before the release of v14.1,
1260 and simply shouldn't have made it (into there).
1261 The v14.1 tarball has been removed from the server.
1263 - A fix for the quoted-printable codec: "message truncation" occurred
1264 when a mail maliciously used a soft linebreak to escape the linebreak
1265 of a completely empty line.
1266 (That resulted in 0 written and 0 leftover bytes, a condition that was
1267 declared erroneous back in november 2012 when i started handling I/O
1270 - The "folders" command will work again when given an argument.
1271 A fault of mine introduced in (cmd1.c: expand() may fail, 2012-10-23).
1273 - The Base64 codec has been touched again, and we are finally capable to
1274 perform sequential decoding; this was targeted for the MIME/send layer
1275 rewrite, but it actually was possible today.
1276 The result as seen in ps(1), running on the Base64 encoded HTML5
1277 standard (4622545 bytes HTML, with a NUL appended to force Base64
1278 encoding, resulting in a 6244793 bytes email):
1280 7420 s006 S+ 2:22pm 0:10.65 plain-nail -f HTML5
1281 1440 s006 S+ 2:23pm 0:00.36 ./s-nail -f HTML5
1283 (So the only thing that is left for a good throughput is sequential
1284 decoding of quoted-printable encoded parts that maliciously use soft
1285 linebreaks to convert an entire part to a single line. And i've seen
1286 that from Apple Mail.)
1288 - New option: *mime-allow-text-controls* (rather long manual entry).
1290 - *smtp-auth-password-user@host* and *smtp-auth-user-user@host* will
1292 (Reported by jgw@txo.org in November 2011, fixed by Gavin Troy in
1295 - Most *headline* formats now do support the '-' left-alignment flag.
1296 Note that you most likely have to change your *headline* accordingly.
1297 (The still missing %n format is one reason why there will be v14.2.)
1299 - *datefield* and *datefield-markout-older* can now be set to
1300 strftime(3) format strings (except %n).
1301 (From Stephen Isard's wishlist.)
1303 - A possible SEGV has been found and also fixed by Stephen Isard.
1304 (The "legendary" cross-world stereo fix!)
1306 - Wow! S-nail will finally compile on GNU based Linux systems like
1307 Slackware 14 etc. (Found while hunting bug reported by
1310 - New option: *datefield-markout-older* can be used to choose
1311 a different date display for mails that are older than six months,
1312 in equal spirit to what POSIX describes for the -l option of the ls(1)
1313 command (Stephen Isard).
1315 - (Exotic) Years are (would) now (be) interpreted correctly according to
1318 - CRAM-MD5 usage has been fixed.
1320 - *folder* updates are now tracked when set, and we will show the
1321 realpath(3) name of it, showing PREFIX..SUFFIX if that wouldn't fit on
1323 Tracking updates made it also possible to perform other more expensive
1324 tasks when setting *folder*, so that it is now possible to do
1330 et cetera (both ideas by Christos Zoulas).
1332 - Bugfix for the ~@ tilde-escape in non-interactive mode.
1333 (readtty(): quick shot: work in pipelines (on non-TTY).., 2013-01-25)
1334 introduced the possibility to "read data from the terminal" (STDIN
1335 that is) in non-interactive mode.
1336 The manual documents that attachment input must be terminated with an
1337 empty line, but if that had been omitted, as in the example below, we
1338 would have yet entered an endless loop.
1340 $ cat <<_EOT | /s-nail -~ -s boom ./OUT
1346 - Alias expansion will now be performed for members of Reply-To: fields
1349 - Decoding quoted-printable will now be more relaxed.
1350 (Even though the standard says that users should be given a hint when
1351 input is not absolutely clean; a possible warning will be added later,
1352 when we have an error message ring.)
1354 - New option: *mimetypes-load-control* can be used to control which of
1355 the mime.types resources will be loaded.
1357 - The builtin default mime.types have been extended a bit.
1362 I want to give prominence to the following people that helped to
1363 improve S-nail(1) during this development cycle, in order of
1364 appearance: John Dodson, Gianluca Ramunno, and Anon Ymous from the
1370 - Encoding defaults to *quoted-printable* not *8bit*.
1371 This has no technical background except that i think it's the better
1374 - Small progress for the "getting stuck due to the current folder
1375 becomes inaccessible due to whatever reasons" problem.
1376 (schdir(): realpath() local files before leaving CWD.., 2013-01-08)
1378 - The names of temporary files have changed. Whereas not all uses of
1379 temporary files already use really meaningful names, it has yet become
1380 possible to use the pattern "*mail-*"; or, to be compatible with
1381 NetBSD Mail(1) in one go, "*mail*". (E.g., in my ~/.vimrc you'd read:
1382 :au BufRead,BufNewFile *mutt*,*mail* setl fenc= | setf mail
1383 [the *mutt* is a leftover from times when i've used MUAs that suck].)
1388 - The Quoted-Printable MIME handling has been rewritten completely.
1389 We now correctly encode files with the MS-DOS newline sequence (CRLF).
1390 (Part of the *mime-cte* topic branch.)
1392 S-nail(1) continues to be able to handle text messages and text
1393 attachments without a trailing newline, but because these
1394 Content-Transfer-Encoding related things are now handled by the C-T-E
1395 layer instead of by sendout.c a text message body that comes in as
1396 part of a complete message via the -t command line option will loose
1397 the missing final newline (i.e., it'll gain one).
1398 This problem does *not* occur when *only* the message body comes in
1399 via STDIN, as in 'cat FILE | s-nail', but *only* when the -t option is
1401 (sendout.c: does no(t/ longer) know about CTE internals!, 2013-02-09)
1403 - Filename arguments for -a are now processed *after* all the resource
1404 files have been loaded etc., so that the usual "folder" specifics can
1405 be used (provided that proper care for shell quoting was taken).
1406 ((main(): delay -a processing.., 2013-01-10), as a part of the
1407 *mainaflags* topic branch.)
1409 - (d38c5bd, When the write command asks.., 2004-11-23) added support
1410 for pipes when saving attachments during a "write" command.
1411 It however used the wrong SIGPIPE signal handler; e.g.:
1413 Enter filename for part 2 (application/x-gzip): |exit
1416 Of course, it still performs a jump and that most likely leaves memory
1417 chunks behind, thus causing some memory leaks. This will be
1418 a long-term problem (you may want to read [mime.c:fwrite_td(): TODO
1419 notes on unfixable leaks, 2013-01-14] for more).
1420 (send.c:sendpart(): fix longjmp() SIGSEGV.., 2013-01-29)
1422 - Fixed a name quoting regression that i've introduced in
1423 (Rewrite *extract().., 2012-10-20), that would have caused
1424 "x \"y\" z" to become "x"y" z" instead of "x "y" z".
1425 (S-nail still does not really have RFC compliant parsers, just as
1426 NetBSD Mail(1) has, i.e., there are structured and unstructured fields
1427 etc... I hope i can provide them in v15.0.)
1428 (names.c:yankname(): fix quote regression.., 2013-01-29)
1430 - The IDNA conversion now assumes domain names are specified in
1431 *ttycharset*, rather than in the LC_CTYPE locale charset.
1432 I.e., it integrates into the usual character set specifications.
1433 (IDNA: honour *ttycharset* for domain names, 2013-01-18)
1435 - The new *editalong* variable will automatically spawn an editor when
1436 composing a mail in interactive mode, just as if `~e' was given.
1437 (Add new *editalong* variable, 2012-01-07)
1439 - The manual has been converted to mdoc.
1440 (The manual has been converted to mdoc, 2012-12-28)
1442 - The ~@ tilde escape, when given filename arguments, will treat the
1443 arguments as a comma-separated instead of a whitespace-separated list.
1444 (collect: change separator of ~@ tilde escape.., 2012-12-28)
1446 The interactive mode of ~@ has also been changed, rather massively.
1447 Please do reread what the manual says.
1448 ((collect: support multiple attachment charsets.., 2013-01-23), as
1449 part of the *attach* topic branch.)
1451 - Thanks to Gianluca Ramunno (ramunno DOT gianluca AT gmail DOT com)
1452 S-Nail will no longer try to issue a STARTTLS command when it is about
1453 to establish a SMTPS connection, a task that logically fails since the
1454 connection is already secured.
1455 (Interestingly the nail codebase performs the necessary test for IMAP
1457 While here the undocumented nail v11.0 *smtp-use-tls* legacy option
1459 (Fix SMPTS with a set *smtp-use-starttls*.., 2012-12-22)
1461 - The RFC 4155 compliant MBOX quoting is now exclusively used, the
1462 shitty *posix-mbox* variable has been removed again.
1463 (Shitty because i've implemented RFC 4155 compliant MBOX quoting and
1464 tested it, then added *posix-mbox* for those who liked the old
1465 behaviour and did not re-test -- the final code path was buggy.)
1467 In mails newly created and saved by S-nail(1) no From_ quoting at all
1468 will be used no more, but instead the rewritten MIME file classifier
1469 will detect unquoted From_ lines and enforce quoted-printable encoding.
1470 (This is an approach that is S/MIME compatible all through the way as
1471 the file data is not modified at all, but only encoded, so that the
1472 data checksum is not changed.)
1474 In yet existent mails that S-nail copies or moves around without
1475 reclassification an RFC 4155 compliant From_ line detector will apply
1476 MBOXO quoting (prepend a single '>') as necessary.
1477 Different to the old MBOXRD behaviour S-nail will neither quote yet
1478 quoted From_ lines ('>>From xy' -> '>>>From xy') nor will it unquote
1479 one quote level when reading etc. mails ('>> From xy' -> '>From xy').
1480 As a result the code could be simplified.
1482 This changeset also incorporates a fix for NetBSD PR bin/47453, as
1483 reported by Martin Brandenburg. I.e., some mailers, noticeably
1484 UW-imap (with MBX format only?), use non-compliant From_ lines with
1485 RFC 822 date specifications. Be aware of 'em.
1486 (RFC 4155 MBOX, and drop *posix-mbox* and foldergets().., 2013-01-06)
1488 - *rfc822-show-all* has been removed.
1489 It didn't work properly for more complex MIME structures, like
1490 message/rfc822 messages with attachments etc., just as i've seen today
1491 on the file(1) mailing list.
1492 So, instead of hacking it now i've dropped it and will come back with
1493 a better solution when the MIME and send layers have been overhauled.
1494 I.e., the real intent was to be able to specify that an embedded
1495 message/rfc822 is treated as a *unity*, and that's the goal.
1496 (Drop *rfc822-show-all*, 2013-01-23)
1497 [The manual will be adjusted in a different commit.]
1499 - *rfc822-no-body-from_* has been renamed to *rfc822-body-from_*.
1500 It thus must be set explicitly.
1501 On the other hand it now catches all cases...
1502 (*rfc822-no-body-from_* -> *rfc822-body-from_*, 2013-01-23)
1503 [The manual will be adjusted in a different commit.]
1505 - The new *charset-7bit* (defaults to US-ASCII) and *charset-8bit*
1506 (defaults to UTF-8) have been introduced.
1507 These are used if seven bit clean data is to be sent, and no
1508 *sendcharsets* are set or the convertion of all of them failed,
1511 - There is no functional change unless there is iconv(3) support.
1512 - There is no functional change unless you set them.
1513 (Introduce *charset-8bit* and *charset-7bit* variables.., 2013-01-18)
1514 [The manual will be adjusted in a different commit.]
1516 In addition the new *sendcharsets-else-ttycharset* variable can now
1517 be used to automatically use *ttycharset* as a *sendcharset(s)*,
1518 regardless of the new *charset-8bit* variable.
1519 (Add *sendcharsets-else-ttycharset* variable, 2013-01-24)
1520 [The manual will be adjusted in a different commit.]
1522 NOTE: before we apply charset conversion we now perform a string
1523 comparison to see wether character sets are identical. If the strings
1524 match (case-insensitively), then *no* conversion is performed.
1525 This means that code like
1527 $ printf "LATIN1: \0376" | s-nail -Ssendcharsets= -s boom ./out.txt
1529 *succeeds* in an UTF-8 environment now, whereas older versions would
1530 fail with an "illegal byte sequence" error (unless the iconv(3)
1531 library of the system would not perform any conversion that seems
1532 superflous, of course).
1534 I thought about making this optional, but, in fact, if this would be
1535 done in an environment without iconv(3) support then the result would
1536 be equally corrupt. And the way it is now we save the expensive and
1537 superflous conversions. (See TODO for more.)
1539 Please *do* reread the manual section "Character sets".
1540 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1542 - An attempt was made to improve MIME Content-XY: detection.
1543 It should be more RFC compliant, and just overall better :);
1544 a simple one-pass classifier cannot match libmagic(3), of course.
1546 This changeset removes support of the long obsoleted (4fee1ef,
1547 2005-01-06) *charset* variable, as well as for the
1548 *maximum-unencoded-line-length* variable that has been introduced in
1549 (48a652bd, 2005-07-26).
1551 For S-nail v14.0 it'll be no longer necessary to do
1553 $ tr -d '\015' < input | s-nail ...
1555 to transport files which use the $-DOS (terminal) newline (sequence).
1556 We still depend upon *sendcharsets* for a while, though.
1557 (Rewrite file-content classification.., 2013-01-02)
1559 - The new *mime-counter-evidence* variable can be used to force
1560 a classification of non-text MIME parts (attachments) by their
1561 filename, i.e., a "reverse-classification" just as would be performed
1562 if S-nail(1) would itself *send* the file(name). This can help
1563 against some stupid MUAs (Apple Mail?) that send .diff etc. files as
1564 `application/octet-stream' parts etc.
1566 At a later time this may become a valued option, causing a temporary
1567 save of unnamed attachments followed by a MIME classification of the
1568 file contents, followed by forced treatment as plain text if it seems
1569 to be human readable. But not yet. Just to warn you.
1570 (Add *mime-counter-evidence* variable.., 2012-12-29)
1572 - The special "pipe-" command "@" can be used to force treatment of
1573 a MIME message part as plain text (e.g.,
1574 'set pipe-application/pgp-signature=@' will henceforth print those
1575 signatures inline and as plain text).
1576 (Introduce the special "@" "pipe-" command, 2012-12-27)
1578 - The MIME types (as from mime.types(5)) will now be cached. Before
1579 all possible sources would have been opened, read and parsed for each
1580 and every message part that required detection of the MIME
1582 The new "mimetypes" command can be used to show or clear that cache.
1583 (Add mime.types(5) cache.., 2012-12-27)
1585 - A small set of MIME types (template: ./mime.types) will now become
1586 compiled into S-nail(1), and be used as a fallback if there are no
1587 ~/.mime.types and/or no /etc/mime.types, or those didn't contain
1588 a matching type. E.g., NetBSD 6 doesn't ship a default database.
1589 Also, file extensions will be matched case-insensitively (case of
1590 attribute values is not specified afaik?).
1591 (Introduce compiled-in mime.types(5).., 2012-12-21)
1593 - The undocumented *charset7* variable was removed.
1595 - The "Message X:" display leader has been changed and will henceforth
1596 be matchable via "^[-- Message \d+ -- \d+ lines, \d+ bytes --]:$".
1597 These lines can no longer be suppressed by setting the *quiet*
1598 option (which was yet possible for print and top, though undocumented).
1599 (Change "Message X:" display message.., 2012-12-20)
1601 - When displaying multipart messages the "Part X:" introductional string
1602 has been changed; if the Content-type: header is not *retain*ed, then
1603 this string will include the part's type and size. Ditto for
1604 Content-disposition: and a mentioned attachment filename.
1605 This is a first step only, for the final version the MIME and send
1606 layers will have to be adjusted. But the string will be matchable via
1607 a "^[-- #.* --]$" regular expression from now on.
1608 (Change "Part X:" display message.., 2012-12-20)
1610 - MIME boundaries in multipart messages are now handled better in that
1611 no boundary string should get through to the display.
1612 (Tweak MIME boundary detection.., 2012-12-20)
1614 - A couple of long standing, even pre-Heirloom mailx(1) memory leaks and
1615 segmentation violations, most of them related to configurations
1616 without alloca(3) support, as well as one leak that i have introduced
1617 when i implemented RFC 4155 MBOX handling, have been fixed.
1618 But S-nail should now survive non-alloca(3) configurations.
1619 (*memtracer* topic branch.)
1621 - The Base64 MIME handling has been rewritten completely.
1622 This was an urgent topic, because the old implementation (a) read in
1623 all lines of a base64 encoded text part, repeatedly resizing a string
1624 storage and repeatedly decoding that string until all the lines have
1625 been swallowed (i.e., or by accident the last decoded byte was
1626 a newline character, and that in turn may of course have fucked up for
1627 multi-octet encodings, dependent on the actual byte-order), (b) used
1628 function local static data to keep state in between multiple
1629 invocations, which messed up multi-byte/-octet encodings like this
1631 �5��ɽ���Aɥ����́��٥��������[lots of data follows]
1633 and (c) did not perform any error checking at all.
1634 The new one does not run into the problem that (a) tried to circumvent
1635 since leftover decoded data (as opposed to leftover *encoded* data) is
1636 transported along the call-chain for later use. It adds a minimal set
1637 of error handling ('may now see "[Invalid Base64 encoding ignored]"),
1638 with more to become possible in later S-nail versions when the entire
1639 layers are reworked. (Until then DOS newline sequences [CRLF]
1640 embedded into base64 will no longer be decoded to Unix LF newlines.)
1641 Base64 encoded lines will now be 76 characters long, as stated (as
1642 a maximum value) in RFC 2045, not 72 as before.
1644 The Base64 code core has been shamelessly stolen from NetBSD's
1645 Mail(1), and i guess it was the second time that this happened :=).
1646 (*base64-rewrite* topic branch; and reworked later on the *mime-cte*
1649 - The string allocation strategy has been tweaked some more to, i think,
1650 a final version (regarding algorithm).
1651 In normal non-interactive send mode it should now no longer need any
1652 dynamic memory at all (unless some dozen recipients are specified).
1653 (Several other places still use normal dynamic memory, of course.)
1654 (*dope-stringdope-again* topic branch.)
1656 - Support for NSS (Network Security Services) has been removed.
1657 I've never worked with it and are, regarding the complexity of
1658 network security, not willing to spend any time on it.
1659 SSL is installed on all systems i'm using and/or testing on by
1660 default, and so i've choosen to go this way.
1661 (It may be that sometime in the future S-nail will add support for
1662 libcurl(3) connectivity, and then it may happen that not only NSS
1663 support is reintroduced again, but also GNU TLS. All of that applies
1664 to network connectivity only, however, not to S/MIME afaik.)
1665 (*drop-nss-support* topic branch.)
1667 - I finally got a glue and understood that Sourceforge does (a) not
1668 support symbolic links and (b) doesn't like dots as regular parts of
1669 filenames. This means that all this time the promised s-nail.tar.gz
1670 symbolic link did not work, and that s-nailv13.3.tar.gz wasn't
1671 accessible either (via the web interface).
1672 In the future S-nail(1) will not provide any more symbolic links (the
1673 Sourceforge website offers a "download latest" thing which seems to
1674 work), and use underscores in filenames -- s-nailv13.3.tar.gz has been
1675 renamed to s-nailv13_3.tar.gz. The tags continue to use dot notation.
1678 - The *heirloom-plus* support branch has been removed.
1679 The code bases diverged a lot and even more to come.
1680 It doesn't make sense to put any effort in that.
1685 - Configuration on UnixWare 7.1.4 will succeed (shell issue fixed).
1687 - Even on DragonFly BSD the IMAP GSSAPI is now found
1688 (in /usr/pkg/include/krb5/gssapi/gssapi.h).
1690 - Support for pkgsrc(7) systems and automatic integration of
1691 C_INCLUDE_PATH and LD_LIBRARY_PATH path configurations.
1694 - Fixes a mortally embarassing regression that the current maintainer
1695 introduced before i really knew what i was doing, in (If *record* is
1696 set, avoid writing dead content twice.., 2012-09-14).
1697 It hit users that send through a MTA and have *record* set; in this
1698 combination data would not have reached the MTA.
1699 Interested parties may read the comment in savedeadletter() (part of
1700 the changeset) or the (Fix MTA/*record* descriptor clash..,
1701 2012-11-10) commit log.
1703 Deepest apologies to tortured users from the current maintainer!
1705 - RFC 4155 compatible MBOX file handling has been introduced, and so
1706 S-nail is now on par with (at least) NetBSD Mail in respect to this.
1707 It can be turned off with the new *posix-mbox* variable, which you may
1708 need to use since not all MUAs are capable to dig those MBOX files.
1709 E.g., less cutting-edge (.-) MUAs fail for this:
1711 |From - Thu May 10 20:40:54 2012
1712 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1713 |To: super@duper.com
1718 |From - Thu May 10 20:40:54 2012
1719 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1720 |To: super@duper.com
1723 |>From - Thu May 10 20:40:54 2012
1724 |From - Thu May 10 20:40:54 2012
1726 I'm not completely happy since S-nail *does* still quote those lines,
1727 how rare they may be -- it *does* modify message content. mutt(1)
1728 implements something more clever and that is quoted-printable encoding
1729 of the "F" from "From", when seen at the beginning of a line.
1730 This, when applied to just *any* "^From", will be a non-modifying and
1731 all-compatible solution.
1733 - SEND_MBOX handling has been changed to discard any Content-Length: and
1734 Lines: headers when it rewrites a message by default.
1735 I know that mutt(1) generates them (why, after
1736 http://www.jwz.org/doc/content-length.html?).
1737 Anyway, S-nail does neither use nor manage them, so that any
1738 modification renders those fields invalid, and then it seems best to
1739 discard them anyway.
1740 You may turn the new behaviour off with *keep-content-length*.
1745 The problem was that i really wanted to release on a 25th.
1746 But i have been able to improve S-nail(1) some more, so that this is
1747 possibly the first real release of it. So i'll add only things that
1748 have changed since v13 -- please see below for the complete picture.
1750 - A new CONFIG=CUSTOM make directive was added, and the new user.conf
1751 variables WANT_SCORE and WANT_DOCSTRINGS have been added. It is
1752 possible to create a floating-point free S-nail(1) now.
1755 - If a feature is disabled not even functions stubs should remain now.
1757 - Many places which will work only with local filenames do now actually
1758 check that the target is a local filename.
1760 - Space-separated lists should work again, at a few places at least.
1762 - Tilde commands will be possible, even with -r.
1764 - The *sendmail-progname* has been added after NetBSD 6 dropped the
1765 send-mail entry in mailer.conf(5), which broke S-nail(1). Now users
1768 - When editing messages via ~e or ~v file and pipe addressees will no
1771 - If recipients occur multiple times spread over lists, i.e., To:, Cc:,
1772 Bcc:, then only one occurrence remains, and in the "highest-order"
1775 - The "list" command prints the list alphabetically sorted (somewhat).
1777 - The "help" and "?" commands take an optional argument that shows
1778 a synopsis string for the given command (unless WANT_DOCSTRINGS was
1781 - String allocations are now more efficient. The situation can still be
1782 improved. However, for the first time Berkeley Mail(1) integrates
1783 harmonically into the system allocator, which may madvise(2) unused
1784 memory to the operating system as necessary and/or possible!
1789 Well, a version number 13 is anyway an ugly thing...
1791 commit 4f534bb33b7c911272cc66a0e3a9e47b73ad8deb
1792 Date: 2012-10-25 20:46:07 +0200
1794 FIX MIME quoted-printable encoding (char cast)..
1799 Well, one of the things that have already been started in v13 is
1800 the turn from using "int" when working with 8-bit characters to
1801 "unsigned char" (and as long as we do not support wide
1804 Unfortunately one very important piece of code, that is handling
1805 encoding to quoted-printable, still used integer instead of
1806 unsigned char, which caused an automatic extension cast to take
1807 place, and that resulted in a messed up output.
1813 I want to give prominence to the following people that helped to improve
1814 S-nail(1) during this development cycle, in order of appearance: Martin
1815 Neitzel, Ezequiel Garzón, Björn Persson, Paul Vojta, and, especially,
1816 John Dodson for warm words from beautiful Australia! Many thanks also
1819 After i've officially forked nail(1) aka Heirloom mailx(1) as S-nail(1)
1820 on 2012-09-18 i have been able to work five weeks almost fulltime on
1821 S-nail(1) development. The first three weeks can be characterized as
1822 hectic fireworks here and there, but then it got better and i was able
1823 to work more or less topic-centric. In the meanwhile S-nail(1) is more
1824 than 230 commits away from the Heirloom base--and drifting further apart.
1826 S-nail(1) v13 is the first release of S-nail(1), but it was forked from
1827 Heirloom mailx(1) 12.5 7/5/10 that arose from Berkeley Mail 8. unless
1828 i'm mistaken. What characterizes S-nail(1) v13?
1830 - The build system has been reworked almost completely.
1831 It is possible to fine-tune which features should be present in the
1832 binary and which don't. The name of the binary can be chosen, and
1833 that choice is reflected all through the manual and the template
1834 resource file. The manual is always complete and thus may document
1835 features that are not supported by the actual binary, though.
1836 Please see INSTALL for more.
1838 - Compiler warnings can now be used. Please see the example WARN= flags
1839 in the Makefile, but '-Wall -Wextra -pedantic' should be silent though
1840 certainly insufficient to reflect the complex work of modern compilers.
1842 - The following recipient address list combines some of the major
1843 improvements that have been made:
1845 <addr1@cdröm.de> (bier) , ./file1,
1846 Steffen Smöregäs (Humbabä) <sauer@bäüer.de> (Hummpäa) ,
1847 sabberlot@träbbel.de , (bier2) <a2@bür2.de> ,
1848 a3@b3.de (bier3) , <a4@b4.de> (bier4, und \"bier5\") ,
1849 |cat > pipe1 , (bier 6) <a6@bür6.de> , ./file2 ,
1850 (co\$mm1) abc1@düf.de (cö,bmm,2) (co\"m\"m.3) ,
1851 co\$bmm1 \"c,ömm2\" co\"m\"m.3 <abc2@däf2.de> , |cat > pipe2 ,
1854 That, on a single line, may be given to ":m" or (quoted) on the
1855 command line, or to "~c" or whatever, and it will work as expected
1856 (well, everything else would be a bug..) and result in the following
1857 sendmail(1) invocation:
1860 <-i a2@xn--br2-hoa.de a3@b3.de a4@b4.de a6@xn--br6-hoa.de abc1@xn--df-xka.de abc2@xn--df2-qla.de addr1@xn--cdrm-7qa.de moppel@xn--hppel-jua.org sabberlot@xn--trbbel-cua.de sauer@xn--ber-qla4j.de>
1862 Date: Thu, 25 Oct 2012 17:12:15 +0200
1864 Cc: Steffen =?utf-8?Q?Sm=C3=B6reg=C3=A4s?=
1865 =?utf-8?Q?_(Humbab=C3=A4)?= <sauer@xn--ber-qla4j.de> (=?utf-8?Q?Hummp=C3=A4a?=),
1866 sabberlot@xn--trbbel-cua.de, moppel@xn--hppel-jua.org,
1867 <addr1@xn--cdrm-7qa.de> (bier),
1868 co$bmm1 =?utf-8?Q?"c,=C3=B6mm2"?= co"m"m.3 <abc2@xn--df2-qla.de>,
1869 (co$mm1) abc1@xn--df-xka.de (=?utf-8?Q?c=C3=B6,bmm,2?=) (co"m"m.3),
1870 (bier 6) <a6@xn--br6-hoa.de>, <a4@b4.de> (bier4, und "bier5"),
1871 a3@b3.de (bier3), (bier2) <a2@xn--br2-hoa.de>
1872 Subject: Re: SubjectTest
1874 Content-Type: text/plain; charset=us-ascii
1875 Content-Transfer-Encoding: 7bit
1880 So list parsing has been fixed, IDNA support has been added, and it is
1881 possible to mix pipe and file recipients *and* multiple thereof, and
1882 the result is still correct for *all* of them.
1883 I think this kind of list can be given wherever a user can directly
1884 enter such a list. And i think all that is unique to S-nail(1).
1886 - When writing back edited messages the target MBOX mailbox can no
1887 longer become "corrupted" when the trailing newline was removed during
1888 the edit. Also affected FreeBSD and NetBSD mail(1).
1890 - A security fix for CVE-2011-2895 was applied.
1892 - The generated Message-Id: is now more human-friendly.
1894 - The -h command line option has been dropped. Use "-O -h XY" if your
1895 MTA really supports that.
1897 - The -O and -r command line options no longer enforce a one-shot send
1898 mode, and instead persist for the duration of the entire session.
1900 - Variables set via the -S command line option are now (un)set twice;
1901 immediately and after all the resource files have been loaded.
1903 - Other new or changed options/commands, in order of appearance:
1904 recipients-in-cc, smime-sign-include-certs, quote-fold, stealthmua,
1905 add-file-recipients, write, rfc822-no-body-from_, rfc822-show-all,
1906 mail/Mail, idna-disable, idna-strict-checks, ??
1908 - In the codebase itself an effort to reduce duplicate work and
1909 introduce caching, and to minimize the use of local variables, was
1910 started, but that is long term. A lot of improvements here and there,
1911 too, like using the well MD5 optimization from Wei Dai, Chris Torek's
1912 hash algorithm for hash tables etc.
1914 - Incredibly important: an heraldic animal was found: snailmail.jpg!
1916 The full history can be inspected by issuing the git(1) command
1918 $ git log --reverse s-nail..s-nailv13
1920 A new TODO has been introduced, and it is getting longer and longer.