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.2:
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 Many thanks to the perpetual Gavin Troy.
23 - Faulty notational change of system call return values from `<0' to
24 `==-1' caused endless waitpid(2) loop. [d6f316a; test(!): 79fd761]
27 - (GLibC) STD I/O overoptimizes rewind(3) so that underlaying file
28 descriptor offset is not reset to 0. Generalize the already
29 used `really_rewind()' hack and use it not only in
30 `savedeadletter()' but also in `page_or_print()'. It is likely
31 that this not also fixes `history' listing but also some other
32 things which go through the pager, dependend on the setting of
33 *crt* etc., and on at least GNU/Linux systems. [463660f]
35 Note: standard I/O does NOT offer a possibility to do this in
36 a non-hackish way. It is thus likely that S-nail will gain
37 a completely new I/O layer in the future. That'll also be faster.
40 This note is false: POSIX Issue 7 overloaded the meaning of
41 fflush(3): when used on readable streams the file offset of the
42 underlaying file descriptor is adjusted to that of the stream.
43 (nail.h: adjust really_rewind(): POSIX Issue 7 defined a way..)
44 uses this official approach instead if _POSIX_VERSION>=200809L.
46 - Old shells will now correctly execute an error-condition
47 execution path in `mk-conf.sh'. [afef55f]
52 Thanks to Andy Switala (andy DOT switala AT gmail DOT com).
53 And thanks to all package maintainers for their stamina.
55 At the first workday after the release i've run into a bug that was
56 caused by an oversight, a double-Fclose() that would be harmless if we
57 wouldn't forcefully panic() when we encounter it!
59 So i've spent another week on a review, and despite fixing many
60 additional notational oversights i haven't found more oversights of
61 newly introduced problems. On the other hand i've found and fixed some
62 old problems during the review, and tweaked some other things:
64 - The INSTALL file now has a `Current codebase state' section.
66 - Commands invoked via `!' should now be interruptable.
67 I'm afraid the exit status of such a command will not be reflected by
68 the return value of the `!' command yet, but hey, at least `!sleep 10'
69 can now be interrupted -- try this with another Berkeley Mail!
72 - All credential prompts should now be interruptable.
73 (Inspired from Andy Switala) [c3bb2a2]
75 - 'make test' will now test a silly S/MIME case when WANT_DEBUG (or
76 'make devel') was used. [8cff17f]
78 - *batch-exit-on-error* should now look at the exit status of *every*
79 command when the command loop ticks. [c7e7d53]
81 - The new `[?name-list]?search-pattern' search expression has been
82 changed to `[@name-list]@search-pattern' -- like this it doesn't clash
83 with the `?' help command and can thus be used on a line by itself,
84 causing the default command (`next') to be invoked on its' result,
85 shall there be one. Ok, yes, that was surely also an oversight.
88 - *attrlist* must now be exactly 13 characters, just as it should
89 be. An error message is printed if not. It was always komisch,
90 but i'd buggified it somewhen in the past. Now fixed.
93 - The NCL WANT_TABEXPAND feature now also works if *newfolders* is
94 set to `maildir'. Yet, if a folder was assumed to be of maildir
95 type, shell globbing would not occur. [part of f5c184c]
97 - The `X-Decoding-Data' S/MIME header field was set to the epoch
98 origin instead of NOW in v14.6.
100 Also the `certsave' command now supports file globbing (i.e.,
101 '~/.certs/' should end up in your $HOME now).
102 [both part of 7e0aec7]
107 + With this release the S-nail codebase has been converted to my usual
108 style of function-code-flow and notation.
110 ?0[]$ git diff --shortstat v14.5.2..HEAD
111 55 files changed, 28065 insertions(+), 25356 deletions(-)
112 ?0[]$ git diff --ignore-all-space --shortstat v14.5.2..HEAD
113 55 files changed, 14664 insertions(+), 11955 deletions(-)
115 Maildir and S/MIME support have been restored, and a MIME bug that
116 could have led to missing data in header display+ has been fixed.
117 Ah, and users of compressed boxes should now feel luckier, too --
118 at least once they've realized that the compress extension is no
119 longer appended automatically, but must be given explicitly.
121 Thus: i hope that all those i-am-new-to-the-codebase bugs i've
122 introduced over a year ago have been found and fixed, and that
123 v14.6 is the true "sweet sixteen" (months of maintainership).
125 ChangeLog (packager-affine)
126 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
128 - If WANT_AMALGAMATION is set, `-pipe' will be added to our CFLAGS
129 (which are only honoured with WANT_AUTOCC, of course). [1330411]
131 - New configuration option: WANT_IMAP_SEARCH, enabled by default.
133 The regular expression support for IMAP-style search expressions has
134 been removed again: it changed the IMAP search semantic in that it
135 couldn't be executed on the server, but only local, and the syntax
136 sucked, too. (And we have a new `?' search expression.) [402b7c6]
138 - CONFIG=MEDIUM and CONFIG=NETSEND now both WANT_REGEX. [dee954e]
140 - The `make test' target should *really* work gracefully, now that usage
141 of the `-#' command line option also sets the folder to be opened to
142 `/dev/null'. (Still no `void' box in sight.) [0119d514]
144 - All published patches may also be found in a new [patches] branch.
149 - Several fixes that saw published patches (with equivalent
150 functionality), and are thus described in NEWS, are included:
152 . s-nail-14.5.2-sort-alt.patch
153 Fixes a hasty commit that introduced string relaxation in a faulty
156 . s-nail-14_5_2-mimeheader.patch
157 Fixes data loss if multiple MIME encoded-words follow each other in
158 header bodies. [c81afce]
160 . s-nail-14_5_2-maildir.patch
161 Effectively restores proper maildir support. [1c2563b, 13f325f]
163 . s-nail-14_5_2-smime.patch
164 Fixes an off-by-one error and, in effect, restores S/MIME sign and
165 encryption etc. support. [e759f75]
167 - The `screen' terminal type is by default recognized as being
168 colour-capable. [e759f75]
170 - With the NCL command line editor and WANT_TABEXPAND hitting <TAB>
171 should now act as if an "implicit asterisk" had been given in case
172 there was no expansion of the original user input; e.g., '? ls <TAB>'
173 may exceed your line limit now ;). [0910a8f]
175 - The S/MIME cipher list was outdated, RFC 5751 requires AES-128 as
176 the default, the RC2 ones are long obsoleted (etc.). Also we now
177 should handle that OpenSSL may not support individual algorithms.
179 Note: we use the option value `des3' for `DES EDE3' from now on!
180 (Maybe see *smime-cipher-user@host* manual entry.)
182 *ssl-method* may now also be assigned the new (default) method `auto'
186 - Messages will now be stored in a set *record* even if only file or
187 pipe addressees were given. [a11935b]
189 - Support for xz(1) compressed mailboxes has been added.
190 (The `Can't canonicalize' warning for compressed boxes had the same
191 cause that made maildir usage impossible, but i don't feel _too_ bad
192 because looking into the code a bit revealed that the *newmail*
193 mechanism never worked for such boxes anyway. And will for a while.)
196 - S-nail now supports nested if..else..endif conditionals. [3c22c04]
198 - The NCL command line editor now locks its' history file when it reads
199 and writes it, so as to protect against concurrent usage. [c3a39ce]
201 - You can now say 'fi%', 'fi&', 'p&10' and `ghost ps '!ps axu'' followed
202 by 'ps|grep nail'. [c3266c6]
204 - Invocation cleanup: usage of -f and -u is mutual, -H and -u is ok, -u
205 in send mode not. [fa0a0aa]
207 - New message specification: `[?name-list]?search-string' will search
208 in locally available messages. If the optional `?name-list' part is
209 given, that specifies the (comma-separated list of) header fields to
210 search in. The special names `body' and `text' can be used to search
211 in message bodies alone and bodies including the headers fields,
212 respectively. Note that "message bodies" unfortunately still means
213 "including headers of attachments and attachments themselves", and
214 until some later time. [61bb460]
216 - The new command line option `-L spec-list' prints a header summary of
217 only those messages that comply to the specification list `spec-list'.
218 If -L and -H are used in combination, no summary is printed at all,
219 but the exit status reports wether `spec-list' would have matched some
220 messages or not. [934e12c]
222 ChangeLog (purely technical)
223 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
225 - Most of the work was changing the code-flow of the entire codebase to
226 my usual style of programming, with a single function entry and
227 a single function exit, including the addition of N(ot) Y(et) D(ead)
228 points of interest, which finally enabled me to get rid of (sic!)
229 using a debugger for S-nail development. Just compile via 'make
230 devel', and in case of a crash you should get a nice backtrace
231 listing. (You use IMAP, do you?)
233 However, because practically every line of code has been touched, this
234 caused some other changes along the way, e.g., the handling of
235 temporary files was changed completely (the formerly used Ftemp()
236 function has been replaced with a new Ftmp(), which handles unlinking
237 itself as necessary etc.), it was detected that the S/MIME support was
238 no longer compliant to any RFC, some resource leaks have been
239 eliminated... It is likely that a change so large introduced some
240 other flees and flaws, however. But it looks good so far.
246 + No official release, only exists as git(1) tag.
248 v14.5.2: fix 4: 2014-02-15 (2014-02-14)
249 ---------------------------------------
251 - s-nail-14_5_2-smime.patch
252 Fix a very stupid off-by-one error that i've introduced
253 in [7bdf330] (OpenBSD 5.3: sigh, address strcpy(),strcat()
255 Until we've changed the used data from string to something
256 line-wise, use strcat(3) again.
258 v14.5.2: fix 3: 2014-02-10
259 --------------------------
261 - s-nail-14_5_2-maildir.patch
262 maildir folders would have caused problems in environments which
263 provide the realpath(3) function: beside a "cannot canonicalize PATH"
264 warning the finally used path would be wrong (`test3' would end up as
265 `test3/test3'), so that any further access would try to use the wrong
266 path. Please read the description of this patch and/or the commit
267 logs of the commits [1c2563b] and [13f325f].
269 v14.5.2: fix 2: 2014-02-05
270 --------------------------
272 - s-nail-14_5_2-mimeheader.patch
275 Subject: ehm, .getElementById("blink") needs <span
276 =?US-ASCII?Q?id=3D"blink">,?= not =?US-ASCII?Q?class=3D"id"?=
278 would yet be displayed without the " not " in between the two encoded
279 words because of faulty "encoded-word-continuation" detection (note
280 the quotation marks). The error path could also have been seen in
281 mail forwarding and in faulty searching etc.
282 This patch is in a row of fixes for my hasty [0f9ad93] from 2013-03-12
283 that already caused the v14.2 minor release (because of [b608c6b] from
284 2013-03-14). Those with mercy may read the commit message of [c81afce].
286 v14.5.2: fix 1: 2014-01-30
287 --------------------------
289 - s-nail-14_5_2-sort.patch
290 Reverses (sort(),thread(): use srelax()!, 2014-01-18, [a9b67e9]),
291 which was a hasty commit of an untested diff that i've added few
294 As a rather careless last-minute change i've added string relaxation
295 to threaded and sorted display, but it's really one more step towards
296 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
298 An alternative, forward-heading patch that keeps string relaxation has
299 been pushed to [master] as [5e75529] and is also available as
300 s-nail-14_5_2-sort-alt.patch.
305 Thanks to Ypnose, Sunil Nimmagadda and Gavin Troy.
306 Gavin Troy *really* deserves special thanks for facing [next]!
307 And i want to dedicate the new coloured message display functionality
308 to John Dodson and Ypnose. Thank you.
309 (And best wishes to beautiful Australia!)
311 ChangeLog (packager-affine)
312 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
314 - All utilities can now be overwritten during configuration so that
315 their values are fixated in the generated makefile (`mk.mk').
316 I.e., talking about MAKE=, STRIP=, awk=, cat=, chmod=, cp=, cmp=,
317 grep=, mkdir=, mv=, tee=.
318 rm= and sed= have to be overwritten from the command line, they're
319 needed before `conf.rc' is read.
320 [5c03347, 072ec65, 39a00ab, 23a1245, ?]
323 - The release tarball is now also available in a xz(1) version.
325 - New configuration option: WANT_COLOUR, by default enabled.
327 - 'make test' should now really work, even if the running user has
328 a mailbox with content. [f223a91]
330 - WANT_AUTOCC is now by default enabled, so as for normal users which
331 don't have the need to embed into a defined packaging environment.
334 - Installation no longer strip(1)s away debug symbols if WANT_DEBUG was
341 - Fixes to some bugs that are present since the first cvs(1) commit of
342 Heirloom mailx(1); includes that *ssl-key-user@host* should now work.
343 [4405a2cc, 9770c26f, 692976b9]
345 - Some off-by-XY fixes, thanks to the debug memory canaries.
346 [19b2b0d, 202506e, 43df6e4]
348 - Fixes for (other) stupidisms (of mine): [1c2161f]
350 This includes true implementation of in-memory history limit for the
351 NCL, which was the final and real solution to a segmentation fault
352 that Gavin Troy had to deal with on [next]. [1089f2b]
355 - For completeness: new command `var-inspect' shows information about
356 all given options. Mostly ment for implementing future tests.
359 - The `pipe' command no longer embeds message information into the
360 data passed through to the command (when *piperaw* is set).
361 [ef5ecc6 (part of topic/colour)]
363 - Simple coloured message (header) display is now possible. Please
364 read the new manual section "Coloured message display", use
365 *colour-disable* to turn it off. (It is enabled by default if it
366 knows the terminal is capable and, if used, the pager can, too. Note
367 we now set LESS=FRXi when starting PAGER and no LESS= is in the
370 Dedicated to John Dodson and Ypnose.
371 [topic/colour, c6e84c7]
373 - The `if', `else', `endif' syntax has been extended.
374 You can now "if 0" (never), "if 1" (always), "if $OPTION" (boolean
375 check for OPTION) and "if $OPTION == 'VALUE'" as well as "if $OPTION
376 != 'VALUE'". Unfortunately it is still not possible to use
377 conditionals inside conditionals. [0fb2ae7]
379 - -# now also sets MBOX=/dev/null. [4be2f1e]
381 - The NCL command line editor now supports cursor keys when the terminal
382 produces xterm(1)-compatible keycodes ('ESC' + '[' + [DACB] for left,
383 up, right and down, respectively). What a thrill, yay!!! [0cbf672]
385 - New (optional) command: `history': show or clear command line history,
386 or select a specific command line from in there.
387 History works a bit different now, and should no longer include
388 command lines which include specific message numbers; more to come.
389 [59c6195, topic/hist2]
391 I plan to join all the history management and use only the one that is
392 part of NCL now, hooking it into editline(3) and readline(3). That
393 would shrink tty.c a bit and also introduce duplicate elimination for
396 - The new ~u and ~U tilde escapes work like ~f and ~m, respectively, but
397 don't include any header lines. Inspired by a patch from
398 Sunil Nimmagadda on openbsd-tech@. [c37b8b3]
400 - The `|' command should work again -- it has stopped working on
401 2013-09-09 when i've accidentally changed the command name from `|' to
405 - As a rather careless last-minute change i've added string relaxation
406 to threaded and sorted display, but it's really one more step towards
407 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
408 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
409 Buffer allocs ever/max simultan. : 14/14
410 Overall alloc count/bytes : 17165/881088
411 Cycle maximums: alloc count/bytes: 16906/876984+0
412 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
413 Buffer allocs ever/max simultan. : 0/0
414 Overall alloc count/bytes : 16515/841816
415 Cycle maximums: alloc count/bytes: 16256/837712+829560
417 ChangeLog (purely technical)
418 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
420 - We now have debug canaries for all memory sources now that [8419d44]
421 added them to the "string dope".
423 - The most work has been done on our value system, which manages the
424 binary and value options, like *folder* etc.
425 It is now based on enumerations, i.e., constant integers, not on
426 strings. This of course only relates to non-dynamic options.
427 Anyway, this saves us key hashing and allows more compact data
428 representation in general (see the new header `okeys.h' for more).
434 ChangeLog (packager-affine)
435 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
437 - The build system *only* uses the automatically detected $CFLAGS and
438 $LDFLAGS if WANT_AUTOCC=1. I.e., even unset or empty $CFLAGS and
439 $LDFLAGS are not touched until then.
440 (We do however still set $CC if that is unset or empty or set to the
441 plain string "cc".) [856625f6]
446 - Fixed segmentation faults / bus errors when setting *nofolder*
447 / *line-editor-cursor-right* to the null string (only with WANT_NCL),
448 respectively. [d1f1a19b, 21e5c285, 9f6ff25d]
450 - *prompt* handling is now really POSIX compliant (thus no prompting
451 occurs not only for 'set noprompt', but also for setting *prompt* to
454 This was indeed a rather large changeset that also introduced the new
455 *prompt* escape character \&, which expands to `?' by default and to
456 `&' if *bsdcompat* is set.
458 Like that we now can simply assign "\& " to *prompt* at program
459 startup, which (a) allows to do 'set noprompt' without error (once)
460 and (b) allows for POSIX compliance in respect to prompt handling
461 without any complicated conditional code, but (c) gives us the
462 opportunity to continue to support BSD prompts.
465 - For completeness: new command: `features'. (Rather useful for being
466 able to implement more tests in the future, and act according to what
467 is really compiled into the tested binary.
469 - The `-#' command line option now also sets *quiet* by itself.
472 - nail.1: a newly introduced empty line in the manual produced error
473 messages on some systems. Fixed.
475 - The return value of the `mimetypes' command has been reversed and
476 should now be fixed. [acf56ac52]
478 - In threaded display the Subject: followup suppression no longer
479 takes into account invisible messages.
480 Also, rudely hack in a messages-already-written-in-this-round counter,
481 so that the followup suppression knows when "the top of the screen" is
482 reached, which (seems to) help(s) against missing subjects up there as
483 well as after a `newmail'. [topic/subject]
485 - Added a WANT_REGEX=1 toggle in `conf.rc'.
486 When we find regular expressions then a new regex-enabled IMAP-style
487 search is available (see the manual for more) [1ec8fe68]
489 ? f (/or subject ^\[S-nail (subject ^\[nail-devel))
490 ? f (/subject ^\[S-nail) (/subject ^\[nail-devel)
491 ? f (/subject "^\\[(S-nail|nail-devel)")
493 I'm looking forward for being able to add another, simplified, syntax.
495 ChangeLog (purely technical)
496 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
498 - The cc-test.sh has seen some tweaks, for easier future extension, and
499 for adding a test for [d1f1a19]. [several, mentioned: 21e5c285]
501 - On systems without a real wordexp(3) implementations deadlocks could
502 occur because we sometimes hold_all_sigs() to avoid longjmp(3)s away
503 (and will do so for quite some time, still), and that resulted in the
504 SIGCHLD that reported the exit of the started subshell to be blocked,
505 too (e.g., after '? *.h<Tab>': endless hang). Fixed.
510 Many thanks: Gaetan Bisson, William Yodlowsky, Gavin Troy,
511 Thomas (wasd AT gmx DOT net), Ypnose.
512 And Gavin Troy definetely deserves a very special credit.
513 But thank you all, and very much indeed!
515 ChangeLog (packager-affine)
516 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
518 - The `test' make target has been fixed. [f0991e14]
521 - It is possible to gain a different kind of make(1) verbosity by
522 using a VERBOSE=1 command line argument (this knob is not taken into
523 account when deciding wether a rebuild is needed). [498e4ad0]
526 - On Crux 3 Linux and OpenBSD the readline(3) and editline(3),
527 respectively, libraries will now be found when desired. [a7d1aa78]
530 - WANT_LINE_EDITOR has been renamed to WANT_NCL, *plus*.
531 So now there are WANT_READLINE, WANT_EDITLINE and WANT_NLC, each of
532 them can be set individually, and they are tested in the shown order.
533 Also, WANT_TABEXPAND and WANT_HISTORY have been introduced and can be
534 used to fine-tune functionality. [ae4e01e1, b2635feb, 9742bf40]
536 (While here, i've fixed WANT_TABEXPAND code so that it is more
537 sensitive to line excess; on Linux etc., where MAX_INPUT is 255,
538 strange behaviour could be seen because we didn't take into account
539 the length of the prompt at all. The NCL is assumed to have only
540 one remaining, but unfixable problem: backspace often is incapable
541 to cross visual line boundaries; use ^A/^E + ^L, then. [e832c04a]
543 Also, cursor (now ^B and ^F) and history movement (now ^P and ^N) of
544 the NCL have been changed. [d7d928da])
546 - WANT_QUOTE_FOLD is now enabled by default. And WANT_ASSERTS has been
547 renamed to WANT_DEBUG. [1e10da1f]
549 - The build system has seen yet another overhaul in general. CC, CFLAGS
550 and LDFLAGS plus are now tracked and changes will force rebuilds.
551 The new WANT_AUTOCC option can be used to let the build system figure
552 out a compiler and choose known-to-work flags. Use the new ADDCFLAGS=
553 and ADDLDFLAGS= command line arguments to add your specific flags on
554 top of those -- the final CFLAGS etc. are what is change-tracked.
556 This rather massive internal rework revealed that old Bourne shells
557 were yet not supported by the new build system, and so did testing
558 that UnixWare installation was yet impossible due to tool
559 incompatibility. [75c4b74e]
561 - The new WANT_AMALGAMATION option will force compilation of all the
562 sources in a single compilation unit. This requires a rather large
563 amount of memory, but may produce a more compact, maybe more optimized
564 binary. (Implementing this revealed quite some bugs which could
565 therefore be fixed.) [topic/amalgam]
567 - `nail.rc' has been pimped a bit (mostly comments, but
568 *mime-counter-evidence* is now always set). [e3094ba7]
570 That changeset was however buggy. [f3dcb46]
573 - We no longer use install(1) for `install'ation make rules. [80b02cd9]
578 - Even '$ s-nail & fg $!' will now work with the NCL. [2a8b5c55]
580 - Several off-by-one (off-by-two) fixes. [32ce9836, 71e6d013, f139dc36]
583 - Setting *noprompt* now prevents prompting, as per POSIX. [ecefaf63]
585 - *prompt*: new \$ (exit status of last command) and \@ (name of
586 currently active mailbox) escape sequences. [6f652046]
588 - One may now omit the space in '? unc' ('?unc') [05fcb383]
590 - New commands: `ghost' and `unghost' define command aliases (since
591 `alias' is taken for a different purpose) [topic/commands]
596 - There is now a pseudo account `null' (case-insensitive).
597 Also a new `localopts' command exists; when used from within an
598 `account' block, options changed will be reverted back to its former
599 value when the account is left (e.g. by switching to `null'):
602 alternates sdaoden@users.sf.net sdaoden@users.sourceforge.net \
603 sdaoden@googlemail.com sdaoden@gmail.com
604 set Sign="\n--steffen\nForza Figa!" sign="\n--steffen"
605 set smtp=smtp.gmail.com smtp-auth=plain smtp-use-starttls
611 set from="Steffen \"Daode\" Nurpmeso <sdaoden@gmail.com>"
616 set from="Steffen \"Daode\" Nurpmeso <sdaoden@users.sf.net>"
624 neither of *Sign*, *sign*, *smtp** nor *from* should be set.
625 Please see the manual for more.
626 TODO - neither command-ghosts nor alternates etc. are yet tracked
627 TODO - we should have a boolify() so as to say 'localopts yes' etc.
630 - New command: `cwd' (print current working directory).
631 Also fixing the `chdir' return value. [eff4397c]
633 - The *ssl-method* now allows explicit setting of 'tls.1.1' and
634 'tls1.2' values. [c66b4196]
636 - When sending to display, be aware that filenames in MIME parts may of
637 course be MIME-encoded! [1454be03]
639 - *hostname* is now honoured even if *smtp* is not set. (We always
640 supported *from*, so why not *hostname*?)
642 - The `-u user' option now acts identically to setting the $USER
643 environment variable and both now tend to mean something like
644 "impersonate as user in some aspects". Note that we have always used
645 the latter in one or the other way, and `-u user' always ment more
646 than just "open mailbox of user", so i think this change sharpens the
647 edge in the right direction. [09632731]
649 - Filename argument quoting has been tweaked for (some) function(s which
650 take a filename argument last). The following snippet as reported by
651 Gavin Troy should work now: [2bb9b80e]
653 ? mv +inbox.Junk\ Mail
655 - The GNU implementation of wordexp(3) is also (i've added a workaround
656 for the very same bug for Mac OS X in S-nail v14.3 [63273772]) buggy,
657 which causes segmentation faults when expansions failed (`fi &VOID').
661 - The `fi' command no longer uses the (possibly truncated) display
662 version of a filename, but the full path. [5cd85b07]
664 ChangeLog (purely technical)
665 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
667 - Large rework of internal structure: bundle inclusion of most of the
668 external and the content of most of the internal #include files in the
669 new nail.h. If that would have been done very first bugs like the
670 infamous MAXPATHLEN bug as reported by Paul Vojta (see v14.4.2) would
671 never have occurred. [21f3155b]
673 - Support for -fstrict-overflow cc(1) flags. [topic/strict-overflow]
675 - Fixed the quotation filter which yet allocated memory even if not
678 - String relaxation reduces memory pressure rather drastically when
679 working with many (especially MIME) mails at a time, e.g., when
680 writing a modified mailbox. Before all messages of a mailbox had to
681 be worked without releasing any memory in between, now we give back
682 memory (to our pool, not the system) after each and every message.
685 - The other memory source now uses bound canaries, which also found some
688 - We now use the EL_PROMPT_ESC editline(3) mode for prompting, which
689 should offer the possibility to use coloured prompts etc. with
690 (even those) editline(3) (versions which do offer it -- older versions
691 should just do fine by themselves).
692 S-nail uses the special trigger control character \1. [ea30d818]
695 Note however that all tested editline(3) versions are buggy and
696 either don't get it right (`\1COLOR-ON\1stuff\1COLOR-OFF\1') or are
697 incapable of proper repainting (`\1COLOR-ONstuffCOLOR-OFF\1').
699 - We now use the MD5 digest code from the OpenSSL library if that is
705 Many thanks: Gaetan Bisson, Stephen Isard, Jérémie Courrèges-Anglas,
706 William Yodlowsky, and Adam Sjøgren from GMANE.org!
708 ChangeLog (packager-affine)
709 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
711 - The packager-install: target has been fixed. [a8c1b0b]
712 (Gaetan Bisson and William Yodlowsky)
714 - As suggested by Gaetan Bisson the several build system tasks are now
715 individually addressable, i.e., 'make [OPTIONS] config', 'make build',
716 'make test', 'make packager-install'); nothing changes unless you want
717 to, in which case: please see INSTALL. [4d3b799]
719 The new target 'test' will call cc-test.sh with its new --check-only
720 option which will only perform the (too few) function tests on the
722 And cc-test.sh will no longer create output files, but simply echoes
723 to STDOUT and STDERR. [629e1ee, 786f219]
726 - The default configuration file now sets *bsdannounce* and *bsdflags*,
727 all in one line, as suggested by William Yodlowsky.
728 (If *header* is disabled, *bsdannounce* is ignored, but *header* must
729 be enabled by default according to POSIX, and *bsdannounce* is just
730 the same as *header*, but for the folder-switched event. Thus setting
731 *bsdannounce* is the more sane default, imho.) [6161f10]
734 - Announcement messages are now tagged '[ANNOUNCE]'. [26e1b35]
735 (Tagging suggested by Stephen Isard and Jérémie Courrèges-Anglas)
737 - The manual NAME now includes the version (but it's somewhat ugly).
743 - When switching folders when in compose mode, message attachments
744 become invalid. For v14.4.5, at least warn when this happens.
747 - When reading multipart/alternative messages which do not contain
748 a text/plain part, the (most likely HTML) part is not displayed (even
749 if S-nail is configured to display HTML). The reason is a bug i've
750 introduced with [0d43a999] (Change "Part X:" display message..,
751 2012-12-20). (Note that the committed fix i've posted to the list was
752 not correct either and has been fixed itself.) [225c02b, ecfa149]
757 Thanked, Gavin Troy, Gaetan Bisson.
759 - Fix output buffer confusion that would have occurred when parts of
760 a multipart mail had a pipe command set. Longer story in [e75d16dd].
763 - The makefile now supports a `packager-install' target that bypasses
764 the reevaluation of the configuration (after checking that there is
765 one) and directly steps ahead to the install process.
768 - Notes in INSTALL that CFLAGS and LDFLAGS need to be overwritten from
769 within (conf.rc or) the command line.
775 I convey special thanks to Karol Błażewicz and Gaetan Bisson.
777 - The new build system didn't allow to overwrite CFLAGS= when used in
778 conjunction with GNU make(1). To make a long story short, removing
779 a `.POSIX:' directive from the makefile fixed the problem. Luckily.
782 - More INSTALL notes for UnixWare 7.1.4, which suffers from the same
783 problem: here the fix is to use the -e option of make(1).
785 - Karol Błażewicz reported a segmentation violation he got when using an
786 Arch Linux S-nail test package, and Gaetan Bisson informed me about
787 that. The problem was that we didn't assign the resulting default
788 address (which gets used when *from* is not set) to the result which
789 gets used, effectively resulting in a NULL dereference. [cfd60479]
794 Many thanks to Paul Vojta.
796 - On GNU/Linux there is no MAXPATHLEN constant defined by default, as
797 this is a non-standard legacy constant. Mozilla ran into this some
798 time ago, though a bit different [1]. It made it easier for S-nail.
800 [1] <https://bugzilla.mozilla.org/show_bug.cgi?id=412610>
802 We could include `sys/limits.h' to get at MAXPATHLEN, there it is
803 defined to be PATH_MAX, but let's just include the standard `limits.h'
804 and ensure MAXPATHLEN ends up >= PATH_MAX. With this condition being
805 true even FORTIFYd sources won't bail with reported buffer overflows
806 because realpath(3) expects a buffer of PATH_MAX bytes. [bee5e57c]
809 - With the builtin LINE_EDITOR, ensure proper interaction with GNU
810 rlogind(8), which is alone in its quest to set the ISTRIP termios(4)
813 - Bugfix a codepath that would have prevented compilation when
814 HAVE_ICONV is not set.
815 While there, allow to unselect message attachments when using the `~@'
816 tilde command interactively, which i mysteriously had forgotten when
817 allowing selection of 'em. (oops?) [4f58ffea]
819 - It's now easier for packagers to get at debug-enabled CFLAGS; simply
820 use WANT_ASSERTS=1 (should not be enabled in shipouts, please).
823 - Fixed a terrible bug that i've introduced in november 2012, that would
824 have corrupted MBOX files when using the `resend' command. (The
825 so-called "From_ line" would have been quoted to ">From_ line" instead
826 of simply being stripped.) [19d449e2]
828 - Fixed a SIGSEGV for the builtin LINE_EDITOR, that would have occurred
829 if a history traversal (^B or ^F) would have been continued by
830 a reverse history completion (^R).
831 While there, avoid some multiple-beeps-in-a-row that yet occurred due
832 to code reuse, and document that ^G etc. reset the multibyte state
835 Also, the expand-on-tab code could have excessed line input maximums,
836 e.g., after `? /usr/bin/*<Tab>'. This was of course known, but
837 i wanted to keep it because all tested (modern) terminals "mess up but
838 won't break", and thus made it possible to use the data, even if it's
839 visual representation was messed up. The real solution will be much,
840 *much* more complicated, i.e., show possible *completions*, page-wise,
841 etc., i.e., just like is known by tab *completion*. This will need
842 far more time because it doesn't make sense to embed such complicated
843 code into the current bed.
844 Now i've chosen to simply don't display excess, but replace the
845 content with a message that says that there was excess. It simply
846 looks better. [0320c8ba]
848 - I've changed the use of `[?]' as a replacement sequence for invalid
849 / non-displayable characters to `?' (again). There are still code
850 paths (from the original codebase) which use the real Unicode
851 replacement character instead, so our display is still not unique.
852 On the long term the codepath can anticipate in all levels wether
853 use of Unicode is possible, so that, then, we will be unique again,
854 using either only `?' or the Unicode replacement character. [faf6380]
856 - I've anticipated in v15.0 and implemented *quote-fold* as a stream
857 filter. It is now multibyte safe and takes into account the visual
858 width of characters, i.e., ideographs etc. It is working almost as
859 good as an algorithm can work that looks at data linewise, but is yet
860 experimental and incomplete in that it will break lines even if only
861 whitespace or a backslash escape follows. It is code that is only
862 a few hours old, which is why it is not enabled by default. [
869 - Fix some harmless stylos and typos in the manual and `conf.rc'.
872 - Ensure *complete* proper cleanup on signal-caused configuration run
875 - Bugfix: reenable empty configuration variable overrides, as in
877 $ make install SID= NAIL=mailx ...
880 - Bugfix: rename the `conf.rc' variables SHELL, LISTER and PAGER because
881 they clash with the POSIX standard variables of the same names, which
882 hurts now that the configuration is run through the shell itself.
883 The configuration names are now XSHELL, XLISTER and XPAGER (ouch).
886 - nail.rc: comment out some non-portable S-nail(1) specifics, for those
887 who install this file as mailx.rc or so, somewhere. [3f14b01]
889 - From now on S-nail will use simple version tags, as, e.g., `14.4.1',
890 i.e., no more `s-nail-14.4.1'. [a75437d, 183d59c] (Jürgen Daubert)
892 Also move UAGENT out of `version.h' [f7be5be]
894 Uh! v14.4 must have originated in a bad dream; good it's vanished.
899 Thanks to the entire vivid and virile S-nail(1) user community is
900 proper, especially Stephen Isard, Gavin Troy, Martin Neitzel.
901 Not to forget Ryan Kavanagh and Ayan George.
903 Note this time the changes are in reverse order, i.e., oldest first.
908 15fbe09 ^bf9173f 'topic/varmac-unite'
909 Simplification and unification of variable and macro handling
910 40f6f58 ^15fbe09 'topic/cledit1'
911 Command line editor; new manual section `Line editor'
912 ad28a32 ^40f6f58 'topic/termsize'
913 Honour POSIX mailx(1) and respect $COLUMNS and $LINES on startup
914 dc3cd49 ^a446fd8 'topic/qf'
916 b8738f7 ^0651fd0 'topic/spam1'
917 Interaction with SpamAssassin; new manual section `Handling spam'
918 5419d6f ^b8738f7 'topic/make1'
919 Reworked build system; please read `INSTALL' and `conf.rc'
920 9ab4d6b ^5419d6f 'topic/list1'
921 Slightly tweaked message thread display, fix `:u :r' to mean it
926 - The default PAGER is now more(1). (But read on.)
928 - The `echo' command is now compliant, and fully supports XSI.
930 - The `group' and `ungroup' command aliases have been removed, they are
931 `alias' and `unalias'.
933 - We now have the capability of line editing and history.
934 One may choose from not less than three different implementations:
935 a builtin editor as well as possible linkage against BSD editline(3)
936 and also a GNU readline(3) compatible layer.
937 Please read the new manual section `Line editor'.
939 Input is now compliant in that an interactive line may be continued
940 after escaping the newline character with a backslash.
941 [topic/cledit1] (all of them)
943 The *prompt* variable may now contain shell escapes, just like the
944 `echo' command. [0938d8a]
945 As a special extension the new \? escape, when used within *prompt*,
946 will expand to the exit status of the last command. [41076d2]
948 - The POSIX standard environment variables $COLUMNS and $LINES are now
949 honoured upon startup. [topic/termsize]
951 - The `help' / `?' commands now support abbreviation, i.e.,
952 ``$ ? unc'' should now find `uncollapse'. [7b86195]
954 - The `~' abbreviation that has been introduced as an alias for `call'
955 is now a real command, not a magic shortcut. [9987289]
957 - The new variable *quote-as-attachment* can be used to additionally
958 embed the quoted message as a `message/rfc822' MIME attachment.
961 - The compose-mode command `~@' will now attach messages from the
962 current mailbox if given a filename of the style `#NUMBER'.
963 Please read the corresponding manual section `Tilde escapes', though.
965 - The `WANT_JUNK' and `WANT_SCORE', as well as Gunnar Ritters junk mail
966 management have been removed.
968 Instead S-nail(1) can now support interaction with SpamAssassin, but
969 sofar only via the spamc(1) / spamd(1) client / server pair of
970 programs that ships as part of SpamAssassin. The new configuration
971 directive `WANT_SPAM' controls wether this feature is desired.
973 Please read the new manual section `Handling spam'.
974 [topic/spam1] (Martin Neitzel)
976 (S-nail(1) is now *definitely* floating-point free.)
978 - The configuration and make system have been overhauled / reorganized.
979 The configuration is now in `conf.rc', also contains directives like
980 `PREFIX' etc, and is always read in. However, only those directives
981 which are not yet set (via environment or command line overwrites) are
982 incorporated into the set of configuration options. Therefore
987 will now build S-nail(1) twice, because of the changed configuration.
989 Note that `WANT_GSSAPI' is now by default disabled, which shrunk
990 a freshly started s-nail image by more than 30 percent.
992 We're not finished yet in that there is no dependency graph etc.
993 Please do read `INSTALL' and `conf.rc'.
996 - Message selection has been slightly bugfixed in that `:u :r' really
997 means `:u' AND `:r'. Compared to NetBSD Mail(1) it's still a shame.
999 Threaded message display has been slightly changed in that within
1000 a thread identical Subject: lines are not repeated. It may not be
1001 perfect yet due to the general list / thread state. [topic/list1]
1003 - If, upon startup, the environment variable `NAIL_NO_SYSTEM_RC' is set,
1004 then the system wide initialization file isn't read, just as if the
1005 `-n' option had been given. [1b31535]
1007 - It is now possible to use CTRL-C during connection hangs. (But in
1008 general error recovery capabilities of the socket related
1009 infrastructure is non-existent, practically speaking.) [45a9f36]
1011 - *quote-fold* has been temporarily disabled, as it is not multibyte
1014 No review for v14.4. And today is Friday, the 13th. Ouuuh!
1019 I should *maybe* should have and want to give prominence to
1020 Martin Neitzel for this, i maybe have misunderstood.
1022 - Bugfix *synchronous* *pipe-** execution..
1024 Well, unfortunately yet another newly introduced bug slept in
1025 S-nail v14.3[.1] -- [a8d724b3, Add @ and @& shell command prefixes
1026 for pipe-MIMETYPE, 2013-05-03] falsely changed the waiting state
1027 for subprocesses, as has shown up by a HTML-only mail on the
1029 'Seems i'm collecting one line fixes in this codebase; this needs
1030 to change in the future.
1035 I want to give prominence to Juergen Daubert (jue AT jue DOT li), who
1036 reported that i've broken plain-old unfancy send mode in 14.3.
1038 + Ok, i'll hope we're out of new errors for the v14.3 series with that.
1040 - New variable: *batch-exit-on-error*.
1041 Only works if the new -# command line option has been given, and will
1042 check the "current" exit status whenever one operation completes
1043 (S-nail returns to the command prompt).
1044 If the exit status implies error (e.g., sending the last message
1045 failed) then we exit forcefully with that error status. (The normal
1046 behaviour is that the status is reset when the command loop ticks.)
1049 - While here again, i've added the new -# command line option.
1050 This is the first step to implement a reliable batch mode;
1051 unfortunately it still selects the users system mailbox on startup,
1052 because we simply cannot go to "no" mailbox for quite some time -- at
1053 some future time we will be able to go to some VOID thing, and then
1054 this will end up as a rather efficient batch mode.
1055 For now it sets *dot*, *emptystart*, *noheader* and *sendwait*, and
1056 also implies the -~ command line option. [7549569]
1059 printf "m ${MBOX}\n~s subject1\nE-Mail Körper 1\n.\n" &&
1060 printf "m ${MBOX}\n~s subject2\nEmail body 2\n.\n" &&
1062 ) | MAILRC=/dev/null "${NAIL}" -n -#
1064 - Also, -N set *header* instead of *noheader*. [7b4a13f6]
1067 - Plain old unfancy invocations like
1070 $ echo bla|s-nail ./FILE1
1072 had been broken (by [522cb3ec]). [260e19d]
1078 Thanks to Gavin Troy (gavtroy AT gmail DOT com) who inspired the @ and
1079 @& pipe-command prefixes.
1084 - S-nail has been registered at Coverity Scan, and the third build
1085 (after topic branches *coverity-444* and *coverity-444.2*) produced no
1086 more errors. (<http://scan2.coverity.com/projects/444>.)
1087 (Then i used POP3 and IMAP and fixed some SIGSEGV. ;) Still didn't
1088 look at S/MIME, Maildir, caches etc... o()
1090 - S-nail v14.3 doesn't produce any spurious linker warnings on
1091 OpenBSD 5.3; all (correct!) use cases of strcpy() and strcat() have
1092 been replaced. [7bdf330, 2c8d7cb]
1094 - This is the first release with a (though very short) review -- i'm
1095 slowly getting comfortable with the code. (But i'm too stupid to
1096 perform reviews on patches, 'always did reviews on C++/Perl/xy
1097 classes. Aaah, how beautiful ... objects.)
1102 - It is now possible to "call" macros without using the `call' command
1103 by prefixing them with a tilde, as in
1112 - Added the *pop3-bulk-load* option.
1113 Yes, there are mailing lists etc. which use plain text email, and,
1114 there, headers are often more data than the body, so it doesn't make
1115 sense to download the headers twice (unfortunately POP3 doesn't
1116 support a BODY command; if only it would support a RETRDELE command..)
1119 And yep, from this changeset on i personally use S-nail even over the
1120 network, no longer my stale and incomplete S-Postman. And i can tell
1121 you, this damn thing is so silent, i always set *verbose* not to go
1122 grazy ... but .. i hate to say it .. the healing will take time.
1124 - POP3 will now try to use APOP authentication automatically; thus the
1125 *use-apop* stuff has been replaced by *pop3-no-apop* options (just in
1126 case there are POP3 servers which advertise they support APOP but in
1127 fact fail to do so; anyone?) [6c3c5575]
1129 - Some IMAP segmentation violations have been fixed:
1131 ? fi imaps://user1@localhost
1132 Password:Interrupt <- CNTRL-C
1133 ? set imap-auth=cram-md5 <- hey, 'forgot to set correct auth
1134 ? fi imaps://user1@localhost
1135 IMAP write error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown
1138 And also, when *folder* was set to an IMAP account but hasn't been
1139 opened yet, and no IMAP account ever has been opened, a string
1140 comparison against a NULL pointer yet caused a SIGSEGV, too.
1143 - `set folder=' now tolerates `%:' and expands PROTOs stuff etc.:
1145 ? short xp %:imaps://user1@localhost
1148 Pure convenience so that it doesn't need to be typed twice (still no
1149 completion in sight...). Note that setting *folder* to a POP3 box
1150 will now be actively rejected. [b12b17f5]
1152 NOTE: while implementing this i've detected another dead-end
1153 miscondition in S-nail -- you really should ensure that your target
1154 folder/box is connected before you leave your current POP3/network
1155 based folder, if there is data to be moved to the target (i.e.,
1156 mbox). This problem will persist for a long time due to the way the
1157 entire codebase functions; i hope i can find a short/mid-term
1158 solution, but the real healing will take years. The mentioned
1159 solution would at least make S-nail interruptable, currently we get
1160 stuck and interrupts are blocked...
1162 - If you're using S-nail on Mac OS X and have seen some segmentation
1163 faults when expanding shell stuff then you may be pleased to hear that
1164 S-nail now works around an Apple bug. [63273772]
1166 - The builtin mime.types have been corrected and a lot of new ones have
1167 been added. New data from
1168 <http://svn.apache.org/viewvc/tika/trunk/tika-core/src/main/resources/\
1169 org/apache/tika/mime/tika-mimetypes.xml>, thanks! [8072fcb6]
1171 - BEWARE: handling of command line arguments has changed a bit!
1173 1. The -D, -d, -E, -i, -N and -v command line options are now
1174 implemented by means of setting the respective option, as via -S.
1175 (This means that from now on resource files can only *temporarily*
1176 overwrite command line arguments.)
1178 2. The -I and -T command line arguments have been dropped.
1179 It seems Gunnar Ritter stopped developing nail/Heirloom mailx once he
1180 started implementing Newsreader functionality. It'll take a long time
1181 until we get there, so for now drop all the Newsreader stuff.
1183 3. Handling of -r has been changed. E.g.:
1185 s-nail -A test -Snoeditalong -r 'La mort est <fem@me>' -d
1186 ? set from=bummer@m1.com
1190 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t1"
1191 ? set from=bummer@m2.com
1194 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t2"
1198 s-nail -A test -Snoeditalong -r '' -d
1199 ? set from=bummer@m1.com
1203 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m1.com" "t1"
1204 ? set from=bummer@m2.com
1207 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m2.com" "t2"
1209 [*main-fun-cleanup* topic branch]
1211 - *smime-sign-include-certs-** stuff works again, oops.. [9a8597c6]
1213 - A whole lot of smallest and small fixes due to registration at
1214 Coverity Scan, as project 444. Error handling in S-nail is ridiculous.
1215 [*coverity-444* and *coverity-444.2* topic branches. The sheer number
1216 of fixes was the reason to sit down and go for unplanned S-nail v14.3]
1218 - *idna-strict-checks* has been dropped. It's silly to have in a MUA,
1219 especially given that GNU LibIDN doesn't ship with a lot of rules.
1220 We were able to drop quite some code (and a use-after-free, too :().
1223 - The ~p tilde command displays attachments more verbose.
1224 Until the big big MIME and send layer rewrite :) this is intermediate
1225 since until then we do not really know neither MIME type nor charset
1226 of an attachment at the time this is displayed (for sure). Yet
1227 i think it's nicer to show what we have than keep it the way it was.
1230 - @ and @& shell command prefixes have been added for the pipe-MIMETYPE
1231 mechanism. The former suppresses filters if multiple messages are
1232 displayed at once, the latter adds asynchronous program execution on
1233 top of that. E.g., to display PDF documents, but only if you
1234 *explicitly* address the message *alone and by itself*, and without
1235 blocking S-nail and the $PAGER, do:
1237 set pipe-application/pdf="@&cat >"${TMPDIR}"/s-nail${$}.pdf;\
1238 mupdf "${TMPDIR}"/s-nail${$}.pdf; rm "${TMPDIR}"/s-nail${$}.pdf"
1240 (Inspired by Gavin Troy.) [a8d724b3]
1242 Note: most of that had been posted to nail-devel@ already, but it was
1243 tweaked ([251b636]) so that you now *really* have to say `p MSGNO' to
1246 - The NETLESS CONFIG= has been removed; it is almost identical to
1247 MINIMAL now (i.e., without WANT_JUNK and WANT_SCORE).
1249 - WANT_JUNK and WANT_SCORE have been disabled by default.
1250 They don't seem to be too useful; i hope i can implement
1251 a SpamAssassin hook for (downloaded) mail messages for v14.4.
1252 If so, expect these two "modules" to become removed completely.
1257 Another unplanned (minor) bugfix release after Gavin Troy (gavtroy AT
1258 gmail DOT com) pointed out that MIME CTE decoding was broken, who
1259 i therefore want to give a lot of prominence right here.
1261 - Fix MIME content decoding which has been broken by [01c0e135].
1268 An unplanned (minor) bugfix release after i've found two bugs today and
1269 heard from Jérémie Courrèges-Anglas (jca+nail AT wxcvbn DOT org) that
1270 there exists a S-nail OpenBSD package.
1272 I want to give prominence to the following people that helped to
1273 improve S-nail(1) during this development cycle, in order of
1274 appearance: Dirk Peters (peters AT schwertfisch DOT de).
1276 Thank you very much, and best from Germany!
1278 - Some warnings of newer clang(1) versions were silenced, including yet
1279 another alloca(3) problem (see *memtracer* topic branch in v14.0
1282 - Tweaking the MIME boundary detection left a little hole that could
1283 cause boundaries not to be detected, as has been shown by a Microsoft
1284 Word generated mail on the ICU list. [11e5fb5b]
1286 - A format string could overflow bounds if unrealistic
1287 (18446744073709551615) line numbers or message sizes would have been
1288 produced. [faa65c40]
1290 - An algorithmic error could cause overlong lines which wrapped around
1291 to the next display line. [ade52660]
1294 v14.2, 2013-03-15 [v14.1, 2013-03-12]
1295 -------------------------------------
1297 I want to give prominence to the following people that helped to
1298 improve S-nail(1) during this development cycle, in order of
1299 appearance: Martin Neitzel, Christos Zoulas, Stephen Isard, jgw@txo.org
1302 Thank you very much, and best from Germany!
1304 + v14.2 differs from v14.1 only by one commit, one that fixes
1305 (mime_fromhdr(): partial rewrite using n_iconv_str(), 2013-03-12),
1306 which i hastily implemented just hours before the release of v14.1,
1307 and simply shouldn't have made it (into there).
1308 The v14.1 tarball has been removed from the server.
1310 - A fix for the quoted-printable codec: "message truncation" occurred
1311 when a mail maliciously used a soft linebreak to escape the linebreak
1312 of a completely empty line.
1313 (That resulted in 0 written and 0 leftover bytes, a condition that was
1314 declared erroneous back in november 2012 when i started handling I/O
1317 - The "folders" command will work again when given an argument.
1318 A fault of mine introduced in (cmd1.c: expand() may fail, 2012-10-23).
1320 - The Base64 codec has been touched again, and we are finally capable to
1321 perform sequential decoding; this was targeted for the MIME/send layer
1322 rewrite, but it actually was possible today.
1323 The result as seen in ps(1), running on the Base64 encoded HTML5
1324 standard (4622545 bytes HTML, with a NUL appended to force Base64
1325 encoding, resulting in a 6244793 bytes email):
1327 7420 s006 S+ 2:22pm 0:10.65 plain-nail -f HTML5
1328 1440 s006 S+ 2:23pm 0:00.36 ./s-nail -f HTML5
1330 (So the only thing that is left for a good throughput is sequential
1331 decoding of quoted-printable encoded parts that maliciously use soft
1332 linebreaks to convert an entire part to a single line. And i've seen
1333 that from Apple Mail.)
1335 - New option: *mime-allow-text-controls* (rather long manual entry).
1337 - *smtp-auth-password-user@host* and *smtp-auth-user-user@host* will
1339 (Reported by jgw@txo.org in November 2011, fixed by Gavin Troy in
1342 - Most *headline* formats now do support the '-' left-alignment flag.
1343 Note that you most likely have to change your *headline* accordingly.
1344 (The still missing %n format is one reason why there will be v14.2.)
1346 - *datefield* and *datefield-markout-older* can now be set to
1347 strftime(3) format strings (except %n).
1348 (From Stephen Isard's wishlist.)
1350 - A possible SEGV has been found and also fixed by Stephen Isard.
1351 (The "legendary" cross-world stereo fix!)
1353 - Wow! S-nail will finally compile on GNU based Linux systems like
1354 Slackware 14 etc. (Found while hunting bug reported by
1357 - New option: *datefield-markout-older* can be used to choose
1358 a different date display for mails that are older than six months,
1359 in equal spirit to what POSIX describes for the -l option of the ls(1)
1360 command (Stephen Isard).
1362 - (Exotic) Years are (would) now (be) interpreted correctly according to
1365 - CRAM-MD5 usage has been fixed.
1367 - *folder* updates are now tracked when set, and we will show the
1368 realpath(3) name of it, showing PREFIX..SUFFIX if that wouldn't fit on
1370 Tracking updates made it also possible to perform other more expensive
1371 tasks when setting *folder*, so that it is now possible to do
1377 et cetera (both ideas by Christos Zoulas).
1379 - Bugfix for the ~@ tilde-escape in non-interactive mode.
1380 (readtty(): quick shot: work in pipelines (on non-TTY).., 2013-01-25)
1381 introduced the possibility to "read data from the terminal" (STDIN
1382 that is) in non-interactive mode.
1383 The manual documents that attachment input must be terminated with an
1384 empty line, but if that had been omitted, as in the example below, we
1385 would have yet entered an endless loop.
1387 $ cat <<_EOT | /s-nail -~ -s boom ./OUT
1393 - Alias expansion will now be performed for members of Reply-To: fields
1396 - Decoding quoted-printable will now be more relaxed.
1397 (Even though the standard says that users should be given a hint when
1398 input is not absolutely clean; a possible warning will be added later,
1399 when we have an error message ring.)
1401 - New option: *mimetypes-load-control* can be used to control which of
1402 the mime.types resources will be loaded.
1404 - The builtin default mime.types have been extended a bit.
1409 I want to give prominence to the following people that helped to
1410 improve S-nail(1) during this development cycle, in order of
1411 appearance: John Dodson, Gianluca Ramunno, and Anon Ymous from the
1417 - Encoding defaults to *quoted-printable* not *8bit*.
1418 This has no technical background except that i think it's the better
1421 - Small progress for the "getting stuck due to the current folder
1422 becomes inaccessible due to whatever reasons" problem.
1423 (schdir(): realpath() local files before leaving CWD.., 2013-01-08)
1425 - The names of temporary files have changed. Whereas not all uses of
1426 temporary files already use really meaningful names, it has yet become
1427 possible to use the pattern "*mail-*"; or, to be compatible with
1428 NetBSD Mail(1) in one go, "*mail*". (E.g., in my ~/.vimrc you'd read:
1429 :au BufRead,BufNewFile *mutt*,*mail* setl fenc= | setf mail
1430 [the *mutt* is a leftover from times when i've used MUAs that suck].)
1435 - The Quoted-Printable MIME handling has been rewritten completely.
1436 We now correctly encode files with the MS-DOS newline sequence (CRLF).
1437 (Part of the *mime-cte* topic branch.)
1439 S-nail(1) continues to be able to handle text messages and text
1440 attachments without a trailing newline, but because these
1441 Content-Transfer-Encoding related things are now handled by the C-T-E
1442 layer instead of by sendout.c a text message body that comes in as
1443 part of a complete message via the -t command line option will loose
1444 the missing final newline (i.e., it'll gain one).
1445 This problem does *not* occur when *only* the message body comes in
1446 via STDIN, as in 'cat FILE | s-nail', but *only* when the -t option is
1448 (sendout.c: does no(t/ longer) know about CTE internals!, 2013-02-09)
1450 - Filename arguments for -a are now processed *after* all the resource
1451 files have been loaded etc., so that the usual "folder" specifics can
1452 be used (provided that proper care for shell quoting was taken).
1453 ((main(): delay -a processing.., 2013-01-10), as a part of the
1454 *mainaflags* topic branch.)
1456 - (d38c5bd, When the write command asks.., 2004-11-23) added support
1457 for pipes when saving attachments during a "write" command.
1458 It however used the wrong SIGPIPE signal handler; e.g.:
1460 Enter filename for part 2 (application/x-gzip): |exit
1463 Of course, it still performs a jump and that most likely leaves memory
1464 chunks behind, thus causing some memory leaks. This will be
1465 a long-term problem (you may want to read [mime.c:fwrite_td(): TODO
1466 notes on unfixable leaks, 2013-01-14] for more).
1467 (send.c:sendpart(): fix longjmp() SIGSEGV.., 2013-01-29)
1469 - Fixed a name quoting regression that i've introduced in
1470 (Rewrite *extract().., 2012-10-20), that would have caused
1471 "x \"y\" z" to become "x"y" z" instead of "x "y" z".
1472 (S-nail still does not really have RFC compliant parsers, just as
1473 NetBSD Mail(1) has, i.e., there are structured and unstructured fields
1474 etc... I hope i can provide them in v15.0.)
1475 (names.c:yankname(): fix quote regression.., 2013-01-29)
1477 - The IDNA conversion now assumes domain names are specified in
1478 *ttycharset*, rather than in the LC_CTYPE locale charset.
1479 I.e., it integrates into the usual character set specifications.
1480 (IDNA: honour *ttycharset* for domain names, 2013-01-18)
1482 - The new *editalong* variable will automatically spawn an editor when
1483 composing a mail in interactive mode, just as if `~e' was given.
1484 (Add new *editalong* variable, 2012-01-07)
1486 - The manual has been converted to mdoc.
1487 (The manual has been converted to mdoc, 2012-12-28)
1489 - The ~@ tilde escape, when given filename arguments, will treat the
1490 arguments as a comma-separated instead of a whitespace-separated list.
1491 (collect: change separator of ~@ tilde escape.., 2012-12-28)
1493 The interactive mode of ~@ has also been changed, rather massively.
1494 Please do reread what the manual says.
1495 ((collect: support multiple attachment charsets.., 2013-01-23), as
1496 part of the *attach* topic branch.)
1498 - Thanks to Gianluca Ramunno (ramunno DOT gianluca AT gmail DOT com)
1499 S-Nail will no longer try to issue a STARTTLS command when it is about
1500 to establish a SMTPS connection, a task that logically fails since the
1501 connection is already secured.
1502 (Interestingly the nail codebase performs the necessary test for IMAP
1504 While here the undocumented nail v11.0 *smtp-use-tls* legacy option
1506 (Fix SMPTS with a set *smtp-use-starttls*.., 2012-12-22)
1508 - The RFC 4155 compliant MBOX quoting is now exclusively used, the
1509 shitty *posix-mbox* variable has been removed again.
1510 (Shitty because i've implemented RFC 4155 compliant MBOX quoting and
1511 tested it, then added *posix-mbox* for those who liked the old
1512 behaviour and did not re-test -- the final code path was buggy.)
1514 In mails newly created and saved by S-nail(1) no From_ quoting at all
1515 will be used no more, but instead the rewritten MIME file classifier
1516 will detect unquoted From_ lines and enforce quoted-printable encoding.
1517 (This is an approach that is S/MIME compatible all through the way as
1518 the file data is not modified at all, but only encoded, so that the
1519 data checksum is not changed.)
1521 In yet existent mails that S-nail copies or moves around without
1522 reclassification an RFC 4155 compliant From_ line detector will apply
1523 MBOXO quoting (prepend a single '>') as necessary.
1524 Different to the old MBOXRD behaviour S-nail will neither quote yet
1525 quoted From_ lines ('>>From xy' -> '>>>From xy') nor will it unquote
1526 one quote level when reading etc. mails ('>> From xy' -> '>From xy').
1527 As a result the code could be simplified.
1529 This changeset also incorporates a fix for NetBSD PR bin/47453, as
1530 reported by Martin Brandenburg. I.e., some mailers, noticeably
1531 UW-imap (with MBX format only?), use non-compliant From_ lines with
1532 RFC 822 date specifications. Be aware of 'em.
1533 (RFC 4155 MBOX, and drop *posix-mbox* and foldergets().., 2013-01-06)
1535 - *rfc822-show-all* has been removed.
1536 It didn't work properly for more complex MIME structures, like
1537 message/rfc822 messages with attachments etc., just as i've seen today
1538 on the file(1) mailing list.
1539 So, instead of hacking it now i've dropped it and will come back with
1540 a better solution when the MIME and send layers have been overhauled.
1541 I.e., the real intent was to be able to specify that an embedded
1542 message/rfc822 is treated as a *unity*, and that's the goal.
1543 (Drop *rfc822-show-all*, 2013-01-23)
1544 [The manual will be adjusted in a different commit.]
1546 - *rfc822-no-body-from_* has been renamed to *rfc822-body-from_*.
1547 It thus must be set explicitly.
1548 On the other hand it now catches all cases...
1549 (*rfc822-no-body-from_* -> *rfc822-body-from_*, 2013-01-23)
1550 [The manual will be adjusted in a different commit.]
1552 - The new *charset-7bit* (defaults to US-ASCII) and *charset-8bit*
1553 (defaults to UTF-8) have been introduced.
1554 These are used if seven bit clean data is to be sent, and no
1555 *sendcharsets* are set or the convertion of all of them failed,
1558 - There is no functional change unless there is iconv(3) support.
1559 - There is no functional change unless you set them.
1560 (Introduce *charset-8bit* and *charset-7bit* variables.., 2013-01-18)
1561 [The manual will be adjusted in a different commit.]
1563 In addition the new *sendcharsets-else-ttycharset* variable can now
1564 be used to automatically use *ttycharset* as a *sendcharset(s)*,
1565 regardless of the new *charset-8bit* variable.
1566 (Add *sendcharsets-else-ttycharset* variable, 2013-01-24)
1567 [The manual will be adjusted in a different commit.]
1569 NOTE: before we apply charset conversion we now perform a string
1570 comparison to see wether character sets are identical. If the strings
1571 match (case-insensitively), then *no* conversion is performed.
1572 This means that code like
1574 $ printf "LATIN1: \0376" | s-nail -Ssendcharsets= -s boom ./out.txt
1576 *succeeds* in an UTF-8 environment now, whereas older versions would
1577 fail with an "illegal byte sequence" error (unless the iconv(3)
1578 library of the system would not perform any conversion that seems
1579 superflous, of course).
1581 I thought about making this optional, but, in fact, if this would be
1582 done in an environment without iconv(3) support then the result would
1583 be equally corrupt. And the way it is now we save the expensive and
1584 superflous conversions. (See TODO for more.)
1586 Please *do* reread the manual section "Character sets".
1587 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1589 - An attempt was made to improve MIME Content-XY: detection.
1590 It should be more RFC compliant, and just overall better :);
1591 a simple one-pass classifier cannot match libmagic(3), of course.
1593 This changeset removes support of the long obsoleted (4fee1ef,
1594 2005-01-06) *charset* variable, as well as for the
1595 *maximum-unencoded-line-length* variable that has been introduced in
1596 (48a652bd, 2005-07-26).
1598 For S-nail v14.0 it'll be no longer necessary to do
1600 $ tr -d '\015' < input | s-nail ...
1602 to transport files which use the $-DOS (terminal) newline (sequence).
1603 We still depend upon *sendcharsets* for a while, though.
1604 (Rewrite file-content classification.., 2013-01-02)
1606 - The new *mime-counter-evidence* variable can be used to force
1607 a classification of non-text MIME parts (attachments) by their
1608 filename, i.e., a "reverse-classification" just as would be performed
1609 if S-nail(1) would itself *send* the file(name). This can help
1610 against some stupid MUAs (Apple Mail?) that send .diff etc. files as
1611 `application/octet-stream' parts etc.
1613 At a later time this may become a valued option, causing a temporary
1614 save of unnamed attachments followed by a MIME classification of the
1615 file contents, followed by forced treatment as plain text if it seems
1616 to be human readable. But not yet. Just to warn you.
1617 (Add *mime-counter-evidence* variable.., 2012-12-29)
1619 - The special "pipe-" command "@" can be used to force treatment of
1620 a MIME message part as plain text (e.g.,
1621 'set pipe-application/pgp-signature=@' will henceforth print those
1622 signatures inline and as plain text).
1623 (Introduce the special "@" "pipe-" command, 2012-12-27)
1625 - The MIME types (as from mime.types(5)) will now be cached. Before
1626 all possible sources would have been opened, read and parsed for each
1627 and every message part that required detection of the MIME
1629 The new "mimetypes" command can be used to show or clear that cache.
1630 (Add mime.types(5) cache.., 2012-12-27)
1632 - A small set of MIME types (template: ./mime.types) will now become
1633 compiled into S-nail(1), and be used as a fallback if there are no
1634 ~/.mime.types and/or no /etc/mime.types, or those didn't contain
1635 a matching type. E.g., NetBSD 6 doesn't ship a default database.
1636 Also, file extensions will be matched case-insensitively (case of
1637 attribute values is not specified afaik?).
1638 (Introduce compiled-in mime.types(5).., 2012-12-21)
1640 - The undocumented *charset7* variable was removed.
1642 - The "Message X:" display leader has been changed and will henceforth
1643 be matchable via "^[-- Message \d+ -- \d+ lines, \d+ bytes --]:$".
1644 These lines can no longer be suppressed by setting the *quiet*
1645 option (which was yet possible for print and top, though undocumented).
1646 (Change "Message X:" display message.., 2012-12-20)
1648 - When displaying multipart messages the "Part X:" introductional string
1649 has been changed; if the Content-type: header is not *retain*ed, then
1650 this string will include the part's type and size. Ditto for
1651 Content-disposition: and a mentioned attachment filename.
1652 This is a first step only, for the final version the MIME and send
1653 layers will have to be adjusted. But the string will be matchable via
1654 a "^[-- #.* --]$" regular expression from now on.
1655 (Change "Part X:" display message.., 2012-12-20)
1657 - MIME boundaries in multipart messages are now handled better in that
1658 no boundary string should get through to the display.
1659 (Tweak MIME boundary detection.., 2012-12-20)
1661 - A couple of long standing, even pre-Heirloom mailx(1) memory leaks and
1662 segmentation violations, most of them related to configurations
1663 without alloca(3) support, as well as one leak that i have introduced
1664 when i implemented RFC 4155 MBOX handling, have been fixed.
1665 But S-nail should now survive non-alloca(3) configurations.
1666 (*memtracer* topic branch.)
1668 - The Base64 MIME handling has been rewritten completely.
1669 This was an urgent topic, because the old implementation (a) read in
1670 all lines of a base64 encoded text part, repeatedly resizing a string
1671 storage and repeatedly decoding that string until all the lines have
1672 been swallowed (i.e., or by accident the last decoded byte was
1673 a newline character, and that in turn may of course have fucked up for
1674 multi-octet encodings, dependent on the actual byte-order), (b) used
1675 function local static data to keep state in between multiple
1676 invocations, which messed up multi-byte/-octet encodings like this
1678 �5��ɽ���Aɥ����́��٥��������[lots of data follows]
1680 and (c) did not perform any error checking at all.
1681 The new one does not run into the problem that (a) tried to circumvent
1682 since leftover decoded data (as opposed to leftover *encoded* data) is
1683 transported along the call-chain for later use. It adds a minimal set
1684 of error handling ('may now see "[Invalid Base64 encoding ignored]"),
1685 with more to become possible in later S-nail versions when the entire
1686 layers are reworked. (Until then DOS newline sequences [CRLF]
1687 embedded into base64 will no longer be decoded to Unix LF newlines.)
1688 Base64 encoded lines will now be 76 characters long, as stated (as
1689 a maximum value) in RFC 2045, not 72 as before.
1691 The Base64 code core has been shamelessly stolen from NetBSD's
1692 Mail(1), and i guess it was the second time that this happened :=).
1693 (*base64-rewrite* topic branch; and reworked later on the *mime-cte*
1696 - The string allocation strategy has been tweaked some more to, i think,
1697 a final version (regarding algorithm).
1698 In normal non-interactive send mode it should now no longer need any
1699 dynamic memory at all (unless some dozen recipients are specified).
1700 (Several other places still use normal dynamic memory, of course.)
1701 (*dope-stringdope-again* topic branch.)
1703 - Support for NSS (Network Security Services) has been removed.
1704 I've never worked with it and are, regarding the complexity of
1705 network security, not willing to spend any time on it.
1706 SSL is installed on all systems i'm using and/or testing on by
1707 default, and so i've choosen to go this way.
1708 (It may be that sometime in the future S-nail will add support for
1709 libcurl(3) connectivity, and then it may happen that not only NSS
1710 support is reintroduced again, but also GNU TLS. All of that applies
1711 to network connectivity only, however, not to S/MIME afaik.)
1712 (*drop-nss-support* topic branch.)
1714 - I finally got a glue and understood that Sourceforge does (a) not
1715 support symbolic links and (b) doesn't like dots as regular parts of
1716 filenames. This means that all this time the promised s-nail.tar.gz
1717 symbolic link did not work, and that s-nailv13.3.tar.gz wasn't
1718 accessible either (via the web interface).
1719 In the future S-nail(1) will not provide any more symbolic links (the
1720 Sourceforge website offers a "download latest" thing which seems to
1721 work), and use underscores in filenames -- s-nailv13.3.tar.gz has been
1722 renamed to s-nailv13_3.tar.gz. The tags continue to use dot notation.
1725 - The *heirloom-plus* support branch has been removed.
1726 The code bases diverged a lot and even more to come.
1727 It doesn't make sense to put any effort in that.
1732 - Configuration on UnixWare 7.1.4 will succeed (shell issue fixed).
1734 - Even on DragonFly BSD the IMAP GSSAPI is now found
1735 (in /usr/pkg/include/krb5/gssapi/gssapi.h).
1737 - Support for pkgsrc(7) systems and automatic integration of
1738 C_INCLUDE_PATH and LD_LIBRARY_PATH path configurations.
1741 - Fixes a mortally embarassing regression that the current maintainer
1742 introduced before i really knew what i was doing, in (If *record* is
1743 set, avoid writing dead content twice.., 2012-09-14).
1744 It hit users that send through a MTA and have *record* set; in this
1745 combination data would not have reached the MTA.
1746 Interested parties may read the comment in savedeadletter() (part of
1747 the changeset) or the (Fix MTA/*record* descriptor clash..,
1748 2012-11-10) commit log.
1750 Deepest apologies to tortured users from the current maintainer!
1752 - RFC 4155 compatible MBOX file handling has been introduced, and so
1753 S-nail is now on par with (at least) NetBSD Mail in respect to this.
1754 It can be turned off with the new *posix-mbox* variable, which you may
1755 need to use since not all MUAs are capable to dig those MBOX files.
1756 E.g., less cutting-edge (.-) MUAs fail for this:
1758 |From - Thu May 10 20:40:54 2012
1759 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1760 |To: super@duper.com
1765 |From - Thu May 10 20:40:54 2012
1766 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1767 |To: super@duper.com
1770 |>From - Thu May 10 20:40:54 2012
1771 |From - Thu May 10 20:40:54 2012
1773 I'm not completely happy since S-nail *does* still quote those lines,
1774 how rare they may be -- it *does* modify message content. mutt(1)
1775 implements something more clever and that is quoted-printable encoding
1776 of the "F" from "From", when seen at the beginning of a line.
1777 This, when applied to just *any* "^From", will be a non-modifying and
1778 all-compatible solution.
1780 - SEND_MBOX handling has been changed to discard any Content-Length: and
1781 Lines: headers when it rewrites a message by default.
1782 I know that mutt(1) generates them (why, after
1783 http://www.jwz.org/doc/content-length.html?).
1784 Anyway, S-nail does neither use nor manage them, so that any
1785 modification renders those fields invalid, and then it seems best to
1786 discard them anyway.
1787 You may turn the new behaviour off with *keep-content-length*.
1792 The problem was that i really wanted to release on a 25th.
1793 But i have been able to improve S-nail(1) some more, so that this is
1794 possibly the first real release of it. So i'll add only things that
1795 have changed since v13 -- please see below for the complete picture.
1797 - A new CONFIG=CUSTOM make directive was added, and the new user.conf
1798 variables WANT_SCORE and WANT_DOCSTRINGS have been added. It is
1799 possible to create a floating-point free S-nail(1) now.
1802 - If a feature is disabled not even functions stubs should remain now.
1804 - Many places which will work only with local filenames do now actually
1805 check that the target is a local filename.
1807 - Space-separated lists should work again, at a few places at least.
1809 - Tilde commands will be possible, even with -r.
1811 - The *sendmail-progname* has been added after NetBSD 6 dropped the
1812 send-mail entry in mailer.conf(5), which broke S-nail(1). Now users
1815 - When editing messages via ~e or ~v file and pipe addressees will no
1818 - If recipients occur multiple times spread over lists, i.e., To:, Cc:,
1819 Bcc:, then only one occurrence remains, and in the "highest-order"
1822 - The "list" command prints the list alphabetically sorted (somewhat).
1824 - The "help" and "?" commands take an optional argument that shows
1825 a synopsis string for the given command (unless WANT_DOCSTRINGS was
1828 - String allocations are now more efficient. The situation can still be
1829 improved. However, for the first time Berkeley Mail(1) integrates
1830 harmonically into the system allocator, which may madvise(2) unused
1831 memory to the operating system as necessary and/or possible!
1836 Well, a version number 13 is anyway an ugly thing...
1838 commit 4f534bb33b7c911272cc66a0e3a9e47b73ad8deb
1839 Date: 2012-10-25 20:46:07 +0200
1841 FIX MIME quoted-printable encoding (char cast)..
1846 Well, one of the things that have already been started in v13 is
1847 the turn from using "int" when working with 8-bit characters to
1848 "unsigned char" (and as long as we do not support wide
1851 Unfortunately one very important piece of code, that is handling
1852 encoding to quoted-printable, still used integer instead of
1853 unsigned char, which caused an automatic extension cast to take
1854 place, and that resulted in a messed up output.
1860 I want to give prominence to the following people that helped to improve
1861 S-nail(1) during this development cycle, in order of appearance: Martin
1862 Neitzel, Ezequiel Garzón, Björn Persson, Paul Vojta, and, especially,
1863 John Dodson for warm words from beautiful Australia! Many thanks also
1866 After i've officially forked nail(1) aka Heirloom mailx(1) as S-nail(1)
1867 on 2012-09-18 i have been able to work five weeks almost fulltime on
1868 S-nail(1) development. The first three weeks can be characterized as
1869 hectic fireworks here and there, but then it got better and i was able
1870 to work more or less topic-centric. In the meanwhile S-nail(1) is more
1871 than 230 commits away from the Heirloom base--and drifting further apart.
1873 S-nail(1) v13 is the first release of S-nail(1), but it was forked from
1874 Heirloom mailx(1) 12.5 7/5/10 that arose from Berkeley Mail 8. unless
1875 i'm mistaken. What characterizes S-nail(1) v13?
1877 - The build system has been reworked almost completely.
1878 It is possible to fine-tune which features should be present in the
1879 binary and which don't. The name of the binary can be chosen, and
1880 that choice is reflected all through the manual and the template
1881 resource file. The manual is always complete and thus may document
1882 features that are not supported by the actual binary, though.
1883 Please see INSTALL for more.
1885 - Compiler warnings can now be used. Please see the example WARN= flags
1886 in the Makefile, but '-Wall -Wextra -pedantic' should be silent though
1887 certainly insufficient to reflect the complex work of modern compilers.
1889 - The following recipient address list combines some of the major
1890 improvements that have been made:
1892 <addr1@cdröm.de> (bier) , ./file1,
1893 Steffen Smöregäs (Humbabä) <sauer@bäüer.de> (Hummpäa) ,
1894 sabberlot@träbbel.de , (bier2) <a2@bür2.de> ,
1895 a3@b3.de (bier3) , <a4@b4.de> (bier4, und \"bier5\") ,
1896 |cat > pipe1 , (bier 6) <a6@bür6.de> , ./file2 ,
1897 (co\$mm1) abc1@düf.de (cö,bmm,2) (co\"m\"m.3) ,
1898 co\$bmm1 \"c,ömm2\" co\"m\"m.3 <abc2@däf2.de> , |cat > pipe2 ,
1901 That, on a single line, may be given to ":m" or (quoted) on the
1902 command line, or to "~c" or whatever, and it will work as expected
1903 (well, everything else would be a bug..) and result in the following
1904 sendmail(1) invocation:
1907 <-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>
1909 Date: Thu, 25 Oct 2012 17:12:15 +0200
1911 Cc: Steffen =?utf-8?Q?Sm=C3=B6reg=C3=A4s?=
1912 =?utf-8?Q?_(Humbab=C3=A4)?= <sauer@xn--ber-qla4j.de> (=?utf-8?Q?Hummp=C3=A4a?=),
1913 sabberlot@xn--trbbel-cua.de, moppel@xn--hppel-jua.org,
1914 <addr1@xn--cdrm-7qa.de> (bier),
1915 co$bmm1 =?utf-8?Q?"c,=C3=B6mm2"?= co"m"m.3 <abc2@xn--df2-qla.de>,
1916 (co$mm1) abc1@xn--df-xka.de (=?utf-8?Q?c=C3=B6,bmm,2?=) (co"m"m.3),
1917 (bier 6) <a6@xn--br6-hoa.de>, <a4@b4.de> (bier4, und "bier5"),
1918 a3@b3.de (bier3), (bier2) <a2@xn--br2-hoa.de>
1919 Subject: Re: SubjectTest
1921 Content-Type: text/plain; charset=us-ascii
1922 Content-Transfer-Encoding: 7bit
1927 So list parsing has been fixed, IDNA support has been added, and it is
1928 possible to mix pipe and file recipients *and* multiple thereof, and
1929 the result is still correct for *all* of them.
1930 I think this kind of list can be given wherever a user can directly
1931 enter such a list. And i think all that is unique to S-nail(1).
1933 - When writing back edited messages the target MBOX mailbox can no
1934 longer become "corrupted" when the trailing newline was removed during
1935 the edit. Also affected FreeBSD and NetBSD mail(1).
1937 - A security fix for CVE-2011-2895 was applied.
1939 - The generated Message-Id: is now more human-friendly.
1941 - The -h command line option has been dropped. Use "-O -h XY" if your
1942 MTA really supports that.
1944 - The -O and -r command line options no longer enforce a one-shot send
1945 mode, and instead persist for the duration of the entire session.
1947 - Variables set via the -S command line option are now (un)set twice;
1948 immediately and after all the resource files have been loaded.
1950 - Other new or changed options/commands, in order of appearance:
1951 recipients-in-cc, smime-sign-include-certs, quote-fold, stealthmua,
1952 add-file-recipients, write, rfc822-no-body-from_, rfc822-show-all,
1953 mail/Mail, idna-disable, idna-strict-checks, ??
1955 - In the codebase itself an effort to reduce duplicate work and
1956 introduce caching, and to minimize the use of local variables, was
1957 started, but that is long term. A lot of improvements here and there,
1958 too, like using the well MD5 optimization from Wei Dai, Chris Torek's
1959 hash algorithm for hash tables etc.
1961 - Incredibly important: an heraldic animal was found: snailmail.jpg!
1963 The full history can be inspected by issuing the git(1) command
1965 $ git log --reverse s-nail..s-nailv13
1967 A new TODO has been introduced, and it is getting longer and longer.