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.6 and v14.7:
9 $ git log --reverse --topo-order --abbrev-commit OLD..NEW
10 # Only topic branch headers (--no-merges for content commits only):
11 $ git log --oneline --reverse --topo-order --merges OLD..NEW
12 # Same, but truly accessible:
13 $ git log --oneline --reverse --topo-order --merges --parents OLD..NEW |
14 while read c1 c2 c3 c4 c5 c6; do
15 printf "%-24s: \$ git log --oneline --no-merges ${c1} ^${c2}\n" "${c6}";
21 Thanks go to Tarqi Kazan (tarqi AT cfs DOT or DOT gs) and Johannes
22 Löthberg (johannes AT kyriasis DOT com), as well as Martin Neitzel.
23 (And the winner is... Gavin Troy for his role in "Silence from Ireland".
29 - Since S-nail now performs more-or-less proper percent-encoding as per
30 RFC 3986 users of *imap-cache* have to (either throw away and recreate
31 or) adjust their local cache, e.g. as follows (adjust CACHEDIR and
32 echo(1) to mv(1) as necessary; won't work with paths with whitespace):
34 $ CACHEDIR=${HOME}/traffic/.mail-cache; \
35 find ${CACHEDIR}/ -depth -type d |
38 r=`echo ${b} | sed -e s/:/%3A/g -e s/@/%40/g`
39 if [ ${b} != ${r} ]; then
41 echo ${d}/${b} ${d}/${r}
48 - New variable *history-gabby* can be set to add much, much entries into
49 the history than is done normally.
50 For the NCL only, setting *history-gabby-persist* will cause those
51 entries to be saved into *NAIL_HISTFILE*, too, which they are not by
52 default with it (the other command line editors should always save).
55 - The `online' alias for `connect' has been obsoleted. [d5cfde4]
57 - New CONFIG=MAXIMAL make option. [c0d4087]
59 - Support compilation on new OpenBSD with their reduced OpenSSL clone.
60 This topic also includes the real solution for getting rid of
61 a strcat(3) warning that i reintroduced with s-nail-14_5_2-smime.patch.
64 - Our -r command line option is now mapped to a `-f' MTA option -- the
65 sendmail(1)-compatible `-r' is long obsoleted! (Johannes Löthberg)
68 - New `elif' command so that we now have if..elif..else..endif.
69 If the optional regular expression support is available the new
70 conditions `=~' and `!~' can be used to perform (case-insensitive)
71 regex matching with `if' and `elif'. [topic/condsplus]
73 - New `~R' tilde escape (like `~r', but indent lines). [fae1f29]
75 - Improved multibyte-safety (e.g. for *prompt*) and a bit of
76 compatibility ("support" would be a wording much too strong) for
77 bidirectional text via the new *headline-bidi* variable.
78 [topic/unibidi, topic/mbbidi]
80 - Diversified behaviour of -v command line option as well as *verbose*
81 to support multiple levels of verbosity; the latter is now ternary
82 when set and boolean when unset.
83 This was the ground on which SSL certificate validition verbosity was
84 implemented (*verbose* level 1: certificates, level 2: network
85 communication et cetera), though much is left to do.
86 This has been suggested long ago by (Martin Neitzel). [topic/smverb]
88 - ^C in compose mode with *ignore* set acts now POSIX compatible
91 - If *encoding* is set to base64 then we don't ignore that user
92 wish and use quoted-printable (when 7bit doesn't suffice) [2ca201f]
94 - New `urldec' and `urlenc' commands. [63e869e, fbd95e8, 0af5b1b]
96 - New `setenv' and `unsetenv' commands. [5e2ed79]
98 - Support for GSS-API authentification has been added (request and
99 testing by Tarqi Kazan).
101 Note that the following implicit relation is gone:
103 If set to `login', or if unset and smtp-auth-user is set, `AUTH
106 This topic branch also added support for the SUBMISSION protocol of
107 RFC 6409, so re-reading the *smtp* manual may bring benefits.
110 - A new, backward-incompatible URL syntax and credential lookup scheme
111 has been introduced that is accessible when the new *v15-compat*
112 variable is set. If used, credential lookup occurs before a network
115 The new manual section "URL syntax" describes the new credential
116 variable chains, and documentation of *from* should be read again, as
117 i now also refers to the new *smtp-hostname* variable.
119 Note that the generated `Message-Id' has also changed.
121 (Messy old way pointed out by Tarqi Kazan)
122 [topic/url, topic/cred]
124 - `resend' should be truly fixed and (fwiw) can also resend to pipe and
125 file addressees. [topic/resend]
127 - Support for empty lines in macro and account definition blocks (as
128 required by POSIX for startup files in general) [43cdf92]
130 - The nail command line editor gained the possibility to use PgUp /
131 PgDown / Home / End instead of z[-+0$] commands on xterm-compatible
132 terminals; and ^O equals a `dp' there, too. [8c57be2, 7c30e61, 95e672f]
137 Many thanks to Gaetan Bisson.
142 - Avoid segmentation faults with -L option if s-nail is opened on
143 non-existent mailboxes, e.g. '$ MAIL= s-nail -Lx'. (Gaetan Bisson)
149 Thanks and greetings to Gavin Troy, Gaetan Bisson and Tarqi Kazan (tarqi
150 AT cfs DOT dyndns DOT biz).
152 ChangeLog (packager-affine)
153 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
155 - WANT_AUTOCC knows that clang(1) version 1 can dig -Wstrict-overflow=5.
158 - '$ make test' should work even if you are not steffen.
159 (Gaetan Bisson, Gaetan Bisson, Gaetan Bisson, Gaetan Bisson,
160 Gavin Troy, Gavin Troy) [8b796ba]
165 - *autoinc* is gone -- this is *newmail*. [07a8462]
167 - Working with large(r) IMAP boxes should work again without causing
168 segmentation violations. (Gavin Troy) [761dd87, b0ce180]
170 - With our builtin getopt a.k.a. WANT_NOGETOPT=1 usage of the -L option
171 caused segmentation violations. (Tarqi Kazan, Gaetan Bisson) [f2c2646]
173 - The decision wether we need $PAGER or not now also incorporates the
174 informational lines we inject for messages. [316b4cd]
176 - Drop `defines', add `unaccount', rename `undefine'..
177 The `defines' command has been united with `define' -- just like
178 `account' will list all defined accounts when used without arguments
179 `define' will now do so for macros. And `undefine' is the new name of
180 `undef'. The new command `unaccount' can be used to delete all given
181 accounts, in equal spirit to `undefine' and macros.
182 All of this is still vulnerable against recursivity, e.g., deleting
183 an executing macro still works, but don't that. [b0b3275]
185 - Rename `var-inspect' to `varshow'; silly oversight that `var-inspect'
186 will try to lookup a variable "-inspect". Ouch. [afffd30]
188 - Without HAVE_ICONV the character set iterator sofar used
189 *charset-8bit* as the last resort, whereas it should have used
191 P.S.: All this still preliminary, we await the MIME and send layer
192 rewrite to calm down the stuff for real. [edc3226, df9aefd]
194 - During `~@' editing it is possible to leave the possibly endless
195 character set selection loop by interrupting via ^C.
196 In the meanwhile this effectively drops the currently edited
197 attachment and leaves the entire attachment selection session; it
198 doesn't make sense to make it any better until we have our signal
199 manager and stop jumping around.
201 This changeset should also fix dangling Content-Xy MIME information of
202 attachments which were in the same slot before, e.g., if #1 was
203 a message attachment and that was changed on-the-fly to be a real file
204 attachment then the Content-Description would still have stated that
205 it is a message attachment.
208 ChangeLog (purely technical)
209 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
211 - Since it has been decided to remain compatible to ISO C89 we cannot
212 use the ISO C99 `z' format string modifier (printf(3)).
213 Since quite some time we make efforts to provide our own `ZFMT' macro
214 (in `nail.h') which provides somethint compatible, but on 32-bit
215 platforms compilers often complain nonetheless.
216 Therefore we now also have a compile-time assertion that proves that
217 our `ZFMT' macro is really correct. [397e4d1]
222 Many thanks to the perpetual Gavin Troy.
224 - Faulty notational change of system call return values from `<0' to
225 `==-1' caused endless waitpid(2) loop. [d6f316a; test(!): 79fd761]
228 - (GLibC) STD I/O overoptimizes rewind(3) so that underlaying file
229 descriptor offset is not reset to 0. Generalize the already
230 used `really_rewind()' hack and use it not only in
231 `savedeadletter()' but also in `page_or_print()'. It is likely
232 that this not also fixes `history' listing but also some other
233 things which go through the pager, dependend on the setting of
234 *crt* etc., and on at least GNU/Linux systems. [463660f]
236 Note: standard I/O does NOT offer a possibility to do this in
237 a non-hackish way. It is thus likely that S-nail will gain
238 a completely new I/O layer in the future. That'll also be faster.
241 This note is false: POSIX Issue 7 overloaded the meaning of
242 fflush(3): when used on readable streams the file offset of the
243 underlaying file descriptor is adjusted to that of the stream.
244 (nail.h: adjust really_rewind(): POSIX Issue 7 defined a way..)
245 uses this official approach instead if _POSIX_VERSION>=200809L.
247 - Old shells will now correctly execute an error-condition
248 execution path in `mk-conf.sh'. [afef55f]
253 Thanks to Andy Switala (andy DOT switala AT gmail DOT com).
254 And thanks to all package maintainers for their stamina.
256 At the first workday after the release i've run into a bug that was
257 caused by an oversight, a double-Fclose() that would be harmless if we
258 wouldn't forcefully panic() when we encounter it!
260 So i've spent another week on a review, and despite fixing many
261 additional notational oversights i haven't found more oversights of
262 newly introduced problems. On the other hand i've found and fixed some
263 old problems during the review, and tweaked some other things:
265 - The INSTALL file now has a `Current codebase state' section.
267 - Commands invoked via `!' should now be interruptable.
268 I'm afraid the exit status of such a command will not be reflected by
269 the return value of the `!' command yet, but hey, at least `!sleep 10'
270 can now be interrupted -- try this with another Berkeley Mail!
273 - All credential prompts should now be interruptable.
274 (Inspired from Andy Switala) [c3bb2a2]
276 - 'make test' will now test a silly S/MIME case when WANT_DEBUG (or
277 'make devel') was used. [8cff17f]
279 - *batch-exit-on-error* should now look at the exit status of *every*
280 command when the command loop ticks. [c7e7d53]
282 - The new `[?name-list]?search-pattern' search expression has been
283 changed to `[@name-list]@search-pattern' -- like this it doesn't clash
284 with the `?' help command and can thus be used on a line by itself,
285 causing the default command (`next') to be invoked on its' result,
286 shall there be one. Ok, yes, that was surely also an oversight.
289 - *attrlist* must now be exactly 13 characters, just as it should
290 be. An error message is printed if not. It was always komisch,
291 but i'd buggified it somewhen in the past. Now fixed.
294 - The NCL WANT_TABEXPAND feature now also works if *newfolders* is
295 set to `maildir'. Yet, if a folder was assumed to be of maildir
296 type, shell globbing would not occur. [part of f5c184c]
298 - The `X-Decoding-Data' S/MIME header field was set to the epoch
299 origin instead of NOW in v14.6.
301 Also the `certsave' command now supports file globbing (i.e.,
302 '~/.certs/' should end up in your $HOME now).
303 [both part of 7e0aec7]
308 + With this release the S-nail codebase has been converted to my usual
309 style of function-code-flow and notation.
311 ?0[]$ git diff --shortstat v14.5.2..HEAD
312 55 files changed, 28065 insertions(+), 25356 deletions(-)
313 ?0[]$ git diff --ignore-all-space --shortstat v14.5.2..HEAD
314 55 files changed, 14664 insertions(+), 11955 deletions(-)
316 Maildir and S/MIME support have been restored, and a MIME bug that
317 could have led to missing data in header display+ has been fixed.
318 Ah, and users of compressed boxes should now feel luckier, too --
319 at least once they've realized that the compress extension is no
320 longer appended automatically, but must be given explicitly.
322 Thus: i hope that all those i-am-new-to-the-codebase bugs i've
323 introduced over a year ago have been found and fixed, and that
324 v14.6 is the true "sweet sixteen" (months of maintainership).
326 ChangeLog (packager-affine)
327 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
329 - If WANT_AMALGAMATION is set, `-pipe' will be added to our CFLAGS
330 (which are only honoured with WANT_AUTOCC, of course). [1330411]
332 - New configuration option: WANT_IMAP_SEARCH, enabled by default.
334 The regular expression support for IMAP-style search expressions has
335 been removed again: it changed the IMAP search semantic in that it
336 couldn't be executed on the server, but only local, and the syntax
337 sucked, too. (And we have a new `?' search expression.) [402b7c6]
339 - CONFIG=MEDIUM and CONFIG=NETSEND now both WANT_REGEX. [dee954e]
341 - The `make test' target should *really* work gracefully, now that usage
342 of the `-#' command line option also sets the folder to be opened to
343 `/dev/null'. (Still no `void' box in sight.) [0119d514]
345 - All published patches may also be found in a new [patches] branch.
350 - Several fixes that saw published patches (with equivalent
351 functionality), and are thus described in NEWS, are included:
353 . s-nail-14.5.2-sort-alt.patch
354 Fixes a hasty commit that introduced string relaxation in a faulty
357 . s-nail-14_5_2-mimeheader.patch
358 Fixes data loss if multiple MIME encoded-words follow each other in
359 header bodies. [c81afce]
361 . s-nail-14_5_2-maildir.patch
362 Effectively restores proper maildir support. [1c2563b, 13f325f]
364 . s-nail-14_5_2-smime.patch
365 Fixes an off-by-one error and, in effect, restores S/MIME sign and
366 encryption etc. support. [e759f75]
368 - The `screen' terminal type is by default recognized as being
369 colour-capable. [e759f75]
371 - With the NCL command line editor and WANT_TABEXPAND hitting <TAB>
372 should now act as if an "implicit asterisk" had been given in case
373 there was no expansion of the original user input; e.g., '? ls <TAB>'
374 may exceed your line limit now ;). [0910a8f]
376 - The S/MIME cipher list was outdated, RFC 5751 requires AES-128 as
377 the default, the RC2 ones are long obsoleted (etc.). Also we now
378 should handle that OpenSSL may not support individual algorithms.
380 Note: we use the option value `des3' for `DES EDE3' from now on!
381 (Maybe see *smime-cipher-user@host* manual entry.)
383 *ssl-method* may now also be assigned the new (default) method `auto'
387 - Messages will now be stored in a set *record* even if only file or
388 pipe addressees were given. [a11935b]
390 - Support for xz(1) compressed mailboxes has been added.
391 (The `Can't canonicalize' warning for compressed boxes had the same
392 cause that made maildir usage impossible, but i don't feel _too_ bad
393 because looking into the code a bit revealed that the *newmail*
394 mechanism never worked for such boxes anyway. And will for a while.)
397 - S-nail now supports nested if..else..endif conditionals. [3c22c04]
399 - The NCL command line editor now locks its' history file when it reads
400 and writes it, so as to protect against concurrent usage. [c3a39ce]
402 - You can now say 'fi%', 'fi&', 'p&10' and `ghost ps '!ps axu'' followed
403 by 'ps|grep nail'. [c3266c6]
405 - Invocation cleanup: usage of -f and -u is mutual, -H and -u is ok, -u
406 in send mode not. [fa0a0aa]
408 - New message specification: `[?name-list]?search-string' will search
409 in locally available messages. If the optional `?name-list' part is
410 given, that specifies the (comma-separated list of) header fields to
411 search in. The special names `body' and `text' can be used to search
412 in message bodies alone and bodies including the headers fields,
413 respectively. Note that "message bodies" unfortunately still means
414 "including headers of attachments and attachments themselves", and
415 until some later time. [61bb460]
417 - The new command line option `-L spec-list' prints a header summary of
418 only those messages that comply to the specification list `spec-list'.
419 If -L and -H are used in combination, no summary is printed at all,
420 but the exit status reports wether `spec-list' would have matched some
421 messages or not. [934e12c]
423 ChangeLog (purely technical)
424 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
426 - Most of the work was changing the code-flow of the entire codebase to
427 my usual style of programming, with a single function entry and
428 a single function exit, including the addition of N(ot) Y(et) D(ead)
429 points of interest, which finally enabled me to get rid of (sic!)
430 using a debugger for S-nail development. Just compile via 'make
431 devel', and in case of a crash you should get a nice backtrace
432 listing. (You use IMAP, do you?)
434 However, because practically every line of code has been touched, this
435 caused some other changes along the way, e.g., the handling of
436 temporary files was changed completely (the formerly used Ftemp()
437 function has been replaced with a new Ftmp(), which handles unlinking
438 itself as necessary etc.), it was detected that the S/MIME support was
439 no longer compliant to any RFC, some resource leaks have been
440 eliminated... It is likely that a change so large introduced some
441 other flees and flaws, however. But it looks good so far.
447 + No official release, only exists as git(1) tag.
449 v14.5.2: fix 4: 2014-02-15 (2014-02-14)
450 ---------------------------------------
452 - s-nail-14_5_2-smime.patch
453 Fix a very stupid off-by-one error that i've introduced
454 in [7bdf330] (OpenBSD 5.3: sigh, address strcpy(),strcat()
456 Until we've changed the used data from string to something
457 line-wise, use strcat(3) again.
459 v14.5.2: fix 3: 2014-02-10
460 --------------------------
462 - s-nail-14_5_2-maildir.patch
463 maildir folders would have caused problems in environments which
464 provide the realpath(3) function: beside a "cannot canonicalize PATH"
465 warning the finally used path would be wrong (`test3' would end up as
466 `test3/test3'), so that any further access would try to use the wrong
467 path. Please read the description of this patch and/or the commit
468 logs of the commits [1c2563b] and [13f325f].
470 v14.5.2: fix 2: 2014-02-05
471 --------------------------
473 - s-nail-14_5_2-mimeheader.patch
476 Subject: ehm, .getElementById("blink") needs <span
477 =?US-ASCII?Q?id=3D"blink">,?= not =?US-ASCII?Q?class=3D"id"?=
479 would yet be displayed without the " not " in between the two encoded
480 words because of faulty "encoded-word-continuation" detection (note
481 the quotation marks). The error path could also have been seen in
482 mail forwarding and in faulty searching etc.
483 This patch is in a row of fixes for my hasty [0f9ad93] from 2013-03-12
484 that already caused the v14.2 minor release (because of [b608c6b] from
485 2013-03-14). Those with mercy may read the commit message of [c81afce].
487 v14.5.2: fix 1: 2014-01-30
488 --------------------------
490 - s-nail-14_5_2-sort.patch
491 Reverses (sort(),thread(): use srelax()!, 2014-01-18, [a9b67e9]),
492 which was a hasty commit of an untested diff that i've added few
495 As a rather careless last-minute change i've added string relaxation
496 to threaded and sorted display, but it's really one more step towards
497 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
499 An alternative, forward-heading patch that keeps string relaxation has
500 been pushed to [master] as [5e75529] and is also available as
501 s-nail-14_5_2-sort-alt.patch.
506 Thanks to Ypnose, Sunil Nimmagadda and Gavin Troy.
507 Gavin Troy *really* deserves special thanks for facing [next]!
508 And i want to dedicate the new coloured message display functionality
509 to John Dodson and Ypnose. Thank you.
510 (And best wishes to beautiful Australia!)
512 ChangeLog (packager-affine)
513 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
515 - All utilities can now be overwritten during configuration so that
516 their values are fixated in the generated makefile (`mk.mk').
517 I.e., talking about MAKE=, STRIP=, awk=, cat=, chmod=, cp=, cmp=,
518 grep=, mkdir=, mv=, tee=.
519 rm= and sed= have to be overwritten from the command line, they're
520 needed before `conf.rc' is read.
521 [5c03347, 072ec65, 39a00ab, 23a1245, ?]
524 - The release tarball is now also available in a xz(1) version.
526 - New configuration option: WANT_COLOUR, by default enabled.
528 - 'make test' should now really work, even if the running user has
529 a mailbox with content. [f223a91]
531 - WANT_AUTOCC is now by default enabled, so as for normal users which
532 don't have the need to embed into a defined packaging environment.
535 - Installation no longer strip(1)s away debug symbols if WANT_DEBUG was
542 - Fixes to some bugs that are present since the first cvs(1) commit of
543 Heirloom mailx(1); includes that *ssl-key-user@host* should now work.
544 [4405a2cc, 9770c26f, 692976b9]
546 - Some off-by-XY fixes, thanks to the debug memory canaries.
547 [19b2b0d, 202506e, 43df6e4]
549 - Fixes for (other) stupidisms (of mine): [1c2161f]
551 This includes true implementation of in-memory history limit for the
552 NCL, which was the final and real solution to a segmentation fault
553 that Gavin Troy had to deal with on [next]. [1089f2b]
556 - For completeness: new command `var-inspect' shows information about
557 all given options. Mostly ment for implementing future tests.
560 - The `pipe' command no longer embeds message information into the
561 data passed through to the command (when *piperaw* is set).
562 [ef5ecc6 (part of topic/colour)]
564 - Simple coloured message (header) display is now possible. Please
565 read the new manual section "Coloured message display", use
566 *colour-disable* to turn it off. (It is enabled by default if it
567 knows the terminal is capable and, if used, the pager can, too. Note
568 we now set LESS=FRXi when starting PAGER and no LESS= is in the
571 Dedicated to John Dodson and Ypnose.
572 [topic/colour, c6e84c7]
574 - The `if', `else', `endif' syntax has been extended.
575 You can now "if 0" (never), "if 1" (always), "if $OPTION" (boolean
576 check for OPTION) and "if $OPTION == 'VALUE'" as well as "if $OPTION
577 != 'VALUE'". Unfortunately it is still not possible to use
578 conditionals inside conditionals. [0fb2ae7]
580 - -# now also sets MBOX=/dev/null. [4be2f1e]
582 - The NCL command line editor now supports cursor keys when the terminal
583 produces xterm(1)-compatible keycodes ('ESC' + '[' + [DACB] for left,
584 up, right and down, respectively). What a thrill, yay!!! [0cbf672]
586 - New (optional) command: `history': show or clear command line history,
587 or select a specific command line from in there.
588 History works a bit different now, and should no longer include
589 command lines which include specific message numbers; more to come.
590 [59c6195, topic/hist2]
592 I plan to join all the history management and use only the one that is
593 part of NCL now, hooking it into editline(3) and readline(3). That
594 would shrink tty.c a bit and also introduce duplicate elimination for
597 - The new ~u and ~U tilde escapes work like ~f and ~m, respectively, but
598 don't include any header lines. Inspired by a patch from
599 Sunil Nimmagadda on openbsd-tech@. [c37b8b3]
601 - The `|' command should work again -- it has stopped working on
602 2013-09-09 when i've accidentally changed the command name from `|' to
606 - As a rather careless last-minute change i've added string relaxation
607 to threaded and sorted display, but it's really one more step towards
608 lowering memory pressure -- i couldn't resist [a9b67e9] after seeing
609 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
610 Buffer allocs ever/max simultan. : 14/14
611 Overall alloc count/bytes : 17165/881088
612 Cycle maximums: alloc count/bytes: 16906/876984+0
613 ?0[ /Users/steffen/src/nail.git/t.mbox]? sst
614 Buffer allocs ever/max simultan. : 0/0
615 Overall alloc count/bytes : 16515/841816
616 Cycle maximums: alloc count/bytes: 16256/837712+829560
618 ChangeLog (purely technical)
619 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
621 - We now have debug canaries for all memory sources now that [8419d44]
622 added them to the "string dope".
624 - The most work has been done on our value system, which manages the
625 binary and value options, like *folder* etc.
626 It is now based on enumerations, i.e., constant integers, not on
627 strings. This of course only relates to non-dynamic options.
628 Anyway, this saves us key hashing and allows more compact data
629 representation in general (see the new header `okeys.h' for more).
635 ChangeLog (packager-affine)
636 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
638 - The build system *only* uses the automatically detected $CFLAGS and
639 $LDFLAGS if WANT_AUTOCC=1. I.e., even unset or empty $CFLAGS and
640 $LDFLAGS are not touched until then.
641 (We do however still set $CC if that is unset or empty or set to the
642 plain string "cc".) [856625f6]
647 - Fixed segmentation faults / bus errors when setting *nofolder*
648 / *line-editor-cursor-right* to the null string (only with WANT_NCL),
649 respectively. [d1f1a19b, 21e5c285, 9f6ff25d]
651 - *prompt* handling is now really POSIX compliant (thus no prompting
652 occurs not only for 'set noprompt', but also for setting *prompt* to
655 This was indeed a rather large changeset that also introduced the new
656 *prompt* escape character \&, which expands to `?' by default and to
657 `&' if *bsdcompat* is set.
659 Like that we now can simply assign "\& " to *prompt* at program
660 startup, which (a) allows to do 'set noprompt' without error (once)
661 and (b) allows for POSIX compliance in respect to prompt handling
662 without any complicated conditional code, but (c) gives us the
663 opportunity to continue to support BSD prompts.
666 - For completeness: new command: `features'. (Rather useful for being
667 able to implement more tests in the future, and act according to what
668 is really compiled into the tested binary.
670 - The `-#' command line option now also sets *quiet* by itself.
673 - nail.1: a newly introduced empty line in the manual produced error
674 messages on some systems. Fixed.
676 - The return value of the `mimetypes' command has been reversed and
677 should now be fixed. [acf56ac52]
679 - In threaded display the Subject: followup suppression no longer
680 takes into account invisible messages.
681 Also, rudely hack in a messages-already-written-in-this-round counter,
682 so that the followup suppression knows when "the top of the screen" is
683 reached, which (seems to) help(s) against missing subjects up there as
684 well as after a `newmail'. [topic/subject]
686 - Added a WANT_REGEX=1 toggle in `conf.rc'.
687 When we find regular expressions then a new regex-enabled IMAP-style
688 search is available (see the manual for more) [1ec8fe68]
690 ? f (/or subject ^\[S-nail (subject ^\[nail-devel))
691 ? f (/subject ^\[S-nail) (/subject ^\[nail-devel)
692 ? f (/subject "^\\[(S-nail|nail-devel)")
694 I'm looking forward for being able to add another, simplified, syntax.
696 ChangeLog (purely technical)
697 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
699 - The cc-test.sh has seen some tweaks, for easier future extension, and
700 for adding a test for [d1f1a19]. [several, mentioned: 21e5c285]
702 - On systems without a real wordexp(3) implementations deadlocks could
703 occur because we sometimes hold_all_sigs() to avoid longjmp(3)s away
704 (and will do so for quite some time, still), and that resulted in the
705 SIGCHLD that reported the exit of the started subshell to be blocked,
706 too (e.g., after '? *.h<Tab>': endless hang). Fixed.
711 Many thanks: Gaetan Bisson, William Yodlowsky, Gavin Troy,
712 Thomas (wasd AT gmx DOT net), Ypnose.
713 And Gavin Troy definetely deserves a very special credit.
714 But thank you all, and very much indeed!
716 ChangeLog (packager-affine)
717 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
719 - The `test' make target has been fixed. [f0991e14]
722 - It is possible to gain a different kind of make(1) verbosity by
723 using a VERBOSE=1 command line argument (this knob is not taken into
724 account when deciding wether a rebuild is needed). [498e4ad0]
727 - On Crux 3 Linux and OpenBSD the readline(3) and editline(3),
728 respectively, libraries will now be found when desired. [a7d1aa78]
731 - WANT_LINE_EDITOR has been renamed to WANT_NCL, *plus*.
732 So now there are WANT_READLINE, WANT_EDITLINE and WANT_NLC, each of
733 them can be set individually, and they are tested in the shown order.
734 Also, WANT_TABEXPAND and WANT_HISTORY have been introduced and can be
735 used to fine-tune functionality. [ae4e01e1, b2635feb, 9742bf40]
737 (While here, i've fixed WANT_TABEXPAND code so that it is more
738 sensitive to line excess; on Linux etc., where MAX_INPUT is 255,
739 strange behaviour could be seen because we didn't take into account
740 the length of the prompt at all. The NCL is assumed to have only
741 one remaining, but unfixable problem: backspace often is incapable
742 to cross visual line boundaries; use ^A/^E + ^L, then. [e832c04a]
744 Also, cursor (now ^B and ^F) and history movement (now ^P and ^N) of
745 the NCL have been changed. [d7d928da])
747 - WANT_QUOTE_FOLD is now enabled by default. And WANT_ASSERTS has been
748 renamed to WANT_DEBUG. [1e10da1f]
750 - The build system has seen yet another overhaul in general. CC, CFLAGS
751 and LDFLAGS plus are now tracked and changes will force rebuilds.
752 The new WANT_AUTOCC option can be used to let the build system figure
753 out a compiler and choose known-to-work flags. Use the new ADDCFLAGS=
754 and ADDLDFLAGS= command line arguments to add your specific flags on
755 top of those -- the final CFLAGS etc. are what is change-tracked.
757 This rather massive internal rework revealed that old Bourne shells
758 were yet not supported by the new build system, and so did testing
759 that UnixWare installation was yet impossible due to tool
760 incompatibility. [75c4b74e]
762 - The new WANT_AMALGAMATION option will force compilation of all the
763 sources in a single compilation unit. This requires a rather large
764 amount of memory, but may produce a more compact, maybe more optimized
765 binary. (Implementing this revealed quite some bugs which could
766 therefore be fixed.) [topic/amalgam]
768 - `nail.rc' has been pimped a bit (mostly comments, but
769 *mime-counter-evidence* is now always set). [e3094ba7]
771 That changeset was however buggy. [f3dcb46]
774 - We no longer use install(1) for `install'ation make rules. [80b02cd9]
779 - Even '$ s-nail & fg $!' will now work with the NCL. [2a8b5c55]
781 - Several off-by-one (off-by-two) fixes. [32ce9836, 71e6d013, f139dc36]
784 - Setting *noprompt* now prevents prompting, as per POSIX. [ecefaf63]
786 - *prompt*: new \$ (exit status of last command) and \@ (name of
787 currently active mailbox) escape sequences. [6f652046]
789 - One may now omit the space in '? unc' ('?unc') [05fcb383]
791 - New commands: `ghost' and `unghost' define command aliases (since
792 `alias' is taken for a different purpose) [topic/commands]
797 - There is now a pseudo account `null' (case-insensitive).
798 Also a new `localopts' command exists; when used from within an
799 `account' block, options changed will be reverted back to its former
800 value when the account is left (e.g. by switching to `null'):
803 alternates sdaoden@users.sf.net sdaoden@users.sourceforge.net \
804 sdaoden@googlemail.com sdaoden@gmail.com
805 set Sign="\n--steffen\nForza Figa!" sign="\n--steffen"
806 set smtp=smtp.gmail.com smtp-auth=plain smtp-use-starttls
812 set from="Steffen \"Daode\" Nurpmeso <sdaoden@gmail.com>"
817 set from="Steffen \"Daode\" Nurpmeso <sdaoden@users.sf.net>"
825 neither of *Sign*, *sign*, *smtp** nor *from* should be set.
826 Please see the manual for more.
827 TODO - neither command-ghosts nor alternates etc. are yet tracked
828 TODO - we should have a boolify() so as to say 'localopts yes' etc.
831 - New command: `cwd' (print current working directory).
832 Also fixing the `chdir' return value. [eff4397c]
834 - The *ssl-method* now allows explicit setting of 'tls.1.1' and
835 'tls1.2' values. [c66b4196]
837 - When sending to display, be aware that filenames in MIME parts may of
838 course be MIME-encoded! [1454be03]
840 - *hostname* is now honoured even if *smtp* is not set. (We always
841 supported *from*, so why not *hostname*?)
843 - The `-u user' option now acts identically to setting the $USER
844 environment variable and both now tend to mean something like
845 "impersonate as user in some aspects". Note that we have always used
846 the latter in one or the other way, and `-u user' always ment more
847 than just "open mailbox of user", so i think this change sharpens the
848 edge in the right direction. [09632731]
850 - Filename argument quoting has been tweaked for (some) function(s which
851 take a filename argument last). The following snippet as reported by
852 Gavin Troy should work now: [2bb9b80e]
854 ? mv +inbox.Junk\ Mail
856 - The GNU implementation of wordexp(3) is also (i've added a workaround
857 for the very same bug for Mac OS X in S-nail v14.3 [63273772]) buggy,
858 which causes segmentation faults when expansions failed (`fi &VOID').
862 - The `fi' command no longer uses the (possibly truncated) display
863 version of a filename, but the full path. [5cd85b07]
865 ChangeLog (purely technical)
866 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
868 - Large rework of internal structure: bundle inclusion of most of the
869 external and the content of most of the internal #include files in the
870 new nail.h. If that would have been done very first bugs like the
871 infamous MAXPATHLEN bug as reported by Paul Vojta (see v14.4.2) would
872 never have occurred. [21f3155b]
874 - Support for -fstrict-overflow cc(1) flags. [topic/strict-overflow]
876 - Fixed the quotation filter which yet allocated memory even if not
879 - String relaxation reduces memory pressure rather drastically when
880 working with many (especially MIME) mails at a time, e.g., when
881 writing a modified mailbox. Before all messages of a mailbox had to
882 be worked without releasing any memory in between, now we give back
883 memory (to our pool, not the system) after each and every message.
886 - The other memory source now uses bound canaries, which also found some
889 - We now use the EL_PROMPT_ESC editline(3) mode for prompting, which
890 should offer the possibility to use coloured prompts etc. with
891 (even those) editline(3) (versions which do offer it -- older versions
892 should just do fine by themselves).
893 S-nail uses the special trigger control character \1. [ea30d818]
896 Note however that all tested editline(3) versions are buggy and
897 either don't get it right (`\1COLOR-ON\1stuff\1COLOR-OFF\1') or are
898 incapable of proper repainting (`\1COLOR-ONstuffCOLOR-OFF\1').
900 - We now use the MD5 digest code from the OpenSSL library if that is
906 Many thanks: Gaetan Bisson, Stephen Isard, Jérémie Courrèges-Anglas,
907 William Yodlowsky, and Adam Sjøgren from GMANE.org!
909 ChangeLog (packager-affine)
910 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
912 - The packager-install: target has been fixed. [a8c1b0b]
913 (Gaetan Bisson and William Yodlowsky)
915 - As suggested by Gaetan Bisson the several build system tasks are now
916 individually addressable, i.e., 'make [OPTIONS] config', 'make build',
917 'make test', 'make packager-install'); nothing changes unless you want
918 to, in which case: please see INSTALL. [4d3b799]
920 The new target 'test' will call cc-test.sh with its new --check-only
921 option which will only perform the (too few) function tests on the
923 And cc-test.sh will no longer create output files, but simply echoes
924 to STDOUT and STDERR. [629e1ee, 786f219]
927 - The default configuration file now sets *bsdannounce* and *bsdflags*,
928 all in one line, as suggested by William Yodlowsky.
929 (If *header* is disabled, *bsdannounce* is ignored, but *header* must
930 be enabled by default according to POSIX, and *bsdannounce* is just
931 the same as *header*, but for the folder-switched event. Thus setting
932 *bsdannounce* is the more sane default, imho.) [6161f10]
935 - Announcement messages are now tagged '[ANNOUNCE]'. [26e1b35]
936 (Tagging suggested by Stephen Isard and Jérémie Courrèges-Anglas)
938 - The manual NAME now includes the version (but it's somewhat ugly).
944 - When switching folders when in compose mode, message attachments
945 become invalid. For v14.4.5, at least warn when this happens.
948 - When reading multipart/alternative messages which do not contain
949 a text/plain part, the (most likely HTML) part is not displayed (even
950 if S-nail is configured to display HTML). The reason is a bug i've
951 introduced with [0d43a999] (Change "Part X:" display message..,
952 2012-12-20). (Note that the committed fix i've posted to the list was
953 not correct either and has been fixed itself.) [225c02b, ecfa149]
958 Thanked, Gavin Troy, Gaetan Bisson.
960 - Fix output buffer confusion that would have occurred when parts of
961 a multipart mail had a pipe command set. Longer story in [e75d16dd].
964 - The makefile now supports a `packager-install' target that bypasses
965 the reevaluation of the configuration (after checking that there is
966 one) and directly steps ahead to the install process.
969 - Notes in INSTALL that CFLAGS and LDFLAGS need to be overwritten from
970 within (conf.rc or) the command line.
976 I convey special thanks to Karol Błażewicz and Gaetan Bisson.
978 - The new build system didn't allow to overwrite CFLAGS= when used in
979 conjunction with GNU make(1). To make a long story short, removing
980 a `.POSIX:' directive from the makefile fixed the problem. Luckily.
983 - More INSTALL notes for UnixWare 7.1.4, which suffers from the same
984 problem: here the fix is to use the -e option of make(1).
986 - Karol Błażewicz reported a segmentation violation he got when using an
987 Arch Linux S-nail test package, and Gaetan Bisson informed me about
988 that. The problem was that we didn't assign the resulting default
989 address (which gets used when *from* is not set) to the result which
990 gets used, effectively resulting in a NULL dereference. [cfd60479]
995 Many thanks to Paul Vojta.
997 - On GNU/Linux there is no MAXPATHLEN constant defined by default, as
998 this is a non-standard legacy constant. Mozilla ran into this some
999 time ago, though a bit different [1]. It made it easier for S-nail.
1001 [1] <https://bugzilla.mozilla.org/show_bug.cgi?id=412610>
1003 We could include `sys/limits.h' to get at MAXPATHLEN, there it is
1004 defined to be PATH_MAX, but let's just include the standard `limits.h'
1005 and ensure MAXPATHLEN ends up >= PATH_MAX. With this condition being
1006 true even FORTIFYd sources won't bail with reported buffer overflows
1007 because realpath(3) expects a buffer of PATH_MAX bytes. [bee5e57c]
1010 - With the builtin LINE_EDITOR, ensure proper interaction with GNU
1011 rlogind(8), which is alone in its quest to set the ISTRIP termios(4)
1014 - Bugfix a codepath that would have prevented compilation when
1015 HAVE_ICONV is not set.
1016 While there, allow to unselect message attachments when using the `~@'
1017 tilde command interactively, which i mysteriously had forgotten when
1018 allowing selection of 'em. (oops?) [4f58ffea]
1020 - It's now easier for packagers to get at debug-enabled CFLAGS; simply
1021 use WANT_ASSERTS=1 (should not be enabled in shipouts, please).
1024 - Fixed a terrible bug that i've introduced in november 2012, that would
1025 have corrupted MBOX files when using the `resend' command. (The
1026 so-called "From_ line" would have been quoted to ">From_ line" instead
1027 of simply being stripped.) [19d449e2]
1029 - Fixed a SIGSEGV for the builtin LINE_EDITOR, that would have occurred
1030 if a history traversal (^B or ^F) would have been continued by
1031 a reverse history completion (^R).
1032 While there, avoid some multiple-beeps-in-a-row that yet occurred due
1033 to code reuse, and document that ^G etc. reset the multibyte state
1036 Also, the expand-on-tab code could have excessed line input maximums,
1037 e.g., after `? /usr/bin/*<Tab>'. This was of course known, but
1038 i wanted to keep it because all tested (modern) terminals "mess up but
1039 won't break", and thus made it possible to use the data, even if it's
1040 visual representation was messed up. The real solution will be much,
1041 *much* more complicated, i.e., show possible *completions*, page-wise,
1042 etc., i.e., just like is known by tab *completion*. This will need
1043 far more time because it doesn't make sense to embed such complicated
1044 code into the current bed.
1045 Now i've chosen to simply don't display excess, but replace the
1046 content with a message that says that there was excess. It simply
1047 looks better. [0320c8ba]
1049 - I've changed the use of `[?]' as a replacement sequence for invalid
1050 / non-displayable characters to `?' (again). There are still code
1051 paths (from the original codebase) which use the real Unicode
1052 replacement character instead, so our display is still not unique.
1053 On the long term the codepath can anticipate in all levels wether
1054 use of Unicode is possible, so that, then, we will be unique again,
1055 using either only `?' or the Unicode replacement character. [faf6380]
1057 - I've anticipated in v15.0 and implemented *quote-fold* as a stream
1058 filter. It is now multibyte safe and takes into account the visual
1059 width of characters, i.e., ideographs etc. It is working almost as
1060 good as an algorithm can work that looks at data linewise, but is yet
1061 experimental and incomplete in that it will break lines even if only
1062 whitespace or a backslash escape follows. It is code that is only
1063 a few hours old, which is why it is not enabled by default. [
1070 - Fix some harmless stylos and typos in the manual and `conf.rc'.
1073 - Ensure *complete* proper cleanup on signal-caused configuration run
1076 - Bugfix: reenable empty configuration variable overrides, as in
1078 $ make install SID= NAIL=mailx ...
1081 - Bugfix: rename the `conf.rc' variables SHELL, LISTER and PAGER because
1082 they clash with the POSIX standard variables of the same names, which
1083 hurts now that the configuration is run through the shell itself.
1084 The configuration names are now XSHELL, XLISTER and XPAGER (ouch).
1087 - nail.rc: comment out some non-portable S-nail(1) specifics, for those
1088 who install this file as mailx.rc or so, somewhere. [3f14b01]
1090 - From now on S-nail will use simple version tags, as, e.g., `14.4.1',
1091 i.e., no more `s-nail-14.4.1'. [a75437d, 183d59c] (Jürgen Daubert)
1093 Also move UAGENT out of `version.h' [f7be5be]
1095 Uh! v14.4 must have originated in a bad dream; good it's vanished.
1100 Thanks to the entire vivid and virile S-nail(1) user community is
1101 proper, especially Stephen Isard, Gavin Troy, Martin Neitzel.
1102 Not to forget Ryan Kavanagh and Ayan George.
1104 Note this time the changes are in reverse order, i.e., oldest first.
1109 15fbe09 ^bf9173f 'topic/varmac-unite'
1110 Simplification and unification of variable and macro handling
1111 40f6f58 ^15fbe09 'topic/cledit1'
1112 Command line editor; new manual section `Line editor'
1113 ad28a32 ^40f6f58 'topic/termsize'
1114 Honour POSIX mailx(1) and respect $COLUMNS and $LINES on startup
1115 dc3cd49 ^a446fd8 'topic/qf'
1116 You don't wanna know
1117 b8738f7 ^0651fd0 'topic/spam1'
1118 Interaction with SpamAssassin; new manual section `Handling spam'
1119 5419d6f ^b8738f7 'topic/make1'
1120 Reworked build system; please read `INSTALL' and `conf.rc'
1121 9ab4d6b ^5419d6f 'topic/list1'
1122 Slightly tweaked message thread display, fix `:u :r' to mean it
1127 - The default PAGER is now more(1). (But read on.)
1129 - The `echo' command is now compliant, and fully supports XSI.
1131 - The `group' and `ungroup' command aliases have been removed, they are
1132 `alias' and `unalias'.
1134 - We now have the capability of line editing and history.
1135 One may choose from not less than three different implementations:
1136 a builtin editor as well as possible linkage against BSD editline(3)
1137 and also a GNU readline(3) compatible layer.
1138 Please read the new manual section `Line editor'.
1140 Input is now compliant in that an interactive line may be continued
1141 after escaping the newline character with a backslash.
1142 [topic/cledit1] (all of them)
1144 The *prompt* variable may now contain shell escapes, just like the
1145 `echo' command. [0938d8a]
1146 As a special extension the new \? escape, when used within *prompt*,
1147 will expand to the exit status of the last command. [41076d2]
1149 - The POSIX standard environment variables $COLUMNS and $LINES are now
1150 honoured upon startup. [topic/termsize]
1152 - The `help' / `?' commands now support abbreviation, i.e.,
1153 ``$ ? unc'' should now find `uncollapse'. [7b86195]
1155 - The `~' abbreviation that has been introduced as an alias for `call'
1156 is now a real command, not a magic shortcut. [9987289]
1158 - The new variable *quote-as-attachment* can be used to additionally
1159 embed the quoted message as a `message/rfc822' MIME attachment.
1162 - The compose-mode command `~@' will now attach messages from the
1163 current mailbox if given a filename of the style `#NUMBER'.
1164 Please read the corresponding manual section `Tilde escapes', though.
1166 - The `WANT_JUNK' and `WANT_SCORE', as well as Gunnar Ritters junk mail
1167 management have been removed.
1169 Instead S-nail(1) can now support interaction with SpamAssassin, but
1170 sofar only via the spamc(1) / spamd(1) client / server pair of
1171 programs that ships as part of SpamAssassin. The new configuration
1172 directive `WANT_SPAM' controls wether this feature is desired.
1174 Please read the new manual section `Handling spam'.
1175 [topic/spam1] (Martin Neitzel)
1177 (S-nail(1) is now *definitely* floating-point free.)
1179 - The configuration and make system have been overhauled / reorganized.
1180 The configuration is now in `conf.rc', also contains directives like
1181 `PREFIX' etc, and is always read in. However, only those directives
1182 which are not yet set (via environment or command line overwrites) are
1183 incorporated into the set of configuration options. Therefore
1188 will now build S-nail(1) twice, because of the changed configuration.
1190 Note that `WANT_GSSAPI' is now by default disabled, which shrunk
1191 a freshly started s-nail image by more than 30 percent.
1193 We're not finished yet in that there is no dependency graph etc.
1194 Please do read `INSTALL' and `conf.rc'.
1197 - Message selection has been slightly bugfixed in that `:u :r' really
1198 means `:u' AND `:r'. Compared to NetBSD Mail(1) it's still a shame.
1200 Threaded message display has been slightly changed in that within
1201 a thread identical Subject: lines are not repeated. It may not be
1202 perfect yet due to the general list / thread state. [topic/list1]
1204 - If, upon startup, the environment variable `NAIL_NO_SYSTEM_RC' is set,
1205 then the system wide initialization file isn't read, just as if the
1206 `-n' option had been given. [1b31535]
1208 - It is now possible to use CTRL-C during connection hangs. (But in
1209 general error recovery capabilities of the socket related
1210 infrastructure is non-existent, practically speaking.) [45a9f36]
1212 - *quote-fold* has been temporarily disabled, as it is not multibyte
1215 No review for v14.4. And today is Friday, the 13th. Ouuuh!
1220 I should *maybe* should have and want to give prominence to
1221 Martin Neitzel for this, i maybe have misunderstood.
1223 - Bugfix *synchronous* *pipe-** execution..
1225 Well, unfortunately yet another newly introduced bug slept in
1226 S-nail v14.3[.1] -- [a8d724b3, Add @ and @& shell command prefixes
1227 for pipe-MIMETYPE, 2013-05-03] falsely changed the waiting state
1228 for subprocesses, as has shown up by a HTML-only mail on the
1230 'Seems i'm collecting one line fixes in this codebase; this needs
1231 to change in the future.
1236 I want to give prominence to Juergen Daubert (jue AT jue DOT li), who
1237 reported that i've broken plain-old unfancy send mode in 14.3.
1239 + Ok, i'll hope we're out of new errors for the v14.3 series with that.
1241 - New variable: *batch-exit-on-error*.
1242 Only works if the new -# command line option has been given, and will
1243 check the "current" exit status whenever one operation completes
1244 (S-nail returns to the command prompt).
1245 If the exit status implies error (e.g., sending the last message
1246 failed) then we exit forcefully with that error status. (The normal
1247 behaviour is that the status is reset when the command loop ticks.)
1250 - While here again, i've added the new -# command line option.
1251 This is the first step to implement a reliable batch mode;
1252 unfortunately it still selects the users system mailbox on startup,
1253 because we simply cannot go to "no" mailbox for quite some time -- at
1254 some future time we will be able to go to some VOID thing, and then
1255 this will end up as a rather efficient batch mode.
1256 For now it sets *dot*, *emptystart*, *noheader* and *sendwait*, and
1257 also implies the -~ command line option. [7549569]
1260 printf "m ${MBOX}\n~s subject1\nE-Mail Körper 1\n.\n" &&
1261 printf "m ${MBOX}\n~s subject2\nEmail body 2\n.\n" &&
1263 ) | MAILRC=/dev/null "${NAIL}" -n -#
1265 - Also, -N set *header* instead of *noheader*. [7b4a13f6]
1268 - Plain old unfancy invocations like
1271 $ echo bla|s-nail ./FILE1
1273 had been broken (by [522cb3ec]). [260e19d]
1279 Thanks to Gavin Troy (gavtroy AT gmail DOT com) who inspired the @ and
1280 @& pipe-command prefixes.
1285 - S-nail has been registered at Coverity Scan, and the third build
1286 (after topic branches *coverity-444* and *coverity-444.2*) produced no
1287 more errors. (<http://scan2.coverity.com/projects/444>.)
1288 (Then i used POP3 and IMAP and fixed some SIGSEGV. ;) Still didn't
1289 look at S/MIME, Maildir, caches etc... o()
1291 - S-nail v14.3 doesn't produce any spurious linker warnings on
1292 OpenBSD 5.3; all (correct!) use cases of strcpy() and strcat() have
1293 been replaced. [7bdf330, 2c8d7cb]
1295 - This is the first release with a (though very short) review -- i'm
1296 slowly getting comfortable with the code. (But i'm too stupid to
1297 perform reviews on patches, 'always did reviews on C++/Perl/xy
1298 classes. Aaah, how beautiful ... objects.)
1303 - It is now possible to "call" macros without using the `call' command
1304 by prefixing them with a tilde, as in
1313 - Added the *pop3-bulk-load* option.
1314 Yes, there are mailing lists etc. which use plain text email, and,
1315 there, headers are often more data than the body, so it doesn't make
1316 sense to download the headers twice (unfortunately POP3 doesn't
1317 support a BODY command; if only it would support a RETRDELE command..)
1320 And yep, from this changeset on i personally use S-nail even over the
1321 network, no longer my stale and incomplete S-Postman. And i can tell
1322 you, this damn thing is so silent, i always set *verbose* not to go
1323 grazy ... but .. i hate to say it .. the healing will take time.
1325 - POP3 will now try to use APOP authentication automatically; thus the
1326 *use-apop* stuff has been replaced by *pop3-no-apop* options (just in
1327 case there are POP3 servers which advertise they support APOP but in
1328 fact fail to do so; anyone?) [6c3c5575]
1330 - Some IMAP segmentation violations have been fixed:
1332 ? fi imaps://user1@localhost
1333 Password:Interrupt <- CNTRL-C
1334 ? set imap-auth=cram-md5 <- hey, 'forgot to set correct auth
1335 ? fi imaps://user1@localhost
1336 IMAP write error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown
1339 And also, when *folder* was set to an IMAP account but hasn't been
1340 opened yet, and no IMAP account ever has been opened, a string
1341 comparison against a NULL pointer yet caused a SIGSEGV, too.
1344 - `set folder=' now tolerates `%:' and expands PROTOs stuff etc.:
1346 ? short xp %:imaps://user1@localhost
1349 Pure convenience so that it doesn't need to be typed twice (still no
1350 completion in sight...). Note that setting *folder* to a POP3 box
1351 will now be actively rejected. [b12b17f5]
1353 NOTE: while implementing this i've detected another dead-end
1354 miscondition in S-nail -- you really should ensure that your target
1355 folder/box is connected before you leave your current POP3/network
1356 based folder, if there is data to be moved to the target (i.e.,
1357 mbox). This problem will persist for a long time due to the way the
1358 entire codebase functions; i hope i can find a short/mid-term
1359 solution, but the real healing will take years. The mentioned
1360 solution would at least make S-nail interruptable, currently we get
1361 stuck and interrupts are blocked...
1363 - If you're using S-nail on Mac OS X and have seen some segmentation
1364 faults when expanding shell stuff then you may be pleased to hear that
1365 S-nail now works around an Apple bug. [63273772]
1367 - The builtin mime.types have been corrected and a lot of new ones have
1368 been added. New data from
1369 <http://svn.apache.org/viewvc/tika/trunk/tika-core/src/main/resources/\
1370 org/apache/tika/mime/tika-mimetypes.xml>, thanks! [8072fcb6]
1372 - BEWARE: handling of command line arguments has changed a bit!
1374 1. The -D, -d, -E, -i, -N and -v command line options are now
1375 implemented by means of setting the respective option, as via -S.
1376 (This means that from now on resource files can only *temporarily*
1377 overwrite command line arguments.)
1379 2. The -I and -T command line arguments have been dropped.
1380 It seems Gunnar Ritter stopped developing nail/Heirloom mailx once he
1381 started implementing Newsreader functionality. It'll take a long time
1382 until we get there, so for now drop all the Newsreader stuff.
1384 3. Handling of -r has been changed. E.g.:
1386 s-nail -A test -Snoeditalong -r 'La mort est <fem@me>' -d
1387 ? set from=bummer@m1.com
1391 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t1"
1392 ? set from=bummer@m2.com
1395 Sendmail arguments: "sendmail" "-i" "-r" "fem@me" "t2"
1399 s-nail -A test -Snoeditalong -r '' -d
1400 ? set from=bummer@m1.com
1404 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m1.com" "t1"
1405 ? set from=bummer@m2.com
1408 Sendmail arguments: "sendmail" "-i" "-r" "bummer@m2.com" "t2"
1410 [*main-fun-cleanup* topic branch]
1412 - *smime-sign-include-certs-** stuff works again, oops.. [9a8597c6]
1414 - A whole lot of smallest and small fixes due to registration at
1415 Coverity Scan, as project 444. Error handling in S-nail is ridiculous.
1416 [*coverity-444* and *coverity-444.2* topic branches. The sheer number
1417 of fixes was the reason to sit down and go for unplanned S-nail v14.3]
1419 - *idna-strict-checks* has been dropped. It's silly to have in a MUA,
1420 especially given that GNU LibIDN doesn't ship with a lot of rules.
1421 We were able to drop quite some code (and a use-after-free, too :().
1424 - The ~p tilde command displays attachments more verbose.
1425 Until the big big MIME and send layer rewrite :) this is intermediate
1426 since until then we do not really know neither MIME type nor charset
1427 of an attachment at the time this is displayed (for sure). Yet
1428 i think it's nicer to show what we have than keep it the way it was.
1431 - @ and @& shell command prefixes have been added for the pipe-MIMETYPE
1432 mechanism. The former suppresses filters if multiple messages are
1433 displayed at once, the latter adds asynchronous program execution on
1434 top of that. E.g., to display PDF documents, but only if you
1435 *explicitly* address the message *alone and by itself*, and without
1436 blocking S-nail and the $PAGER, do:
1438 set pipe-application/pdf="@&cat >"${TMPDIR}"/s-nail${$}.pdf;\
1439 mupdf "${TMPDIR}"/s-nail${$}.pdf; rm "${TMPDIR}"/s-nail${$}.pdf"
1441 (Inspired by Gavin Troy.) [a8d724b3]
1443 Note: most of that had been posted to nail-devel@ already, but it was
1444 tweaked ([251b636]) so that you now *really* have to say `p MSGNO' to
1447 - The NETLESS CONFIG= has been removed; it is almost identical to
1448 MINIMAL now (i.e., without WANT_JUNK and WANT_SCORE).
1450 - WANT_JUNK and WANT_SCORE have been disabled by default.
1451 They don't seem to be too useful; i hope i can implement
1452 a SpamAssassin hook for (downloaded) mail messages for v14.4.
1453 If so, expect these two "modules" to become removed completely.
1458 Another unplanned (minor) bugfix release after Gavin Troy (gavtroy AT
1459 gmail DOT com) pointed out that MIME CTE decoding was broken, who
1460 i therefore want to give a lot of prominence right here.
1462 - Fix MIME content decoding which has been broken by [01c0e135].
1469 An unplanned (minor) bugfix release after i've found two bugs today and
1470 heard from Jérémie Courrèges-Anglas (jca+nail AT wxcvbn DOT org) that
1471 there exists a S-nail OpenBSD package.
1473 I want to give prominence to the following people that helped to
1474 improve S-nail(1) during this development cycle, in order of
1475 appearance: Dirk Peters (peters AT schwertfisch DOT de).
1477 Thank you very much, and best from Germany!
1479 - Some warnings of newer clang(1) versions were silenced, including yet
1480 another alloca(3) problem (see *memtracer* topic branch in v14.0
1483 - Tweaking the MIME boundary detection left a little hole that could
1484 cause boundaries not to be detected, as has been shown by a Microsoft
1485 Word generated mail on the ICU list. [11e5fb5b]
1487 - A format string could overflow bounds if unrealistic
1488 (18446744073709551615) line numbers or message sizes would have been
1489 produced. [faa65c40]
1491 - An algorithmic error could cause overlong lines which wrapped around
1492 to the next display line. [ade52660]
1495 v14.2, 2013-03-15 [v14.1, 2013-03-12]
1496 -------------------------------------
1498 I want to give prominence to the following people that helped to
1499 improve S-nail(1) during this development cycle, in order of
1500 appearance: Martin Neitzel, Christos Zoulas, Stephen Isard, jgw@txo.org
1503 Thank you very much, and best from Germany!
1505 + v14.2 differs from v14.1 only by one commit, one that fixes
1506 (mime_fromhdr(): partial rewrite using n_iconv_str(), 2013-03-12),
1507 which i hastily implemented just hours before the release of v14.1,
1508 and simply shouldn't have made it (into there).
1509 The v14.1 tarball has been removed from the server.
1511 - A fix for the quoted-printable codec: "message truncation" occurred
1512 when a mail maliciously used a soft linebreak to escape the linebreak
1513 of a completely empty line.
1514 (That resulted in 0 written and 0 leftover bytes, a condition that was
1515 declared erroneous back in november 2012 when i started handling I/O
1518 - The "folders" command will work again when given an argument.
1519 A fault of mine introduced in (cmd1.c: expand() may fail, 2012-10-23).
1521 - The Base64 codec has been touched again, and we are finally capable to
1522 perform sequential decoding; this was targeted for the MIME/send layer
1523 rewrite, but it actually was possible today.
1524 The result as seen in ps(1), running on the Base64 encoded HTML5
1525 standard (4622545 bytes HTML, with a NUL appended to force Base64
1526 encoding, resulting in a 6244793 bytes email):
1528 7420 s006 S+ 2:22pm 0:10.65 plain-nail -f HTML5
1529 1440 s006 S+ 2:23pm 0:00.36 ./s-nail -f HTML5
1531 (So the only thing that is left for a good throughput is sequential
1532 decoding of quoted-printable encoded parts that maliciously use soft
1533 linebreaks to convert an entire part to a single line. And i've seen
1534 that from Apple Mail.)
1536 - New option: *mime-allow-text-controls* (rather long manual entry).
1538 - *smtp-auth-password-user@host* and *smtp-auth-user-user@host* will
1540 (Reported by jgw@txo.org in November 2011, fixed by Gavin Troy in
1543 - Most *headline* formats now do support the '-' left-alignment flag.
1544 Note that you most likely have to change your *headline* accordingly.
1545 (The still missing %n format is one reason why there will be v14.2.)
1547 - *datefield* and *datefield-markout-older* can now be set to
1548 strftime(3) format strings (except %n).
1549 (From Stephen Isard's wishlist.)
1551 - A possible SEGV has been found and also fixed by Stephen Isard.
1552 (The "legendary" cross-world stereo fix!)
1554 - Wow! S-nail will finally compile on GNU based Linux systems like
1555 Slackware 14 etc. (Found while hunting bug reported by
1558 - New option: *datefield-markout-older* can be used to choose
1559 a different date display for mails that are older than six months,
1560 in equal spirit to what POSIX describes for the -l option of the ls(1)
1561 command (Stephen Isard).
1563 - (Exotic) Years are (would) now (be) interpreted correctly according to
1566 - CRAM-MD5 usage has been fixed.
1568 - *folder* updates are now tracked when set, and we will show the
1569 realpath(3) name of it, showing PREFIX..SUFFIX if that wouldn't fit on
1571 Tracking updates made it also possible to perform other more expensive
1572 tasks when setting *folder*, so that it is now possible to do
1578 et cetera (both ideas by Christos Zoulas).
1580 - Bugfix for the ~@ tilde-escape in non-interactive mode.
1581 (readtty(): quick shot: work in pipelines (on non-TTY).., 2013-01-25)
1582 introduced the possibility to "read data from the terminal" (STDIN
1583 that is) in non-interactive mode.
1584 The manual documents that attachment input must be terminated with an
1585 empty line, but if that had been omitted, as in the example below, we
1586 would have yet entered an endless loop.
1588 $ cat <<_EOT | /s-nail -~ -s boom ./OUT
1594 - Alias expansion will now be performed for members of Reply-To: fields
1597 - Decoding quoted-printable will now be more relaxed.
1598 (Even though the standard says that users should be given a hint when
1599 input is not absolutely clean; a possible warning will be added later,
1600 when we have an error message ring.)
1602 - New option: *mimetypes-load-control* can be used to control which of
1603 the mime.types resources will be loaded.
1605 - The builtin default mime.types have been extended a bit.
1610 I want to give prominence to the following people that helped to
1611 improve S-nail(1) during this development cycle, in order of
1612 appearance: John Dodson, Gianluca Ramunno, and Anon Ymous from the
1618 - Encoding defaults to *quoted-printable* not *8bit*.
1619 This has no technical background except that i think it's the better
1622 - Small progress for the "getting stuck due to the current folder
1623 becomes inaccessible due to whatever reasons" problem.
1624 (schdir(): realpath() local files before leaving CWD.., 2013-01-08)
1626 - The names of temporary files have changed. Whereas not all uses of
1627 temporary files already use really meaningful names, it has yet become
1628 possible to use the pattern "*mail-*"; or, to be compatible with
1629 NetBSD Mail(1) in one go, "*mail*". (E.g., in my ~/.vimrc you'd read:
1630 :au BufRead,BufNewFile *mutt*,*mail* setl fenc= | setf mail
1631 [the *mutt* is a leftover from times when i've used MUAs that suck].)
1636 - The Quoted-Printable MIME handling has been rewritten completely.
1637 We now correctly encode files with the MS-DOS newline sequence (CRLF).
1638 (Part of the *mime-cte* topic branch.)
1640 S-nail(1) continues to be able to handle text messages and text
1641 attachments without a trailing newline, but because these
1642 Content-Transfer-Encoding related things are now handled by the C-T-E
1643 layer instead of by sendout.c a text message body that comes in as
1644 part of a complete message via the -t command line option will loose
1645 the missing final newline (i.e., it'll gain one).
1646 This problem does *not* occur when *only* the message body comes in
1647 via STDIN, as in 'cat FILE | s-nail', but *only* when the -t option is
1649 (sendout.c: does no(t/ longer) know about CTE internals!, 2013-02-09)
1651 - Filename arguments for -a are now processed *after* all the resource
1652 files have been loaded etc., so that the usual "folder" specifics can
1653 be used (provided that proper care for shell quoting was taken).
1654 ((main(): delay -a processing.., 2013-01-10), as a part of the
1655 *mainaflags* topic branch.)
1657 - (d38c5bd, When the write command asks.., 2004-11-23) added support
1658 for pipes when saving attachments during a "write" command.
1659 It however used the wrong SIGPIPE signal handler; e.g.:
1661 Enter filename for part 2 (application/x-gzip): |exit
1664 Of course, it still performs a jump and that most likely leaves memory
1665 chunks behind, thus causing some memory leaks. This will be
1666 a long-term problem (you may want to read [mime.c:fwrite_td(): TODO
1667 notes on unfixable leaks, 2013-01-14] for more).
1668 (send.c:sendpart(): fix longjmp() SIGSEGV.., 2013-01-29)
1670 - Fixed a name quoting regression that i've introduced in
1671 (Rewrite *extract().., 2012-10-20), that would have caused
1672 "x \"y\" z" to become "x"y" z" instead of "x "y" z".
1673 (S-nail still does not really have RFC compliant parsers, just as
1674 NetBSD Mail(1) has, i.e., there are structured and unstructured fields
1675 etc... I hope i can provide them in v15.0.)
1676 (names.c:yankname(): fix quote regression.., 2013-01-29)
1678 - The IDNA conversion now assumes domain names are specified in
1679 *ttycharset*, rather than in the LC_CTYPE locale charset.
1680 I.e., it integrates into the usual character set specifications.
1681 (IDNA: honour *ttycharset* for domain names, 2013-01-18)
1683 - The new *editalong* variable will automatically spawn an editor when
1684 composing a mail in interactive mode, just as if `~e' was given.
1685 (Add new *editalong* variable, 2012-01-07)
1687 - The manual has been converted to mdoc.
1688 (The manual has been converted to mdoc, 2012-12-28)
1690 - The ~@ tilde escape, when given filename arguments, will treat the
1691 arguments as a comma-separated instead of a whitespace-separated list.
1692 (collect: change separator of ~@ tilde escape.., 2012-12-28)
1694 The interactive mode of ~@ has also been changed, rather massively.
1695 Please do reread what the manual says.
1696 ((collect: support multiple attachment charsets.., 2013-01-23), as
1697 part of the *attach* topic branch.)
1699 - Thanks to Gianluca Ramunno (ramunno DOT gianluca AT gmail DOT com)
1700 S-Nail will no longer try to issue a STARTTLS command when it is about
1701 to establish a SMTPS connection, a task that logically fails since the
1702 connection is already secured.
1703 (Interestingly the nail codebase performs the necessary test for IMAP
1705 While here the undocumented nail v11.0 *smtp-use-tls* legacy option
1707 (Fix SMPTS with a set *smtp-use-starttls*.., 2012-12-22)
1709 - The RFC 4155 compliant MBOX quoting is now exclusively used, the
1710 shitty *posix-mbox* variable has been removed again.
1711 (Shitty because i've implemented RFC 4155 compliant MBOX quoting and
1712 tested it, then added *posix-mbox* for those who liked the old
1713 behaviour and did not re-test -- the final code path was buggy.)
1715 In mails newly created and saved by S-nail(1) no From_ quoting at all
1716 will be used no more, but instead the rewritten MIME file classifier
1717 will detect unquoted From_ lines and enforce quoted-printable encoding.
1718 (This is an approach that is S/MIME compatible all through the way as
1719 the file data is not modified at all, but only encoded, so that the
1720 data checksum is not changed.)
1722 In yet existent mails that S-nail copies or moves around without
1723 reclassification an RFC 4155 compliant From_ line detector will apply
1724 MBOXO quoting (prepend a single '>') as necessary.
1725 Different to the old MBOXRD behaviour S-nail will neither quote yet
1726 quoted From_ lines ('>>From xy' -> '>>>From xy') nor will it unquote
1727 one quote level when reading etc. mails ('>> From xy' -> '>From xy').
1728 As a result the code could be simplified.
1730 This changeset also incorporates a fix for NetBSD PR bin/47453, as
1731 reported by Martin Brandenburg. I.e., some mailers, noticeably
1732 UW-imap (with MBX format only?), use non-compliant From_ lines with
1733 RFC 822 date specifications. Be aware of 'em.
1734 (RFC 4155 MBOX, and drop *posix-mbox* and foldergets().., 2013-01-06)
1736 - *rfc822-show-all* has been removed.
1737 It didn't work properly for more complex MIME structures, like
1738 message/rfc822 messages with attachments etc., just as i've seen today
1739 on the file(1) mailing list.
1740 So, instead of hacking it now i've dropped it and will come back with
1741 a better solution when the MIME and send layers have been overhauled.
1742 I.e., the real intent was to be able to specify that an embedded
1743 message/rfc822 is treated as a *unity*, and that's the goal.
1744 (Drop *rfc822-show-all*, 2013-01-23)
1745 [The manual will be adjusted in a different commit.]
1747 - *rfc822-no-body-from_* has been renamed to *rfc822-body-from_*.
1748 It thus must be set explicitly.
1749 On the other hand it now catches all cases...
1750 (*rfc822-no-body-from_* -> *rfc822-body-from_*, 2013-01-23)
1751 [The manual will be adjusted in a different commit.]
1753 - The new *charset-7bit* (defaults to US-ASCII) and *charset-8bit*
1754 (defaults to UTF-8) have been introduced.
1755 These are used if seven bit clean data is to be sent, and no
1756 *sendcharsets* are set or the convertion of all of them failed,
1759 - There is no functional change unless there is iconv(3) support.
1760 - There is no functional change unless you set them.
1761 (Introduce *charset-8bit* and *charset-7bit* variables.., 2013-01-18)
1762 [The manual will be adjusted in a different commit.]
1764 In addition the new *sendcharsets-else-ttycharset* variable can now
1765 be used to automatically use *ttycharset* as a *sendcharset(s)*,
1766 regardless of the new *charset-8bit* variable.
1767 (Add *sendcharsets-else-ttycharset* variable, 2013-01-24)
1768 [The manual will be adjusted in a different commit.]
1770 NOTE: before we apply charset conversion we now perform a string
1771 comparison to see wether character sets are identical. If the strings
1772 match (case-insensitively), then *no* conversion is performed.
1773 This means that code like
1775 $ printf "LATIN1: \0376" | s-nail -Ssendcharsets= -s boom ./out.txt
1777 *succeeds* in an UTF-8 environment now, whereas older versions would
1778 fail with an "illegal byte sequence" error (unless the iconv(3)
1779 library of the system would not perform any conversion that seems
1780 superflous, of course).
1782 I thought about making this optional, but, in fact, if this would be
1783 done in an environment without iconv(3) support then the result would
1784 be equally corrupt. And the way it is now we save the expensive and
1785 superflous conversions. (See TODO for more.)
1787 Please *do* reread the manual section "Character sets".
1788 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1790 - An attempt was made to improve MIME Content-XY: detection.
1791 It should be more RFC compliant, and just overall better :);
1792 a simple one-pass classifier cannot match libmagic(3), of course.
1794 This changeset removes support of the long obsoleted (4fee1ef,
1795 2005-01-06) *charset* variable, as well as for the
1796 *maximum-unencoded-line-length* variable that has been introduced in
1797 (48a652bd, 2005-07-26).
1799 For S-nail v14.0 it'll be no longer necessary to do
1801 $ tr -d '\015' < input | s-nail ...
1803 to transport files which use the $-DOS (terminal) newline (sequence).
1804 We still depend upon *sendcharsets* for a while, though.
1805 (Rewrite file-content classification.., 2013-01-02)
1807 - The new *mime-counter-evidence* variable can be used to force
1808 a classification of non-text MIME parts (attachments) by their
1809 filename, i.e., a "reverse-classification" just as would be performed
1810 if S-nail(1) would itself *send* the file(name). This can help
1811 against some stupid MUAs (Apple Mail?) that send .diff etc. files as
1812 `application/octet-stream' parts etc.
1814 At a later time this may become a valued option, causing a temporary
1815 save of unnamed attachments followed by a MIME classification of the
1816 file contents, followed by forced treatment as plain text if it seems
1817 to be human readable. But not yet. Just to warn you.
1818 (Add *mime-counter-evidence* variable.., 2012-12-29)
1820 - The special "pipe-" command "@" can be used to force treatment of
1821 a MIME message part as plain text (e.g.,
1822 'set pipe-application/pgp-signature=@' will henceforth print those
1823 signatures inline and as plain text).
1824 (Introduce the special "@" "pipe-" command, 2012-12-27)
1826 - The MIME types (as from mime.types(5)) will now be cached. Before
1827 all possible sources would have been opened, read and parsed for each
1828 and every message part that required detection of the MIME
1830 The new "mimetypes" command can be used to show or clear that cache.
1831 (Add mime.types(5) cache.., 2012-12-27)
1833 - A small set of MIME types (template: ./mime.types) will now become
1834 compiled into S-nail(1), and be used as a fallback if there are no
1835 ~/.mime.types and/or no /etc/mime.types, or those didn't contain
1836 a matching type. E.g., NetBSD 6 doesn't ship a default database.
1837 Also, file extensions will be matched case-insensitively (case of
1838 attribute values is not specified afaik?).
1839 (Introduce compiled-in mime.types(5).., 2012-12-21)
1841 - The undocumented *charset7* variable was removed.
1843 - The "Message X:" display leader has been changed and will henceforth
1844 be matchable via "^[-- Message \d+ -- \d+ lines, \d+ bytes --]:$".
1845 These lines can no longer be suppressed by setting the *quiet*
1846 option (which was yet possible for print and top, though undocumented).
1847 (Change "Message X:" display message.., 2012-12-20)
1849 - When displaying multipart messages the "Part X:" introductional string
1850 has been changed; if the Content-type: header is not *retain*ed, then
1851 this string will include the part's type and size. Ditto for
1852 Content-disposition: and a mentioned attachment filename.
1853 This is a first step only, for the final version the MIME and send
1854 layers will have to be adjusted. But the string will be matchable via
1855 a "^[-- #.* --]$" regular expression from now on.
1856 (Change "Part X:" display message.., 2012-12-20)
1858 - MIME boundaries in multipart messages are now handled better in that
1859 no boundary string should get through to the display.
1860 (Tweak MIME boundary detection.., 2012-12-20)
1862 - A couple of long standing, even pre-Heirloom mailx(1) memory leaks and
1863 segmentation violations, most of them related to configurations
1864 without alloca(3) support, as well as one leak that i have introduced
1865 when i implemented RFC 4155 MBOX handling, have been fixed.
1866 But S-nail should now survive non-alloca(3) configurations.
1867 (*memtracer* topic branch.)
1869 - The Base64 MIME handling has been rewritten completely.
1870 This was an urgent topic, because the old implementation (a) read in
1871 all lines of a base64 encoded text part, repeatedly resizing a string
1872 storage and repeatedly decoding that string until all the lines have
1873 been swallowed (i.e., or by accident the last decoded byte was
1874 a newline character, and that in turn may of course have fucked up for
1875 multi-octet encodings, dependent on the actual byte-order), (b) used
1876 function local static data to keep state in between multiple
1877 invocations, which messed up multi-byte/-octet encodings like this
1879 �5��ɽ���Aɥ����́��٥��������[lots of data follows]
1881 and (c) did not perform any error checking at all.
1882 The new one does not run into the problem that (a) tried to circumvent
1883 since leftover decoded data (as opposed to leftover *encoded* data) is
1884 transported along the call-chain for later use. It adds a minimal set
1885 of error handling ('may now see "[Invalid Base64 encoding ignored]"),
1886 with more to become possible in later S-nail versions when the entire
1887 layers are reworked. (Until then DOS newline sequences [CRLF]
1888 embedded into base64 will no longer be decoded to Unix LF newlines.)
1889 Base64 encoded lines will now be 76 characters long, as stated (as
1890 a maximum value) in RFC 2045, not 72 as before.
1892 The Base64 code core has been shamelessly stolen from NetBSD's
1893 Mail(1), and i guess it was the second time that this happened :=).
1894 (*base64-rewrite* topic branch; and reworked later on the *mime-cte*
1897 - The string allocation strategy has been tweaked some more to, i think,
1898 a final version (regarding algorithm).
1899 In normal non-interactive send mode it should now no longer need any
1900 dynamic memory at all (unless some dozen recipients are specified).
1901 (Several other places still use normal dynamic memory, of course.)
1902 (*dope-stringdope-again* topic branch.)
1904 - Support for NSS (Network Security Services) has been removed.
1905 I've never worked with it and are, regarding the complexity of
1906 network security, not willing to spend any time on it.
1907 SSL is installed on all systems i'm using and/or testing on by
1908 default, and so i've choosen to go this way.
1909 (It may be that sometime in the future S-nail will add support for
1910 libcurl(3) connectivity, and then it may happen that not only NSS
1911 support is reintroduced again, but also GNU TLS. All of that applies
1912 to network connectivity only, however, not to S/MIME afaik.)
1913 (*drop-nss-support* topic branch.)
1915 - I finally got a glue and understood that Sourceforge does (a) not
1916 support symbolic links and (b) doesn't like dots as regular parts of
1917 filenames. This means that all this time the promised s-nail.tar.gz
1918 symbolic link did not work, and that s-nailv13.3.tar.gz wasn't
1919 accessible either (via the web interface).
1920 In the future S-nail(1) will not provide any more symbolic links (the
1921 Sourceforge website offers a "download latest" thing which seems to
1922 work), and use underscores in filenames -- s-nailv13.3.tar.gz has been
1923 renamed to s-nailv13_3.tar.gz. The tags continue to use dot notation.
1926 - The *heirloom-plus* support branch has been removed.
1927 The code bases diverged a lot and even more to come.
1928 It doesn't make sense to put any effort in that.
1933 - Configuration on UnixWare 7.1.4 will succeed (shell issue fixed).
1935 - Even on DragonFly BSD the IMAP GSSAPI is now found
1936 (in /usr/pkg/include/krb5/gssapi/gssapi.h).
1938 - Support for pkgsrc(7) systems and automatic integration of
1939 C_INCLUDE_PATH and LD_LIBRARY_PATH path configurations.
1942 - Fixes a mortally embarassing regression that the current maintainer
1943 introduced before i really knew what i was doing, in (If *record* is
1944 set, avoid writing dead content twice.., 2012-09-14).
1945 It hit users that send through a MTA and have *record* set; in this
1946 combination data would not have reached the MTA.
1947 Interested parties may read the comment in savedeadletter() (part of
1948 the changeset) or the (Fix MTA/*record* descriptor clash..,
1949 2012-11-10) commit log.
1951 Deepest apologies to tortured users from the current maintainer!
1953 - RFC 4155 compatible MBOX file handling has been introduced, and so
1954 S-nail is now on par with (at least) NetBSD Mail in respect to this.
1955 It can be turned off with the new *posix-mbox* variable, which you may
1956 need to use since not all MUAs are capable to dig those MBOX files.
1957 E.g., less cutting-edge (.-) MUAs fail for this:
1959 |From - Thu May 10 20:40:54 2012
1960 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1961 |To: super@duper.com
1966 |From - Thu May 10 20:40:54 2012
1967 |Date: Wed, 07 Nov 2012 11:48:30 +0100
1968 |To: super@duper.com
1971 |>From - Thu May 10 20:40:54 2012
1972 |From - Thu May 10 20:40:54 2012
1974 I'm not completely happy since S-nail *does* still quote those lines,
1975 how rare they may be -- it *does* modify message content. mutt(1)
1976 implements something more clever and that is quoted-printable encoding
1977 of the "F" from "From", when seen at the beginning of a line.
1978 This, when applied to just *any* "^From", will be a non-modifying and
1979 all-compatible solution.
1981 - SEND_MBOX handling has been changed to discard any Content-Length: and
1982 Lines: headers when it rewrites a message by default.
1983 I know that mutt(1) generates them (why, after
1984 http://www.jwz.org/doc/content-length.html?).
1985 Anyway, S-nail does neither use nor manage them, so that any
1986 modification renders those fields invalid, and then it seems best to
1987 discard them anyway.
1988 You may turn the new behaviour off with *keep-content-length*.
1993 The problem was that i really wanted to release on a 25th.
1994 But i have been able to improve S-nail(1) some more, so that this is
1995 possibly the first real release of it. So i'll add only things that
1996 have changed since v13 -- please see below for the complete picture.
1998 - A new CONFIG=CUSTOM make directive was added, and the new user.conf
1999 variables WANT_SCORE and WANT_DOCSTRINGS have been added. It is
2000 possible to create a floating-point free S-nail(1) now.
2003 - If a feature is disabled not even functions stubs should remain now.
2005 - Many places which will work only with local filenames do now actually
2006 check that the target is a local filename.
2008 - Space-separated lists should work again, at a few places at least.
2010 - Tilde commands will be possible, even with -r.
2012 - The *sendmail-progname* has been added after NetBSD 6 dropped the
2013 send-mail entry in mailer.conf(5), which broke S-nail(1). Now users
2016 - When editing messages via ~e or ~v file and pipe addressees will no
2019 - If recipients occur multiple times spread over lists, i.e., To:, Cc:,
2020 Bcc:, then only one occurrence remains, and in the "highest-order"
2023 - The "list" command prints the list alphabetically sorted (somewhat).
2025 - The "help" and "?" commands take an optional argument that shows
2026 a synopsis string for the given command (unless WANT_DOCSTRINGS was
2029 - String allocations are now more efficient. The situation can still be
2030 improved. However, for the first time Berkeley Mail(1) integrates
2031 harmonically into the system allocator, which may madvise(2) unused
2032 memory to the operating system as necessary and/or possible!
2037 Well, a version number 13 is anyway an ugly thing...
2039 commit 4f534bb33b7c911272cc66a0e3a9e47b73ad8deb
2040 Date: 2012-10-25 20:46:07 +0200
2042 FIX MIME quoted-printable encoding (char cast)..
2047 Well, one of the things that have already been started in v13 is
2048 the turn from using "int" when working with 8-bit characters to
2049 "unsigned char" (and as long as we do not support wide
2052 Unfortunately one very important piece of code, that is handling
2053 encoding to quoted-printable, still used integer instead of
2054 unsigned char, which caused an automatic extension cast to take
2055 place, and that resulted in a messed up output.
2061 I want to give prominence to the following people that helped to improve
2062 S-nail(1) during this development cycle, in order of appearance: Martin
2063 Neitzel, Ezequiel Garzón, Björn Persson, Paul Vojta, and, especially,
2064 John Dodson for warm words from beautiful Australia! Many thanks also
2067 After i've officially forked nail(1) aka Heirloom mailx(1) as S-nail(1)
2068 on 2012-09-18 i have been able to work five weeks almost fulltime on
2069 S-nail(1) development. The first three weeks can be characterized as
2070 hectic fireworks here and there, but then it got better and i was able
2071 to work more or less topic-centric. In the meanwhile S-nail(1) is more
2072 than 230 commits away from the Heirloom base--and drifting further apart.
2074 S-nail(1) v13 is the first release of S-nail(1), but it was forked from
2075 Heirloom mailx(1) 12.5 7/5/10 that arose from Berkeley Mail 8. unless
2076 i'm mistaken. What characterizes S-nail(1) v13?
2078 - The build system has been reworked almost completely.
2079 It is possible to fine-tune which features should be present in the
2080 binary and which don't. The name of the binary can be chosen, and
2081 that choice is reflected all through the manual and the template
2082 resource file. The manual is always complete and thus may document
2083 features that are not supported by the actual binary, though.
2084 Please see INSTALL for more.
2086 - Compiler warnings can now be used. Please see the example WARN= flags
2087 in the Makefile, but '-Wall -Wextra -pedantic' should be silent though
2088 certainly insufficient to reflect the complex work of modern compilers.
2090 - The following recipient address list combines some of the major
2091 improvements that have been made:
2093 <addr1@cdröm.de> (bier) , ./file1,
2094 Steffen Smöregäs (Humbabä) <sauer@bäüer.de> (Hummpäa) ,
2095 sabberlot@träbbel.de , (bier2) <a2@bür2.de> ,
2096 a3@b3.de (bier3) , <a4@b4.de> (bier4, und \"bier5\") ,
2097 |cat > pipe1 , (bier 6) <a6@bür6.de> , ./file2 ,
2098 (co\$mm1) abc1@düf.de (cö,bmm,2) (co\"m\"m.3) ,
2099 co\$bmm1 \"c,ömm2\" co\"m\"m.3 <abc2@däf2.de> , |cat > pipe2 ,
2102 That, on a single line, may be given to ":m" or (quoted) on the
2103 command line, or to "~c" or whatever, and it will work as expected
2104 (well, everything else would be a bug..) and result in the following
2105 sendmail(1) invocation:
2108 <-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>
2110 Date: Thu, 25 Oct 2012 17:12:15 +0200
2112 Cc: Steffen =?utf-8?Q?Sm=C3=B6reg=C3=A4s?=
2113 =?utf-8?Q?_(Humbab=C3=A4)?= <sauer@xn--ber-qla4j.de> (=?utf-8?Q?Hummp=C3=A4a?=),
2114 sabberlot@xn--trbbel-cua.de, moppel@xn--hppel-jua.org,
2115 <addr1@xn--cdrm-7qa.de> (bier),
2116 co$bmm1 =?utf-8?Q?"c,=C3=B6mm2"?= co"m"m.3 <abc2@xn--df2-qla.de>,
2117 (co$mm1) abc1@xn--df-xka.de (=?utf-8?Q?c=C3=B6,bmm,2?=) (co"m"m.3),
2118 (bier 6) <a6@xn--br6-hoa.de>, <a4@b4.de> (bier4, und "bier5"),
2119 a3@b3.de (bier3), (bier2) <a2@xn--br2-hoa.de>
2120 Subject: Re: SubjectTest
2122 Content-Type: text/plain; charset=us-ascii
2123 Content-Transfer-Encoding: 7bit
2128 So list parsing has been fixed, IDNA support has been added, and it is
2129 possible to mix pipe and file recipients *and* multiple thereof, and
2130 the result is still correct for *all* of them.
2131 I think this kind of list can be given wherever a user can directly
2132 enter such a list. And i think all that is unique to S-nail(1).
2134 - When writing back edited messages the target MBOX mailbox can no
2135 longer become "corrupted" when the trailing newline was removed during
2136 the edit. Also affected FreeBSD and NetBSD mail(1).
2138 - A security fix for CVE-2011-2895 was applied.
2140 - The generated Message-Id: is now more human-friendly.
2142 - The -h command line option has been dropped. Use "-O -h XY" if your
2143 MTA really supports that.
2145 - The -O and -r command line options no longer enforce a one-shot send
2146 mode, and instead persist for the duration of the entire session.
2148 - Variables set via the -S command line option are now (un)set twice;
2149 immediately and after all the resource files have been loaded.
2151 - Other new or changed options/commands, in order of appearance:
2152 recipients-in-cc, smime-sign-include-certs, quote-fold, stealthmua,
2153 add-file-recipients, write, rfc822-no-body-from_, rfc822-show-all,
2154 mail/Mail, idna-disable, idna-strict-checks, ??
2156 - In the codebase itself an effort to reduce duplicate work and
2157 introduce caching, and to minimize the use of local variables, was
2158 started, but that is long term. A lot of improvements here and there,
2159 too, like using the well MD5 optimization from Wei Dai, Chris Torek's
2160 hash algorithm for hash tables etc.
2162 - Incredibly important: an heraldic animal was found: snailmail.jpg!
2164 The full history can be inspected by issuing the git(1) command
2166 $ git log --reverse s-nail..s-nailv13
2168 A new TODO has been introduced, and it is getting longer and longer.