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.4:
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 Gaetan Bisson.
26 - Avoid segmentation faults with -L option if s-nail is opened on
27 non-existent mailboxes, e.g. '$ MAIL= s-nail -Lx'. (Gaetan Bisson)
33 Thanks and greetings to Gavin Troy, Gaetan Bisson and Tarqi Kazan (tarqi
34 AT cfs DOT dyndns DOT biz).
36 ChangeLog (packager-affine)
37 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
39 - WANT_AUTOCC knows that clang(1) version 1 can dig -Wstrict-overflow=5.
42 - '$ make test' should work even if you are not steffen.
43 (Gaetan Bisson, Gaetan Bisson, Gaetan Bisson, Gaetan Bisson,
44 Gavin Troy, Gavin Troy) [8b796ba]
49 - *autoinc* is gone -- this is *newmail*. [07a8462]
51 - Working with large(r) IMAP boxes should work again without causing
52 segmentation violations. (Gavin Troy) [761dd87, b0ce180]
54 - With our builtin getopt a.k.a. WANT_NOGETOPT=1 usage of the -L option
55 caused segmentation violations. (Tarqi Kazan, Gaetan Bisson) [f2c2646]
57 - The decision wether we need $PAGER or not now also incorporates the
58 informational lines we inject for messages. [316b4cd]
60 - Drop `defines', add `unaccount', rename `undefine'..
61 The `defines' command has been united with `define' -- just like
62 `account' will list all defined accounts when used without arguments
63 `define' will now do so for macros. And `undefine' is the new name of
64 `undef'. The new command `unaccount' can be used to delete all given
65 accounts, in equal spirit to `undefine' and macros.
66 All of this is still vulnerable against recursivity, e.g., deleting
67 an executing macro still works, but don't that. [b0b3275]
69 - Rename `var-inspect' to `varshow'; silly oversight that `var-inspect'
70 will try to lookup a variable "-inspect". Ouch. [afffd30]
72 - Without HAVE_ICONV the character set iterator sofar used
73 *charset-8bit* as the last resort, whereas it should have used
75 P.S.: All this still preliminary, we await the MIME and send layer
76 rewrite to calm down the stuff for real. [edc3226, df9aefd]
78 - During `~@' editing it is possible to leave the possibly endless
79 character set selection loop by interrupting via ^C.
80 In the meanwhile this effectively drops the currently edited
81 attachment and leaves the entire attachment selection session; it
82 doesn't make sense to make it any better until we have our signal
83 manager and stop jumping around.
85 This changeset should also fix dangling Content-Xy MIME information of
86 attachments which were in the same slot before, e.g., if #1 was
87 a message attachment and that was changed on-the-fly to be a real file
88 attachment then the Content-Description would still have stated that
89 it is a message attachment.
92 ChangeLog (purely technical)
93 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
95 - Since it has been decided to remain compatible to ISO C89 we cannot
96 use the ISO C99 `z' format string modifier (printf(3)).
97 Since quite some time we make efforts to provide our own `ZFMT' macro
98 (in `nail.h') which provides somethint compatible, but on 32-bit
99 platforms compilers often complain nonetheless.
100 Therefore we now also have a compile-time assertion that proves that
101 our `ZFMT' macro is really correct. [397e4d1]
106 Many thanks to the perpetual Gavin Troy.
108 - Faulty notational change of system call return values from `<0' to
109 `==-1' caused endless waitpid(2) loop. [d6f316a; test(!): 79fd761]
112 - (GLibC) STD I/O overoptimizes rewind(3) so that underlaying file
113 descriptor offset is not reset to 0. Generalize the already
114 used `really_rewind()' hack and use it not only in
115 `savedeadletter()' but also in `page_or_print()'. It is likely
116 that this not also fixes `history' listing but also some other
117 things which go through the pager, dependend on the setting of
118 *crt* etc., and on at least GNU/Linux systems. [463660f]
120 Note: standard I/O does NOT offer a possibility to do this in
121 a non-hackish way. It is thus likely that S-nail will gain
122 a completely new I/O layer in the future. That'll also be faster.
125 This note is false: POSIX Issue 7 overloaded the meaning of
126 fflush(3): when used on readable streams the file offset of the
127 underlaying file descriptor is adjusted to that of the stream.
128 (nail.h: adjust really_rewind(): POSIX Issue 7 defined a way..)
129 uses this official approach instead if _POSIX_VERSION>=200809L.
131 - Old shells will now correctly execute an error-condition
132 execution path in `mk-conf.sh'. [afef55f]
137 Thanks to Andy Switala (andy DOT switala AT gmail DOT com).
138 And thanks to all package maintainers for their stamina.
140 At the first workday after the release i've run into a bug that was
141 caused by an oversight, a double-Fclose() that would be harmless if we
142 wouldn't forcefully panic() when we encounter it!
144 So i've spent another week on a review, and despite fixing many
145 additional notational oversights i haven't found more oversights of
146 newly introduced problems. On the other hand i've found and fixed some
147 old problems during the review, and tweaked some other things:
149 - The INSTALL file now has a `Current codebase state' section.
151 - Commands invoked via `!' should now be interruptable.
152 I'm afraid the exit status of such a command will not be reflected by
153 the return value of the `!' command yet, but hey, at least `!sleep 10'
154 can now be interrupted -- try this with another Berkeley Mail!
157 - All credential prompts should now be interruptable.
158 (Inspired from Andy Switala) [c3bb2a2]
160 - 'make test' will now test a silly S/MIME case when WANT_DEBUG (or
161 'make devel') was used. [8cff17f]
163 - *batch-exit-on-error* should now look at the exit status of *every*
164 command when the command loop ticks. [c7e7d53]
166 - The new `[?name-list]?search-pattern' search expression has been
167 changed to `[@name-list]@search-pattern' -- like this it doesn't clash
168 with the `?' help command and can thus be used on a line by itself,
169 causing the default command (`next') to be invoked on its' result,
170 shall there be one. Ok, yes, that was surely also an oversight.
173 - *attrlist* must now be exactly 13 characters, just as it should
174 be. An error message is printed if not. It was always komisch,
175 but i'd buggified it somewhen in the past. Now fixed.
178 - The NCL WANT_TABEXPAND feature now also works if *newfolders* is
179 set to `maildir'. Yet, if a folder was assumed to be of maildir
180 type, shell globbing would not occur. [part of f5c184c]
182 - The `X-Decoding-Data' S/MIME header field was set to the epoch
183 origin instead of NOW in v14.6.
185 Also the `certsave' command now supports file globbing (i.e.,
186 '~/.certs/' should end up in your $HOME now).
187 [both part of 7e0aec7]
192 + With this release the S-nail codebase has been converted to my usual
193 style of function-code-flow and notation.
195 ?0[]$ git diff --shortstat v14.5.2..HEAD
196 55 files changed, 28065 insertions(+), 25356 deletions(-)
197 ?0[]$ git diff --ignore-all-space --shortstat v14.5.2..HEAD
198 55 files changed, 14664 insertions(+), 11955 deletions(-)
200 Maildir and S/MIME support have been restored, and a MIME bug that
201 could have led to missing data in header display+ has been fixed.
202 Ah, and users of compressed boxes should now feel luckier, too --
203 at least once they've realized that the compress extension is no
204 longer appended automatically, but must be given explicitly.
206 Thus: i hope that all those i-am-new-to-the-codebase bugs i've
207 introduced over a year ago have been found and fixed, and that
208 v14.6 is the true "sweet sixteen" (months of maintainership).
210 ChangeLog (packager-affine)
211 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
213 - If WANT_AMALGAMATION is set, `-pipe' will be added to our CFLAGS
214 (which are only honoured with WANT_AUTOCC, of course). [1330411]
216 - New configuration option: WANT_IMAP_SEARCH, enabled by default.
218 The regular expression support for IMAP-style search expressions has
219 been removed again: it changed the IMAP search semantic in that it
220 couldn't be executed on the server, but only local, and the syntax
221 sucked, too. (And we have a new `?' search expression.) [402b7c6]
223 - CONFIG=MEDIUM and CONFIG=NETSEND now both WANT_REGEX. [dee954e]
225 - The `make test' target should *really* work gracefully, now that usage
226 of the `-#' command line option also sets the folder to be opened to
227 `/dev/null'. (Still no `void' box in sight.) [0119d514]
229 - All published patches may also be found in a new [patches] branch.
234 - Several fixes that saw published patches (with equivalent
235 functionality), and are thus described in NEWS, are included:
237 . s-nail-14.5.2-sort-alt.patch
238 Fixes a hasty commit that introduced string relaxation in a faulty
241 . s-nail-14_5_2-mimeheader.patch
242 Fixes data loss if multiple MIME encoded-words follow each other in
243 header bodies. [c81afce]
245 . s-nail-14_5_2-maildir.patch
246 Effectively restores proper maildir support. [1c2563b, 13f325f]
248 . s-nail-14_5_2-smime.patch
249 Fixes an off-by-one error and, in effect, restores S/MIME sign and
250 encryption etc. support. [e759f75]
252 - The `screen' terminal type is by default recognized as being
253 colour-capable. [e759f75]
255 - With the NCL command line editor and WANT_TABEXPAND hitting <TAB>
256 should now act as if an "implicit asterisk" had been given in case
257 there was no expansion of the original user input; e.g., '? ls <TAB>'
258 may exceed your line limit now ;). [0910a8f]
260 - The S/MIME cipher list was outdated, RFC 5751 requires AES-128 as
261 the default, the RC2 ones are long obsoleted (etc.). Also we now
262 should handle that OpenSSL may not support individual algorithms.
264 Note: we use the option value `des3' for `DES EDE3' from now on!
265 (Maybe see *smime-cipher-user@host* manual entry.)
267 *ssl-method* may now also be assigned the new (default) method `auto'
271 - Messages will now be stored in a set *record* even if only file or
272 pipe addressees were given. [a11935b]
274 - Support for xz(1) compressed mailboxes has been added.
275 (The `Can't canonicalize' warning for compressed boxes had the same
276 cause that made maildir usage impossible, but i don't feel _too_ bad
277 because looking into the code a bit revealed that the *newmail*
278 mechanism never worked for such boxes anyway. And will for a while.)
281 - S-nail now supports nested if..else..endif conditionals. [3c22c04]
283 - The NCL command line editor now locks its' history file when it reads
284 and writes it, so as to protect against concurrent usage. [c3a39ce]
286 - You can now say 'fi%', 'fi&', 'p&10' and `ghost ps '!ps axu'' followed
287 by 'ps|grep nail'. [c3266c6]
289 - Invocation cleanup: usage of -f and -u is mutual, -H and -u is ok, -u
290 in send mode not. [fa0a0aa]
292 - New message specification: `[?name-list]?search-string' will search
293 in locally available messages. If the optional `?name-list' part is
294 given, that specifies the (comma-separated list of) header fields to
295 search in. The special names `body' and `text' can be used to search
296 in message bodies alone and bodies including the headers fields,
297 respectively. Note that "message bodies" unfortunately still means
298 "including headers of attachments and attachments themselves", and
299 until some later time. [61bb460]
301 - The new command line option `-L spec-list' prints a header summary of
302 only those messages that comply to the specification list `spec-list'.
303 If -L and -H are used in combination, no summary is printed at all,
304 but the exit status reports wether `spec-list' would have matched some
305 messages or not. [934e12c]
307 ChangeLog (purely technical)
308 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
310 - Most of the work was changing the code-flow of the entire codebase to
311 my usual style of programming, with a single function entry and
312 a single function exit, including the addition of N(ot) Y(et) D(ead)
313 points of interest, which finally enabled me to get rid of (sic!)
314 using a debugger for S-nail development. Just compile via 'make
315 devel', and in case of a crash you should get a nice backtrace
316 listing. (You use IMAP, do you?)
318 However, because practically every line of code has been touched, this
319 caused some other changes along the way, e.g., the handling of
320 temporary files was changed completely (the formerly used Ftemp()
321 function has been replaced with a new Ftmp(), which handles unlinking
322 itself as necessary etc.), it was detected that the S/MIME support was
323 no longer compliant to any RFC, some resource leaks have been
324 eliminated... It is likely that a change so large introduced some
325 other flees and flaws, however. But it looks good so far.
331 + No official release, only exists as git(1) tag.
333 v14.5.2: fix 4: 2014-02-15 (2014-02-14)
334 ---------------------------------------
336 - s-nail-14_5_2-smime.patch
337 Fix a very stupid off-by-one error that i've introduced
338 in [7bdf330] (OpenBSD 5.3: sigh, address strcpy(),strcat()
340 Until we've changed the used data from string to something
341 line-wise, use strcat(3) again.
343 v14.5.2: fix 3: 2014-02-10
344 --------------------------
346 - s-nail-14_5_2-maildir.patch
347 maildir folders would have caused problems in environments which
348 provide the realpath(3) function: beside a "cannot canonicalize PATH"
349 warning the finally used path would be wrong (`test3' would end up as
350 `test3/test3'), so that any further access would try to use the wrong
351 path. Please read the description of this patch and/or the commit
352 logs of the commits [1c2563b] and [13f325f].
354 v14.5.2: fix 2: 2014-02-05
355 --------------------------
357 - s-nail-14_5_2-mimeheader.patch
360 Subject: ehm, .getElementById("blink") needs <span
361 =?US-ASCII?Q?id=3D"blink">,?= not =?US-ASCII?Q?class=3D"id"?=
363 would yet be displayed without the " not " in between the two encoded
364 words because of faulty "encoded-word-continuation" detection (note
365 the quotation marks). The error path could also have been seen in
366 mail forwarding and in faulty searching etc.
367 This patch is in a row of fixes for my hasty [0f9ad93] from 2013-03-12
368 that already caused the v14.2 minor release (because of [b608c6b] from
369 2013-03-14). Those with mercy may read the commit message of [c81afce].
371 v14.5.2: fix 1: 2014-01-30
372 --------------------------
374 - s-nail-14_5_2-sort.patch
375 Reverses (sort(),thread(): use srelax()!, 2014-01-18, [a9b67e9]),
376 which was a hasty commit of an untested diff that i've added few
379 As a rather careless last-minute change i've added string relaxation
380 to threaded and sorted display, but it's really one more step towards
381 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
383 An alternative, forward-heading patch that keeps string relaxation has
384 been pushed to [master] as [5e75529] and is also available as
385 s-nail-14_5_2-sort-alt.patch.
390 Thanks to Ypnose, Sunil Nimmagadda and Gavin Troy.
391 Gavin Troy *really* deserves special thanks for facing [next]!
392 And i want to dedicate the new coloured message display functionality
393 to John Dodson and Ypnose. Thank you.
394 (And best wishes to beautiful Australia!)
396 ChangeLog (packager-affine)
397 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
399 - All utilities can now be overwritten during configuration so that
400 their values are fixated in the generated makefile (`mk.mk').
401 I.e., talking about MAKE=, STRIP=, awk=, cat=, chmod=, cp=, cmp=,
402 grep=, mkdir=, mv=, tee=.
403 rm= and sed= have to be overwritten from the command line, they're
404 needed before `conf.rc' is read.
405 [5c03347, 072ec65, 39a00ab, 23a1245, ?]
408 - The release tarball is now also available in a xz(1) version.
410 - New configuration option: WANT_COLOUR, by default enabled.
412 - 'make test' should now really work, even if the running user has
413 a mailbox with content. [f223a91]
415 - WANT_AUTOCC is now by default enabled, so as for normal users which
416 don't have the need to embed into a defined packaging environment.
419 - Installation no longer strip(1)s away debug symbols if WANT_DEBUG was
426 - Fixes to some bugs that are present since the first cvs(1) commit of
427 Heirloom mailx(1); includes that *ssl-key-user@host* should now work.
428 [4405a2cc, 9770c26f, 692976b9]
430 - Some off-by-XY fixes, thanks to the debug memory canaries.
431 [19b2b0d, 202506e, 43df6e4]
433 - Fixes for (other) stupidisms (of mine): [1c2161f]
435 This includes true implementation of in-memory history limit for the
436 NCL, which was the final and real solution to a segmentation fault
437 that Gavin Troy had to deal with on [next]. [1089f2b]
440 - For completeness: new command `var-inspect' shows information about
441 all given options. Mostly ment for implementing future tests.
444 - The `pipe' command no longer embeds message information into the
445 data passed through to the command (when *piperaw* is set).
446 [ef5ecc6 (part of topic/colour)]
448 - Simple coloured message (header) display is now possible. Please
449 read the new manual section "Coloured message display", use
450 *colour-disable* to turn it off. (It is enabled by default if it
451 knows the terminal is capable and, if used, the pager can, too. Note
452 we now set LESS=FRXi when starting PAGER and no LESS= is in the
455 Dedicated to John Dodson and Ypnose.
456 [topic/colour, c6e84c7]
458 - The `if', `else', `endif' syntax has been extended.
459 You can now "if 0" (never), "if 1" (always), "if $OPTION" (boolean
460 check for OPTION) and "if $OPTION == 'VALUE'" as well as "if $OPTION
461 != 'VALUE'". Unfortunately it is still not possible to use
462 conditionals inside conditionals. [0fb2ae7]
464 - -# now also sets MBOX=/dev/null. [4be2f1e]
466 - The NCL command line editor now supports cursor keys when the terminal
467 produces xterm(1)-compatible keycodes ('ESC' + '[' + [DACB] for left,
468 up, right and down, respectively). What a thrill, yay!!! [0cbf672]
470 - New (optional) command: `history': show or clear command line history,
471 or select a specific command line from in there.
472 History works a bit different now, and should no longer include
473 command lines which include specific message numbers; more to come.
474 [59c6195, topic/hist2]
476 I plan to join all the history management and use only the one that is
477 part of NCL now, hooking it into editline(3) and readline(3). That
478 would shrink tty.c a bit and also introduce duplicate elimination for
481 - The new ~u and ~U tilde escapes work like ~f and ~m, respectively, but
482 don't include any header lines. Inspired by a patch from
483 Sunil Nimmagadda on openbsd-tech@. [c37b8b3]
485 - The `|' command should work again -- it has stopped working on
486 2013-09-09 when i've accidentally changed the command name from `|' to
490 - As a rather careless last-minute change i've added string relaxation
491 to threaded and sorted display, but it's really one more step towards
492 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
493 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
494 Buffer allocs ever/max simultan. : 14/14
495 Overall alloc count/bytes : 17165/881088
496 Cycle maximums: alloc count/bytes: 16906/876984+0
497 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
498 Buffer allocs ever/max simultan. : 0/0
499 Overall alloc count/bytes : 16515/841816
500 Cycle maximums: alloc count/bytes: 16256/837712+829560
502 ChangeLog (purely technical)
503 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
505 - We now have debug canaries for all memory sources now that [8419d44]
506 added them to the "string dope".
508 - The most work has been done on our value system, which manages the
509 binary and value options, like *folder* etc.
510 It is now based on enumerations, i.e., constant integers, not on
511 strings. This of course only relates to non-dynamic options.
512 Anyway, this saves us key hashing and allows more compact data
513 representation in general (see the new header `okeys.h' for more).
519 ChangeLog (packager-affine)
520 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
522 - The build system *only* uses the automatically detected $CFLAGS and
523 $LDFLAGS if WANT_AUTOCC=1. I.e., even unset or empty $CFLAGS and
524 $LDFLAGS are not touched until then.
525 (We do however still set $CC if that is unset or empty or set to the
526 plain string "cc".) [856625f6]
531 - Fixed segmentation faults / bus errors when setting *nofolder*
532 / *line-editor-cursor-right* to the null string (only with WANT_NCL),
533 respectively. [d1f1a19b, 21e5c285, 9f6ff25d]
535 - *prompt* handling is now really POSIX compliant (thus no prompting
536 occurs not only for 'set noprompt', but also for setting *prompt* to
539 This was indeed a rather large changeset that also introduced the new
540 *prompt* escape character \&, which expands to `?' by default and to
541 `&' if *bsdcompat* is set.
543 Like that we now can simply assign "\& " to *prompt* at program
544 startup, which (a) allows to do 'set noprompt' without error (once)
545 and (b) allows for POSIX compliance in respect to prompt handling
546 without any complicated conditional code, but (c) gives us the
547 opportunity to continue to support BSD prompts.
550 - For completeness: new command: `features'. (Rather useful for being
551 able to implement more tests in the future, and act according to what
552 is really compiled into the tested binary.
554 - The `-#' command line option now also sets *quiet* by itself.
557 - nail.1: a newly introduced empty line in the manual produced error
558 messages on some systems. Fixed.
560 - The return value of the `mimetypes' command has been reversed and
561 should now be fixed. [acf56ac52]
563 - In threaded display the Subject: followup suppression no longer
564 takes into account invisible messages.
565 Also, rudely hack in a messages-already-written-in-this-round counter,
566 so that the followup suppression knows when "the top of the screen" is
567 reached, which (seems to) help(s) against missing subjects up there as
568 well as after a `newmail'. [topic/subject]
570 - Added a WANT_REGEX=1 toggle in `conf.rc'.
571 When we find regular expressions then a new regex-enabled IMAP-style
572 search is available (see the manual for more) [1ec8fe68]
574 ? f (/or subject ^\[S-nail (subject ^\[nail-devel))
575 ? f (/subject ^\[S-nail) (/subject ^\[nail-devel)
576 ? f (/subject "^\\[(S-nail|nail-devel)")
578 I'm looking forward for being able to add another, simplified, syntax.
580 ChangeLog (purely technical)
581 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
583 - The cc-test.sh has seen some tweaks, for easier future extension, and
584 for adding a test for [d1f1a19]. [several, mentioned: 21e5c285]
586 - On systems without a real wordexp(3) implementations deadlocks could
587 occur because we sometimes hold_all_sigs() to avoid longjmp(3)s away
588 (and will do so for quite some time, still), and that resulted in the
589 SIGCHLD that reported the exit of the started subshell to be blocked,
590 too (e.g., after '? *.h<Tab>': endless hang). Fixed.
595 Many thanks: Gaetan Bisson, William Yodlowsky, Gavin Troy,
596 Thomas (wasd AT gmx DOT net), Ypnose.
597 And Gavin Troy definetely deserves a very special credit.
598 But thank you all, and very much indeed!
600 ChangeLog (packager-affine)
601 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
603 - The `test' make target has been fixed. [f0991e14]
606 - It is possible to gain a different kind of make(1) verbosity by
607 using a VERBOSE=1 command line argument (this knob is not taken into
608 account when deciding wether a rebuild is needed). [498e4ad0]
611 - On Crux 3 Linux and OpenBSD the readline(3) and editline(3),
612 respectively, libraries will now be found when desired. [a7d1aa78]
615 - WANT_LINE_EDITOR has been renamed to WANT_NCL, *plus*.
616 So now there are WANT_READLINE, WANT_EDITLINE and WANT_NLC, each of
617 them can be set individually, and they are tested in the shown order.
618 Also, WANT_TABEXPAND and WANT_HISTORY have been introduced and can be
619 used to fine-tune functionality. [ae4e01e1, b2635feb, 9742bf40]
621 (While here, i've fixed WANT_TABEXPAND code so that it is more
622 sensitive to line excess; on Linux etc., where MAX_INPUT is 255,
623 strange behaviour could be seen because we didn't take into account
624 the length of the prompt at all. The NCL is assumed to have only
625 one remaining, but unfixable problem: backspace often is incapable
626 to cross visual line boundaries; use ^A/^E + ^L, then. [e832c04a]
628 Also, cursor (now ^B and ^F) and history movement (now ^P and ^N) of
629 the NCL have been changed. [d7d928da])
631 - WANT_QUOTE_FOLD is now enabled by default. And WANT_ASSERTS has been
632 renamed to WANT_DEBUG. [1e10da1f]
634 - The build system has seen yet another overhaul in general. CC, CFLAGS
635 and LDFLAGS plus are now tracked and changes will force rebuilds.
636 The new WANT_AUTOCC option can be used to let the build system figure
637 out a compiler and choose known-to-work flags. Use the new ADDCFLAGS=
638 and ADDLDFLAGS= command line arguments to add your specific flags on
639 top of those -- the final CFLAGS etc. are what is change-tracked.
641 This rather massive internal rework revealed that old Bourne shells
642 were yet not supported by the new build system, and so did testing
643 that UnixWare installation was yet impossible due to tool
644 incompatibility. [75c4b74e]
646 - The new WANT_AMALGAMATION option will force compilation of all the
647 sources in a single compilation unit. This requires a rather large
648 amount of memory, but may produce a more compact, maybe more optimized
649 binary. (Implementing this revealed quite some bugs which could
650 therefore be fixed.) [topic/amalgam]
652 - `nail.rc' has been pimped a bit (mostly comments, but
653 *mime-counter-evidence* is now always set). [e3094ba7]
655 That changeset was however buggy. [f3dcb46]
658 - We no longer use install(1) for `install'ation make rules. [80b02cd9]
663 - Even '$ s-nail & fg $!' will now work with the NCL. [2a8b5c55]
665 - Several off-by-one (off-by-two) fixes. [32ce9836, 71e6d013, f139dc36]
668 - Setting *noprompt* now prevents prompting, as per POSIX. [ecefaf63]
670 - *prompt*: new \$ (exit status of last command) and \@ (name of
671 currently active mailbox) escape sequences. [6f652046]
673 - One may now omit the space in '? unc' ('?unc') [05fcb383]
675 - New commands: `ghost' and `unghost' define command aliases (since
676 `alias' is taken for a different purpose) [topic/commands]
681 - There is now a pseudo account `null' (case-insensitive).
682 Also a new `localopts' command exists; when used from within an
683 `account' block, options changed will be reverted back to its former
684 value when the account is left (e.g. by switching to `null'):
687 alternates sdaoden@users.sf.net sdaoden@users.sourceforge.net \
688 sdaoden@googlemail.com sdaoden@gmail.com
689 set Sign="\n--steffen\nForza Figa!" sign="\n--steffen"
690 set smtp=smtp.gmail.com smtp-auth=plain smtp-use-starttls
696 set from="Steffen \"Daode\" Nurpmeso <sdaoden@gmail.com>"
701 set from="Steffen \"Daode\" Nurpmeso <sdaoden@users.sf.net>"
709 neither of *Sign*, *sign*, *smtp** nor *from* should be set.
710 Please see the manual for more.
711 TODO - neither command-ghosts nor alternates etc. are yet tracked
712 TODO - we should have a boolify() so as to say 'localopts yes' etc.
715 - New command: `cwd' (print current working directory).
716 Also fixing the `chdir' return value. [eff4397c]
718 - The *ssl-method* now allows explicit setting of 'tls.1.1' and
719 'tls1.2' values. [c66b4196]
721 - When sending to display, be aware that filenames in MIME parts may of
722 course be MIME-encoded! [1454be03]
724 - *hostname* is now honoured even if *smtp* is not set. (We always
725 supported *from*, so why not *hostname*?)
727 - The `-u user' option now acts identically to setting the $USER
728 environment variable and both now tend to mean something like
729 "impersonate as user in some aspects". Note that we have always used
730 the latter in one or the other way, and `-u user' always ment more
731 than just "open mailbox of user", so i think this change sharpens the
732 edge in the right direction. [09632731]
734 - Filename argument quoting has been tweaked for (some) function(s which
735 take a filename argument last). The following snippet as reported by
736 Gavin Troy should work now: [2bb9b80e]
738 ? mv +inbox.Junk\ Mail
740 - The GNU implementation of wordexp(3) is also (i've added a workaround
741 for the very same bug for Mac OS X in S-nail v14.3 [63273772]) buggy,
742 which causes segmentation faults when expansions failed (`fi &VOID').
746 - The `fi' command no longer uses the (possibly truncated) display
747 version of a filename, but the full path. [5cd85b07]
749 ChangeLog (purely technical)
750 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
752 - Large rework of internal structure: bundle inclusion of most of the
753 external and the content of most of the internal #include files in the
754 new nail.h. If that would have been done very first bugs like the
755 infamous MAXPATHLEN bug as reported by Paul Vojta (see v14.4.2) would
756 never have occurred. [21f3155b]
758 - Support for -fstrict-overflow cc(1) flags. [topic/strict-overflow]
760 - Fixed the quotation filter which yet allocated memory even if not
763 - String relaxation reduces memory pressure rather drastically when
764 working with many (especially MIME) mails at a time, e.g., when
765 writing a modified mailbox. Before all messages of a mailbox had to
766 be worked without releasing any memory in between, now we give back
767 memory (to our pool, not the system) after each and every message.
770 - The other memory source now uses bound canaries, which also found some
773 - We now use the EL_PROMPT_ESC editline(3) mode for prompting, which
774 should offer the possibility to use coloured prompts etc. with
775 (even those) editline(3) (versions which do offer it -- older versions
776 should just do fine by themselves).
777 S-nail uses the special trigger control character \1. [ea30d818]
780 Note however that all tested editline(3) versions are buggy and
781 either don't get it right (`\1COLOR-ON\1stuff\1COLOR-OFF\1') or are
782 incapable of proper repainting (`\1COLOR-ONstuffCOLOR-OFF\1').
784 - We now use the MD5 digest code from the OpenSSL library if that is
790 Many thanks: Gaetan Bisson, Stephen Isard, Jérémie Courrèges-Anglas,
791 William Yodlowsky, and Adam Sjøgren from GMANE.org!
793 ChangeLog (packager-affine)
794 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
796 - The packager-install: target has been fixed. [a8c1b0b]
797 (Gaetan Bisson and William Yodlowsky)
799 - As suggested by Gaetan Bisson the several build system tasks are now
800 individually addressable, i.e., 'make [OPTIONS] config', 'make build',
801 'make test', 'make packager-install'); nothing changes unless you want
802 to, in which case: please see INSTALL. [4d3b799]
804 The new target 'test' will call cc-test.sh with its new --check-only
805 option which will only perform the (too few) function tests on the
807 And cc-test.sh will no longer create output files, but simply echoes
808 to STDOUT and STDERR. [629e1ee, 786f219]
811 - The default configuration file now sets *bsdannounce* and *bsdflags*,
812 all in one line, as suggested by William Yodlowsky.
813 (If *header* is disabled, *bsdannounce* is ignored, but *header* must
814 be enabled by default according to POSIX, and *bsdannounce* is just
815 the same as *header*, but for the folder-switched event. Thus setting
816 *bsdannounce* is the more sane default, imho.) [6161f10]
819 - Announcement messages are now tagged '[ANNOUNCE]'. [26e1b35]
820 (Tagging suggested by Stephen Isard and Jérémie Courrèges-Anglas)
822 - The manual NAME now includes the version (but it's somewhat ugly).
828 - When switching folders when in compose mode, message attachments
829 become invalid. For v14.4.5, at least warn when this happens.
832 - When reading multipart/alternative messages which do not contain
833 a text/plain part, the (most likely HTML) part is not displayed (even
834 if S-nail is configured to display HTML). The reason is a bug i've
835 introduced with [0d43a999] (Change "Part X:" display message..,
836 2012-12-20). (Note that the committed fix i've posted to the list was
837 not correct either and has been fixed itself.) [225c02b, ecfa149]
842 Thanked, Gavin Troy, Gaetan Bisson.
844 - Fix output buffer confusion that would have occurred when parts of
845 a multipart mail had a pipe command set. Longer story in [e75d16dd].
848 - The makefile now supports a `packager-install' target that bypasses
849 the reevaluation of the configuration (after checking that there is
850 one) and directly steps ahead to the install process.
853 - Notes in INSTALL that CFLAGS and LDFLAGS need to be overwritten from
854 within (conf.rc or) the command line.
860 I convey special thanks to Karol Błażewicz and Gaetan Bisson.
862 - The new build system didn't allow to overwrite CFLAGS= when used in
863 conjunction with GNU make(1). To make a long story short, removing
864 a `.POSIX:' directive from the makefile fixed the problem. Luckily.
867 - More INSTALL notes for UnixWare 7.1.4, which suffers from the same
868 problem: here the fix is to use the -e option of make(1).
870 - Karol Błażewicz reported a segmentation violation he got when using an
871 Arch Linux S-nail test package, and Gaetan Bisson informed me about
872 that. The problem was that we didn't assign the resulting default
873 address (which gets used when *from* is not set) to the result which
874 gets used, effectively resulting in a NULL dereference. [cfd60479]
879 Many thanks to Paul Vojta.
881 - On GNU/Linux there is no MAXPATHLEN constant defined by default, as
882 this is a non-standard legacy constant. Mozilla ran into this some
883 time ago, though a bit different [1]. It made it easier for S-nail.
885 [1] <https://bugzilla.mozilla.org/show_bug.cgi?id=412610>
887 We could include `sys/limits.h' to get at MAXPATHLEN, there it is
888 defined to be PATH_MAX, but let's just include the standard `limits.h'
889 and ensure MAXPATHLEN ends up >= PATH_MAX. With this condition being
890 true even FORTIFYd sources won't bail with reported buffer overflows
891 because realpath(3) expects a buffer of PATH_MAX bytes. [bee5e57c]
894 - With the builtin LINE_EDITOR, ensure proper interaction with GNU
895 rlogind(8), which is alone in its quest to set the ISTRIP termios(4)
898 - Bugfix a codepath that would have prevented compilation when
899 HAVE_ICONV is not set.
900 While there, allow to unselect message attachments when using the `~@'
901 tilde command interactively, which i mysteriously had forgotten when
902 allowing selection of 'em. (oops?) [4f58ffea]
904 - It's now easier for packagers to get at debug-enabled CFLAGS; simply
905 use WANT_ASSERTS=1 (should not be enabled in shipouts, please).
908 - Fixed a terrible bug that i've introduced in november 2012, that would
909 have corrupted MBOX files when using the `resend' command. (The
910 so-called "From_ line" would have been quoted to ">From_ line" instead
911 of simply being stripped.) [19d449e2]
913 - Fixed a SIGSEGV for the builtin LINE_EDITOR, that would have occurred
914 if a history traversal (^B or ^F) would have been continued by
915 a reverse history completion (^R).
916 While there, avoid some multiple-beeps-in-a-row that yet occurred due
917 to code reuse, and document that ^G etc. reset the multibyte state
920 Also, the expand-on-tab code could have excessed line input maximums,
921 e.g., after `? /usr/bin/*<Tab>'. This was of course known, but
922 i wanted to keep it because all tested (modern) terminals "mess up but
923 won't break", and thus made it possible to use the data, even if it's
924 visual representation was messed up. The real solution will be much,
925 *much* more complicated, i.e., show possible *completions*, page-wise,
926 etc., i.e., just like is known by tab *completion*. This will need
927 far more time because it doesn't make sense to embed such complicated
928 code into the current bed.
929 Now i've chosen to simply don't display excess, but replace the
930 content with a message that says that there was excess. It simply
931 looks better. [0320c8ba]
933 - I've changed the use of `[?]' as a replacement sequence for invalid
934 / non-displayable characters to `?' (again). There are still code
935 paths (from the original codebase) which use the real Unicode
936 replacement character instead, so our display is still not unique.
937 On the long term the codepath can anticipate in all levels wether
938 use of Unicode is possible, so that, then, we will be unique again,
939 using either only `?' or the Unicode replacement character. [faf6380]
941 - I've anticipated in v15.0 and implemented *quote-fold* as a stream
942 filter. It is now multibyte safe and takes into account the visual
943 width of characters, i.e., ideographs etc. It is working almost as
944 good as an algorithm can work that looks at data linewise, but is yet
945 experimental and incomplete in that it will break lines even if only
946 whitespace or a backslash escape follows. It is code that is only
947 a few hours old, which is why it is not enabled by default. [
954 - Fix some harmless stylos and typos in the manual and `conf.rc'.
957 - Ensure *complete* proper cleanup on signal-caused configuration run
960 - Bugfix: reenable empty configuration variable overrides, as in
962 $ make install SID= NAIL=mailx ...
965 - Bugfix: rename the `conf.rc' variables SHELL, LISTER and PAGER because
966 they clash with the POSIX standard variables of the same names, which
967 hurts now that the configuration is run through the shell itself.
968 The configuration names are now XSHELL, XLISTER and XPAGER (ouch).
971 - nail.rc: comment out some non-portable S-nail(1) specifics, for those
972 who install this file as mailx.rc or so, somewhere. [3f14b01]
974 - From now on S-nail will use simple version tags, as, e.g., `14.4.1',
975 i.e., no more `s-nail-14.4.1'. [a75437d, 183d59c] (Jürgen Daubert)
977 Also move UAGENT out of `version.h' [f7be5be]
979 Uh! v14.4 must have originated in a bad dream; good it's vanished.
984 Thanks to the entire vivid and virile S-nail(1) user community is
985 proper, especially Stephen Isard, Gavin Troy, Martin Neitzel.
986 Not to forget Ryan Kavanagh and Ayan George.
988 Note this time the changes are in reverse order, i.e., oldest first.
993 15fbe09 ^bf9173f 'topic/varmac-unite'
994 Simplification and unification of variable and macro handling
995 40f6f58 ^15fbe09 'topic/cledit1'
996 Command line editor; new manual section `Line editor'
997 ad28a32 ^40f6f58 'topic/termsize'
998 Honour POSIX mailx(1) and respect $COLUMNS and $LINES on startup
999 dc3cd49 ^a446fd8 'topic/qf'
1000 You don't wanna know
1001 b8738f7 ^0651fd0 'topic/spam1'
1002 Interaction with SpamAssassin; new manual section `Handling spam'
1003 5419d6f ^b8738f7 'topic/make1'
1004 Reworked build system; please read `INSTALL' and `conf.rc'
1005 9ab4d6b ^5419d6f 'topic/list1'
1006 Slightly tweaked message thread display, fix `:u :r' to mean it
1011 - The default PAGER is now more(1). (But read on.)
1013 - The `echo' command is now compliant, and fully supports XSI.
1015 - The `group' and `ungroup' command aliases have been removed, they are
1016 `alias' and `unalias'.
1018 - We now have the capability of line editing and history.
1019 One may choose from not less than three different implementations:
1020 a builtin editor as well as possible linkage against BSD editline(3)
1021 and also a GNU readline(3) compatible layer.
1022 Please read the new manual section `Line editor'.
1024 Input is now compliant in that an interactive line may be continued
1025 after escaping the newline character with a backslash.
1026 [topic/cledit1] (all of them)
1028 The *prompt* variable may now contain shell escapes, just like the
1029 `echo' command. [0938d8a]
1030 As a special extension the new \? escape, when used within *prompt*,
1031 will expand to the exit status of the last command. [41076d2]
1033 - The POSIX standard environment variables $COLUMNS and $LINES are now
1034 honoured upon startup. [topic/termsize]
1036 - The `help' / `?' commands now support abbreviation, i.e.,
1037 ``$ ? unc'' should now find `uncollapse'. [7b86195]
1039 - The `~' abbreviation that has been introduced as an alias for `call'
1040 is now a real command, not a magic shortcut. [9987289]
1042 - The new variable *quote-as-attachment* can be used to additionally
1043 embed the quoted message as a `message/rfc822' MIME attachment.
1046 - The compose-mode command `~@' will now attach messages from the
1047 current mailbox if given a filename of the style `#NUMBER'.
1048 Please read the corresponding manual section `Tilde escapes', though.
1050 - The `WANT_JUNK' and `WANT_SCORE', as well as Gunnar Ritters junk mail
1051 management have been removed.
1053 Instead S-nail(1) can now support interaction with SpamAssassin, but
1054 sofar only via the spamc(1) / spamd(1) client / server pair of
1055 programs that ships as part of SpamAssassin. The new configuration
1056 directive `WANT_SPAM' controls wether this feature is desired.
1058 Please read the new manual section `Handling spam'.
1059 [topic/spam1] (Martin Neitzel)
1061 (S-nail(1) is now *definitely* floating-point free.)
1063 - The configuration and make system have been overhauled / reorganized.
1064 The configuration is now in `conf.rc', also contains directives like
1065 `PREFIX' etc, and is always read in. However, only those directives
1066 which are not yet set (via environment or command line overwrites) are
1067 incorporated into the set of configuration options. Therefore
1072 will now build S-nail(1) twice, because of the changed configuration.
1074 Note that `WANT_GSSAPI' is now by default disabled, which shrunk
1075 a freshly started s-nail image by more than 30 percent.
1077 We're not finished yet in that there is no dependency graph etc.
1078 Please do read `INSTALL' and `conf.rc'.
1081 - Message selection has been slightly bugfixed in that `:u :r' really
1082 means `:u' AND `:r'. Compared to NetBSD Mail(1) it's still a shame.
1084 Threaded message display has been slightly changed in that within
1085 a thread identical Subject: lines are not repeated. It may not be
1086 perfect yet due to the general list / thread state. [topic/list1]
1088 - If, upon startup, the environment variable `NAIL_NO_SYSTEM_RC' is set,
1089 then the system wide initialization file isn't read, just as if the
1090 `-n' option had been given. [1b31535]
1092 - It is now possible to use CTRL-C during connection hangs. (But in
1093 general error recovery capabilities of the socket related
1094 infrastructure is non-existent, practically speaking.) [45a9f36]
1096 - *quote-fold* has been temporarily disabled, as it is not multibyte
1099 No review for v14.4. And today is Friday, the 13th. Ouuuh!
1104 I should *maybe* should have and want to give prominence to
1105 Martin Neitzel for this, i maybe have misunderstood.
1107 - Bugfix *synchronous* *pipe-** execution..
1109 Well, unfortunately yet another newly introduced bug slept in
1110 S-nail v14.3[.1] -- [a8d724b3, Add @ and @& shell command prefixes
1111 for pipe-MIMETYPE, 2013-05-03] falsely changed the waiting state
1112 for subprocesses, as has shown up by a HTML-only mail on the
1114 'Seems i'm collecting one line fixes in this codebase; this needs
1115 to change in the future.
1120 I want to give prominence to Juergen Daubert (jue AT jue DOT li), who
1121 reported that i've broken plain-old unfancy send mode in 14.3.
1123 + Ok, i'll hope we're out of new errors for the v14.3 series with that.
1125 - New variable: *batch-exit-on-error*.
1126 Only works if the new -# command line option has been given, and will
1127 check the "current" exit status whenever one operation completes
1128 (S-nail returns to the command prompt).
1129 If the exit status implies error (e.g., sending the last message
1130 failed) then we exit forcefully with that error status. (The normal
1131 behaviour is that the status is reset when the command loop ticks.)
1134 - While here again, i've added the new -# command line option.
1135 This is the first step to implement a reliable batch mode;
1136 unfortunately it still selects the users system mailbox on startup,
1137 because we simply cannot go to "no" mailbox for quite some time -- at
1138 some future time we will be able to go to some VOID thing, and then
1139 this will end up as a rather efficient batch mode.
1140 For now it sets *dot*, *emptystart*, *noheader* and *sendwait*, and
1141 also implies the -~ command line option. [7549569]
1144 printf "m ${MBOX}\n~s subject1\nE-Mail Körper 1\n.\n" &&
1145 printf "m ${MBOX}\n~s subject2\nEmail body 2\n.\n" &&
1147 ) | MAILRC=/dev/null "${NAIL}" -n -#
1149 - Also, -N set *header* instead of *noheader*. [7b4a13f6]
1152 - Plain old unfancy invocations like
1155 $ echo bla|s-nail ./FILE1
1157 had been broken (by [522cb3ec]). [260e19d]
1163 Thanks to Gavin Troy (gavtroy AT gmail DOT com) who inspired the @ and
1164 @& pipe-command prefixes.
1169 - S-nail has been registered at Coverity Scan, and the third build
1170 (after topic branches *coverity-444* and *coverity-444.2*) produced no
1171 more errors. (<http://scan2.coverity.com/projects/444>.)
1172 (Then i used POP3 and IMAP and fixed some SIGSEGV. ;) Still didn't
1173 look at S/MIME, Maildir, caches etc... o()
1175 - S-nail v14.3 doesn't produce any spurious linker warnings on
1176 OpenBSD 5.3; all (correct!) use cases of strcpy() and strcat() have
1177 been replaced. [7bdf330, 2c8d7cb]
1179 - This is the first release with a (though very short) review -- i'm
1180 slowly getting comfortable with the code. (But i'm too stupid to
1181 perform reviews on patches, 'always did reviews on C++/Perl/xy
1182 classes. Aaah, how beautiful ... objects.)
1187 - It is now possible to "call" macros without using the `call' command
1188 by prefixing them with a tilde, as in
1197 - Added the *pop3-bulk-load* option.
1198 Yes, there are mailing lists etc. which use plain text email, and,
1199 there, headers are often more data than the body, so it doesn't make
1200 sense to download the headers twice (unfortunately POP3 doesn't
1201 support a BODY command; if only it would support a RETRDELE command..)
1204 And yep, from this changeset on i personally use S-nail even over the
1205 network, no longer my stale and incomplete S-Postman. And i can tell
1206 you, this damn thing is so silent, i always set *verbose* not to go
1207 grazy ... but .. i hate to say it .. the healing will take time.
1209 - POP3 will now try to use APOP authentication automatically; thus the
1210 *use-apop* stuff has been replaced by *pop3-no-apop* options (just in
1211 case there are POP3 servers which advertise they support APOP but in
1212 fact fail to do so; anyone?) [6c3c5575]
1214 - Some IMAP segmentation violations have been fixed:
1216 ? fi imaps://user1@localhost
1217 Password:Interrupt <- CNTRL-C
1218 ? set imap-auth=cram-md5 <- hey, 'forgot to set correct auth
1219 ? fi imaps://user1@localhost
1220 IMAP write error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown
1223 And also, when *folder* was set to an IMAP account but hasn't been
1224 opened yet, and no IMAP account ever has been opened, a string
1225 comparison against a NULL pointer yet caused a SIGSEGV, too.
1228 - `set folder=' now tolerates `%:' and expands PROTOs stuff etc.:
1230 ? short xp %:imaps://user1@localhost
1233 Pure convenience so that it doesn't need to be typed twice (still no
1234 completion in sight...). Note that setting *folder* to a POP3 box
1235 will now be actively rejected. [b12b17f5]
1237 NOTE: while implementing this i've detected another dead-end
1238 miscondition in S-nail -- you really should ensure that your target
1239 folder/box is connected before you leave your current POP3/network
1240 based folder, if there is data to be moved to the target (i.e.,
1241 mbox). This problem will persist for a long time due to the way the
1242 entire codebase functions; i hope i can find a short/mid-term
1243 solution, but the real healing will take years. The mentioned
1244 solution would at least make S-nail interruptable, currently we get
1245 stuck and interrupts are blocked...
1247 - If you're using S-nail on Mac OS X and have seen some segmentation
1248 faults when expanding shell stuff then you may be pleased to hear that
1249 S-nail now works around an Apple bug. [63273772]
1251 - The builtin mime.types have been corrected and a lot of new ones have
1252 been added. New data from
1253 <http://svn.apache.org/viewvc/tika/trunk/tika-core/src/main/resources/\
1254 org/apache/tika/mime/tika-mimetypes.xml>, thanks! [8072fcb6]
1256 - BEWARE: handling of command line arguments has changed a bit!
1258 1. The -D, -d, -E, -i, -N and -v command line options are now
1259 implemented by means of setting the respective option, as via -S.
1260 (This means that from now on resource files can only *temporarily*
1261 overwrite command line arguments.)
1263 2. The -I and -T command line arguments have been dropped.
1264 It seems Gunnar Ritter stopped developing nail/Heirloom mailx once he
1265 started implementing Newsreader functionality. It'll take a long time
1266 until we get there, so for now drop all the Newsreader stuff.
1268 3. Handling of -r has been changed. E.g.:
1270 s-nail -A test -Snoeditalong -r 'La mort est <fem@me>' -d
1271 ? set from=bummer@m1.com
1275 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t1"
1276 ? set from=bummer@m2.com
1279 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t2"
1283 s-nail -A test -Snoeditalong -r '' -d
1284 ? set from=bummer@m1.com
1288 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m1.com" "t1"
1289 ? set from=bummer@m2.com
1292 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m2.com" "t2"
1294 [*main-fun-cleanup* topic branch]
1296 - *smime-sign-include-certs-** stuff works again, oops.. [9a8597c6]
1298 - A whole lot of smallest and small fixes due to registration at
1299 Coverity Scan, as project 444. Error handling in S-nail is ridiculous.
1300 [*coverity-444* and *coverity-444.2* topic branches. The sheer number
1301 of fixes was the reason to sit down and go for unplanned S-nail v14.3]
1303 - *idna-strict-checks* has been dropped. It's silly to have in a MUA,
1304 especially given that GNU LibIDN doesn't ship with a lot of rules.
1305 We were able to drop quite some code (and a use-after-free, too :().
1308 - The ~p tilde command displays attachments more verbose.
1309 Until the big big MIME and send layer rewrite :) this is intermediate
1310 since until then we do not really know neither MIME type nor charset
1311 of an attachment at the time this is displayed (for sure). Yet
1312 i think it's nicer to show what we have than keep it the way it was.
1315 - @ and @& shell command prefixes have been added for the pipe-MIMETYPE
1316 mechanism. The former suppresses filters if multiple messages are
1317 displayed at once, the latter adds asynchronous program execution on
1318 top of that. E.g., to display PDF documents, but only if you
1319 *explicitly* address the message *alone and by itself*, and without
1320 blocking S-nail and the $PAGER, do:
1322 set pipe-application/pdf="@&cat >"${TMPDIR}"/s-nail${$}.pdf;\
1323 mupdf "${TMPDIR}"/s-nail${$}.pdf; rm "${TMPDIR}"/s-nail${$}.pdf"
1325 (Inspired by Gavin Troy.) [a8d724b3]
1327 Note: most of that had been posted to nail-devel@ already, but it was
1328 tweaked ([251b636]) so that you now *really* have to say `p MSGNO' to
1331 - The NETLESS CONFIG= has been removed; it is almost identical to
1332 MINIMAL now (i.e., without WANT_JUNK and WANT_SCORE).
1334 - WANT_JUNK and WANT_SCORE have been disabled by default.
1335 They don't seem to be too useful; i hope i can implement
1336 a SpamAssassin hook for (downloaded) mail messages for v14.4.
1337 If so, expect these two "modules" to become removed completely.
1342 Another unplanned (minor) bugfix release after Gavin Troy (gavtroy AT
1343 gmail DOT com) pointed out that MIME CTE decoding was broken, who
1344 i therefore want to give a lot of prominence right here.
1346 - Fix MIME content decoding which has been broken by [01c0e135].
1353 An unplanned (minor) bugfix release after i've found two bugs today and
1354 heard from Jérémie Courrèges-Anglas (jca+nail AT wxcvbn DOT org) that
1355 there exists a S-nail OpenBSD package.
1357 I want to give prominence to the following people that helped to
1358 improve S-nail(1) during this development cycle, in order of
1359 appearance: Dirk Peters (peters AT schwertfisch DOT de).
1361 Thank you very much, and best from Germany!
1363 - Some warnings of newer clang(1) versions were silenced, including yet
1364 another alloca(3) problem (see *memtracer* topic branch in v14.0
1367 - Tweaking the MIME boundary detection left a little hole that could
1368 cause boundaries not to be detected, as has been shown by a Microsoft
1369 Word generated mail on the ICU list. [11e5fb5b]
1371 - A format string could overflow bounds if unrealistic
1372 (18446744073709551615) line numbers or message sizes would have been
1373 produced. [faa65c40]
1375 - An algorithmic error could cause overlong lines which wrapped around
1376 to the next display line. [ade52660]
1379 v14.2, 2013-03-15 [v14.1, 2013-03-12]
1380 -------------------------------------
1382 I want to give prominence to the following people that helped to
1383 improve S-nail(1) during this development cycle, in order of
1384 appearance: Martin Neitzel, Christos Zoulas, Stephen Isard, jgw@txo.org
1387 Thank you very much, and best from Germany!
1389 + v14.2 differs from v14.1 only by one commit, one that fixes
1390 (mime_fromhdr(): partial rewrite using n_iconv_str(), 2013-03-12),
1391 which i hastily implemented just hours before the release of v14.1,
1392 and simply shouldn't have made it (into there).
1393 The v14.1 tarball has been removed from the server.
1395 - A fix for the quoted-printable codec: "message truncation" occurred
1396 when a mail maliciously used a soft linebreak to escape the linebreak
1397 of a completely empty line.
1398 (That resulted in 0 written and 0 leftover bytes, a condition that was
1399 declared erroneous back in november 2012 when i started handling I/O
1402 - The "folders" command will work again when given an argument.
1403 A fault of mine introduced in (cmd1.c: expand() may fail, 2012-10-23).
1405 - The Base64 codec has been touched again, and we are finally capable to
1406 perform sequential decoding; this was targeted for the MIME/send layer
1407 rewrite, but it actually was possible today.
1408 The result as seen in ps(1), running on the Base64 encoded HTML5
1409 standard (4622545 bytes HTML, with a NUL appended to force Base64
1410 encoding, resulting in a 6244793 bytes email):
1412 7420 s006 S+ 2:22pm 0:10.65 plain-nail -f HTML5
1413 1440 s006 S+ 2:23pm 0:00.36 ./s-nail -f HTML5
1415 (So the only thing that is left for a good throughput is sequential
1416 decoding of quoted-printable encoded parts that maliciously use soft
1417 linebreaks to convert an entire part to a single line. And i've seen
1418 that from Apple Mail.)
1420 - New option: *mime-allow-text-controls* (rather long manual entry).
1422 - *smtp-auth-password-user@host* and *smtp-auth-user-user@host* will
1424 (Reported by jgw@txo.org in November 2011, fixed by Gavin Troy in
1427 - Most *headline* formats now do support the '-' left-alignment flag.
1428 Note that you most likely have to change your *headline* accordingly.
1429 (The still missing %n format is one reason why there will be v14.2.)
1431 - *datefield* and *datefield-markout-older* can now be set to
1432 strftime(3) format strings (except %n).
1433 (From Stephen Isard's wishlist.)
1435 - A possible SEGV has been found and also fixed by Stephen Isard.
1436 (The "legendary" cross-world stereo fix!)
1438 - Wow! S-nail will finally compile on GNU based Linux systems like
1439 Slackware 14 etc. (Found while hunting bug reported by
1442 - New option: *datefield-markout-older* can be used to choose
1443 a different date display for mails that are older than six months,
1444 in equal spirit to what POSIX describes for the -l option of the ls(1)
1445 command (Stephen Isard).
1447 - (Exotic) Years are (would) now (be) interpreted correctly according to
1450 - CRAM-MD5 usage has been fixed.
1452 - *folder* updates are now tracked when set, and we will show the
1453 realpath(3) name of it, showing PREFIX..SUFFIX if that wouldn't fit on
1455 Tracking updates made it also possible to perform other more expensive
1456 tasks when setting *folder*, so that it is now possible to do
1462 et cetera (both ideas by Christos Zoulas).
1464 - Bugfix for the ~@ tilde-escape in non-interactive mode.
1465 (readtty(): quick shot: work in pipelines (on non-TTY).., 2013-01-25)
1466 introduced the possibility to "read data from the terminal" (STDIN
1467 that is) in non-interactive mode.
1468 The manual documents that attachment input must be terminated with an
1469 empty line, but if that had been omitted, as in the example below, we
1470 would have yet entered an endless loop.
1472 $ cat <<_EOT | /s-nail -~ -s boom ./OUT
1478 - Alias expansion will now be performed for members of Reply-To: fields
1481 - Decoding quoted-printable will now be more relaxed.
1482 (Even though the standard says that users should be given a hint when
1483 input is not absolutely clean; a possible warning will be added later,
1484 when we have an error message ring.)
1486 - New option: *mimetypes-load-control* can be used to control which of
1487 the mime.types resources will be loaded.
1489 - The builtin default mime.types have been extended a bit.
1494 I want to give prominence to the following people that helped to
1495 improve S-nail(1) during this development cycle, in order of
1496 appearance: John Dodson, Gianluca Ramunno, and Anon Ymous from the
1502 - Encoding defaults to *quoted-printable* not *8bit*.
1503 This has no technical background except that i think it's the better
1506 - Small progress for the "getting stuck due to the current folder
1507 becomes inaccessible due to whatever reasons" problem.
1508 (schdir(): realpath() local files before leaving CWD.., 2013-01-08)
1510 - The names of temporary files have changed. Whereas not all uses of
1511 temporary files already use really meaningful names, it has yet become
1512 possible to use the pattern "*mail-*"; or, to be compatible with
1513 NetBSD Mail(1) in one go, "*mail*". (E.g., in my ~/.vimrc you'd read:
1514 :au BufRead,BufNewFile *mutt*,*mail* setl fenc= | setf mail
1515 [the *mutt* is a leftover from times when i've used MUAs that suck].)
1520 - The Quoted-Printable MIME handling has been rewritten completely.
1521 We now correctly encode files with the MS-DOS newline sequence (CRLF).
1522 (Part of the *mime-cte* topic branch.)
1524 S-nail(1) continues to be able to handle text messages and text
1525 attachments without a trailing newline, but because these
1526 Content-Transfer-Encoding related things are now handled by the C-T-E
1527 layer instead of by sendout.c a text message body that comes in as
1528 part of a complete message via the -t command line option will loose
1529 the missing final newline (i.e., it'll gain one).
1530 This problem does *not* occur when *only* the message body comes in
1531 via STDIN, as in 'cat FILE | s-nail', but *only* when the -t option is
1533 (sendout.c: does no(t/ longer) know about CTE internals!, 2013-02-09)
1535 - Filename arguments for -a are now processed *after* all the resource
1536 files have been loaded etc., so that the usual "folder" specifics can
1537 be used (provided that proper care for shell quoting was taken).
1538 ((main(): delay -a processing.., 2013-01-10), as a part of the
1539 *mainaflags* topic branch.)
1541 - (d38c5bd, When the write command asks.., 2004-11-23) added support
1542 for pipes when saving attachments during a "write" command.
1543 It however used the wrong SIGPIPE signal handler; e.g.:
1545 Enter filename for part 2 (application/x-gzip): |exit
1548 Of course, it still performs a jump and that most likely leaves memory
1549 chunks behind, thus causing some memory leaks. This will be
1550 a long-term problem (you may want to read [mime.c:fwrite_td(): TODO
1551 notes on unfixable leaks, 2013-01-14] for more).
1552 (send.c:sendpart(): fix longjmp() SIGSEGV.., 2013-01-29)
1554 - Fixed a name quoting regression that i've introduced in
1555 (Rewrite *extract().., 2012-10-20), that would have caused
1556 "x \"y\" z" to become "x"y" z" instead of "x "y" z".
1557 (S-nail still does not really have RFC compliant parsers, just as
1558 NetBSD Mail(1) has, i.e., there are structured and unstructured fields
1559 etc... I hope i can provide them in v15.0.)
1560 (names.c:yankname(): fix quote regression.., 2013-01-29)
1562 - The IDNA conversion now assumes domain names are specified in
1563 *ttycharset*, rather than in the LC_CTYPE locale charset.
1564 I.e., it integrates into the usual character set specifications.
1565 (IDNA: honour *ttycharset* for domain names, 2013-01-18)
1567 - The new *editalong* variable will automatically spawn an editor when
1568 composing a mail in interactive mode, just as if `~e' was given.
1569 (Add new *editalong* variable, 2012-01-07)
1571 - The manual has been converted to mdoc.
1572 (The manual has been converted to mdoc, 2012-12-28)
1574 - The ~@ tilde escape, when given filename arguments, will treat the
1575 arguments as a comma-separated instead of a whitespace-separated list.
1576 (collect: change separator of ~@ tilde escape.., 2012-12-28)
1578 The interactive mode of ~@ has also been changed, rather massively.
1579 Please do reread what the manual says.
1580 ((collect: support multiple attachment charsets.., 2013-01-23), as
1581 part of the *attach* topic branch.)
1583 - Thanks to Gianluca Ramunno (ramunno DOT gianluca AT gmail DOT com)
1584 S-Nail will no longer try to issue a STARTTLS command when it is about
1585 to establish a SMTPS connection, a task that logically fails since the
1586 connection is already secured.
1587 (Interestingly the nail codebase performs the necessary test for IMAP
1589 While here the undocumented nail v11.0 *smtp-use-tls* legacy option
1591 (Fix SMPTS with a set *smtp-use-starttls*.., 2012-12-22)
1593 - The RFC 4155 compliant MBOX quoting is now exclusively used, the
1594 shitty *posix-mbox* variable has been removed again.
1595 (Shitty because i've implemented RFC 4155 compliant MBOX quoting and
1596 tested it, then added *posix-mbox* for those who liked the old
1597 behaviour and did not re-test -- the final code path was buggy.)
1599 In mails newly created and saved by S-nail(1) no From_ quoting at all
1600 will be used no more, but instead the rewritten MIME file classifier
1601 will detect unquoted From_ lines and enforce quoted-printable encoding.
1602 (This is an approach that is S/MIME compatible all through the way as
1603 the file data is not modified at all, but only encoded, so that the
1604 data checksum is not changed.)
1606 In yet existent mails that S-nail copies or moves around without
1607 reclassification an RFC 4155 compliant From_ line detector will apply
1608 MBOXO quoting (prepend a single '>') as necessary.
1609 Different to the old MBOXRD behaviour S-nail will neither quote yet
1610 quoted From_ lines ('>>From xy' -> '>>>From xy') nor will it unquote
1611 one quote level when reading etc. mails ('>> From xy' -> '>From xy').
1612 As a result the code could be simplified.
1614 This changeset also incorporates a fix for NetBSD PR bin/47453, as
1615 reported by Martin Brandenburg. I.e., some mailers, noticeably
1616 UW-imap (with MBX format only?), use non-compliant From_ lines with
1617 RFC 822 date specifications. Be aware of 'em.
1618 (RFC 4155 MBOX, and drop *posix-mbox* and foldergets().., 2013-01-06)
1620 - *rfc822-show-all* has been removed.
1621 It didn't work properly for more complex MIME structures, like
1622 message/rfc822 messages with attachments etc., just as i've seen today
1623 on the file(1) mailing list.
1624 So, instead of hacking it now i've dropped it and will come back with
1625 a better solution when the MIME and send layers have been overhauled.
1626 I.e., the real intent was to be able to specify that an embedded
1627 message/rfc822 is treated as a *unity*, and that's the goal.
1628 (Drop *rfc822-show-all*, 2013-01-23)
1629 [The manual will be adjusted in a different commit.]
1631 - *rfc822-no-body-from_* has been renamed to *rfc822-body-from_*.
1632 It thus must be set explicitly.
1633 On the other hand it now catches all cases...
1634 (*rfc822-no-body-from_* -> *rfc822-body-from_*, 2013-01-23)
1635 [The manual will be adjusted in a different commit.]
1637 - The new *charset-7bit* (defaults to US-ASCII) and *charset-8bit*
1638 (defaults to UTF-8) have been introduced.
1639 These are used if seven bit clean data is to be sent, and no
1640 *sendcharsets* are set or the convertion of all of them failed,
1643 - There is no functional change unless there is iconv(3) support.
1644 - There is no functional change unless you set them.
1645 (Introduce *charset-8bit* and *charset-7bit* variables.., 2013-01-18)
1646 [The manual will be adjusted in a different commit.]
1648 In addition the new *sendcharsets-else-ttycharset* variable can now
1649 be used to automatically use *ttycharset* as a *sendcharset(s)*,
1650 regardless of the new *charset-8bit* variable.
1651 (Add *sendcharsets-else-ttycharset* variable, 2013-01-24)
1652 [The manual will be adjusted in a different commit.]
1654 NOTE: before we apply charset conversion we now perform a string
1655 comparison to see wether character sets are identical. If the strings
1656 match (case-insensitively), then *no* conversion is performed.
1657 This means that code like
1659 $ printf "LATIN1: \0376" | s-nail -Ssendcharsets= -s boom ./out.txt
1661 *succeeds* in an UTF-8 environment now, whereas older versions would
1662 fail with an "illegal byte sequence" error (unless the iconv(3)
1663 library of the system would not perform any conversion that seems
1664 superflous, of course).
1666 I thought about making this optional, but, in fact, if this would be
1667 done in an environment without iconv(3) support then the result would
1668 be equally corrupt. And the way it is now we save the expensive and
1669 superflous conversions. (See TODO for more.)
1671 Please *do* reread the manual section "Character sets".
1672 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1674 - An attempt was made to improve MIME Content-XY: detection.
1675 It should be more RFC compliant, and just overall better :);
1676 a simple one-pass classifier cannot match libmagic(3), of course.
1678 This changeset removes support of the long obsoleted (4fee1ef,
1679 2005-01-06) *charset* variable, as well as for the
1680 *maximum-unencoded-line-length* variable that has been introduced in
1681 (48a652bd, 2005-07-26).
1683 For S-nail v14.0 it'll be no longer necessary to do
1685 $ tr -d '\015' < input | s-nail ...
1687 to transport files which use the $-DOS (terminal) newline (sequence).
1688 We still depend upon *sendcharsets* for a while, though.
1689 (Rewrite file-content classification.., 2013-01-02)
1691 - The new *mime-counter-evidence* variable can be used to force
1692 a classification of non-text MIME parts (attachments) by their
1693 filename, i.e., a "reverse-classification" just as would be performed
1694 if S-nail(1) would itself *send* the file(name). This can help
1695 against some stupid MUAs (Apple Mail?) that send .diff etc. files as
1696 `application/octet-stream' parts etc.
1698 At a later time this may become a valued option, causing a temporary
1699 save of unnamed attachments followed by a MIME classification of the
1700 file contents, followed by forced treatment as plain text if it seems
1701 to be human readable. But not yet. Just to warn you.
1702 (Add *mime-counter-evidence* variable.., 2012-12-29)
1704 - The special "pipe-" command "@" can be used to force treatment of
1705 a MIME message part as plain text (e.g.,
1706 'set pipe-application/pgp-signature=@' will henceforth print those
1707 signatures inline and as plain text).
1708 (Introduce the special "@" "pipe-" command, 2012-12-27)
1710 - The MIME types (as from mime.types(5)) will now be cached. Before
1711 all possible sources would have been opened, read and parsed for each
1712 and every message part that required detection of the MIME
1714 The new "mimetypes" command can be used to show or clear that cache.
1715 (Add mime.types(5) cache.., 2012-12-27)
1717 - A small set of MIME types (template: ./mime.types) will now become
1718 compiled into S-nail(1), and be used as a fallback if there are no
1719 ~/.mime.types and/or no /etc/mime.types, or those didn't contain
1720 a matching type. E.g., NetBSD 6 doesn't ship a default database.
1721 Also, file extensions will be matched case-insensitively (case of
1722 attribute values is not specified afaik?).
1723 (Introduce compiled-in mime.types(5).., 2012-12-21)
1725 - The undocumented *charset7* variable was removed.
1727 - The "Message X:" display leader has been changed and will henceforth
1728 be matchable via "^[-- Message \d+ -- \d+ lines, \d+ bytes --]:$".
1729 These lines can no longer be suppressed by setting the *quiet*
1730 option (which was yet possible for print and top, though undocumented).
1731 (Change "Message X:" display message.., 2012-12-20)
1733 - When displaying multipart messages the "Part X:" introductional string
1734 has been changed; if the Content-type: header is not *retain*ed, then
1735 this string will include the part's type and size. Ditto for
1736 Content-disposition: and a mentioned attachment filename.
1737 This is a first step only, for the final version the MIME and send
1738 layers will have to be adjusted. But the string will be matchable via
1739 a "^[-- #.* --]$" regular expression from now on.
1740 (Change "Part X:" display message.., 2012-12-20)
1742 - MIME boundaries in multipart messages are now handled better in that
1743 no boundary string should get through to the display.
1744 (Tweak MIME boundary detection.., 2012-12-20)
1746 - A couple of long standing, even pre-Heirloom mailx(1) memory leaks and
1747 segmentation violations, most of them related to configurations
1748 without alloca(3) support, as well as one leak that i have introduced
1749 when i implemented RFC 4155 MBOX handling, have been fixed.
1750 But S-nail should now survive non-alloca(3) configurations.
1751 (*memtracer* topic branch.)
1753 - The Base64 MIME handling has been rewritten completely.
1754 This was an urgent topic, because the old implementation (a) read in
1755 all lines of a base64 encoded text part, repeatedly resizing a string
1756 storage and repeatedly decoding that string until all the lines have
1757 been swallowed (i.e., or by accident the last decoded byte was
1758 a newline character, and that in turn may of course have fucked up for
1759 multi-octet encodings, dependent on the actual byte-order), (b) used
1760 function local static data to keep state in between multiple
1761 invocations, which messed up multi-byte/-octet encodings like this
1763 �5��ɽ���Aɥ����́��٥��������[lots of data follows]
1765 and (c) did not perform any error checking at all.
1766 The new one does not run into the problem that (a) tried to circumvent
1767 since leftover decoded data (as opposed to leftover *encoded* data) is
1768 transported along the call-chain for later use. It adds a minimal set
1769 of error handling ('may now see "[Invalid Base64 encoding ignored]"),
1770 with more to become possible in later S-nail versions when the entire
1771 layers are reworked. (Until then DOS newline sequences [CRLF]
1772 embedded into base64 will no longer be decoded to Unix LF newlines.)
1773 Base64 encoded lines will now be 76 characters long, as stated (as
1774 a maximum value) in RFC 2045, not 72 as before.
1776 The Base64 code core has been shamelessly stolen from NetBSD's
1777 Mail(1), and i guess it was the second time that this happened :=).
1778 (*base64-rewrite* topic branch; and reworked later on the *mime-cte*
1781 - The string allocation strategy has been tweaked some more to, i think,
1782 a final version (regarding algorithm).
1783 In normal non-interactive send mode it should now no longer need any
1784 dynamic memory at all (unless some dozen recipients are specified).
1785 (Several other places still use normal dynamic memory, of course.)
1786 (*dope-stringdope-again* topic branch.)
1788 - Support for NSS (Network Security Services) has been removed.
1789 I've never worked with it and are, regarding the complexity of
1790 network security, not willing to spend any time on it.
1791 SSL is installed on all systems i'm using and/or testing on by
1792 default, and so i've choosen to go this way.
1793 (It may be that sometime in the future S-nail will add support for
1794 libcurl(3) connectivity, and then it may happen that not only NSS
1795 support is reintroduced again, but also GNU TLS. All of that applies
1796 to network connectivity only, however, not to S/MIME afaik.)
1797 (*drop-nss-support* topic branch.)
1799 - I finally got a glue and understood that Sourceforge does (a) not
1800 support symbolic links and (b) doesn't like dots as regular parts of
1801 filenames. This means that all this time the promised s-nail.tar.gz
1802 symbolic link did not work, and that s-nailv13.3.tar.gz wasn't
1803 accessible either (via the web interface).
1804 In the future S-nail(1) will not provide any more symbolic links (the
1805 Sourceforge website offers a "download latest" thing which seems to
1806 work), and use underscores in filenames -- s-nailv13.3.tar.gz has been
1807 renamed to s-nailv13_3.tar.gz. The tags continue to use dot notation.
1810 - The *heirloom-plus* support branch has been removed.
1811 The code bases diverged a lot and even more to come.
1812 It doesn't make sense to put any effort in that.
1817 - Configuration on UnixWare 7.1.4 will succeed (shell issue fixed).
1819 - Even on DragonFly BSD the IMAP GSSAPI is now found
1820 (in /usr/pkg/include/krb5/gssapi/gssapi.h).
1822 - Support for pkgsrc(7) systems and automatic integration of
1823 C_INCLUDE_PATH and LD_LIBRARY_PATH path configurations.
1826 - Fixes a mortally embarassing regression that the current maintainer
1827 introduced before i really knew what i was doing, in (If *record* is
1828 set, avoid writing dead content twice.., 2012-09-14).
1829 It hit users that send through a MTA and have *record* set; in this
1830 combination data would not have reached the MTA.
1831 Interested parties may read the comment in savedeadletter() (part of
1832 the changeset) or the (Fix MTA/*record* descriptor clash..,
1833 2012-11-10) commit log.
1835 Deepest apologies to tortured users from the current maintainer!
1837 - RFC 4155 compatible MBOX file handling has been introduced, and so
1838 S-nail is now on par with (at least) NetBSD Mail in respect to this.
1839 It can be turned off with the new *posix-mbox* variable, which you may
1840 need to use since not all MUAs are capable to dig those MBOX files.
1841 E.g., less cutting-edge (.-) MUAs fail for this:
1843 |From - Thu May 10 20:40:54 2012
1844 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1845 |To: super@duper.com
1850 |From - Thu May 10 20:40:54 2012
1851 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1852 |To: super@duper.com
1855 |>From - Thu May 10 20:40:54 2012
1856 |From - Thu May 10 20:40:54 2012
1858 I'm not completely happy since S-nail *does* still quote those lines,
1859 how rare they may be -- it *does* modify message content. mutt(1)
1860 implements something more clever and that is quoted-printable encoding
1861 of the "F" from "From", when seen at the beginning of a line.
1862 This, when applied to just *any* "^From", will be a non-modifying and
1863 all-compatible solution.
1865 - SEND_MBOX handling has been changed to discard any Content-Length: and
1866 Lines: headers when it rewrites a message by default.
1867 I know that mutt(1) generates them (why, after
1868 http://www.jwz.org/doc/content-length.html?).
1869 Anyway, S-nail does neither use nor manage them, so that any
1870 modification renders those fields invalid, and then it seems best to
1871 discard them anyway.
1872 You may turn the new behaviour off with *keep-content-length*.
1877 The problem was that i really wanted to release on a 25th.
1878 But i have been able to improve S-nail(1) some more, so that this is
1879 possibly the first real release of it. So i'll add only things that
1880 have changed since v13 -- please see below for the complete picture.
1882 - A new CONFIG=CUSTOM make directive was added, and the new user.conf
1883 variables WANT_SCORE and WANT_DOCSTRINGS have been added. It is
1884 possible to create a floating-point free S-nail(1) now.
1887 - If a feature is disabled not even functions stubs should remain now.
1889 - Many places which will work only with local filenames do now actually
1890 check that the target is a local filename.
1892 - Space-separated lists should work again, at a few places at least.
1894 - Tilde commands will be possible, even with -r.
1896 - The *sendmail-progname* has been added after NetBSD 6 dropped the
1897 send-mail entry in mailer.conf(5), which broke S-nail(1). Now users
1900 - When editing messages via ~e or ~v file and pipe addressees will no
1903 - If recipients occur multiple times spread over lists, i.e., To:, Cc:,
1904 Bcc:, then only one occurrence remains, and in the "highest-order"
1907 - The "list" command prints the list alphabetically sorted (somewhat).
1909 - The "help" and "?" commands take an optional argument that shows
1910 a synopsis string for the given command (unless WANT_DOCSTRINGS was
1913 - String allocations are now more efficient. The situation can still be
1914 improved. However, for the first time Berkeley Mail(1) integrates
1915 harmonically into the system allocator, which may madvise(2) unused
1916 memory to the operating system as necessary and/or possible!
1921 Well, a version number 13 is anyway an ugly thing...
1923 commit 4f534bb33b7c911272cc66a0e3a9e47b73ad8deb
1924 Date: 2012-10-25 20:46:07 +0200
1926 FIX MIME quoted-printable encoding (char cast)..
1931 Well, one of the things that have already been started in v13 is
1932 the turn from using "int" when working with 8-bit characters to
1933 "unsigned char" (and as long as we do not support wide
1936 Unfortunately one very important piece of code, that is handling
1937 encoding to quoted-printable, still used integer instead of
1938 unsigned char, which caused an automatic extension cast to take
1939 place, and that resulted in a messed up output.
1945 I want to give prominence to the following people that helped to improve
1946 S-nail(1) during this development cycle, in order of appearance: Martin
1947 Neitzel, Ezequiel Garzón, Björn Persson, Paul Vojta, and, especially,
1948 John Dodson for warm words from beautiful Australia! Many thanks also
1951 After i've officially forked nail(1) aka Heirloom mailx(1) as S-nail(1)
1952 on 2012-09-18 i have been able to work five weeks almost fulltime on
1953 S-nail(1) development. The first three weeks can be characterized as
1954 hectic fireworks here and there, but then it got better and i was able
1955 to work more or less topic-centric. In the meanwhile S-nail(1) is more
1956 than 230 commits away from the Heirloom base--and drifting further apart.
1958 S-nail(1) v13 is the first release of S-nail(1), but it was forked from
1959 Heirloom mailx(1) 12.5 7/5/10 that arose from Berkeley Mail 8. unless
1960 i'm mistaken. What characterizes S-nail(1) v13?
1962 - The build system has been reworked almost completely.
1963 It is possible to fine-tune which features should be present in the
1964 binary and which don't. The name of the binary can be chosen, and
1965 that choice is reflected all through the manual and the template
1966 resource file. The manual is always complete and thus may document
1967 features that are not supported by the actual binary, though.
1968 Please see INSTALL for more.
1970 - Compiler warnings can now be used. Please see the example WARN= flags
1971 in the Makefile, but '-Wall -Wextra -pedantic' should be silent though
1972 certainly insufficient to reflect the complex work of modern compilers.
1974 - The following recipient address list combines some of the major
1975 improvements that have been made:
1977 <addr1@cdröm.de> (bier) , ./file1,
1978 Steffen Smöregäs (Humbabä) <sauer@bäüer.de> (Hummpäa) ,
1979 sabberlot@träbbel.de , (bier2) <a2@bür2.de> ,
1980 a3@b3.de (bier3) , <a4@b4.de> (bier4, und \"bier5\") ,
1981 |cat > pipe1 , (bier 6) <a6@bür6.de> , ./file2 ,
1982 (co\$mm1) abc1@düf.de (cö,bmm,2) (co\"m\"m.3) ,
1983 co\$bmm1 \"c,ömm2\" co\"m\"m.3 <abc2@däf2.de> , |cat > pipe2 ,
1986 That, on a single line, may be given to ":m" or (quoted) on the
1987 command line, or to "~c" or whatever, and it will work as expected
1988 (well, everything else would be a bug..) and result in the following
1989 sendmail(1) invocation:
1992 <-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>
1994 Date: Thu, 25 Oct 2012 17:12:15 +0200
1996 Cc: Steffen =?utf-8?Q?Sm=C3=B6reg=C3=A4s?=
1997 =?utf-8?Q?_(Humbab=C3=A4)?= <sauer@xn--ber-qla4j.de> (=?utf-8?Q?Hummp=C3=A4a?=),
1998 sabberlot@xn--trbbel-cua.de, moppel@xn--hppel-jua.org,
1999 <addr1@xn--cdrm-7qa.de> (bier),
2000 co$bmm1 =?utf-8?Q?"c,=C3=B6mm2"?= co"m"m.3 <abc2@xn--df2-qla.de>,
2001 (co$mm1) abc1@xn--df-xka.de (=?utf-8?Q?c=C3=B6,bmm,2?=) (co"m"m.3),
2002 (bier 6) <a6@xn--br6-hoa.de>, <a4@b4.de> (bier4, und "bier5"),
2003 a3@b3.de (bier3), (bier2) <a2@xn--br2-hoa.de>
2004 Subject: Re: SubjectTest
2006 Content-Type: text/plain; charset=us-ascii
2007 Content-Transfer-Encoding: 7bit
2012 So list parsing has been fixed, IDNA support has been added, and it is
2013 possible to mix pipe and file recipients *and* multiple thereof, and
2014 the result is still correct for *all* of them.
2015 I think this kind of list can be given wherever a user can directly
2016 enter such a list. And i think all that is unique to S-nail(1).
2018 - When writing back edited messages the target MBOX mailbox can no
2019 longer become "corrupted" when the trailing newline was removed during
2020 the edit. Also affected FreeBSD and NetBSD mail(1).
2022 - A security fix for CVE-2011-2895 was applied.
2024 - The generated Message-Id: is now more human-friendly.
2026 - The -h command line option has been dropped. Use "-O -h XY" if your
2027 MTA really supports that.
2029 - The -O and -r command line options no longer enforce a one-shot send
2030 mode, and instead persist for the duration of the entire session.
2032 - Variables set via the -S command line option are now (un)set twice;
2033 immediately and after all the resource files have been loaded.
2035 - Other new or changed options/commands, in order of appearance:
2036 recipients-in-cc, smime-sign-include-certs, quote-fold, stealthmua,
2037 add-file-recipients, write, rfc822-no-body-from_, rfc822-show-all,
2038 mail/Mail, idna-disable, idna-strict-checks, ??
2040 - In the codebase itself an effort to reduce duplicate work and
2041 introduce caching, and to minimize the use of local variables, was
2042 started, but that is long term. A lot of improvements here and there,
2043 too, like using the well MD5 optimization from Wei Dai, Chris Torek's
2044 hash algorithm for hash tables etc.
2046 - Incredibly important: an heraldic animal was found: snailmail.jpg!
2048 The full history can be inspected by issuing the git(1) command
2050 $ git log --reverse s-nail..s-nailv13
2052 A new TODO has been introduced, and it is getting longer and longer.