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.
57 - *attrlist* must now be exactly 13 characters, just as it should
58 be. An error message is printed if not. It was always komisch,
59 but i'd buggified it somewhen in the past. Now fixed.
62 - The NCL WANT_TABEXPAND feature now also works if *newfolders* is
63 set to `maildir'. Yet, if a folder was assumed to be of maildir
64 type, shell globbing would not occur. [part of f5c184c]
66 - The `X-Decoding-Data' S/MIME header field was set to the epoch
67 origin instead of NOW in v14.6.
69 Also the `certsave' command now supports file globbing (i.e.,
70 '~/.certs/' should end up in your $HOME now).
71 [both part of 7e0aec7]
76 + With this release the S-nail codebase has been converted to my usual
77 style of function-code-flow and notation.
79 ?0[]$ git diff --shortstat v14.5.2..HEAD
80 55 files changed, 28065 insertions(+), 25356 deletions(-)
81 ?0[]$ git diff --ignore-all-space --shortstat v14.5.2..HEAD
82 55 files changed, 14664 insertions(+), 11955 deletions(-)
84 Maildir and S/MIME support have been restored, and a MIME bug that
85 could have led to missing data in header display+ has been fixed.
86 Ah, and users of compressed boxes should now feel luckier, too --
87 at least once they've realized that the compress extension is no
88 longer appended automatically, but must be given explicitly.
90 Thus: i hope that all those i-am-new-to-the-codebase bugs i've
91 introduced over a year ago have been found and fixed, and that
92 v14.6 is the true "sweet sixteen" (months of maintainership).
94 ChangeLog (packager-affine)
95 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
97 - If WANT_AMALGAMATION is set, `-pipe' will be added to our CFLAGS
98 (which are only honoured with WANT_AUTOCC, of course). [1330411]
100 - New configuration option: WANT_IMAP_SEARCH, enabled by default.
102 The regular expression support for IMAP-style search expressions has
103 been removed again: it changed the IMAP search semantic in that it
104 couldn't be executed on the server, but only local, and the syntax
105 sucked, too. (And we have a new `?' search expression.) [402b7c6]
107 - CONFIG=MEDIUM and CONFIG=NETSEND now both WANT_REGEX. [dee954e]
109 - The `make test' target should *really* work gracefully, now that usage
110 of the `-#' command line option also sets the folder to be opened to
111 `/dev/null'. (Still no `void' box in sight.) [0119d514]
113 - All published patches may also be found in a new [patches] branch.
118 - Several fixes that saw published patches (with equivalent
119 functionality), and are thus described in NEWS, are included:
121 . s-nail-14.5.2-sort-alt.patch
122 Fixes a hasty commit that introduced string relaxation in a faulty
125 . s-nail-14_5_2-mimeheader.patch
126 Fixes data loss if multiple MIME encoded-words follow each other in
127 header bodies. [c81afce]
129 . s-nail-14_5_2-maildir.patch
130 Effectively restores proper maildir support. [1c2563b, 13f325f]
132 . s-nail-14_5_2-smime.patch
133 Fixes an off-by-one error and, in effect, restores S/MIME sign and
134 encryption etc. support. [e759f75]
136 - The `screen' terminal type is by default recognized as being
137 colour-capable. [e759f75]
139 - With the NCL command line editor and WANT_TABEXPAND hitting <TAB>
140 should now act as if an "implicit asterisk" had been given in case
141 there was no expansion of the original user input; e.g., '? ls <TAB>'
142 may exceed your line limit now ;). [0910a8f]
144 - The S/MIME cipher list was outdated, RFC 5751 requires AES-128 as
145 the default, the RC2 ones are long obsoleted (etc.). Also we now
146 should handle that OpenSSL may not support individual algorithms.
148 Note: we use the option value `des3' for `DES EDE3' from now on!
149 (Maybe see *smime-cipher-user@host* manual entry.)
151 *ssl-method* may now also be assigned the new (default) method `auto'
155 - Messages will now be stored in a set *record* even if only file or
156 pipe addressees were given. [a11935b]
158 - Support for xz(1) compressed mailboxes has been added.
159 (The `Can't canonicalize' warning for compressed boxes had the same
160 cause that made maildir usage impossible, but i don't feel _too_ bad
161 because looking into the code a bit revealed that the *newmail*
162 mechanism never worked for such boxes anyway. And will for a while.)
165 - S-nail now supports nested if..else..endif conditionals. [3c22c04]
167 - The NCL command line editor now locks its' history file when it reads
168 and writes it, so as to protect against concurrent usage. [c3a39ce]
170 - You can now say 'fi%', 'fi&', 'p&10' and `ghost ps '!ps axu'' followed
171 by 'ps|grep nail'. [c3266c6]
173 - Invocation cleanup: usage of -f and -u is mutual, -H and -u is ok, -u
174 in send mode not. [fa0a0aa]
176 - New message specification: `[?name-list]?search-string' will search
177 in locally available messages. If the optional `?name-list' part is
178 given, that specifies the (comma-separated list of) header fields to
179 search in. The special names `body' and `text' can be used to search
180 in message bodies alone and bodies including the headers fields,
181 respectively. Note that "message bodies" unfortunately still means
182 "including headers of attachments and attachments themselves", and
183 until some later time. [61bb460]
185 - The new command line option `-L spec-list' prints a header summary of
186 only those messages that comply to the specification list `spec-list'.
187 If -L and -H are used in combination, no summary is printed at all,
188 but the exit status reports wether `spec-list' would have matched some
189 messages or not. [934e12c]
191 ChangeLog (purely technical)
192 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
194 - Most of the work was changing the code-flow of the entire codebase to
195 my usual style of programming, with a single function entry and
196 a single function exit, including the addition of N(ot) Y(et) D(ead)
197 points of interest, which finally enabled me to get rid of (sic!)
198 using a debugger for S-nail development. Just compile via 'make
199 devel', and in case of a crash you should get a nice backtrace
200 listing. (You use IMAP, do you?)
202 However, because practically every line of code has been touched, this
203 caused some other changes along the way, e.g., the handling of
204 temporary files was changed completely (the formerly used Ftemp()
205 function has been replaced with a new Ftmp(), which handles unlinking
206 itself as necessary etc.), it was detected that the S/MIME support was
207 no longer compliant to any RFC, some resource leaks have been
208 eliminated... It is likely that a change so large introduced some
209 other flees and flaws, however. But it looks good so far.
215 + No official release, only exists as git(1) tag.
217 v14.5.2: fix 4: 2014-02-15 (2014-02-14)
218 ---------------------------------------
220 - s-nail-14_5_2-smime.patch
221 Fix a very stupid off-by-one error that i've introduced
222 in [7bdf330] (OpenBSD 5.3: sigh, address strcpy(),strcat()
224 Until we've changed the used data from string to something
225 line-wise, use strcat(3) again.
227 v14.5.2: fix 3: 2014-02-10
228 --------------------------
230 - s-nail-14_5_2-maildir.patch
231 maildir folders would have caused problems in environments which
232 provide the realpath(3) function: beside a "cannot canonicalize PATH"
233 warning the finally used path would be wrong (`test3' would end up as
234 `test3/test3'), so that any further access would try to use the wrong
235 path. Please read the description of this patch and/or the commit
236 logs of the commits [1c2563b] and [13f325f].
238 v14.5.2: fix 2: 2014-02-05
239 --------------------------
241 - s-nail-14_5_2-mimeheader.patch
244 Subject: ehm, .getElementById("blink") needs <span
245 =?US-ASCII?Q?id=3D"blink">,?= not =?US-ASCII?Q?class=3D"id"?=
247 would yet be displayed without the " not " in between the two encoded
248 words because of faulty "encoded-word-continuation" detection (note
249 the quotation marks). The error path could also have been seen in
250 mail forwarding and in faulty searching etc.
251 This patch is in a row of fixes for my hasty [0f9ad93] from 2013-03-12
252 that already caused the v14.2 minor release (because of [b608c6b] from
253 2013-03-14). Those with mercy may read the commit message of [c81afce].
255 v14.5.2: fix 1: 2014-01-30
256 --------------------------
258 - s-nail-14_5_2-sort.patch
259 Reverses (sort(),thread(): use srelax()!, 2014-01-18, [a9b67e9]),
260 which was a hasty commit of an untested diff that i've added few
263 As a rather careless last-minute change i've added string relaxation
264 to threaded and sorted display, but it's really one more step towards
265 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
267 An alternative, forward-heading patch that keeps string relaxation has
268 been pushed to [master] as [5e75529] and is also available as
269 s-nail-14_5_2-sort-alt.patch.
274 Thanks to Ypnose, Sunil Nimmagadda and Gavin Troy.
275 Gavin Troy *really* deserves special thanks for facing [next]!
276 And i want to dedicate the new coloured message display functionality
277 to John Dodson and Ypnose. Thank you.
278 (And best wishes to beautiful Australia!)
280 ChangeLog (packager-affine)
281 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
283 - All utilities can now be overwritten during configuration so that
284 their values are fixated in the generated makefile (`mk.mk').
285 I.e., talking about MAKE=, STRIP=, awk=, cat=, chmod=, cp=, cmp=,
286 grep=, mkdir=, mv=, tee=.
287 rm= and sed= have to be overwritten from the command line, they're
288 needed before `conf.rc' is read.
289 [5c03347, 072ec65, 39a00ab, 23a1245, ?]
292 - The release tarball is now also available in a xz(1) version.
294 - New configuration option: WANT_COLOUR, by default enabled.
296 - 'make test' should now really work, even if the running user has
297 a mailbox with content. [f223a91]
299 - WANT_AUTOCC is now by default enabled, so as for normal users which
300 don't have the need to embed into a defined packaging environment.
303 - Installation no longer strip(1)s away debug symbols if WANT_DEBUG was
310 - Fixes to some bugs that are present since the first cvs(1) commit of
311 Heirloom mailx(1); includes that *ssl-key-user@host* should now work.
312 [4405a2cc, 9770c26f, 692976b9]
314 - Some off-by-XY fixes, thanks to the debug memory canaries.
315 [19b2b0d, 202506e, 43df6e4]
317 - Fixes for (other) stupidisms (of mine): [1c2161f]
319 This includes true implementation of in-memory history limit for the
320 NCL, which was the final and real solution to a segmentation fault
321 that Gavin Troy had to deal with on [next]. [1089f2b]
324 - For completeness: new command `var-inspect' shows information about
325 all given options. Mostly ment for implementing future tests.
328 - The `pipe' command no longer embeds message information into the
329 data passed through to the command (when *piperaw* is set).
330 [ef5ecc6 (part of topic/colour)]
332 - Simple coloured message (header) display is now possible. Please
333 read the new manual section "Coloured message display", use
334 *colour-disable* to turn it off. (It is enabled by default if it
335 knows the terminal is capable and, if used, the pager can, too. Note
336 we now set LESS=FRXi when starting PAGER and no LESS= is in the
339 Dedicated to John Dodson and Ypnose.
340 [topic/colour, c6e84c7]
342 - The `if', `else', `endif' syntax has been extended.
343 You can now "if 0" (never), "if 1" (always), "if $OPTION" (boolean
344 check for OPTION) and "if $OPTION == 'VALUE'" as well as "if $OPTION
345 != 'VALUE'". Unfortunately it is still not possible to use
346 conditionals inside conditionals. [0fb2ae7]
348 - -# now also sets MBOX=/dev/null. [4be2f1e]
350 - The NCL command line editor now supports cursor keys when the terminal
351 produces xterm(1)-compatible keycodes ('ESC' + '[' + [DACB] for left,
352 up, right and down, respectively). What a thrill, yay!!! [0cbf672]
354 - New (optional) command: `history': show or clear command line history,
355 or select a specific command line from in there.
356 History works a bit different now, and should no longer include
357 command lines which include specific message numbers; more to come.
358 [59c6195, topic/hist2]
360 I plan to join all the history management and use only the one that is
361 part of NCL now, hooking it into editline(3) and readline(3). That
362 would shrink tty.c a bit and also introduce duplicate elimination for
365 - The new ~u and ~U tilde escapes work like ~f and ~m, respectively, but
366 don't include any header lines. Inspired by a patch from
367 Sunil Nimmagadda on openbsd-tech@. [c37b8b3]
369 - The `|' command should work again -- it has stopped working on
370 2013-09-09 when i've accidentally changed the command name from `|' to
374 - As a rather careless last-minute change i've added string relaxation
375 to threaded and sorted display, but it's really one more step towards
376 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
377 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
378 Buffer allocs ever/max simultan. : 14/14
379 Overall alloc count/bytes : 17165/881088
380 Cycle maximums: alloc count/bytes: 16906/876984+0
381 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
382 Buffer allocs ever/max simultan. : 0/0
383 Overall alloc count/bytes : 16515/841816
384 Cycle maximums: alloc count/bytes: 16256/837712+829560
386 ChangeLog (purely technical)
387 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
389 - We now have debug canaries for all memory sources now that [8419d44]
390 added them to the "string dope".
392 - The most work has been done on our value system, which manages the
393 binary and value options, like *folder* etc.
394 It is now based on enumerations, i.e., constant integers, not on
395 strings. This of course only relates to non-dynamic options.
396 Anyway, this saves us key hashing and allows more compact data
397 representation in general (see the new header `okeys.h' for more).
403 ChangeLog (packager-affine)
404 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
406 - The build system *only* uses the automatically detected $CFLAGS and
407 $LDFLAGS if WANT_AUTOCC=1. I.e., even unset or empty $CFLAGS and
408 $LDFLAGS are not touched until then.
409 (We do however still set $CC if that is unset or empty or set to the
410 plain string "cc".) [856625f6]
415 - Fixed segmentation faults / bus errors when setting *nofolder*
416 / *line-editor-cursor-right* to the null string (only with WANT_NCL),
417 respectively. [d1f1a19b, 21e5c285, 9f6ff25d]
419 - *prompt* handling is now really POSIX compliant (thus no prompting
420 occurs not only for 'set noprompt', but also for setting *prompt* to
423 This was indeed a rather large changeset that also introduced the new
424 *prompt* escape character \&, which expands to `?' by default and to
425 `&' if *bsdcompat* is set.
427 Like that we now can simply assign "\& " to *prompt* at program
428 startup, which (a) allows to do 'set noprompt' without error (once)
429 and (b) allows for POSIX compliance in respect to prompt handling
430 without any complicated conditional code, but (c) gives us the
431 opportunity to continue to support BSD prompts.
434 - For completeness: new command: `features'. (Rather useful for being
435 able to implement more tests in the future, and act according to what
436 is really compiled into the tested binary.
438 - The `-#' command line option now also sets *quiet* by itself.
441 - nail.1: a newly introduced empty line in the manual produced error
442 messages on some systems. Fixed.
444 - The return value of the `mimetypes' command has been reversed and
445 should now be fixed. [acf56ac52]
447 - In threaded display the Subject: followup suppression no longer
448 takes into account invisible messages.
449 Also, rudely hack in a messages-already-written-in-this-round counter,
450 so that the followup suppression knows when "the top of the screen" is
451 reached, which (seems to) help(s) against missing subjects up there as
452 well as after a `newmail'. [topic/subject]
454 - Added a WANT_REGEX=1 toggle in `conf.rc'.
455 When we find regular expressions then a new regex-enabled IMAP-style
456 search is available (see the manual for more) [1ec8fe68]
458 ? f (/or subject ^\[S-nail (subject ^\[nail-devel))
459 ? f (/subject ^\[S-nail) (/subject ^\[nail-devel)
460 ? f (/subject "^\\[(S-nail|nail-devel)")
462 I'm looking forward for being able to add another, simplified, syntax.
464 ChangeLog (purely technical)
465 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
467 - The cc-test.sh has seen some tweaks, for easier future extension, and
468 for adding a test for [d1f1a19]. [several, mentioned: 21e5c285]
470 - On systems without a real wordexp(3) implementations deadlocks could
471 occur because we sometimes hold_all_sigs() to avoid longjmp(3)s away
472 (and will do so for quite some time, still), and that resulted in the
473 SIGCHLD that reported the exit of the started subshell to be blocked,
474 too (e.g., after '? *.h<Tab>': endless hang). Fixed.
479 Many thanks: Gaetan Bisson, William Yodlowsky, Gavin Troy,
480 Thomas (wasd AT gmx DOT net), Ypnose.
481 And Gavin Troy definetely deserves a very special credit.
482 But thank you all, and very much indeed!
484 ChangeLog (packager-affine)
485 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
487 - The `test' make target has been fixed. [f0991e14]
490 - It is possible to gain a different kind of make(1) verbosity by
491 using a VERBOSE=1 command line argument (this knob is not taken into
492 account when deciding wether a rebuild is needed). [498e4ad0]
495 - On Crux 3 Linux and OpenBSD the readline(3) and editline(3),
496 respectively, libraries will now be found when desired. [a7d1aa78]
499 - WANT_LINE_EDITOR has been renamed to WANT_NCL, *plus*.
500 So now there are WANT_READLINE, WANT_EDITLINE and WANT_NLC, each of
501 them can be set individually, and they are tested in the shown order.
502 Also, WANT_TABEXPAND and WANT_HISTORY have been introduced and can be
503 used to fine-tune functionality. [ae4e01e1, b2635feb, 9742bf40]
505 (While here, i've fixed WANT_TABEXPAND code so that it is more
506 sensitive to line excess; on Linux etc., where MAX_INPUT is 255,
507 strange behaviour could be seen because we didn't take into account
508 the length of the prompt at all. The NCL is assumed to have only
509 one remaining, but unfixable problem: backspace often is incapable
510 to cross visual line boundaries; use ^A/^E + ^L, then. [e832c04a]
512 Also, cursor (now ^B and ^F) and history movement (now ^P and ^N) of
513 the NCL have been changed. [d7d928da])
515 - WANT_QUOTE_FOLD is now enabled by default. And WANT_ASSERTS has been
516 renamed to WANT_DEBUG. [1e10da1f]
518 - The build system has seen yet another overhaul in general. CC, CFLAGS
519 and LDFLAGS plus are now tracked and changes will force rebuilds.
520 The new WANT_AUTOCC option can be used to let the build system figure
521 out a compiler and choose known-to-work flags. Use the new ADDCFLAGS=
522 and ADDLDFLAGS= command line arguments to add your specific flags on
523 top of those -- the final CFLAGS etc. are what is change-tracked.
525 This rather massive internal rework revealed that old Bourne shells
526 were yet not supported by the new build system, and so did testing
527 that UnixWare installation was yet impossible due to tool
528 incompatibility. [75c4b74e]
530 - The new WANT_AMALGAMATION option will force compilation of all the
531 sources in a single compilation unit. This requires a rather large
532 amount of memory, but may produce a more compact, maybe more optimized
533 binary. (Implementing this revealed quite some bugs which could
534 therefore be fixed.) [topic/amalgam]
536 - `nail.rc' has been pimped a bit (mostly comments, but
537 *mime-counter-evidence* is now always set). [e3094ba7]
539 That changeset was however buggy. [f3dcb46]
542 - We no longer use install(1) for `install'ation make rules. [80b02cd9]
547 - Even '$ s-nail & fg $!' will now work with the NCL. [2a8b5c55]
549 - Several off-by-one (off-by-two) fixes. [32ce9836, 71e6d013, f139dc36]
552 - Setting *noprompt* now prevents prompting, as per POSIX. [ecefaf63]
554 - *prompt*: new \$ (exit status of last command) and \@ (name of
555 currently active mailbox) escape sequences. [6f652046]
557 - One may now omit the space in '? unc' ('?unc') [05fcb383]
559 - New commands: `ghost' and `unghost' define command aliases (since
560 `alias' is taken for a different purpose) [topic/commands]
565 - There is now a pseudo account `null' (case-insensitive).
566 Also a new `localopts' command exists; when used from within an
567 `account' block, options changed will be reverted back to its former
568 value when the account is left (e.g. by switching to `null'):
571 alternates sdaoden@users.sf.net sdaoden@users.sourceforge.net \
572 sdaoden@googlemail.com sdaoden@gmail.com
573 set Sign="\n--steffen\nForza Figa!" sign="\n--steffen"
574 set smtp=smtp.gmail.com smtp-auth=plain smtp-use-starttls
580 set from="Steffen \"Daode\" Nurpmeso <sdaoden@gmail.com>"
585 set from="Steffen \"Daode\" Nurpmeso <sdaoden@users.sf.net>"
593 neither of *Sign*, *sign*, *smtp** nor *from* should be set.
594 Please see the manual for more.
595 TODO - neither command-ghosts nor alternates etc. are yet tracked
596 TODO - we should have a boolify() so as to say 'localopts yes' etc.
599 - New command: `cwd' (print current working directory).
600 Also fixing the `chdir' return value. [eff4397c]
602 - The *ssl-method* now allows explicit setting of 'tls.1.1' and
603 'tls1.2' values. [c66b4196]
605 - When sending to display, be aware that filenames in MIME parts may of
606 course be MIME-encoded! [1454be03]
608 - *hostname* is now honoured even if *smtp* is not set. (We always
609 supported *from*, so why not *hostname*?)
611 - The `-u user' option now acts identically to setting the $USER
612 environment variable and both now tend to mean something like
613 "impersonate as user in some aspects". Note that we have always used
614 the latter in one or the other way, and `-u user' always ment more
615 than just "open mailbox of user", so i think this change sharpens the
616 edge in the right direction. [09632731]
618 - Filename argument quoting has been tweaked for (some) function(s which
619 take a filename argument last). The following snippet as reported by
620 Gavin Troy should work now: [2bb9b80e]
622 ? mv +inbox.Junk\ Mail
624 - The GNU implementation of wordexp(3) is also (i've added a workaround
625 for the very same bug for Mac OS X in S-nail v14.3 [63273772]) buggy,
626 which causes segmentation faults when expansions failed (`fi &VOID').
630 - The `fi' command no longer uses the (possibly truncated) display
631 version of a filename, but the full path. [5cd85b07]
633 ChangeLog (purely technical)
634 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
636 - Large rework of internal structure: bundle inclusion of most of the
637 external and the content of most of the internal #include files in the
638 new nail.h. If that would have been done very first bugs like the
639 infamous MAXPATHLEN bug as reported by Paul Vojta (see v14.4.2) would
640 never have occurred. [21f3155b]
642 - Support for -fstrict-overflow cc(1) flags. [topic/strict-overflow]
644 - Fixed the quotation filter which yet allocated memory even if not
647 - String relaxation reduces memory pressure rather drastically when
648 working with many (especially MIME) mails at a time, e.g., when
649 writing a modified mailbox. Before all messages of a mailbox had to
650 be worked without releasing any memory in between, now we give back
651 memory (to our pool, not the system) after each and every message.
654 - The other memory source now uses bound canaries, which also found some
657 - We now use the EL_PROMPT_ESC editline(3) mode for prompting, which
658 should offer the possibility to use coloured prompts etc. with
659 (even those) editline(3) (versions which do offer it -- older versions
660 should just do fine by themselves).
661 S-nail uses the special trigger control character \1. [ea30d818]
664 Note however that all tested editline(3) versions are buggy and
665 either don't get it right (`\1COLOR-ON\1stuff\1COLOR-OFF\1') or are
666 incapable of proper repainting (`\1COLOR-ONstuffCOLOR-OFF\1').
668 - We now use the MD5 digest code from the OpenSSL library if that is
674 Many thanks: Gaetan Bisson, Stephen Isard, Jérémie Courrèges-Anglas,
675 William Yodlowsky, and Adam Sjøgren from GMANE.org!
677 ChangeLog (packager-affine)
678 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
680 - The packager-install: target has been fixed. [a8c1b0b]
681 (Gaetan Bisson and William Yodlowsky)
683 - As suggested by Gaetan Bisson the several build system tasks are now
684 individually addressable, i.e., 'make [OPTIONS] config', 'make build',
685 'make test', 'make packager-install'); nothing changes unless you want
686 to, in which case: please see INSTALL. [4d3b799]
688 The new target 'test' will call cc-test.sh with its new --check-only
689 option which will only perform the (too few) function tests on the
691 And cc-test.sh will no longer create output files, but simply echoes
692 to STDOUT and STDERR. [629e1ee, 786f219]
695 - The default configuration file now sets *bsdannounce* and *bsdflags*,
696 all in one line, as suggested by William Yodlowsky.
697 (If *header* is disabled, *bsdannounce* is ignored, but *header* must
698 be enabled by default according to POSIX, and *bsdannounce* is just
699 the same as *header*, but for the folder-switched event. Thus setting
700 *bsdannounce* is the more sane default, imho.) [6161f10]
703 - Announcement messages are now tagged '[ANNOUNCE]'. [26e1b35]
704 (Tagging suggested by Stephen Isard and Jérémie Courrèges-Anglas)
706 - The manual NAME now includes the version (but it's somewhat ugly).
712 - When switching folders when in compose mode, message attachments
713 become invalid. For v14.4.5, at least warn when this happens.
716 - When reading multipart/alternative messages which do not contain
717 a text/plain part, the (most likely HTML) part is not displayed (even
718 if S-nail is configured to display HTML). The reason is a bug i've
719 introduced with [0d43a999] (Change "Part X:" display message..,
720 2012-12-20). (Note that the committed fix i've posted to the list was
721 not correct either and has been fixed itself.) [225c02b, ecfa149]
726 Thanked, Gavin Troy, Gaetan Bisson.
728 - Fix output buffer confusion that would have occurred when parts of
729 a multipart mail had a pipe command set. Longer story in [e75d16dd].
732 - The makefile now supports a `packager-install' target that bypasses
733 the reevaluation of the configuration (after checking that there is
734 one) and directly steps ahead to the install process.
737 - Notes in INSTALL that CFLAGS and LDFLAGS need to be overwritten from
738 within (conf.rc or) the command line.
744 I convey special thanks to Karol Błażewicz and Gaetan Bisson.
746 - The new build system didn't allow to overwrite CFLAGS= when used in
747 conjunction with GNU make(1). To make a long story short, removing
748 a `.POSIX:' directive from the makefile fixed the problem. Luckily.
751 - More INSTALL notes for UnixWare 7.1.4, which suffers from the same
752 problem: here the fix is to use the -e option of make(1).
754 - Karol Błażewicz reported a segmentation violation he got when using an
755 Arch Linux S-nail test package, and Gaetan Bisson informed me about
756 that. The problem was that we didn't assign the resulting default
757 address (which gets used when *from* is not set) to the result which
758 gets used, effectively resulting in a NULL dereference. [cfd60479]
763 Many thanks to Paul Vojta.
765 - On GNU/Linux there is no MAXPATHLEN constant defined by default, as
766 this is a non-standard legacy constant. Mozilla ran into this some
767 time ago, though a bit different [1]. It made it easier for S-nail.
769 [1] <https://bugzilla.mozilla.org/show_bug.cgi?id=412610>
771 We could include `sys/limits.h' to get at MAXPATHLEN, there it is
772 defined to be PATH_MAX, but let's just include the standard `limits.h'
773 and ensure MAXPATHLEN ends up >= PATH_MAX. With this condition being
774 true even FORTIFYd sources won't bail with reported buffer overflows
775 because realpath(3) expects a buffer of PATH_MAX bytes. [bee5e57c]
778 - With the builtin LINE_EDITOR, ensure proper interaction with GNU
779 rlogind(8), which is alone in its quest to set the ISTRIP termios(4)
782 - Bugfix a codepath that would have prevented compilation when
783 HAVE_ICONV is not set.
784 While there, allow to unselect message attachments when using the `~@'
785 tilde command interactively, which i mysteriously had forgotten when
786 allowing selection of 'em. (oops?) [4f58ffea]
788 - It's now easier for packagers to get at debug-enabled CFLAGS; simply
789 use WANT_ASSERTS=1 (should not be enabled in shipouts, please).
792 - Fixed a terrible bug that i've introduced in november 2012, that would
793 have corrupted MBOX files when using the `resend' command. (The
794 so-called "From_ line" would have been quoted to ">From_ line" instead
795 of simply being stripped.) [19d449e2]
797 - Fixed a SIGSEGV for the builtin LINE_EDITOR, that would have occurred
798 if a history traversal (^B or ^F) would have been continued by
799 a reverse history completion (^R).
800 While there, avoid some multiple-beeps-in-a-row that yet occurred due
801 to code reuse, and document that ^G etc. reset the multibyte state
804 Also, the expand-on-tab code could have excessed line input maximums,
805 e.g., after `? /usr/bin/*<Tab>'. This was of course known, but
806 i wanted to keep it because all tested (modern) terminals "mess up but
807 won't break", and thus made it possible to use the data, even if it's
808 visual representation was messed up. The real solution will be much,
809 *much* more complicated, i.e., show possible *completions*, page-wise,
810 etc., i.e., just like is known by tab *completion*. This will need
811 far more time because it doesn't make sense to embed such complicated
812 code into the current bed.
813 Now i've chosen to simply don't display excess, but replace the
814 content with a message that says that there was excess. It simply
815 looks better. [0320c8ba]
817 - I've changed the use of `[?]' as a replacement sequence for invalid
818 / non-displayable characters to `?' (again). There are still code
819 paths (from the original codebase) which use the real Unicode
820 replacement character instead, so our display is still not unique.
821 On the long term the codepath can anticipate in all levels wether
822 use of Unicode is possible, so that, then, we will be unique again,
823 using either only `?' or the Unicode replacement character. [faf6380]
825 - I've anticipated in v15.0 and implemented *quote-fold* as a stream
826 filter. It is now multibyte safe and takes into account the visual
827 width of characters, i.e., ideographs etc. It is working almost as
828 good as an algorithm can work that looks at data linewise, but is yet
829 experimental and incomplete in that it will break lines even if only
830 whitespace or a backslash escape follows. It is code that is only
831 a few hours old, which is why it is not enabled by default. [
838 - Fix some harmless stylos and typos in the manual and `conf.rc'.
841 - Ensure *complete* proper cleanup on signal-caused configuration run
844 - Bugfix: reenable empty configuration variable overrides, as in
846 $ make install SID= NAIL=mailx ...
849 - Bugfix: rename the `conf.rc' variables SHELL, LISTER and PAGER because
850 they clash with the POSIX standard variables of the same names, which
851 hurts now that the configuration is run through the shell itself.
852 The configuration names are now XSHELL, XLISTER and XPAGER (ouch).
855 - nail.rc: comment out some non-portable S-nail(1) specifics, for those
856 who install this file as mailx.rc or so, somewhere. [3f14b01]
858 - From now on S-nail will use simple version tags, as, e.g., `14.4.1',
859 i.e., no more `s-nail-14.4.1'. [a75437d, 183d59c] (Jürgen Daubert)
861 Also move UAGENT out of `version.h' [f7be5be]
863 Uh! v14.4 must have originated in a bad dream; good it's vanished.
868 Thanks to the entire vivid and virile S-nail(1) user community is
869 proper, especially Stephen Isard, Gavin Troy, Martin Neitzel.
870 Not to forget Ryan Kavanagh and Ayan George.
872 Note this time the changes are in reverse order, i.e., oldest first.
877 15fbe09 ^bf9173f 'topic/varmac-unite'
878 Simplification and unification of variable and macro handling
879 40f6f58 ^15fbe09 'topic/cledit1'
880 Command line editor; new manual section `Line editor'
881 ad28a32 ^40f6f58 'topic/termsize'
882 Honour POSIX mailx(1) and respect $COLUMNS and $LINES on startup
883 dc3cd49 ^a446fd8 'topic/qf'
885 b8738f7 ^0651fd0 'topic/spam1'
886 Interaction with SpamAssassin; new manual section `Handling spam'
887 5419d6f ^b8738f7 'topic/make1'
888 Reworked build system; please read `INSTALL' and `conf.rc'
889 9ab4d6b ^5419d6f 'topic/list1'
890 Slightly tweaked message thread display, fix `:u :r' to mean it
895 - The default PAGER is now more(1). (But read on.)
897 - The `echo' command is now compliant, and fully supports XSI.
899 - The `group' and `ungroup' command aliases have been removed, they are
900 `alias' and `unalias'.
902 - We now have the capability of line editing and history.
903 One may choose from not less than three different implementations:
904 a builtin editor as well as possible linkage against BSD editline(3)
905 and also a GNU readline(3) compatible layer.
906 Please read the new manual section `Line editor'.
908 Input is now compliant in that an interactive line may be continued
909 after escaping the newline character with a backslash.
910 [topic/cledit1] (all of them)
912 The *prompt* variable may now contain shell escapes, just like the
913 `echo' command. [0938d8a]
914 As a special extension the new \? escape, when used within *prompt*,
915 will expand to the exit status of the last command. [41076d2]
917 - The POSIX standard environment variables $COLUMNS and $LINES are now
918 honoured upon startup. [topic/termsize]
920 - The `help' / `?' commands now support abbreviation, i.e.,
921 ``$ ? unc'' should now find `uncollapse'. [7b86195]
923 - The `~' abbreviation that has been introduced as an alias for `call'
924 is now a real command, not a magic shortcut. [9987289]
926 - The new variable *quote-as-attachment* can be used to additionally
927 embed the quoted message as a `message/rfc822' MIME attachment.
930 - The compose-mode command `~@' will now attach messages from the
931 current mailbox if given a filename of the style `#NUMBER'.
932 Please read the corresponding manual section `Tilde escapes', though.
934 - The `WANT_JUNK' and `WANT_SCORE', as well as Gunnar Ritters junk mail
935 management have been removed.
937 Instead S-nail(1) can now support interaction with SpamAssassin, but
938 sofar only via the spamc(1) / spamd(1) client / server pair of
939 programs that ships as part of SpamAssassin. The new configuration
940 directive `WANT_SPAM' controls wether this feature is desired.
942 Please read the new manual section `Handling spam'.
943 [topic/spam1] (Martin Neitzel)
945 (S-nail(1) is now *definitely* floating-point free.)
947 - The configuration and make system have been overhauled / reorganized.
948 The configuration is now in `conf.rc', also contains directives like
949 `PREFIX' etc, and is always read in. However, only those directives
950 which are not yet set (via environment or command line overwrites) are
951 incorporated into the set of configuration options. Therefore
956 will now build S-nail(1) twice, because of the changed configuration.
958 Note that `WANT_GSSAPI' is now by default disabled, which shrunk
959 a freshly started s-nail image by more than 30 percent.
961 We're not finished yet in that there is no dependency graph etc.
962 Please do read `INSTALL' and `conf.rc'.
965 - Message selection has been slightly bugfixed in that `:u :r' really
966 means `:u' AND `:r'. Compared to NetBSD Mail(1) it's still a shame.
968 Threaded message display has been slightly changed in that within
969 a thread identical Subject: lines are not repeated. It may not be
970 perfect yet due to the general list / thread state. [topic/list1]
972 - If, upon startup, the environment variable `NAIL_NO_SYSTEM_RC' is set,
973 then the system wide initialization file isn't read, just as if the
974 `-n' option had been given. [1b31535]
976 - It is now possible to use CTRL-C during connection hangs. (But in
977 general error recovery capabilities of the socket related
978 infrastructure is non-existent, practically speaking.) [45a9f36]
980 - *quote-fold* has been temporarily disabled, as it is not multibyte
983 No review for v14.4. And today is Friday, the 13th. Ouuuh!
988 I should *maybe* should have and want to give prominence to
989 Martin Neitzel for this, i maybe have misunderstood.
991 - Bugfix *synchronous* *pipe-** execution..
993 Well, unfortunately yet another newly introduced bug slept in
994 S-nail v14.3[.1] -- [a8d724b3, Add @ and @& shell command prefixes
995 for pipe-MIMETYPE, 2013-05-03] falsely changed the waiting state
996 for subprocesses, as has shown up by a HTML-only mail on the
998 'Seems i'm collecting one line fixes in this codebase; this needs
999 to change in the future.
1004 I want to give prominence to Juergen Daubert (jue AT jue DOT li), who
1005 reported that i've broken plain-old unfancy send mode in 14.3.
1007 + Ok, i'll hope we're out of new errors for the v14.3 series with that.
1009 - New variable: *batch-exit-on-error*.
1010 Only works if the new -# command line option has been given, and will
1011 check the "current" exit status whenever one operation completes
1012 (S-nail returns to the command prompt).
1013 If the exit status implies error (e.g., sending the last message
1014 failed) then we exit forcefully with that error status. (The normal
1015 behaviour is that the status is reset when the command loop ticks.)
1018 - While here again, i've added the new -# command line option.
1019 This is the first step to implement a reliable batch mode;
1020 unfortunately it still selects the users system mailbox on startup,
1021 because we simply cannot go to "no" mailbox for quite some time -- at
1022 some future time we will be able to go to some VOID thing, and then
1023 this will end up as a rather efficient batch mode.
1024 For now it sets *dot*, *emptystart*, *noheader* and *sendwait*, and
1025 also implies the -~ command line option. [7549569]
1028 printf "m ${MBOX}\n~s subject1\nE-Mail Körper 1\n.\n" &&
1029 printf "m ${MBOX}\n~s subject2\nEmail body 2\n.\n" &&
1031 ) | MAILRC=/dev/null "${NAIL}" -n -#
1033 - Also, -N set *header* instead of *noheader*. [7b4a13f6]
1036 - Plain old unfancy invocations like
1039 $ echo bla|s-nail ./FILE1
1041 had been broken (by [522cb3ec]). [260e19d]
1047 Thanks to Gavin Troy (gavtroy AT gmail DOT com) who inspired the @ and
1048 @& pipe-command prefixes.
1053 - S-nail has been registered at Coverity Scan, and the third build
1054 (after topic branches *coverity-444* and *coverity-444.2*) produced no
1055 more errors. (<http://scan2.coverity.com/projects/444>.)
1056 (Then i used POP3 and IMAP and fixed some SIGSEGV. ;) Still didn't
1057 look at S/MIME, Maildir, caches etc... o()
1059 - S-nail v14.3 doesn't produce any spurious linker warnings on
1060 OpenBSD 5.3; all (correct!) use cases of strcpy() and strcat() have
1061 been replaced. [7bdf330, 2c8d7cb]
1063 - This is the first release with a (though very short) review -- i'm
1064 slowly getting comfortable with the code. (But i'm too stupid to
1065 perform reviews on patches, 'always did reviews on C++/Perl/xy
1066 classes. Aaah, how beautiful ... objects.)
1071 - It is now possible to "call" macros without using the `call' command
1072 by prefixing them with a tilde, as in
1081 - Added the *pop3-bulk-load* option.
1082 Yes, there are mailing lists etc. which use plain text email, and,
1083 there, headers are often more data than the body, so it doesn't make
1084 sense to download the headers twice (unfortunately POP3 doesn't
1085 support a BODY command; if only it would support a RETRDELE command..)
1088 And yep, from this changeset on i personally use S-nail even over the
1089 network, no longer my stale and incomplete S-Postman. And i can tell
1090 you, this damn thing is so silent, i always set *verbose* not to go
1091 grazy ... but .. i hate to say it .. the healing will take time.
1093 - POP3 will now try to use APOP authentication automatically; thus the
1094 *use-apop* stuff has been replaced by *pop3-no-apop* options (just in
1095 case there are POP3 servers which advertise they support APOP but in
1096 fact fail to do so; anyone?) [6c3c5575]
1098 - Some IMAP segmentation violations have been fixed:
1100 ? fi imaps://user1@localhost
1101 Password:Interrupt <- CNTRL-C
1102 ? set imap-auth=cram-md5 <- hey, 'forgot to set correct auth
1103 ? fi imaps://user1@localhost
1104 IMAP write error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown
1107 And also, when *folder* was set to an IMAP account but hasn't been
1108 opened yet, and no IMAP account ever has been opened, a string
1109 comparison against a NULL pointer yet caused a SIGSEGV, too.
1112 - `set folder=' now tolerates `%:' and expands PROTOs stuff etc.:
1114 ? short xp %:imaps://user1@localhost
1117 Pure convenience so that it doesn't need to be typed twice (still no
1118 completion in sight...). Note that setting *folder* to a POP3 box
1119 will now be actively rejected. [b12b17f5]
1121 NOTE: while implementing this i've detected another dead-end
1122 miscondition in S-nail -- you really should ensure that your target
1123 folder/box is connected before you leave your current POP3/network
1124 based folder, if there is data to be moved to the target (i.e.,
1125 mbox). This problem will persist for a long time due to the way the
1126 entire codebase functions; i hope i can find a short/mid-term
1127 solution, but the real healing will take years. The mentioned
1128 solution would at least make S-nail interruptable, currently we get
1129 stuck and interrupts are blocked...
1131 - If you're using S-nail on Mac OS X and have seen some segmentation
1132 faults when expanding shell stuff then you may be pleased to hear that
1133 S-nail now works around an Apple bug. [63273772]
1135 - The builtin mime.types have been corrected and a lot of new ones have
1136 been added. New data from
1137 <http://svn.apache.org/viewvc/tika/trunk/tika-core/src/main/resources/\
1138 org/apache/tika/mime/tika-mimetypes.xml>, thanks! [8072fcb6]
1140 - BEWARE: handling of command line arguments has changed a bit!
1142 1. The -D, -d, -E, -i, -N and -v command line options are now
1143 implemented by means of setting the respective option, as via -S.
1144 (This means that from now on resource files can only *temporarily*
1145 overwrite command line arguments.)
1147 2. The -I and -T command line arguments have been dropped.
1148 It seems Gunnar Ritter stopped developing nail/Heirloom mailx once he
1149 started implementing Newsreader functionality. It'll take a long time
1150 until we get there, so for now drop all the Newsreader stuff.
1152 3. Handling of -r has been changed. E.g.:
1154 s-nail -A test -Snoeditalong -r 'La mort est <fem@me>' -d
1155 ? set from=bummer@m1.com
1159 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t1"
1160 ? set from=bummer@m2.com
1163 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t2"
1167 s-nail -A test -Snoeditalong -r '' -d
1168 ? set from=bummer@m1.com
1172 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m1.com" "t1"
1173 ? set from=bummer@m2.com
1176 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m2.com" "t2"
1178 [*main-fun-cleanup* topic branch]
1180 - *smime-sign-include-certs-** stuff works again, oops.. [9a8597c6]
1182 - A whole lot of smallest and small fixes due to registration at
1183 Coverity Scan, as project 444. Error handling in S-nail is ridiculous.
1184 [*coverity-444* and *coverity-444.2* topic branches. The sheer number
1185 of fixes was the reason to sit down and go for unplanned S-nail v14.3]
1187 - *idna-strict-checks* has been dropped. It's silly to have in a MUA,
1188 especially given that GNU LibIDN doesn't ship with a lot of rules.
1189 We were able to drop quite some code (and a use-after-free, too :().
1192 - The ~p tilde command displays attachments more verbose.
1193 Until the big big MIME and send layer rewrite :) this is intermediate
1194 since until then we do not really know neither MIME type nor charset
1195 of an attachment at the time this is displayed (for sure). Yet
1196 i think it's nicer to show what we have than keep it the way it was.
1199 - @ and @& shell command prefixes have been added for the pipe-MIMETYPE
1200 mechanism. The former suppresses filters if multiple messages are
1201 displayed at once, the latter adds asynchronous program execution on
1202 top of that. E.g., to display PDF documents, but only if you
1203 *explicitly* address the message *alone and by itself*, and without
1204 blocking S-nail and the $PAGER, do:
1206 set pipe-application/pdf="@&cat >"${TMPDIR}"/s-nail${$}.pdf;\
1207 mupdf "${TMPDIR}"/s-nail${$}.pdf; rm "${TMPDIR}"/s-nail${$}.pdf"
1209 (Inspired by Gavin Troy.) [a8d724b3]
1211 Note: most of that had been posted to nail-devel@ already, but it was
1212 tweaked ([251b636]) so that you now *really* have to say `p MSGNO' to
1215 - The NETLESS CONFIG= has been removed; it is almost identical to
1216 MINIMAL now (i.e., without WANT_JUNK and WANT_SCORE).
1218 - WANT_JUNK and WANT_SCORE have been disabled by default.
1219 They don't seem to be too useful; i hope i can implement
1220 a SpamAssassin hook for (downloaded) mail messages for v14.4.
1221 If so, expect these two "modules" to become removed completely.
1226 Another unplanned (minor) bugfix release after Gavin Troy (gavtroy AT
1227 gmail DOT com) pointed out that MIME CTE decoding was broken, who
1228 i therefore want to give a lot of prominence right here.
1230 - Fix MIME content decoding which has been broken by [01c0e135].
1237 An unplanned (minor) bugfix release after i've found two bugs today and
1238 heard from Jérémie Courrèges-Anglas (jca+nail AT wxcvbn DOT org) that
1239 there exists a S-nail OpenBSD package.
1241 I want to give prominence to the following people that helped to
1242 improve S-nail(1) during this development cycle, in order of
1243 appearance: Dirk Peters (peters AT schwertfisch DOT de).
1245 Thank you very much, and best from Germany!
1247 - Some warnings of newer clang(1) versions were silenced, including yet
1248 another alloca(3) problem (see *memtracer* topic branch in v14.0
1251 - Tweaking the MIME boundary detection left a little hole that could
1252 cause boundaries not to be detected, as has been shown by a Microsoft
1253 Word generated mail on the ICU list. [11e5fb5b]
1255 - A format string could overflow bounds if unrealistic
1256 (18446744073709551615) line numbers or message sizes would have been
1257 produced. [faa65c40]
1259 - An algorithmic error could cause overlong lines which wrapped around
1260 to the next display line. [ade52660]
1263 v14.2, 2013-03-15 [v14.1, 2013-03-12]
1264 -------------------------------------
1266 I want to give prominence to the following people that helped to
1267 improve S-nail(1) during this development cycle, in order of
1268 appearance: Martin Neitzel, Christos Zoulas, Stephen Isard, jgw@txo.org
1271 Thank you very much, and best from Germany!
1273 + v14.2 differs from v14.1 only by one commit, one that fixes
1274 (mime_fromhdr(): partial rewrite using n_iconv_str(), 2013-03-12),
1275 which i hastily implemented just hours before the release of v14.1,
1276 and simply shouldn't have made it (into there).
1277 The v14.1 tarball has been removed from the server.
1279 - A fix for the quoted-printable codec: "message truncation" occurred
1280 when a mail maliciously used a soft linebreak to escape the linebreak
1281 of a completely empty line.
1282 (That resulted in 0 written and 0 leftover bytes, a condition that was
1283 declared erroneous back in november 2012 when i started handling I/O
1286 - The "folders" command will work again when given an argument.
1287 A fault of mine introduced in (cmd1.c: expand() may fail, 2012-10-23).
1289 - The Base64 codec has been touched again, and we are finally capable to
1290 perform sequential decoding; this was targeted for the MIME/send layer
1291 rewrite, but it actually was possible today.
1292 The result as seen in ps(1), running on the Base64 encoded HTML5
1293 standard (4622545 bytes HTML, with a NUL appended to force Base64
1294 encoding, resulting in a 6244793 bytes email):
1296 7420 s006 S+ 2:22pm 0:10.65 plain-nail -f HTML5
1297 1440 s006 S+ 2:23pm 0:00.36 ./s-nail -f HTML5
1299 (So the only thing that is left for a good throughput is sequential
1300 decoding of quoted-printable encoded parts that maliciously use soft
1301 linebreaks to convert an entire part to a single line. And i've seen
1302 that from Apple Mail.)
1304 - New option: *mime-allow-text-controls* (rather long manual entry).
1306 - *smtp-auth-password-user@host* and *smtp-auth-user-user@host* will
1308 (Reported by jgw@txo.org in November 2011, fixed by Gavin Troy in
1311 - Most *headline* formats now do support the '-' left-alignment flag.
1312 Note that you most likely have to change your *headline* accordingly.
1313 (The still missing %n format is one reason why there will be v14.2.)
1315 - *datefield* and *datefield-markout-older* can now be set to
1316 strftime(3) format strings (except %n).
1317 (From Stephen Isard's wishlist.)
1319 - A possible SEGV has been found and also fixed by Stephen Isard.
1320 (The "legendary" cross-world stereo fix!)
1322 - Wow! S-nail will finally compile on GNU based Linux systems like
1323 Slackware 14 etc. (Found while hunting bug reported by
1326 - New option: *datefield-markout-older* can be used to choose
1327 a different date display for mails that are older than six months,
1328 in equal spirit to what POSIX describes for the -l option of the ls(1)
1329 command (Stephen Isard).
1331 - (Exotic) Years are (would) now (be) interpreted correctly according to
1334 - CRAM-MD5 usage has been fixed.
1336 - *folder* updates are now tracked when set, and we will show the
1337 realpath(3) name of it, showing PREFIX..SUFFIX if that wouldn't fit on
1339 Tracking updates made it also possible to perform other more expensive
1340 tasks when setting *folder*, so that it is now possible to do
1346 et cetera (both ideas by Christos Zoulas).
1348 - Bugfix for the ~@ tilde-escape in non-interactive mode.
1349 (readtty(): quick shot: work in pipelines (on non-TTY).., 2013-01-25)
1350 introduced the possibility to "read data from the terminal" (STDIN
1351 that is) in non-interactive mode.
1352 The manual documents that attachment input must be terminated with an
1353 empty line, but if that had been omitted, as in the example below, we
1354 would have yet entered an endless loop.
1356 $ cat <<_EOT | /s-nail -~ -s boom ./OUT
1362 - Alias expansion will now be performed for members of Reply-To: fields
1365 - Decoding quoted-printable will now be more relaxed.
1366 (Even though the standard says that users should be given a hint when
1367 input is not absolutely clean; a possible warning will be added later,
1368 when we have an error message ring.)
1370 - New option: *mimetypes-load-control* can be used to control which of
1371 the mime.types resources will be loaded.
1373 - The builtin default mime.types have been extended a bit.
1378 I want to give prominence to the following people that helped to
1379 improve S-nail(1) during this development cycle, in order of
1380 appearance: John Dodson, Gianluca Ramunno, and Anon Ymous from the
1386 - Encoding defaults to *quoted-printable* not *8bit*.
1387 This has no technical background except that i think it's the better
1390 - Small progress for the "getting stuck due to the current folder
1391 becomes inaccessible due to whatever reasons" problem.
1392 (schdir(): realpath() local files before leaving CWD.., 2013-01-08)
1394 - The names of temporary files have changed. Whereas not all uses of
1395 temporary files already use really meaningful names, it has yet become
1396 possible to use the pattern "*mail-*"; or, to be compatible with
1397 NetBSD Mail(1) in one go, "*mail*". (E.g., in my ~/.vimrc you'd read:
1398 :au BufRead,BufNewFile *mutt*,*mail* setl fenc= | setf mail
1399 [the *mutt* is a leftover from times when i've used MUAs that suck].)
1404 - The Quoted-Printable MIME handling has been rewritten completely.
1405 We now correctly encode files with the MS-DOS newline sequence (CRLF).
1406 (Part of the *mime-cte* topic branch.)
1408 S-nail(1) continues to be able to handle text messages and text
1409 attachments without a trailing newline, but because these
1410 Content-Transfer-Encoding related things are now handled by the C-T-E
1411 layer instead of by sendout.c a text message body that comes in as
1412 part of a complete message via the -t command line option will loose
1413 the missing final newline (i.e., it'll gain one).
1414 This problem does *not* occur when *only* the message body comes in
1415 via STDIN, as in 'cat FILE | s-nail', but *only* when the -t option is
1417 (sendout.c: does no(t/ longer) know about CTE internals!, 2013-02-09)
1419 - Filename arguments for -a are now processed *after* all the resource
1420 files have been loaded etc., so that the usual "folder" specifics can
1421 be used (provided that proper care for shell quoting was taken).
1422 ((main(): delay -a processing.., 2013-01-10), as a part of the
1423 *mainaflags* topic branch.)
1425 - (d38c5bd, When the write command asks.., 2004-11-23) added support
1426 for pipes when saving attachments during a "write" command.
1427 It however used the wrong SIGPIPE signal handler; e.g.:
1429 Enter filename for part 2 (application/x-gzip): |exit
1432 Of course, it still performs a jump and that most likely leaves memory
1433 chunks behind, thus causing some memory leaks. This will be
1434 a long-term problem (you may want to read [mime.c:fwrite_td(): TODO
1435 notes on unfixable leaks, 2013-01-14] for more).
1436 (send.c:sendpart(): fix longjmp() SIGSEGV.., 2013-01-29)
1438 - Fixed a name quoting regression that i've introduced in
1439 (Rewrite *extract().., 2012-10-20), that would have caused
1440 "x \"y\" z" to become "x"y" z" instead of "x "y" z".
1441 (S-nail still does not really have RFC compliant parsers, just as
1442 NetBSD Mail(1) has, i.e., there are structured and unstructured fields
1443 etc... I hope i can provide them in v15.0.)
1444 (names.c:yankname(): fix quote regression.., 2013-01-29)
1446 - The IDNA conversion now assumes domain names are specified in
1447 *ttycharset*, rather than in the LC_CTYPE locale charset.
1448 I.e., it integrates into the usual character set specifications.
1449 (IDNA: honour *ttycharset* for domain names, 2013-01-18)
1451 - The new *editalong* variable will automatically spawn an editor when
1452 composing a mail in interactive mode, just as if `~e' was given.
1453 (Add new *editalong* variable, 2012-01-07)
1455 - The manual has been converted to mdoc.
1456 (The manual has been converted to mdoc, 2012-12-28)
1458 - The ~@ tilde escape, when given filename arguments, will treat the
1459 arguments as a comma-separated instead of a whitespace-separated list.
1460 (collect: change separator of ~@ tilde escape.., 2012-12-28)
1462 The interactive mode of ~@ has also been changed, rather massively.
1463 Please do reread what the manual says.
1464 ((collect: support multiple attachment charsets.., 2013-01-23), as
1465 part of the *attach* topic branch.)
1467 - Thanks to Gianluca Ramunno (ramunno DOT gianluca AT gmail DOT com)
1468 S-Nail will no longer try to issue a STARTTLS command when it is about
1469 to establish a SMTPS connection, a task that logically fails since the
1470 connection is already secured.
1471 (Interestingly the nail codebase performs the necessary test for IMAP
1473 While here the undocumented nail v11.0 *smtp-use-tls* legacy option
1475 (Fix SMPTS with a set *smtp-use-starttls*.., 2012-12-22)
1477 - The RFC 4155 compliant MBOX quoting is now exclusively used, the
1478 shitty *posix-mbox* variable has been removed again.
1479 (Shitty because i've implemented RFC 4155 compliant MBOX quoting and
1480 tested it, then added *posix-mbox* for those who liked the old
1481 behaviour and did not re-test -- the final code path was buggy.)
1483 In mails newly created and saved by S-nail(1) no From_ quoting at all
1484 will be used no more, but instead the rewritten MIME file classifier
1485 will detect unquoted From_ lines and enforce quoted-printable encoding.
1486 (This is an approach that is S/MIME compatible all through the way as
1487 the file data is not modified at all, but only encoded, so that the
1488 data checksum is not changed.)
1490 In yet existent mails that S-nail copies or moves around without
1491 reclassification an RFC 4155 compliant From_ line detector will apply
1492 MBOXO quoting (prepend a single '>') as necessary.
1493 Different to the old MBOXRD behaviour S-nail will neither quote yet
1494 quoted From_ lines ('>>From xy' -> '>>>From xy') nor will it unquote
1495 one quote level when reading etc. mails ('>> From xy' -> '>From xy').
1496 As a result the code could be simplified.
1498 This changeset also incorporates a fix for NetBSD PR bin/47453, as
1499 reported by Martin Brandenburg. I.e., some mailers, noticeably
1500 UW-imap (with MBX format only?), use non-compliant From_ lines with
1501 RFC 822 date specifications. Be aware of 'em.
1502 (RFC 4155 MBOX, and drop *posix-mbox* and foldergets().., 2013-01-06)
1504 - *rfc822-show-all* has been removed.
1505 It didn't work properly for more complex MIME structures, like
1506 message/rfc822 messages with attachments etc., just as i've seen today
1507 on the file(1) mailing list.
1508 So, instead of hacking it now i've dropped it and will come back with
1509 a better solution when the MIME and send layers have been overhauled.
1510 I.e., the real intent was to be able to specify that an embedded
1511 message/rfc822 is treated as a *unity*, and that's the goal.
1512 (Drop *rfc822-show-all*, 2013-01-23)
1513 [The manual will be adjusted in a different commit.]
1515 - *rfc822-no-body-from_* has been renamed to *rfc822-body-from_*.
1516 It thus must be set explicitly.
1517 On the other hand it now catches all cases...
1518 (*rfc822-no-body-from_* -> *rfc822-body-from_*, 2013-01-23)
1519 [The manual will be adjusted in a different commit.]
1521 - The new *charset-7bit* (defaults to US-ASCII) and *charset-8bit*
1522 (defaults to UTF-8) have been introduced.
1523 These are used if seven bit clean data is to be sent, and no
1524 *sendcharsets* are set or the convertion of all of them failed,
1527 - There is no functional change unless there is iconv(3) support.
1528 - There is no functional change unless you set them.
1529 (Introduce *charset-8bit* and *charset-7bit* variables.., 2013-01-18)
1530 [The manual will be adjusted in a different commit.]
1532 In addition the new *sendcharsets-else-ttycharset* variable can now
1533 be used to automatically use *ttycharset* as a *sendcharset(s)*,
1534 regardless of the new *charset-8bit* variable.
1535 (Add *sendcharsets-else-ttycharset* variable, 2013-01-24)
1536 [The manual will be adjusted in a different commit.]
1538 NOTE: before we apply charset conversion we now perform a string
1539 comparison to see wether character sets are identical. If the strings
1540 match (case-insensitively), then *no* conversion is performed.
1541 This means that code like
1543 $ printf "LATIN1: \0376" | s-nail -Ssendcharsets= -s boom ./out.txt
1545 *succeeds* in an UTF-8 environment now, whereas older versions would
1546 fail with an "illegal byte sequence" error (unless the iconv(3)
1547 library of the system would not perform any conversion that seems
1548 superflous, of course).
1550 I thought about making this optional, but, in fact, if this would be
1551 done in an environment without iconv(3) support then the result would
1552 be equally corrupt. And the way it is now we save the expensive and
1553 superflous conversions. (See TODO for more.)
1555 Please *do* reread the manual section "Character sets".
1556 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1558 - An attempt was made to improve MIME Content-XY: detection.
1559 It should be more RFC compliant, and just overall better :);
1560 a simple one-pass classifier cannot match libmagic(3), of course.
1562 This changeset removes support of the long obsoleted (4fee1ef,
1563 2005-01-06) *charset* variable, as well as for the
1564 *maximum-unencoded-line-length* variable that has been introduced in
1565 (48a652bd, 2005-07-26).
1567 For S-nail v14.0 it'll be no longer necessary to do
1569 $ tr -d '\015' < input | s-nail ...
1571 to transport files which use the $-DOS (terminal) newline (sequence).
1572 We still depend upon *sendcharsets* for a while, though.
1573 (Rewrite file-content classification.., 2013-01-02)
1575 - The new *mime-counter-evidence* variable can be used to force
1576 a classification of non-text MIME parts (attachments) by their
1577 filename, i.e., a "reverse-classification" just as would be performed
1578 if S-nail(1) would itself *send* the file(name). This can help
1579 against some stupid MUAs (Apple Mail?) that send .diff etc. files as
1580 `application/octet-stream' parts etc.
1582 At a later time this may become a valued option, causing a temporary
1583 save of unnamed attachments followed by a MIME classification of the
1584 file contents, followed by forced treatment as plain text if it seems
1585 to be human readable. But not yet. Just to warn you.
1586 (Add *mime-counter-evidence* variable.., 2012-12-29)
1588 - The special "pipe-" command "@" can be used to force treatment of
1589 a MIME message part as plain text (e.g.,
1590 'set pipe-application/pgp-signature=@' will henceforth print those
1591 signatures inline and as plain text).
1592 (Introduce the special "@" "pipe-" command, 2012-12-27)
1594 - The MIME types (as from mime.types(5)) will now be cached. Before
1595 all possible sources would have been opened, read and parsed for each
1596 and every message part that required detection of the MIME
1598 The new "mimetypes" command can be used to show or clear that cache.
1599 (Add mime.types(5) cache.., 2012-12-27)
1601 - A small set of MIME types (template: ./mime.types) will now become
1602 compiled into S-nail(1), and be used as a fallback if there are no
1603 ~/.mime.types and/or no /etc/mime.types, or those didn't contain
1604 a matching type. E.g., NetBSD 6 doesn't ship a default database.
1605 Also, file extensions will be matched case-insensitively (case of
1606 attribute values is not specified afaik?).
1607 (Introduce compiled-in mime.types(5).., 2012-12-21)
1609 - The undocumented *charset7* variable was removed.
1611 - The "Message X:" display leader has been changed and will henceforth
1612 be matchable via "^[-- Message \d+ -- \d+ lines, \d+ bytes --]:$".
1613 These lines can no longer be suppressed by setting the *quiet*
1614 option (which was yet possible for print and top, though undocumented).
1615 (Change "Message X:" display message.., 2012-12-20)
1617 - When displaying multipart messages the "Part X:" introductional string
1618 has been changed; if the Content-type: header is not *retain*ed, then
1619 this string will include the part's type and size. Ditto for
1620 Content-disposition: and a mentioned attachment filename.
1621 This is a first step only, for the final version the MIME and send
1622 layers will have to be adjusted. But the string will be matchable via
1623 a "^[-- #.* --]$" regular expression from now on.
1624 (Change "Part X:" display message.., 2012-12-20)
1626 - MIME boundaries in multipart messages are now handled better in that
1627 no boundary string should get through to the display.
1628 (Tweak MIME boundary detection.., 2012-12-20)
1630 - A couple of long standing, even pre-Heirloom mailx(1) memory leaks and
1631 segmentation violations, most of them related to configurations
1632 without alloca(3) support, as well as one leak that i have introduced
1633 when i implemented RFC 4155 MBOX handling, have been fixed.
1634 But S-nail should now survive non-alloca(3) configurations.
1635 (*memtracer* topic branch.)
1637 - The Base64 MIME handling has been rewritten completely.
1638 This was an urgent topic, because the old implementation (a) read in
1639 all lines of a base64 encoded text part, repeatedly resizing a string
1640 storage and repeatedly decoding that string until all the lines have
1641 been swallowed (i.e., or by accident the last decoded byte was
1642 a newline character, and that in turn may of course have fucked up for
1643 multi-octet encodings, dependent on the actual byte-order), (b) used
1644 function local static data to keep state in between multiple
1645 invocations, which messed up multi-byte/-octet encodings like this
1647 �5��ɽ���Aɥ����́��٥��������[lots of data follows]
1649 and (c) did not perform any error checking at all.
1650 The new one does not run into the problem that (a) tried to circumvent
1651 since leftover decoded data (as opposed to leftover *encoded* data) is
1652 transported along the call-chain for later use. It adds a minimal set
1653 of error handling ('may now see "[Invalid Base64 encoding ignored]"),
1654 with more to become possible in later S-nail versions when the entire
1655 layers are reworked. (Until then DOS newline sequences [CRLF]
1656 embedded into base64 will no longer be decoded to Unix LF newlines.)
1657 Base64 encoded lines will now be 76 characters long, as stated (as
1658 a maximum value) in RFC 2045, not 72 as before.
1660 The Base64 code core has been shamelessly stolen from NetBSD's
1661 Mail(1), and i guess it was the second time that this happened :=).
1662 (*base64-rewrite* topic branch; and reworked later on the *mime-cte*
1665 - The string allocation strategy has been tweaked some more to, i think,
1666 a final version (regarding algorithm).
1667 In normal non-interactive send mode it should now no longer need any
1668 dynamic memory at all (unless some dozen recipients are specified).
1669 (Several other places still use normal dynamic memory, of course.)
1670 (*dope-stringdope-again* topic branch.)
1672 - Support for NSS (Network Security Services) has been removed.
1673 I've never worked with it and are, regarding the complexity of
1674 network security, not willing to spend any time on it.
1675 SSL is installed on all systems i'm using and/or testing on by
1676 default, and so i've choosen to go this way.
1677 (It may be that sometime in the future S-nail will add support for
1678 libcurl(3) connectivity, and then it may happen that not only NSS
1679 support is reintroduced again, but also GNU TLS. All of that applies
1680 to network connectivity only, however, not to S/MIME afaik.)
1681 (*drop-nss-support* topic branch.)
1683 - I finally got a glue and understood that Sourceforge does (a) not
1684 support symbolic links and (b) doesn't like dots as regular parts of
1685 filenames. This means that all this time the promised s-nail.tar.gz
1686 symbolic link did not work, and that s-nailv13.3.tar.gz wasn't
1687 accessible either (via the web interface).
1688 In the future S-nail(1) will not provide any more symbolic links (the
1689 Sourceforge website offers a "download latest" thing which seems to
1690 work), and use underscores in filenames -- s-nailv13.3.tar.gz has been
1691 renamed to s-nailv13_3.tar.gz. The tags continue to use dot notation.
1694 - The *heirloom-plus* support branch has been removed.
1695 The code bases diverged a lot and even more to come.
1696 It doesn't make sense to put any effort in that.
1701 - Configuration on UnixWare 7.1.4 will succeed (shell issue fixed).
1703 - Even on DragonFly BSD the IMAP GSSAPI is now found
1704 (in /usr/pkg/include/krb5/gssapi/gssapi.h).
1706 - Support for pkgsrc(7) systems and automatic integration of
1707 C_INCLUDE_PATH and LD_LIBRARY_PATH path configurations.
1710 - Fixes a mortally embarassing regression that the current maintainer
1711 introduced before i really knew what i was doing, in (If *record* is
1712 set, avoid writing dead content twice.., 2012-09-14).
1713 It hit users that send through a MTA and have *record* set; in this
1714 combination data would not have reached the MTA.
1715 Interested parties may read the comment in savedeadletter() (part of
1716 the changeset) or the (Fix MTA/*record* descriptor clash..,
1717 2012-11-10) commit log.
1719 Deepest apologies to tortured users from the current maintainer!
1721 - RFC 4155 compatible MBOX file handling has been introduced, and so
1722 S-nail is now on par with (at least) NetBSD Mail in respect to this.
1723 It can be turned off with the new *posix-mbox* variable, which you may
1724 need to use since not all MUAs are capable to dig those MBOX files.
1725 E.g., less cutting-edge (.-) MUAs fail for this:
1727 |From - Thu May 10 20:40:54 2012
1728 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1729 |To: super@duper.com
1734 |From - Thu May 10 20:40:54 2012
1735 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1736 |To: super@duper.com
1739 |>From - Thu May 10 20:40:54 2012
1740 |From - Thu May 10 20:40:54 2012
1742 I'm not completely happy since S-nail *does* still quote those lines,
1743 how rare they may be -- it *does* modify message content. mutt(1)
1744 implements something more clever and that is quoted-printable encoding
1745 of the "F" from "From", when seen at the beginning of a line.
1746 This, when applied to just *any* "^From", will be a non-modifying and
1747 all-compatible solution.
1749 - SEND_MBOX handling has been changed to discard any Content-Length: and
1750 Lines: headers when it rewrites a message by default.
1751 I know that mutt(1) generates them (why, after
1752 http://www.jwz.org/doc/content-length.html?).
1753 Anyway, S-nail does neither use nor manage them, so that any
1754 modification renders those fields invalid, and then it seems best to
1755 discard them anyway.
1756 You may turn the new behaviour off with *keep-content-length*.
1761 The problem was that i really wanted to release on a 25th.
1762 But i have been able to improve S-nail(1) some more, so that this is
1763 possibly the first real release of it. So i'll add only things that
1764 have changed since v13 -- please see below for the complete picture.
1766 - A new CONFIG=CUSTOM make directive was added, and the new user.conf
1767 variables WANT_SCORE and WANT_DOCSTRINGS have been added. It is
1768 possible to create a floating-point free S-nail(1) now.
1771 - If a feature is disabled not even functions stubs should remain now.
1773 - Many places which will work only with local filenames do now actually
1774 check that the target is a local filename.
1776 - Space-separated lists should work again, at a few places at least.
1778 - Tilde commands will be possible, even with -r.
1780 - The *sendmail-progname* has been added after NetBSD 6 dropped the
1781 send-mail entry in mailer.conf(5), which broke S-nail(1). Now users
1784 - When editing messages via ~e or ~v file and pipe addressees will no
1787 - If recipients occur multiple times spread over lists, i.e., To:, Cc:,
1788 Bcc:, then only one occurrence remains, and in the "highest-order"
1791 - The "list" command prints the list alphabetically sorted (somewhat).
1793 - The "help" and "?" commands take an optional argument that shows
1794 a synopsis string for the given command (unless WANT_DOCSTRINGS was
1797 - String allocations are now more efficient. The situation can still be
1798 improved. However, for the first time Berkeley Mail(1) integrates
1799 harmonically into the system allocator, which may madvise(2) unused
1800 memory to the operating system as necessary and/or possible!
1805 Well, a version number 13 is anyway an ugly thing...
1807 commit 4f534bb33b7c911272cc66a0e3a9e47b73ad8deb
1808 Date: 2012-10-25 20:46:07 +0200
1810 FIX MIME quoted-printable encoding (char cast)..
1815 Well, one of the things that have already been started in v13 is
1816 the turn from using "int" when working with 8-bit characters to
1817 "unsigned char" (and as long as we do not support wide
1820 Unfortunately one very important piece of code, that is handling
1821 encoding to quoted-printable, still used integer instead of
1822 unsigned char, which caused an automatic extension cast to take
1823 place, and that resulted in a messed up output.
1829 I want to give prominence to the following people that helped to improve
1830 S-nail(1) during this development cycle, in order of appearance: Martin
1831 Neitzel, Ezequiel Garzón, Björn Persson, Paul Vojta, and, especially,
1832 John Dodson for warm words from beautiful Australia! Many thanks also
1835 After i've officially forked nail(1) aka Heirloom mailx(1) as S-nail(1)
1836 on 2012-09-18 i have been able to work five weeks almost fulltime on
1837 S-nail(1) development. The first three weeks can be characterized as
1838 hectic fireworks here and there, but then it got better and i was able
1839 to work more or less topic-centric. In the meanwhile S-nail(1) is more
1840 than 230 commits away from the Heirloom base--and drifting further apart.
1842 S-nail(1) v13 is the first release of S-nail(1), but it was forked from
1843 Heirloom mailx(1) 12.5 7/5/10 that arose from Berkeley Mail 8. unless
1844 i'm mistaken. What characterizes S-nail(1) v13?
1846 - The build system has been reworked almost completely.
1847 It is possible to fine-tune which features should be present in the
1848 binary and which don't. The name of the binary can be chosen, and
1849 that choice is reflected all through the manual and the template
1850 resource file. The manual is always complete and thus may document
1851 features that are not supported by the actual binary, though.
1852 Please see INSTALL for more.
1854 - Compiler warnings can now be used. Please see the example WARN= flags
1855 in the Makefile, but '-Wall -Wextra -pedantic' should be silent though
1856 certainly insufficient to reflect the complex work of modern compilers.
1858 - The following recipient address list combines some of the major
1859 improvements that have been made:
1861 <addr1@cdröm.de> (bier) , ./file1,
1862 Steffen Smöregäs (Humbabä) <sauer@bäüer.de> (Hummpäa) ,
1863 sabberlot@träbbel.de , (bier2) <a2@bür2.de> ,
1864 a3@b3.de (bier3) , <a4@b4.de> (bier4, und \"bier5\") ,
1865 |cat > pipe1 , (bier 6) <a6@bür6.de> , ./file2 ,
1866 (co\$mm1) abc1@düf.de (cö,bmm,2) (co\"m\"m.3) ,
1867 co\$bmm1 \"c,ömm2\" co\"m\"m.3 <abc2@däf2.de> , |cat > pipe2 ,
1870 That, on a single line, may be given to ":m" or (quoted) on the
1871 command line, or to "~c" or whatever, and it will work as expected
1872 (well, everything else would be a bug..) and result in the following
1873 sendmail(1) invocation:
1876 <-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>
1878 Date: Thu, 25 Oct 2012 17:12:15 +0200
1880 Cc: Steffen =?utf-8?Q?Sm=C3=B6reg=C3=A4s?=
1881 =?utf-8?Q?_(Humbab=C3=A4)?= <sauer@xn--ber-qla4j.de> (=?utf-8?Q?Hummp=C3=A4a?=),
1882 sabberlot@xn--trbbel-cua.de, moppel@xn--hppel-jua.org,
1883 <addr1@xn--cdrm-7qa.de> (bier),
1884 co$bmm1 =?utf-8?Q?"c,=C3=B6mm2"?= co"m"m.3 <abc2@xn--df2-qla.de>,
1885 (co$mm1) abc1@xn--df-xka.de (=?utf-8?Q?c=C3=B6,bmm,2?=) (co"m"m.3),
1886 (bier 6) <a6@xn--br6-hoa.de>, <a4@b4.de> (bier4, und "bier5"),
1887 a3@b3.de (bier3), (bier2) <a2@xn--br2-hoa.de>
1888 Subject: Re: SubjectTest
1890 Content-Type: text/plain; charset=us-ascii
1891 Content-Transfer-Encoding: 7bit
1896 So list parsing has been fixed, IDNA support has been added, and it is
1897 possible to mix pipe and file recipients *and* multiple thereof, and
1898 the result is still correct for *all* of them.
1899 I think this kind of list can be given wherever a user can directly
1900 enter such a list. And i think all that is unique to S-nail(1).
1902 - When writing back edited messages the target MBOX mailbox can no
1903 longer become "corrupted" when the trailing newline was removed during
1904 the edit. Also affected FreeBSD and NetBSD mail(1).
1906 - A security fix for CVE-2011-2895 was applied.
1908 - The generated Message-Id: is now more human-friendly.
1910 - The -h command line option has been dropped. Use "-O -h XY" if your
1911 MTA really supports that.
1913 - The -O and -r command line options no longer enforce a one-shot send
1914 mode, and instead persist for the duration of the entire session.
1916 - Variables set via the -S command line option are now (un)set twice;
1917 immediately and after all the resource files have been loaded.
1919 - Other new or changed options/commands, in order of appearance:
1920 recipients-in-cc, smime-sign-include-certs, quote-fold, stealthmua,
1921 add-file-recipients, write, rfc822-no-body-from_, rfc822-show-all,
1922 mail/Mail, idna-disable, idna-strict-checks, ??
1924 - In the codebase itself an effort to reduce duplicate work and
1925 introduce caching, and to minimize the use of local variables, was
1926 started, but that is long term. A lot of improvements here and there,
1927 too, like using the well MD5 optimization from Wei Dai, Chris Torek's
1928 hash algorithm for hash tables etc.
1930 - Incredibly important: an heraldic animal was found: snailmail.jpg!
1932 The full history can be inspected by issuing the git(1) command
1934 $ git log --reverse s-nail..s-nailv13
1936 A new TODO has been introduced, and it is getting longer and longer.