Hello list, hereby i announce S-nail v14.9.14, the "Great tit passed moult". This is an unwanted and unplanned but unfortunately necessary bugfix release. I hope it marks the end of the v14.9.* series. I presume you would be surprised if it would not also bring some features, this time mostly support of MTA-style aliases as inquired by Jean-Marc Pigeon, some authentication work (XOAUTH2/ OAUTHBEARER support), and as usual development to the last minute. It fixes IMAP GSSAPI authentication, thanks to Ivan Vučica for reporting and testing this issue (Debian #930691; still have no testbed, but will soon!), and imap-delim, which i broke in July 2017, thanks to Ralph Keller for repetitive reporting. For OpenBSD and SunOS 5.9 this release fixes long standing (must be) race conditions regarding child processes and their I/O setup. Never seen before, but my new box (i stepped a decade of hardware improvements, finally) rather regulary has shown them when running the test suite. (On the OpenCSW cluster my speed varies, but i had a very good day and seen them there once.) This (finally) caused the complete rewrite of the child process (and termios) handling that i (had to) mention in communication with Gavin Troy already back in, i do not know -- 2013? (Still not event loop based, but near getting good feelings there.) Funnily the problem (child descriptors were closed by the parent before the fork(2)ed childs had the opportunity to dup(2)licate their file descriptors) reminded me of a message of the german computer magazine c't, maybe around 2001/2002, when OpenBSD improved their fork(2) performance in a day or two after having appeared declassified in a comparison with other OSes. (Of course it was nothing but our own fault to not synchronize on the child, but blindly assuming that a fork(2) child gets the opportunity to run immediately.) Dear Predrag: would it now be possible for you to upgrade from v14.8.12? I really would like to know! Credits, in order of commit appearance: Martin Lucina, Viktor Szépe, Alexander Harm, Anders Magnusson, Thomas Haigh, Martin T, Ivan Vučica, Nicholas Marriott, Alexander Harm, Steven Penny, Jean-Marc Pigeon, Martin Neitzel, Paul Vojta, Russell Bell, Paride Legovini and Ralph Keller. A special credit to Coverity.com once again, it found bugs! (, project number 444.) We welcome Martin Lucina, Anders Magnusson, Thomas Haigh, Martin T, Ivan Vučica, Nicholas Marriott, Steven Penny and Ralph Keller in THANKS. Number games ^^^^^^^^^^^^ The release commit is [v14.9.14.ar] ([release/v14.9.14]:[e6a2c194]), and it has also been stored as [timeline]:[ba12b24d]. The stable branch was tagged [v14.9.14] ([stable/v14.9]:[13571c33]). The git(1) release commits and tags, as well as the release balls have been signed with the OpenPGP signing subkey EEC8C2FF of key steffen@sdaoden.eu / 1883A0DD (EE19 E1C1 F2F7 054F 8D39 54D8 3089 64B5 1883 A0DD) available on OpenPGP key servers, my website and download area. Release balls and OpenPGP signatures (.asc) can be downloaded via HTTPS/HTTP at \https?://ftp.sdaoden.eu. Copies of the signatures can also be found at the end of this message. s-nail-14.9.14.tar.xz: SHA1 852e84a927b9c14db9c214abd9004e3ce4c1f87e SHA256 1e4e002ff83fb697b9f33a786e6bdac0d6d0511a3cc1089cce299078a04a25ba SHA512 94432db6d64c248d592ed236883118c27066a0d95c22b79f6898c15378532db226425380d6dd029a3236d4f189dc9721c9161a80d3b963bc986e1353d3e1a603 s-nail-14.9.14.tar.gz: SHA1 9915a06a0494c33137b75a430fc708e5cd5f05ce SHA256 f0e3275274c93f3756fba6c58ca53f05b9fa2f89badb8678608b372d93ea510c SHA512 cdf3eb43d5e4770b1369ac949bd8e0651484f1a4a87352f1ae24f536a68cb02812545d0dd6347bff884d1e14fd9370160503466d5495190fe4be5d16bac03fe0 All files are available as "-latest" symbolic links, too, e.g., s-nail-latest.txt (a copy of this announcement text). Announcement : https?://www.sdaoden.eu/code-nail-ann.html Manual : https?://www.sdaoden.eu/code-nail.html Web : https?://www.sdaoden.eu/code.html#s-mailx git(1) clone : \https?://git.sdaoden.eu/scm/s-nail.git git(1) browse: https?://git.sdaoden.eu/cgit/s-nail.git mdocmx(7) anchors are denoted by a number-sign #: typing "^A ANCHOR" while reading the man(1)ual in a capable less(1) will scroll to the manual's Point-Of-Interest, and pointing a web browser to the "#ANCHOR" of the online manual works. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - The (very backward) Debian mawk is now supported directly. (Martin Lucina, Viktor Szépe) - GCC (8.3.0) -Os inlining bug (wmt) is worked around. And GNU awk 5 warnings have been fixed (before CRUX). - "|PIPE RECEIVER" errors seen on SunOS 5.9 and OpenBSD have first been fixed, and then caused a major rewrite of the child and termios handling for a rather "real" fix. The latter has the side effect that *pipe-TYPE/SUBTYPE*#489 handlers will now have their standard output go to /dev/null. - IMAP GSSAPI authentication should work again. (Ivan Vučica) - -C#60 testable can be used more than two times. - The "grappa" mode of mk/make-release.sh can now be used "everywhere". See INSTALL on interest. (It now gracefully fails if s-nail is not installed: we need that for hashing.) - New option OPT_MTA, by default enabled. Set *mta-aliases*#466 to a valid path in aliases(5) syntax, and we will expand them. All Postfix directives but :include: are supported. Only clear text files are supported, no DBs. (Jean-Marc Pigeon) - `~^'#320 will now verify *expandaddr*#409 right away in "~^ head ins to|cc|bcc", as is already done for `~t'#341, `~c'#324 and `~b'#323. - OPT_AGENT and OPT_SPAM_SPAMD are gone; they were obsoleted on 2017-07-16, and it is not expected to become noticed. - *sendwait*#529 is now initially set, and it gained an optional value, a comma-separated list of case-insensitive strings naming specific subsystems for which synchronousness shall be ensured (only). Possible values are "mta" for *mta*#465 delivery, and "pcc" for command-pipe receivers. P.S.: you can get a list of all initial values plus via $ s-nail -:/ -v -Xset -Xx - Colours may now happen even in quickrun mode (-e#65, -H#68, -L#71)! I thought it is ok nonetheless, because we i think always documented to enwrap `colour'#160 setting in an according `if'#215, as in \if terminal && [ "$features" =% +colour ] \colo iso view-header fg=red \end - OPT_SOCKETS has been renamed to OPT_NET. - -Y#87 is now well defined under all conditions, with tests: The commands will be evaluated successively in the given order, and as if given on the program's standard input -- before interactive prompting begins in interactive mode, after standard input has been consumed otherwise. - XOAUTH2 / OAUTHBEARER (OAuth 2.0 bearer token, RFC 6750) autentication is now supported for all protocols. New FAQ entry "But, how about XOAUTH2 / OAUTHBEARER?"#45 For driving the necessary external update tool a new *on-main-loop-tick*#483 hook has been introduced. (I am thinking about adding support for an optional built-in token refresh.) - Support for the EXTERNAL authentication method has been introduced. This is UNTESTED, though. (I am still in the process of re-setting up my VM test environment.) We do not verify presence of a client certificate etc., but only that a TLS secured channel is active, when using this method. (We now *verbose*#592 log the used TLS version and cipher, too.) - *imap-delim*#652 works again as advertised! This was broken in [1b9897a9] ((BWDIC!) Fix *imap-delim* behaviour.., 2017-07-01), and i think i was pretty much irritated by then. Sorry!! While here, take *imap-delim* into account for `imapcodec'#648. (Ralph Keller). ChangeLog ^^^^^^^^^ - Manual section "HISTORY"#51 improved a bit. (Thomas Haigh) - New variable *line-editor-cpl-word-breaks*#444 (yet a bit restricted). - MLE: add mle-raise-{int,quit,tstp} functions. Ie., raising those signals via ^C and ^Z is no longer hard-wired (in the MLE), but can be reassigned. (Nicholas Marriott) - The makefiles no longer contain any awk code, that all has been separated into files under mk/. (Alexander Harm) - We now have "test" *mta*#465, which dumps to standard output or optionally to a file, and honours *mbox-fcc-and-pcc*#452: $ echo text | s-nail -:/ -Smta=test -s ubject user@exam.ple $ OPT_NET 8fcab7b1 (BWDIC!) Fix: clearly define -Y in all conditions, with tests 76dd6011 Add XOAUTH2/OAUTHBEARER (OAuth 2.0 bearer token, RFC 6750) support 3699aa0c (UNTESTED!) Support EXTERNAL (via TLS client certificate) d5ff46a8 n_tls_open(): PO_D_V log used TLS version and cipher fc1a8d06 Use three levels of *verbose*ity.. 2d43201c Add *on-main-loop-tick* hook 4200be37 HTML filter: more HTML 4.0 entities (Russell Bell).. 9b605148 Some: fix a few spelling mistakes (again) (Paride Legovini).. 6812eee0 FIX *imap-delim* behaviour fix, use it in `imapcodec' (Ralph Keller).. 910958a6 THANKS: Ralph Keller v14.9.13 ("Blue tit's spiral marriage swoop"), 2019-03-08 --------------------------------------------------------- Not so much happened as i was busy with other things in the second half of 2018, and could not find a grip: at the source level some efforts to turn this to mailx have taken place, including early work on a code abstraction that will be shared with my (g)roff clone: it was tiring to come back to old ideas that i have already implemented multiple times and in different languages. To mention it for the curious. So: this is a bugfix release, in fact it fixes a tremendous amount thereof, [master] was ahead by 62 commits from [v14.9.11] (not all bugs though, hrmhrm), but also with, well, a few new features, and of course, development to the last minute. ^_^ v14.9.13 replaces v14.9.12 from yesterday which would pick up an ISO C 2011 statement that is impracticable, thanks to Johannes Schöpfer and Jürgen Daubert for reporting this (i should test without OPT_AUTOCC more often.) I have also fixed -T to match NEWS (manual and code did the opposite). v14.9.12 balls will be removed from the server. Credits, in order of commit appearance: Jörg Schilling, Paride Legovini, Olav Mørkrid, Ralph Corderoy, Rich Felker, Predrag Punosevac, Russell Bell, Dirk-Wilhelm Peters, Jean-Marc Pigeon, Warren Toomey, Cág, Martin Neitzel, Dr. Werner Fink, Dr. Matthias St. Pierre, Kurt Roeckx, Mike Sharov, Joan and Johannes Schöpfer. Very special thanks go to Jean-Marc Pigeon of OSUKISS Linux, who provided me access to a VZGOT container on the most "beefy" machine i have ever had access to! It is ever so astonishing to have work done in 90 seconds on this supercomputer which requires an hour or more here. Thank you, Jean-Marc. And thanks to Kimura-san not only my web server became accessible via TLSv1.3 (out-of-line), but we also have landed on FreeBSD! Kimura-san is the one who installed a sympathic cron job that reminds me of cherry petals wafting in a warm spring breeze -- in winter! We welcome Russell Bell, Jean-Marc Pigeon, Warren Toomey, Dr. Matthias St. Pierre, Kurt Roeckx, Mike Sharov, Joan and Johannes Schöpfer in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Packagers could follow stable/* via git(1) and the "grappa" mode of the release script (see README); perl(1) is required to be totally en par with an official release. (Paride Legovini) $ git checkout stable/stable $ sh mk/make-release.sh grappa mybranch ... Program version is [.], packager release addition shall be: xy Is s-nail correct? [y/n] y Switched to branch 'mybranch' $ git commit -S -n -m 'My release [.]-xy' - $MAKEJOBS vanished, just use -j or whatever your make(1) supports. Luckily the tested make(1)s can be persuaded to dig each others .WAIT / .WAIT: / .NOTPARALLEL: targets.. and do the right thing. - $OBJDIR support added, i use it for building / testing on tmpfs. It works in conjunction with make-emerge.sh, too, thus out-of-tree out-of-tree is possible (more or less; see INSTALL). $ make tangerine OBJDIR=/tmp/x/y/z - Option VAL_PRIVSEP_USER has been renamed to VAL_PS_DOTLOCK_USER (to reflect the new "deep tree" directory layout). - Option OPT_QUOTE_FOLD has been renamed to OPT_FILTER_QUOTE_FOLD (to reflect later code changes upwards compatibly). - New options OPT_CMD_VEXPR and OPT_CMD_CSOP, by default enabled. To include the commands `vexpr'#303 and the new `csop'#166, which now provides the byte string functions of the former. (Still available through `vexpr' until v15.) (I hope to be able to later provide a `usop' or `unisop' or so.) - *v15-compat*#591 can now have a value: if it is set, the `wysh'#130 command modifier which chooses shell quoting rules for some commands is implicit. - We have some (more) backward incompatible changes, though it is likely most users will not recognize the differences. o *headline*#425 format %T is obsolete, %L fits better. o `csop'#166 `hash' and `hash32' subcommands (formerly from `vexpr'#303) use a slightly changed hash algorithm. (Which results in an improved distribution for tested sets of words in power-of-two spaced dictionary.) These are affected by the change in the second next item, too. o Changed to use shell quoting rules for arguments: + `mimetype'#223 and `unmimetype'#224. This is affected by the change in the next item, too. + `shortcut'#273 and `unshortcut'#274. + `mlist'#226 and `unmlist'#227 as well as `mlsubscribe'#228 and `unmlsubscribe'#229. + `alias'#143, too. o Changed (with legacy compat) the "@[i]" modifier prefix to a question-mark ?[case|..] suffix, as is known from URLs. We head towards direction URL syntax, now here too. + `if'#215 and `elif'#186. E.g., 'wysh if "abc" ==?case "ABC"' is true, as well as is 'wysh if 0xFFFFFFFFFFFFFFFF -eq?saturated 36#1Y2P0IJ32E8E7'. "==?" and "-eq?" would have been sufficient, here. (No unsigned mode (yet) for `if'#215.) Yes, `if'#215 and `elif'#186 now support `wysh'#130, and see already expanded arguments, then. No more "triggers". This finally makes it possible to write things like ? wysh if X;A;wysh elif Y;B;else;C;end Note 'else;C' not 'else C'. New operators: '-n "$VAR"' and '-z "$VAR"' work like in the shell, '-N varname' and '-Z varname' do not test the expansion but the existence of variables instead. Two argument forms require `wysh'#130. + `mimetype'#223 markers have changed likewise; this also affects *pipe-TYPE/SUBTYPE*#489 and *pipe-EXTENSION*#496 (with legacy compatibility and -v/-d obsoletion warnings)! ? mimetype ?t text/x-awk awk ? wysh set pipe-application/pdf='?=&?\ trap "rm -f \"${MAILX_FILENAME_TEMPORARY}\"" EXIT;\ trap "trap \"\" INT QUIT TERM; exit 1" INT QUIT TERM;\ mupdf "${MAILX_FILENAME_TEMPORARY}"' + `vexpr'#303 (and `csop'#166) modifiers changed likewise. The case-insensitive subcommands "ifind" and "iregex" have been obsoleted, just use the ?[case] modifier to the regular function instead. P.S.: Thanks to Rich Felker the `regex' subcommands now works as desired even with empty intermediate submatches. o Changed address parse mode for command line arguments plus. This modifies decade old tradition, but results in a more predictable behaviour i think. Most people will possibly even be surprised to see the old behaviour: $ , pp , du ' -> To: du, de , pp new: $ , pp , du ' -> To: "du , de , pp , du " Of course anything but perfect, our address parser is very complicated yet far from being acceptable. (Dr. Werner Fink) This affects: + -b#59, -c#61 and To: receivers, as above. (We also have a new -T#81 receiver multiplexer, which is configurable in this regard, please see below for more.) + The -r#78 address. This saw more changes: the content is no longer evaluated via shell expression parser (when *v15-compat* is set).. unless explicitly requested via the *expandaddr*#409 flag "shquote". + *sender*#528 variable. + `addrcodec'#142 command, likewise; old: ? addrc e du , e , d du , e , d #?1!22/INVAL new: ? addrc e du , e , d "du , e , d" #?0!0/NONE + `digmsg'#174 and `~^'#320 now use this parse mode fix for headers which need a single receiver, which is backward compatible but now safer since it can be fooled less easily (to split into a list what should be a single address, as shown above for `addrcodec'#142). They now can also be forced to use that parse mode for To:, Cc:, Bcc: with a new question mark modifier "?single", here the word "single" is optional. ~^ header insert To?single: exa, ~^ header show to - By established rules and popular demand occurrances of '^From_' (see *mbox-rfc4155*#453) will be MBOXO quoted (prefixed with greater-than sign '>') instead of causing a non-destructive encoding like 'quoted-printable' to be chosen, unless context (e.g., message signing) requires otherwise. Only with *mime-encoding*#462=8bit. - We now support long "Options"#5 -- try --long-help. - Finally, it is possible to force sending out messages with the new *mime-force-sendout*#463 variable. If this MUA has been compiled with iconv(3) support it can happen that sending otherwise valid text messages fails because of invalid bytes sequences according to the locale; setting this new variable will avoid this; use *mime-counter-evidence*#461 to view such messages nonetheless. (Dr. Werner Fink) ChangeLog ^^^^^^^^^ - `mimeview'#225 works again with binary formats. (Russell Bell) - IMAP searches via IMAP without matches no longer report a single match. (Dirk-Wilhelm Peters) - New -Y#87 aka --cmd= option to inject commands to be executed when startup is completed (as opposed to the earlier -X#86 aka --startup-cmd=). These commands appear as if the user had typed them in. - A new *on-history-addition*#482 can be used to filter what enters the `history'#213. - New "fcc" flag for *expandaddr*#409. (Olav Mørkrid) And "domaincheck" will cause target domain comparison against entries in the new *expandaddr-domaincheck*#410. (Olav Mørkrid) - New *mbox-fcc-and-pcc*#452 will write out file and pipe addresses as a plain RFC5322 message rather than an MBOX. (Olav Mørkrid) - The `errors'#190 queue existance and size is announced via *^ERRQUEUE-EXISTS*#354 and *^ERRQUEUE-COUNT*#353. (Russell Bell, Martin Neitzel) - Our MBOX parser is now truly compliant to POSIX. (Dr. Werner Fink) - We follow symbolic links again when writing files. (Russell Bell) - *tls-rand-file*#583 is in fact now necessarily one of the optional *tls-features*#580. (Mike Sharov) - New command line option -T#81 aka --target='FIELD: BODY'. FIELD can be To:, Cc:, Bcc: or Fcc:. The BODY is parsed as a list (just as if the given FIELD would be part of a template message fed in via -t#82), but the "?single" modifier suffix can be used to avoid this. (Dr. Werner Fink) git(1) shortlog: Steffen Nurpmeso (277 + 9) v14.9.11 ("Tit family enjoying a bath"), 2018-08-08 --------------------------------------------------- A hot summer bugfix release, but it surely brings in some new features, like TLS fingerprinting and `digmsg' message access. An embarassing number of bugfixes have been seen, to fix IMAP UID handling on 32-bit hosts, UTF-8, `readall' with empty lines, rare endless iconv(3) loops, false qsort(3)ing of addressee lists, crashes due to false user shell quoting, acceptance of "0" port numbers, and more. Most of these cases now have tests. Credits, in order of commit appearance: Paride Legovini, Andrew Gee, Olav Mørkrid, Kevin McCarthy, Michael Dressel, Jürgen Bruckner, Robert Elz, Rudolf Sykora, Doug McIlroy, Gavin Troy and Jörg Schilling. A special credit to Coverity.com again, it found a bug! (, project number 444.) We welcome Andrew Gee, Kevin McCarthy, Michael Dressel, Olav Mørkrid and Jürgen Bruckner in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - I have discovered that GnuPG can --export-secret-subkey so that the real/full private key is no longer needed to --sign, and the excerpts of the private one can have a different password, too. So i have created a new for-signing subkey: EEC8C2FF. Unfortunately it is not possible to verify new signatures with the old public key, an update is necessary. For example via https://ftp.sdaoden.eu/steffen.asc or just update 1883A0DD via normal gpg(1). - Maildir support is now optional but default via OPT_MAILDIR. (Paride Legovini) - I hope for the last time there has been a change to SSL configuration: i have renamed all ssl* variables to tls*. The old ssl* ones still exist until v15, though, yet obsoletion warnings will be produced. This is so because i expect that in a not too distant future only the term TLS will be around. Also the term CipherList was falsely used, it should have been CipherString. - Most (if not all) commands which take a message list and a file target now use shell-style quoting. (Before that say `copy'#165 scanned backwards over "something possibly quoted", took that off, then treated the rest as a message list. Now shell tokens are parsed starting at the front, the last is taken off, and anything before that is the message list.) (Gavin Troy. 2013.) - `~^#'? "header show" now backward-incompatibly shows the address type in field 1, but since this _only_ applies to non-network addresses i made the change. - We will find ncurses on DragonFly BSD. - On Solaris tests no longer need GNU cksum(1): the Solaris cksum is different only for whitespace separators. (Jörg Schilling) - All generated files reside in .obj/, and the tests run in there, too. A "rm -f .obj" should suffice to clean anything up. ChangeLog ^^^^^^^^^ - `~F'#327, `~f'#328, `~M'#333, `~m'#334, `~U'#342 and `~u'#343 now default to the current message (the "dot"). (Andrew Gee) - *indentprefix*#440 handling has had its pitfalls when quoting messages. (Andrew Gee) - -r#78 will again set *from*#422 even after -S#79 has been used to set *from*. (Michael Dressel) - No longer process From: (*from*#422) content via `alternates'#145 when Sender: (*sender*#528) is set. (Michael Dressel) - Because the priority class of headers was not taken into account, it could happen that addressees in Cc: would remain but the same in To: were removed. (Michael Dressel) - IMAP accounts for RFC 4551 (and 7162) and supports 64-bit UIDVALIDITY. - *spamfilter-rate-scanscore*#565 could crash if specification did not match program output. - Shims for TLSv1.3 support, e.g., for *tls-config-pairs*#577. - Obsoleted *dotlock-ignore-error*, added *dotlock-disable*#403. (Paride Legovini) - In compose-mode, removing the In-Reply-To: header breaks an old, and starts a new thread. (Doug McIlroy) - Added new *forward-inject-tail*#421, *quote-inject-head*#511 and *quote-inject-tail*#512 variables, and extended the meaning of *quote*#507. All of *{forward,quote}-inject-{head,tail}* now support a compose-mode specific set of formats (see *quote-inject-head*#511), for now a few only. (This adds meaning onto the content of *forward-inject-head*#420 as introduced in v14.9.0.) The generated output honours *quote-fold*#510, which now takes an optional third argument in order to produce better output. While here, introduce the new command escape `~Q'#336 which performs full *quote*#507 cycles on the given message list. - Fcc: headers are now understood in -t#82 templates or when placed in compose mode (`~v'#344, *editalong*#404 etc.). Since each such header only takes one addressee, no quoting issues apply, the entire header body is the value. - `~|'#319 will pass the entire message including headers when used as "~||", e.g., prepend a file-carbon-copy message header: ~|| echo Fcc: /tmp/test; cat - New `tls'#289 multiplexer command. Yet primitive and only supports a `fingerprint' subcommand. Supports `vput'#129. The new *tls-fingerprint*#581 variable chain aids in adding support for connection verification without an installed CA certificate pool in conjunction with the new *tls-fingerprint-digest*#582 chain. Consequently *smime-sign-message-digest* has been renamed to *smime-sign-digest*#548 (old version will cease in v15). The latter now defaults to SHA512 if possible. - New MLE commands mle-go-screen-bwd and mle-go-screen-fwd to go backward and forward one screenful. And a new mle-clear-screen command. (Todd C. Miller) - New *expandaddr*#409 setting "shquote" will evaluate addresses as if specified within $'' shell-quotes for -b#59, -c#61, and all direct command line receivers. This allows for, e.g., $ s-nail -Sexpandaddr=shquote '\$contact-mail' - *quote-as-attachment*#508 no longer needs to be set before compose mode is entered in order to become honoured. - Even for -H#68 or -L#71 *folder-hook*#415s will now be called. Possible sorting is also applied. - `='#137 now optionally supports message list arguments and the `vput'#129 modifier in order to store the result list. The new `digmsg'#174 multiplexer adds some message access, just like `~^'#320 does in compose mode. In fact the set of commands is shared, yet only in compose mode `digmsg' can change messages or access attachments until v15, however. For example, #?0[steffen@essex nail.git]$ cat > /tmp/z.rc <<'_EOT' define one { if [ "${#}" -gt 0 ] digmsg create $1 - # no `read'/`readall' overlay but stdout #digmsg $1 header list digmsg $1 header show subject digmsg remove $1 shift \eval xcall one "$@" \end } define all { local set all # localize ("localopts yes" would do too) vput = all *; echo all: $all; eval call one $all } _EOT #?0[steffen@essex nail.git]$ MAILRC=/tmp/z.rc \ .obj/s-nail -:u -Snoheader -Squiet -Rf /tmp/z ? call all all: 1 2 3 212 Subject Re: [S-mailx] FYI: after USB stick loss i have rotated keys, plus 212 Subject Re: Problem with page? 212 Subject Re: s-nail Source ... ? x git(1) shortlog: Steffen Nurpmeso (203) v14.9.10 ("(40th Mail anniversary) Blue tit"), 2018-03-25 --------------------------------------------------------- On this day in 1978 Kurt Shoens placed the following comment in def.h (now it is in nail.h): /* * Mail -- a mail program * * Author: Kurt Shoens (UCB) March 25, 1978 */ v14.9.10 is mostly a stability and bugfix release. It has seen a full test series including Coverity.com scans. It fixes bugs i have introduced (also a double free in IMAP cache that i introduced for v14.9.* series to address Coverity CID 1376978..). In the end i am saying thanks to Gunnar Ritter for the IMAP module, and absolutely especially his really neat idea of an IMAP cache including offline work queue. (IMAP will nonetheless temporarily go in v15, but these ideas will come back thereafter.) I have gray hairs now. Credits, in order of commit appearance: William Yodlowsky, Stuart Henderson, Jörg Schilling, Viktor SZÉPE, Rich Felker, Ralph Corderoy and Philipp Gesang. A special credit to Coverity.com again. Because: tcc is 618496 bytes, pcc is 851968+24576 bytes, but gcc is 73355264 bytes and clang is even 147406848 bytes, i wonder why the latter two never said a word that would have addressed the pretty obvious CID 1387053! [Use of initialized value, the author.] We welcome Stuart Henderson and Philipp Gesang in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - The balls are now build with umask 0022 not 0027. (William Yodlowsky, Stuart Henderson) - One actual development of this version was the addition of multiple choice VAL_ues, as documented in make.rc. For now we have VAL_IDNA (for OPT_IDNA) VAL_IDNA="idnkit idn2 idn" and VAL_RANDOM (by itself) VAL_RANDOM="arc4 ssl libgetrandom sysgetrandom urandom builtin" (Stuart Henderson) In brief: The value is interpreted as a whitespace separated list of strings, like "idn2 idn idnkit", case is ignored, order is important. The special strings "all" and "any" as well as the empty value are wildcard matches; if any entry in the list is a wildcard match, the rest of the list is ignored. The special string "error" will abort configuration once its list position is reached; this is only supported if documented, and not with an accompanying OPT_ (which then offers "require", as below). Since this VAL_RANDOM approach is so much better i have dropped OPT_SSL_RANDOM and OPT_NOEXTRANDOM that were recently introduced again. They were c..p. - Support for idnkit 2.3 has been added. Support for idnkit 1 (especially as idnkitlite) has been fixed. - For the first time this codebase should be able to handle invalid MBOX mailboxes (produced by, e.g., dma(1)) gracefully. I hope i have found all places (sic) where code has to be fixed. E.g., "? copy * INVALID-MBOX" now works. (Smalltalk already knew objects which know what they are doing are for the better... This is v15, then.) - P.S.: the two FreeBSD test failures are noted in INSTALL. ChangeLog ^^^^^^^^^ - *asksend*#368 will now really allow recomposing. - `help'#212 now supports recursive `commandalias'#162es, and command self-recursion detection now works differently, it has been false for something like commandalias x q; commandalias q echo au since q became expanded to `quit'#247 (alias expansion equals new command word). New behaviour: we allow equals once: commandalias q q; commandalias x q; x -> x -> q -> q -> quit - *editalong*#404 can have a value, say "set editalong=v" and it will startup $VISUAL#624 not $EDITOR#602. - Path separators are now normalized, thus all places, including MLE tab-expansion ("On terminal control and line editor"#17), can expand something like "///t*////t*". - -E#64 flag will not be obsoleted. -D#62 flag has been reintroduced (sets *disconnected*#649 right away, was not reinstantiated with the rest of the IMAP support.) git(1) shortlog: Steffen Nurpmeso (71) v14.9.9 ("Marsh tit savours first spring sun, II") 2018-03-06 ------------------------------------------------------------- A bugfix release. I hope with this the fallout of the Christmas 2016 "address the Dr. Problem workshop" has been fully resolved and thus MIME for header address fields, even if iconv(3) is involved, been fully restored! We have even more tests for this now. The release v14.9.8 was broken on big endian machines. I will remove the v14.9.8 balls from the server by the weekend. Sorry for the inconvenience! Credits, in order of commit appearance: Slavko, Matej Mužila, Rich Felker, Simon McVittie, Paride Legovini, Cág, Predrag Punosevac. We welcome Slavko, Matej Mužila, Rich Felker and Simon McVittie in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - The v14.9.* series called *pipe-TYPE/SUBTYPE*#489 handlers in display or quote mode with CR (carriage-return) bytes stripped because of a missing output file comparison check, which broke binary formats etc. (Slavko) - We now have native support for Libidn2. (Matej Mužila) - uname(1) is now hookable by setting the shell variable uname when calling make ("uname=MY-UNAME make config" etc.). (Simon McVittie) We no longer bake the kernel version into the binary, and `version'#302 includes uname(2) output. (Simon McVittie, Paride Legovini) - We now support a fallback P(seudo)R(andomNumber)G(enerator) initialization even if getrandom(2)/getrandom(3) has been found by the configuration, just like we do for "/dev/urandom" usage. This does not affect systems with arc4random(3) or OpenSSL random usage. (David Čepelík, Simon McVittie) A new OPT_SSL_RANDOM make.rc variable, by default initialized to the value of OPT_SSL. ChangeLog ^^^^^^^^^ - `~@'#318 list-edit behaviour in -##89 batch mode was broken. - Character set names will now undergo generic normalization, including stripping of iconv(3) //SUFFIXes. git(1) shortlog: Steffen Nurpmeso (33) v14.9.7 ("Marsh tit patiently scraping bark") 2018-02-16 -------------------------------------------------------- A maintenance release which fixes bugs and brings in features. Credits, in order of commit appearance: Alexander Harm, Viktor SZÉPE, Paul Eggert, Joseph Bisch, Paride Legovini, and Peter J. Holzer. A special credit to the disappearing mutt(1) bug tracker. And to Gmane.org for creating gmane.mail.s-mailx.general! Thanks Paride Legovini for becoming maintainer of the Debian port. We welcome Joseph Bisch, Paride Legovini, and Peter J. Holzer in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - The USB stick loss reported for v14.9.6 was fake news, so to say, the stick exists and therefore the old key is not compromised. - We are back at Gmane.org! news.gmane.org/gmane.mail.s-mailx.general - `history'#213 has learned to be context-sensitive a bit, and has two new subcommands, `load' and `save'. This is in parts backward incompatible because it needs a new *history-file*#428 format; however, the old format can be loaded yet compose-mode commands will not appear in compose mode no more. Iirc you can start with an old format then `save' to the new, then replace the "d" in the first column with "c" for compose-mode commands which should appear correctly. - Obsoletion warnings for variables now happen at `set'#269 time instead of when used. Running once via -v#85 may be beneficial. - The saturation modifier of `vexpr'#303 is henceforth a prefix, the suffix version is obsolete (but still supported for a while). - A network address that contains no domain-, but only a valid local user in angle brackets will be automatically expanded to a valid address when *hostname*#433 is set to a non-empty value; setting it to the empty value instructs us that the used *mta*#465 (including builtin SMTP) will perform the necessary expansion. (Viktor SZÉPE) Note that *hostname*#433 as well as *smtp-hostname*#551 will now undergo IDNA expansion if IDNA is supported. And *from*#422 and *sender*#528 are now verified at `set'#269 time, not when used. (Viktor SZÉPE) - The commit message in [d503bd82] is wrong, apologies to Paride Legovini. The test(1) operator "-n" appeared in Seventh Edition UNIX, not V8 as falsely claimed. ChangeLog ^^^^^^^^^ - Our `addrcodec'#142 parser chokes on lesser constructs. - Presence of command-line MTA arguments without *expandargv*#411 are now a hard error. It was my fault that this was not the default from the very start. (Viktor SZÉPE) - Seen on the mutt bug tracker, we also still have had problems with time settings that cross 32-bit boundaries. As that is in parts induced by the C standard, now implement those parts on our own, and be super careful in general. (Joseph Bisch) - The `~@'#318 command escape did not shell-unquote the user input again and was thus a bit broken; message attachments also work again. - Support custom headers from the command line via -C#60. And *customhdr*#397 is verified upon `set'#269 time. - The simple builtin HTML viewer now supports
elements, which many web mailers, most notably gmail, use for citation. (Peter J. Holzer) git(1) shortlog: Paride Legovini (1), Steffen Nurpmeso (66) v14.9.6 ("Marsh tit abiding a snow storm"), 2017-12-05 ------------------------------------------------------ A bugfix release which fixes four serious and three other bugs. A few new features came in, too. Many thanks go to Ralph Corderoy who reported an issue that was caused by a terrible, terrible word reversal that i managed to produce in December 2016, and which caused the v14.9.x series to not MIME encode (non-address) content of address header fields! Credits, in order of commit appearance: Thomas Dickey, Andreas Baumann, Erich Eckner, Gaetan Bisson, Solar Designer, Cág, Ivan Tham, Ralph Corderoy and Doug McIlroy. We welcome Andreas Baumann, Erich Eckner, Solar Designer and Cág in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - After USB stick loss the authors OpenPGP key has been switched to pub 4096R/1883A0DD 2017-11-30 [expires: 2027-11-28] Key fingerprint = EE19 E1C1 F2F7 054F 8D39 54D8 3089 64B5 1883 A0DD uid Steffen Nurpmeso - $TMPDIR#622 no longer honoured for root runs. (Solar Designer) - *mime-encoding*#462 defaults to quoted-printable again. (Cág) - We _can_ MIME encode even header fields which contain addresses. Thanks to Ralph Corderoy we now also _do_ so again! ChangeLog ^^^^^^^^^ - ***#336 now uses *ifs*#435 when splitting. - Freezing *ttycharset*#587 via -S#79 also survives using or setting any of $LC_ALL#604, $LC_CTYPE#605 and $LANG#606 during program startup. - New `local'#126 command modifier to localize changes. Yet supported only for `set'#269, i.e., we have gained macro-local variables. - `vexpr'#303 now supports a BASE#number notation for integers, like 16#AFFE as an alternative to 0xAFFE. Hint: variable settings can most often use several bases, too, e.g., i have "set mime-counter-evidence=0b1111". - Very simple form of *quote-chars*#509 to adjust our knowledge of what actually is to be treated as a quote character. - *mime-counter-evidence*#461 deep inspection (bit four) has been improved for the sole cases of quoting or displaying a message. So messages with less than 25% of control characters and such will now be displayed (made printable). This is yet not configurable nor do we have a way to easily access a message with more than that. (Doug McIlroy) git(1) shortlog: Steffen Nurpmeso (44) v14.9.5 ("Marsh tit engaged with a peanut"), 2017-10-21 ------------------------------------------------------- A bugfix release which fixes two bugs which were cast in stone. A few compatibility improvements (AlpineLinux, Solaris). And minor features. Apologies to Jörg Schilling, a git bug i think it was who caused joining of changesets, losing a credit, and it had been pushed to [master] before the problem was realized. Credits, in order of commit appearance: Jörg Schilling, Doug McIlroy, Random832, Nick Stoughton and Ivan Tham. We welcome Nick Stoughton and Ivan Tham in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - New OPT_USE_PKGSYS option can be disabled to not automatically pick known package system paths (pkg(7), OpenCSW, schily). (Jörg Schilling) ChangeLog ^^^^^^^^^ - The software indeed _never_ dealt with iconv(3) output character set errors (as opposed to invalid input character set byte sequences etc.) for the main message body! And I have missed that when i tweaked our iconv layer a bit! - Fixed a race condition with sigsuspend(2) that i could only see on OpenBSD. config.h offers n_SIGSUSPEND_NOT_WAITPID, by the way, which saves some systemcalls and did not run races, but noone adjusts this file. - Message list specifications gained two new colon modifiers, one can now "search :Ll" to find "Mailing lists"#10. The *headline*#425 format %T now also uses L and l rather than S and L accordingly. New `addrcodec'#142 subcommand `skinlist' acts like `skin' but stores in *!*#348 *^ERR*#350-EXIST if the address is one of the known "Mailing lists"#10. - `echo'#181 family now supports `vput'#129 and *!*#348 error storage, offering some kind of printf(1) experience, almost. git(1) shortlog: Steffen Nurpmeso (35) v14.9.4 ("(5th anniversary) Marsh tit"), 2017-09-18 --------------------------------------------------- This is an update feature release but which also ships a furious number of bug fixes, about six of which were pretty serious. It also applies overall trimming, and improves configuration time compatibility on macOS. Thanks to Alexander Harm there is now a macOS Homebrew package. Credits, in order of commit appearance: Paul Vojta, Daniel Lublin, Alexander Harm, Norman Ramsey, Viktor Szépe, Rich Salz, David Čepelík, Ralph Corderoy, Stéphane Chazelas, Aharon Robbins, Ken Hornstein. We welcome Daniel Lublin, Alexander Harm, David Čepelík and Stéphane Chazelas in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Out-of-tree builds have become possible via the new make-emerge.sh script: $ cd /tmp && mkdir build && cd build && ~/src/nail.git/make-emerge.sh && make tangerine DESTDIR=.ddir We now have a `citron' make target which is like `tangerine' but does not run the tests. - Configuration with OPT_AUTOCC honours $CC=cc. (Norman Ramsey) - SSL/TLS configuration has been revamped (again) in order to support new possibilities of OpenSSL (and LibreSSL) without ending up and introducing more and more variables. Instead we now have *ssl-config-pairs*, a comma-separated list of all options. With e.g. OpenSSL 1.1.xx this will be directly passed through to SSL_CONF_cmd(), so there _anything_ can be passed, otherwise we use a builtin parser to map. The new *ssl-features*#? states what is supported. E.g.: if [ "$ssl-features" =% +ctx-set-maxmin-proto ] wysh set ssl-config-pairs='\ CipherList=TLSv1.2:!aNULL:!eNULL:@STRENGTH,\ Curves=P-521:P-384:P-256,\ MinProtocol=TLSv1.1' else wysh set ssl-config-pairs='\ CipherList=TLSv1.2:!aNULL:!eNULL:@STRENGTH,\ Curves=P-521:P-384:P-256,\ Protocol=-ALL\,+TLSv1.1 \, +TLSv1.2' endif OpenSSL v1.1.xx also introduces an interesting and neat idea to centralize SSL/TLS configuration of (all) programs in a single file. This can be driven via *ssl-config-file* and the new *ssl-config-module* variables, several entries per program are allowed, see *ssl-config-module* for an example. New manual section "Encrypted network communication"#13. - Variables set or unset via -S#79 are now frozen until program startup is complete. ChangeLog ^^^^^^^^^ - Historical behaviour of *askcc*#366 / *askbcc*#367 has been reintroduced. (Norman Ramsey) A new *asksend*#368 variable will show a final header summary and allows reentering compose mode. Set by default. POSIX mirrors *ask* onto *asksub*#370, so dropped" the former. - `~^'#320 no longer normalizes header names to titlecase. - We no longer generate charset=binary MIME parameters. This was introduced on 2013-01-02 and was i think owed to file(1)s -i output as i failed to find any other reference. (Normal Ramsey) - *mime-alternative-favour-rich*#460 now also works for handlers installed via *pipe-TYPE/SUBTYPE*#489. (Viktor Szépe) - v14.9.* series did not generate In-Reply-To: headers! - `alias'#143 now supports high-bit bytes and semicolon. Expect that at some later time the input must be valid according to the locale, though. (Norman Ramsey) - Combinations of *record*#515 could crash because of an unterminated variable function argument list. (Norman Ramsey) - New command `readall'#249 loads an entire file into a variable. *signature*#535 has been obsoleted. - `vexpr'#303 now supports negative arguments for the substring subcommand and adds trim, trim-front and trim-end subcommands. - `!'#133 can be used in send mode. - `~A'#321, `~a'#322, `~I'#331 and `~i'#332 will henceforth expand \t and \n only if *posix*#502 is set. Please use `set'#269 instead (with `wysh'#130, until v15). - New "The mime.types files"#35 type marker: @q ("quiet"). git(1) shortlog (edited): Steffen (Daode) Nurpmeso (90) v14.9.3 ("Crested tit nibbling sunflower seeds"), 2017-08-03 ------------------------------------------------------------ This is a bugfix release but which ships some improvements, too. It silently replaces both of v14.9.1 v14.9.2 from earlier this week, which were broken or not entirely fixed. Credits, in order of commit appearance: Felix Fontein, Paul Vojta, Ralph Corderoy, Christos Zoulas, Gavin Troy, Gaetan Bisson. Thanks, Coverity.com. We welcome Christos Zoulas in THANKS. Apologies to Viktor Szépe for the false spelling of his name in the v14.9.0 announcement. And to Gaetan Bisson for not giving credit for [14fbce97]! NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - fakeroot support was blindly taken from Debian and broken. (Gavin Troy, Gaetan Bisson) - Base64 output was broken for cases which involved iconv(3). The data is not lost, you can read it with S-nail v14.9.0 and above, and save it somewhere. I know of no other base64 decoder which reads those things correctly, though. We now have tests. Along this i fixed an iconv(3) error which likely caused stateful decoding (like, e.g., for ISO-2022-JP) to fail because of an unnecessary reset of the iconv(3) state machine. Thanks to Gaetan Bisson for mentioning this issue! ChangeLog ^^^^^^^^^ - In compose mode the MLE allows empty lines again. - We no longer require a writable $HOME#603. Due to false code flow (but but but: with correct comment) a non-writable $HOME entry in /etc/password (i.e., from getpwuid(3)) would lead to a crash. (Felix Fontain; Ralph Corderoy) - Two faulty string operations slipped into the IMAP code, resulting in a crash and a "is-same-host" test that would fail for IMAPS connections like `save'#266 or `copy'#165 because of an implicit IMAP protocol for the target of those operations (thus IMAP != IMAPS). (Paul Vojta) - The MLE tab-expansion will now automatically append a "/" if there is only one possible expansion and that is a directory, saving the user one . (Christos Zoulas) The shell expression parser had a bug regarding understood metacharacters (;|&), which in turn could cause an infinite loop in the MLE tab-expansion for, e.g., "move &9 +", because the "&" would never have been stepped over. - New `~I'#331 command escape is like `~i'#332 but does not append a newline. - `localopts'#218 gained an optional second argument. It is now possible to specify that any macro `call'#151ed will have localopts enabled, and it is possible to fixate the setting so that it cannot be reverted. - *@*#356 should now act completely compatible to the sh(1)ell, thus obsoleting my hysteric warnings in the v14.9.0 announcement. - The `Lreply'#219, `reply'#254, `Reply'#253 series as well as `mail'#221 now manage the error status *!*#348. I.e., there are now errors like *^ERR*#350-DESTADDRREQ, ^ERR-NODATA, ^ERR-PERM and similar. It is not perfect yet, because $DEAD#601 may have been written (with *save*#523) or not, for example. `Lreply' and `reply' have been rewritten rather completely indeed. They join Reply-To: and Mail-Followup-To: dependent on the context (i.e., *reply-to-honour*#521, *followup-to-honour*#418, see "Mailing lists"#10 for the picture), and if they did, use this list as the receivers exclusively. It now honours *recipients-in-cc*#514 even for such addressees. (And now i wonder whether i should have credited Paul Vojta for that.) Also `Lreply' would have crashed for mails with Reply-To: but without *reply-to-honour*#521 set. We now have a test. Note *replyto* is obsoleted in favour of *reply-to*#520. v14.9.0 ("Long-tailed tit"), 2017-07-16 --------------------------------------- This is a major feature release which took about ~22 months (24 less two) of development to complete, and which imposed massive changes under the hood, but also quite a lot of user visible changes, including some **backward incompatibilities**. As usual, "s-nail -d" will show obsoletion warnings. We gain noticeable improvements regarding scriptability and its reliability, but also for interactive use cases, especially notable to users is our completely new M(ailx)L(ine)E(ditor) that supports rather real tabulator expansion and program-mode-context- sensitive key bindings. We now support macros with arguments, which can be `shift'ed, a `return' status can be used, and a `vexpr' multiplexer offers some arithmetic and string operations. `commandalias'es are recursive, further command modifier prefixes, like `ignerr', give a hand that we otherwise could not offer. In compose-mode the new `~^' command escape allows some message and attachment access, and can be used, e.g., to implement things like custom headers, and has been especially designed for scripted access via the new *on-compose-splice* and *on-compose-splice-shell* hooks. S-nail will move (more or less) backward-incompatibly to sh(1)ell compatible argument quoting (documented in "COMMANDS"), and an increasing number of commands do support this already: new ones exclusively, some old ones have either been switched (like `localopts'), others -- noticeably `set' -- can be switched to the new syntax with a `wysh' command modifier prefix. E.g.: ? define __xv { # Be careful to choose sh(1)ell-style on _entire_ line! localopts yes; wysh set verbose; ignerr eval "${@}"; return $? } ? commandalias call echo boo-boo ? commandalias xv call __xv ? xv list ? commandalias xv '\'call __xv ? xv list Calling the latter `xv' for `list' will give more detailed command information, including which kind of argument is used. I have not managed to implement the three features i have started this development cycle for, these are thus subject to further development, just like wysh for message-list argument commands to support, e.g., negation, wysh for `if' and consorts, the -- terminator to finally overcome the ridiculous requirement to quote entire shell commands filenames for commands like `pipe. And and and. Credits, in order of commit appearance: Antonio Radici, Aharon Robbins, Mike Frysinger, Predrag Punosevac, Michael Convey, Hariskar, Rudolf Sykora, Martin Neitzel, Gavin Troy, Salvatore Bonaccorso, Todd C. Miller, Sergey Matveev, Robert Elz, Mantas Mikulėnas, Respiranto, Jens Schleusener, Walter Alejandro Iglesias, Ralph Corderoy, David Levine, Lyndon Nerenberg, Thomas Dickey, Afan, Justin Ellingwood, Ingo Schwarze, Viktor Szépe, Gaetan Bisson, Juan RP, William Yodlowsky, Hilko Bengen, Matthew Dillon, Colin Watson, Donald Mugnai, Stephen Isard, Jürgen Daubert, Sven Neuhaus, trondd, Ismael Bouya, Felipe Gasper, Paul Eggert, Dr. Werner Fink, Ken Hornstein, Noel Chiappa, Random832, Doug McIlroy, Baptiste Daroussin, Riccardo Ductor, Pietro Cerutti, Jörg Schilling, rain1, Xin LI. We welcome Antonio Radici, Mike Frysinger, Predrag Punosevac, Michael Convey, Rudolf Sykora, Todd C. Miller, Robert Elz, Jens Schleusener, Walter Alejandro Iglesias, Thomas Dickey, Afan, Justin Ellingwood, Viktor Szépe, Juan RP, Matthew Dillon, Colin Watson, Donald Mugnai, Sven Neuhaus, Ismael Bouya, Felipe Gasper, Paul Eggert, Dr. Werner Fink, Ken Hornstein, Noel Chiappa, Random832, Doug McIlroy, Baptiste Daroussin, Riccardo Ductor, Pietro Cerutti, Jörg Schilling, rain1, and Xin LI in THANKS. Apologies: Sergey Matveev. Members of the Roff community which await progress. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * This release brings some backward incompatibilities, outlined in the following. Most users will not be affected, and we have added a lot of compatibility cruft, but that will vanish in v15. "$ s-nail -v"! * The configuration and build system has changed. Packagers have received updated package files. o Anything which was WANT_xy before is now OPT_xy, and compiled-in paths and values, like PREFIX or PAGER, have gained a VAL_ prefix (thus VAL_PREFIX and VAL_PAGER). This is _not_ true for non-persistent or environmental values, e.g., DESTDIR, CC, etc., and also not for the overwritable program variables during configuration, e.g., $awk. o SENDMAIL -> VAL_MTA, SENDMAIL_PROGNAME -> VAL_MTA_ARGV0, MAILSPOOL -> VAL_MAIL. And NAIL -> VAL_MAILX, though this is still a lie. o The make system now needs config..build..install or all..install or tangerine (config..build..test..install). Some constants which some experts may want to fine-tune have been moved to config.h. Usual adjustments+doc via make.rc. o The `build' phase can be parallelized by setting the $MAKEJOBS environment variable, e.g., "make MAKEJOBS=-j4 build". Note this variable is not tracked in the configuration. (Gaetan Bisson) o Unless DESTDIR is set an uninstallation script will be installed along with the rest (see INSTALL file for more). o Set the new OPT_CROSS_BUILD to avoid feature runtime tests, only compile- and link-availability will be tested. (Juan RP) o VERBOSE is implemented straight, but must be given at configuration time in order to become honoured. (William Yodlowsky) o ADDCFLAGS / ADDLDFLAGS -> EXTRA_CFLAGS / EXTRA_LDFLAGS. o The LD_LIBRARY_PATH etc. building processes will skip any path which contains the string "fakeroot". (Hilko Bengen) o We honour a set $SOURCE_DATE_EPOCH#620 environment variable to an extend that allows reproducible tests, which is why the repository gained a [test-out] branch with some expected plain text outputs. (reproducible-builds.org; Colin Watson) The new *log-prefix*#447 variable aids in improving the reproducibility of error messages. o These are upward compatible changes. * "make OPENSSL_API_COMPAT=0x10100000 all" should work. * Internal and environment variables are now explicitly _defined_ and _tracked_ after variable handling has been rewritten completely. Notes: o This means that, e.g., "$ password=NOT_SECRET s-nail" will **NOT** work no more, since *password*#487 is an internal variable! o But if you do, e.g., "? set TMPDIR=~/tmp", then this will also be reflected in the program environment (it is an environment variable) and thus affect child processes. o Therefore we no longer have `setenv' and `unsetenv'. o To integrate any other environment variable transparently into our variable management, the new command `environ'#189 needs to be used, e.g., "? environ set NEWVAR=value" or "? environ link EXISTINGVAR". - -H#68 and -L#71 have been decoupled: it used to be -e#65 -L#71 instead! - *NAIL_{HEAD,TAIL}* have been obsoleted in favour of *message-inject-head*#456 and *message-inject-tail*#457. *NAIL_HIST{FILE,SIZE}* have been obsoleted in favour of *history-file*#428 and *history-size*#431. *NAIL_EXTRA_RC* has been obsoleted in favour of *mailx-extra-rc*#450. *batch-exit-on-error* has been obsoleted by *errexit*#407, which works just like the POSIX sh(1)ell "set -e" construct; the `ignerr'#125 command modifier (`-' for command escapes in compose mode, and see below) can be used to ignore command errors even then. (This will remain even if we at some later time will support at least some of the sh(1) constructs which "swallow" failures with set -e.) *bsdannounce* is obsolete, the feature is integrated in *header*#424 as this is much more useful. (This is however also dependent upon the also new but well-known $POSIXLY_CORRECT#618 <> *posix*#502, but that is just how it is; these affect more behaviour, and increasing.) - Colour support has been changed backward in- and upward (from user interface side) compatibly, see the manual section "Coloured display"#18. + New commands: `colour'#160 and `uncolour'#161. You can define context-sensitive, terminal-capability- sensitive settings, e.g.: if terminal && [ "$features" =% +colour ] colour iso view-header ft=bold,fg=magenta,bg=cyan colour 256 view-header ft=bold,fg=208,bg=230 subject,from colour mono view-header ft=bold colour mono view-header ft=bold,ft=reverse subject,from endif + The variable *colour-pager*#393 defines whether colour and font attribute sequences should be generated when viewing something in $PAGER#616. + Set the variable *colour-disable*#392 to turn colour off without affecting established settings. + It is deduced via termcap(5) (see below) whether the terminal supports colors, e.g., "$ s-nail -Stermcap=Co#256". This is also true if we don't have termcap support. + Support for 256-colour terminals. (Gavin Troy) - `source'#281 series support shell pipes if the last character of the "filename" ends with a vertical bar |, e.g., ? source 'gpg -qd ~/.s-nailrc-private.gpg |' - Shell pipes are also supported as targets for `move'#231, `copy'#165 etc., yet unfortunately not with via a sh(1)ell token parser, so that the target still has to be a single argument. ? copy . '| cat; echo huhu' - Support for custom headers via the new `~^'#320 compose-mode command escape and in addition, or alternatively, with the internal variable *customhdr*#397, which also can be covered by `localopts'#218. (Sergey Matveev) + Support of $ORGANIZATION has been dropped. + Command escape `~e'#326 supports _any_ header. + Command escape `~^'#320 supports _any_ header. - New -:#55 command line option can be used to more easily select which startup files should be loaded, e.g., -:/ loads none. (Robert Elz) - `account'#140s and *folder-hook*#415s now have `localopts'#218 enabled by default. - A first simple form of compose-mode hooks has been implemented: *on-compose-enter*#478, *on-compose-leave*#479 and *on-compose-cleanup*#477 can be set to macros which get invoked at appropriate times. For the `resend'#258 series there is *on-resend-enter*#485 and *on-resend-cleanup*#484: this is very likely to change once true message access is possible even in this mode. An even more powerful mechanism is available via the also new *on-compose-splice*#480 and *on-compose-splice-shell*#481 hooks. These are executed in child processes and communicate with the parent via their standard input and output, and therefore can do anything and act as if they were the user. `localopts'#218 are enabled and cannot be disabled (and extend until the message is sent). (Jens Schleusener, Rudolf Sykora) ? set on-compose-splice=ocs ? define ocs { read ver echo Splice protocol version is $ver echo '~^header list' read hl; vput vexpr es substring "${hl}" 0 1 if [ "$es" != 2 ] echoerr 'Failed to read header list, bailing out' echo '~x' elif [ "$hl" @i!% ' cc' ] echo '~^header insert cc Diet is your ' read es; vput vexpr es substr "${es}" 0 1 if [ "$es" != 2 ] echoerr 'Failed to insert Cc:, bailing out'; echo '~x' end end } - "The .netrc file"#37 + gained support for comments. (Walter Alejandro Iglesias, Ralph Corderoy) + `netrc'#234 now has a "load" subcommand. + the new *netrc-pipe*#472 obsoletes OPT_AGENT and *agent-shell-lookup*, and can be used to load an encrypted .netrc file, e.g.: ? set netrc-lookup netrc-pipe='gpg -qd ~/.netrc.gpg' I.e., this is in usual .netrc syntax and thus possibly much nicer than saying "? source 'gpg -qd ~/.credentials.gpg |'". - termcap(5) / terminfo(5) support has been changed backward in- and upward (from user interface side) compatibly, please read "On terminal control and line editor"#17. + OPT_TERMCAP is by default enabled. The new, by default enabled, configuration option OPT_TERMCAP_VIA_TERMINFO can be used to (try to) use terminfo(5) instead. + The variable *termcap*#568 can be used to freely define or override terminal capabilities, and *termcap-disable*#570 will disable interaction with the chosen library, leaving only *termcap* in charge. To use the so-called ca-mode on supporting terminals, effectively turning S-nail into a fullscreen application, *termcap-ca-mode*#569 must be set. + The built-in line editor has been rather completely rewritten to be the Mailx-Line-Editor (OPT_MLE, default yes), and supports wide glyphs (if possible), infinite line lengths (2 GB) and more. Tabulator expansion is no longer an option (but needs fnmatch(3)). + Optionally (OPT_KEY_BINDINGS, default yes) it has become possible to freely define key bindings for the MLE via the new `bind'#149 and `unbind'#150 commands. These key bindings can make use of termcap(5) and/or terminfo(5) names. The MLE will install a set of default bindings (unless there is a set *line-editor-no-defaults*#446), more so with OPT_TERMCAP, i.e., try "? bind*". Sufficient support provided, one can now, e.g., type "p " and then collect the message numbers to type, scrolling forward and backward via key-bindings, without losing the line content, then commit the final line. + OPT_EDITLINE and OPT_READLINE support have been dropped. The new MLE should not miss anything. Does it? Tip: in an UTF-8 locale try "? !touch /tmp/hall{,öchen}" and then autocomplete that: once, then ^Q, and again. - `source'#281 can be used in `call'#151ed macros. What sounds so innocent replaced an entire machinery and got rid of a brilliant idea of Kurt Shoens from the 70s, but which never worked with Nail/Heirloom extensions, namely macros, and in the right order. Accompanying this -X#86 can (dig multiline arguments and can) be used to define macros and run them etc. Should work: $ s-nail -X'define x {' -Xversion -Xx -X'}' -X'call x' $ s-nail -X'source \' -X'"echo version|"' -Xx Macros can be `undefine'#171d from within themselves, and re- `define'#170d. It is still not possible to define macros from within macros, and/or have inner macros, not to talk about local scoping or anything more sophisticated such. - -u#83 / $LOGNAME#609 ($USER) handling has been redefined, and "-u USER" is now exactly the same as "-f %USER", and $LOGNAME (and $USER) is actively set to the active user. (Afan) $LOGNAME#609 is POSIX standardized and henceforth used and preferred over $USER, which came from BSD. (Todd C. Miller) - In the future (at least non-message-list) argument handling will be changed backward-incompatibly to be sh(1)ell compatible (and thus POSIX standardized), see "Shell-style argument quoting"#23. New commands use it already today (`bind'#149, `colour'#160, `headerpick'#209), some others (most importantly, `set'#269) can be forced to do so via the new `wysh'#130 command prefix, as in: ? wysh set message-inject-tail=$'\n--steffen' ? bind base $'\cA,\x61' 'echo control-A and small a' - We now actively manage *umask*#589: 0077 by default, but an empty string will use the setting that is active upon startup. Just like changes to (known) environment variables, this setting will also be inherited by any child process. (Walter Alejandro Iglesias) - Anything SENDMAIL / *sendmail*-ish has been renamed to *mta*#465, *mta-arguments*#467, *mta-no-default-arguments*#468 and *mta-argv0*#470. The reason is that in v15 we won't even have *smtp*: it is just another form of MTA, and thus obsolete by itself. Note that *mta-arguments* is now parsed via the shell-token parser, so the following ends up exactly as desired. ? set mta-arguments='-t -X "/tmp/my log"' For now we support a hack that understands a file:// URL in *mta*, too, but that is also the default if there is no protocol. E.g.: "? set mta=smtp://a:b@xy.z" - The "spamd" *spam-interface*#555 is obsolete. I haven't tested it since my main machine died, it is error prone since it assumes internals of the spamassassin wire protocol, and there never was a speed improvement over "spamc". (However it could react upon the "is-spam" state of a message, which "spamc" doesn't allow.) - The new *inbox*#439 variable will henceforth be looked up when searching for a primary system mailbox (as in "? File %"), followed by the usual $MAIL#610 and compile-time defined local mailspool search. (Stephen Isard, Jürgen Daubert) - The semantic of -a#57 and `~@'#318 have been changed, and both commands now use the same syntax: -a file[=input-charset[#output-charset]] - New "failinvaddr" keyword for *expandaddr*#409. - We finally "can" the so-called (by myself) "Dr. Problem" (a bit): (Dr. Werner Fink) $ ' 2>&1 |\ grep To: s-nail: >>> To: "Dr. D. Iet" This can be done via the new `addrcodec'#142, too, note this supports multiple modes (and the `vput'#129 command modifier): $ echo 'addrcodec e Dr. Diet Curd' | s-nail -#:/ "Dr. Diet Curd" - All commands with the string "codec" in their name use different argument quoting, namely none at all, please read "Raw data arguments for codec commands"#25. This means that `urlcodec'#299 (and `imapcodec'#648) has slightly changed semantics. And, while here: there is a new `shcodec'#271, too. - We gained "Command modifiers"#21: `\'#124 (avoid expansion of `commandalias'#162es), `vput'#129 (store result in variable), `ignerr'#125 (ignore an error of the following command, even if the new *errexit*#407 is set), `wysh'#130 (use shell-style arguments). $ echo 'vput cwd resvar;echo $resvar' | s-nail -#:/ /home/steffen/src/nail.git And the usual sh(1) stuff: `return'#264, `shift'#275, `eval'#191, plus a `xcall'#307 stack-avoidance optimization (to be used in place of a `call'#151 which would be the last called command). And an "expr(1) like thing", yet simple, `vexpr'#303. $ echo 'vexpr + 1 2' | s-nail -#:/ 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000011 03 | 0x3 | 3 $ echo 'vput vexpr resvar + 1 2;echo $resvar' | s-nail -#:/ 3 We actually start walking (*?*#347, *^*#349). ? vput vexpr res regex 'bananarama' 'Bana(.+)' '\$1\$0' ? echo $?/$^ERRNAME :$res: 1/NODATA :: ? vput vexpr res iregex 'bananarama' '(.+)rama' '\$1\$0' ? echo $?/$^ERRNAME :$res: 0/NONE :bananabananarama: The command `vpospar'#304 can be used to manage the stack of positional parameters, i.e., much like "set --". It also offers the possibility to save and restore the stack to and from variables. Etc. Btw., to contact the maintainer (make.rc variables VAL_CONTACT_WEB and VAL_CONTACT_MAIL): ? echo $contact-web; eval mail $contact-mail - `if'#215 no longer performs automatic number conversion, we use the explicit -lt, -gt etc. syntax of the sh(1). Note: `if' will change to be almost identical to sh(1) if(1), so please ensure proper test bracketing, even if it is less convenient. Moreover, the default string comparison mode has changed to case-sensitive, just like in the shell. This is because in the future this crux with trigger characters will vanish and `if' etc. will simply slurp in already expanded shell tokens, it will act like the shell in that respect. We have modifiers, though, yet only "@i" for case-insensitivity, also for regex matches: LC_ALL=C i=`LC_ALL=C.utf8 s-nail -:/ -# -X ' \define cset_test { \if [ "${ttycharset}" @i=% utf ] \echo $LC_ALL \xit 0 \end \if [ "${#}" -gt 0 ] \wysh set LC_ALL=${1} \shift \eval xcall cset_test "${@}" \end \xit 1 } \call cset_test C.UTF-8 POSIX.utf8 POSIX.UTF-8 \ en_EN.utf8 en_EN.UTF-8 en_US.utf8 en_US.UTF-8 '` [ $? -eq 0 ] && UTF8_LOCALE=$i Please note the `eval' in 'eval xcall cset_test "${@}". This is a difference of S-nail/mailx and the sh(1)ell that will remain, as documented in "COMMANDS"#20: whereas the shell implements a language and performs standardized expansions on the line until finally the command is called, S-nail will decide the type of command line parsing dependent on the seen command, and will then perform a single expansion. Therefore "${@}" will expand to multiple arguments if $# is greater 0, but it will expand to the empty string otherwise, which is not furtherly expanded away since it is meaningless like it is in the shell: therefore $# will be 1 (the empty string) not 0. - Using an explicit proto:// prefix should get you the desired thing apart of *newfolders*#473, e.g.: ? File maildir:///tmp/x.mdir ? copy * file:///tmp/x.mbox - New variable *record-files*#516 can be set to extend the meaning of *record*#515. *record-resent*#517 was there already. - New variable *ifs*#435 acts a bit like the sh(1)ell's $IFS for, e.g., the new `read'#248 command. There is a `readctl'#250 command which can be used to manage the active channel used by `read'#248. - The `~' alias for `call'#151 is gone. - `mimetype'#223 only allows specification of a single type per call, on the other hand no need to quote that. - `mimeview'#225 must now be used explicitly to look at any non-text MIME part, for normal display etc. purposes we only support "copiousoutput"#635 MIME handlers. - New *socks-proxy*#554 can be used to proxy all network traffic over a SOCKS5 proxy. (Gaetan Bisson) ChangeLog ^^^^^^^^^ - The manual has seen another major overhaul, all the variables are now documented in a single, sorted list, and many clarifications should have been added. I hope it has become a better read. (Predrag Punosevac, Michael Convey, Hariskar, Rudolf Sykora, Respiranto, Thomas Dickey, Donald Mugnai) - To support RFC 1524 a.k.a. .mailcap files (see below) many "trigger"-characters have been added for *pipe-TYPE/SUBTYPE*#489, which may (rarely) affect existing values. The .mailcap support itself is not yet implemented. - *mime-counter-evidence*#461 gained bit 4 (perform proper in-depth content inspection as necessary; set to 0xE for all bits). (Aharon Robbins) - Maildir paths are now created recursively as necessary. (Justin Ellingwood) - -M#72 and -m#73 options have been added to enforce a special send mode that will flag standard input / the given file with the specified / detected MIME 'Content-Type:'. This can be used to directly send, e.g., HTML log output. (Viktor Szépe, Ralph Corderoy) - Disallow symlinks on writable files. Note this requires O_NOFOLLOW support for the operating-system-call open(2), but which has been standardized a long time ago. (Matthew Dillon) - `retain'#263, `ignore'#216 etc. now differentiate in between From (the From: header) and From_ (the MBOX ident). In fact we now have a new `headerpick'#209 command which is a multiplexer for all retain and ignore lists used, call it without arguments to see the current setting(s). In v15 only `headerpick' and the standard-imposed wrappers `retain' and `ignore' will remain, all other wrappers will vanish. Regular expressions can now be used if available: ? headerpick headerpick type retain blahblahblah cc date from \ mail-followup-to message-id openpgp reply-to subject to \ user-agent #headerpick type ignore currently covers no fields #headerpick save retain currently covers no fields headerpick save ignore '^Original-.*$' '^X-.*$' '^DKIM.*$' headerpick forward retain cc date from list-id \ mail-followup-to openpgp reply-to subject to #headerpick forward ignore currently covers no fields - `top'#291 has been rewritten completely, `Top'#290 is new. It uses a built-in set of retain/ignore headers, but it is possible to register a custom set via `headerpick'#209. Also, *toplines*#585 has been extended a bit and the new *topsqueeze*#586 variable may pimp your `top' experience. ? headerpick top retain add subject ? top [-- Message 1 -- 87 lines, 4791 bytes --]: Subject: Re: I can't dist to myself I wrote: 3.22. bounce_delivered - `features' has been dropped, `version'#302 extended. - The *prompt*#504 handling has changed: we lost the capability to expand \?, \@ and \$, instead new "private" variables *?*#347, *account*#360, *mailbox-resolved*#449 and *mailbox-display*#448 have been introduced, and the prompt is completely shell expanded (thus twice with `wysh' or in v15), as if dollar-single-quote quoted. We do support the reverse- solidus escaped bracket notation for embedding characters which should not be counted when calculating the width of the prompt. The `colour'#160 command has a slot for the prompt colour. We gained *prompt2*#505 as a second level prompt. ? var prompt wysh set \ prompt='?\${?}!\${!}[\${account}#\${mailbox-display}]? ' - The filename "-" can be used as a receiver, e.g., $ echo Hey,\ you | s-nail -:/ -Sexpandaddr -sUB - - The -s#80 command line option, the `~s'#340 command escape as well as the corresponding slots of `~^'#320 will actively strip [\r\n] from their value (Debian #419840). - New `read'#248 and `echoerr'#182 commands, mostly for *on-compose-splice*#480. But also `echon'#183 and `echoerrn'#184, which do not write a trailing newline. - New variable *r-option-implicit*#513 may be helpful to those who regulary need the functionality of the -r#78 command line option. (Felipe Gasper, Martin Neitzel) - By using new "pseudo-URLs" one can automatize the use of S/MIME keys / (certificates / intermediate include certificates) with passwords. E.g., to drive bob@exam.ple, set *smime-sign-cert-bob@exam.ple* to the private key / certificate pair as usual, the password lookup will then be performed for bob@exam.ple.smime-cert-key, bob@exam.ple.smime-cert-cert and bob@exam.ple.smime-include-certs. Like this the password can be stored in an encrypted .netrc file when *netrc-lookup*#471 and *netrc-pipe*#472 are set, or it may be stored in an encrypted resource file that has been loaded via `source'#281 as a simple *password*#487 variable. Note that the prompting that happens as a last resort of password lookup will still interfere with a possibly running $PAGER#616 instance, dependent on the setting of *crt*#396, of course. Proper job control handling and recognizing that we are running $PAGER when doing that prompt is a TODO for v15. Sorry. - Some commands, like `set'#269, `help'#212, `list'#217, `mlist'#226 etc., now react upon the setting of *verbose*#592 and(/or) *debug*#400. - `write'#306 uses iconv(3) as appropriate. - *mbox-rfc4155*#453 has first been dropped, and was then reintroduced with different semantics. Because, it can be helpful if a messed up MBOX is read, in which case we henceforth will warn you and point you to this: ? define mboxfix { \localopts yes; \wysh set mbox-rfc4155;\ \wysh File "${1}"; \eval copy * "${2}" } ? call mboxfix /tmp/bad.mbox /tmp/good.mbox P.S. Here you see how weird the current thing still is, in v15: ? define mboxfix { localopts yes; set mbox-rfc4155; File "${1}"; copy * -- "${2}" } And also in v15 we will not apply (proper) so-called MBOXO quoting, but instead (simply MIME) re-encode mail messages. - `call_if'#152 is new and, different to "? ignerr call", silent and not messing with the return status. - The new *smime-ca-flags*#539 and *ssl-ca-flags*#? can be used to fine-tune X509_STORE_set_flags(3) a.k.a the X509 CA certificate verification. ? set ssl-ca-flags=partial-chain ? wysh set smime-ca-flags="${ssl-ca-flags}" Also, *ssl-curves*#? for TLSv1.3. - Socket connections use TLS S(erver)N(ame)I(ndication) as appropriate (RFC 7817). - `alternates'#145 checks arguments and supports `vput'#129. It by default no longer replaces but appends alternates, unless *posix*#502 mode is active. There is a new `unalternates'#146 command to remove alternates. - A new `charsetalias'#155 command. (Pietro Cerutti, mutt#3925) - New commands `filetype'#196 and `unfiletype'#197: in the future we will no longer know any builtin filetypes, in fact we already simulate .gz etc. via the new mechanism as necessary: ? filetype \ bz2 'bzip2 -dc' 'bzip2 -zc' \ gpg 'gpg -d' 'gpg -e' \ gz 'gzip -dc' 'gzip -c' \ xz 'xz -dc' 'xz -zc' \ zst 'zstd -dc' 'zstd -19 -zc' \ zst.pgp 'gpg -d | zstd -dc' 'zstd -19 -zc | gpg -e' - `~<'#315 now offers a "- [HERE-delimiter]" mode for pasting etc. (Ralph Corderoy) - `exit'#192 and `quit'#247 take an optional exit status. (That is not fixated yet, though.) - We have a useful -h / --help output. (Doug McIlroy) - *encoding* obsoleted in favour of new *mime-encoding*#462, which now defaults to base64. - *allnet*#362 now works (broken since nail 10.00, 2002-09-29). Appendix ^^^^^^^^ The complete changelog of commits in between two versions OLD and NEW can be inspected by using the git(1) `log' command: $ git log --reverse --topo-order --abbrev-commit OLD..NEW # Only topic branch headers (--no-merges for content commits only): $ git log --oneline --reverse --topo-order --merges OLD..NEW # Same, but truly accessible: $ git log --oneline --reverse --topo-order --merges --parents OLD..NEW | while read c1 c2 c3 c4 c5 c6; do printf "%-24s: \$ git log --oneline --no-merges %s ^%s\n" \ "${c6}" "${c1}" "${c2}"; done Entries for releases before v14.9.0 have been cut off and can be found in the git(1) repository: v14.8.0 - v14.8.16: $ git show v14.8.16:NEWS v13 - v14.8.5 : $ git show v14.8.5:NEWS 9.0 - 12.5 : $ git show heirloom:ChangeLog Also accessible via HTTPS?, just replace X.Y.Z accordingly: \https?://git.sdaoden.eu/cgit/s-nail.git/tree/NEWS?h=vX.Y.Y For even older releases you need to look into the [timeline] branch, but no changelog has been administrated for them. # s-tm-mode -----BEGIN PGP SIGNATURE----- iQIcBAABCgAGBQJdPMAjAAoJEN8IL2ruyML/6hYQAIMfU0Rw2KXyyD6Gll8x0Btt EiJD9L2WyMUai51QsJoUquOesmHEKfGYYGRLCJNTBcmzDQrvrydEqEPrqvzh2aL6 Le/uxHZ0xc3O5LIwESuu3nl0hwmYyIKhtl/R2nb8G8lj8lzp09g6bJWuSpFOEm+g chb1xnZTTN52NLPdJFcQeEVF/GrtS3yLXnHKx+ej/uQNR4IRHG18P1vn1QPP3Xvq Wg+xyXzL4XeB67VZBGQNinKkO44J3AtcodbUNkNL52XA31qLGFGtXu5FGmkul3u4 V5qMFNWif+nk9uPyHl1/Iyi58+UBlqHVn6w2BPFiRmu7fGUOvsy5ayBevL3TskH9 KGIaMf9v46qXh7aQWgrvLbI1fh/hsWM1XHolg5Tk08cYY3e+Lbp73FTXPKLck/Rg 6ZyxR7zkktex2/9UZNf4iGT6Yr/TwZ1XBU0bjm2srrN9A+V3eo/f6f/tctMV010y LtsgxkePFFrwxm4K5E6blpiM8hrudIZ90sw5UpnfHktUNwRxZ2N4ZEQ7ioZFM76w m6XIu/phopeLfsNquGWc0eofWCfkKRYFJRQc8r7K1ANu4qbFvR0irNn5mEaLv+G8 Pyo5Dpxnnka8aav2tm0PGR8dF2nW8vBrMM+vVTc/Jolxjxnf37Ksh6NND/gM7cax xt+9K2uJafSjnp2rXeRU =Fi1E -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIcBAABCgAGBQJdPMAkAAoJEN8IL2ruyML/0vUP/3woDqIXVoybg12QNvnAKv+x owY+ge1v8sAw+mHo4ZQSfeoc6+f+/RANlzQEassqmQ79i9L0J3z0agc64QzZY/79 pq8OSz8awecL2efdAQJ0HfdC3m0vTIKnBYd+h/ltymjlrZNIzlLcz+EOvoLTI0fv HLXbo7INPL7e3/wlPNH679steu6U796T2ySCeuJL6xNMrrBmTLt4jufHk4lk07DS aT2G+3D76SOCJICySFY3XbR63uKcdDguTNT8kG1hBcwLrKV6J8P0lSSUbktjqiDO PiC9pqF/HUFVn7wbH4u739FpvSqcdePshCRXFjlSksionQpyz6l2why+rZr0Ng1Z Tm4WlfWIe08KxVX6PpxUN3b3q207WigheVzWxR8qnDxrYEY+nGRpoHr1Jv4bDRzJ Zj8JgWsoIln42mE6rIHKLPmgy1R0xDJB9fvxyygry9QPp5T7FXDQOQ8E2sZ+vQJs DQELMcqY/UR7bcidZ1Dr2S4gy7XZiMLaPA1JWdO70dnOk/DxdF1t1j7GzmmsFEkp X/hsM7XVT9RfR70FeqOUMb+OOcF0FD/777UUpjnZ7hPOmjzO7tVzhHr2CriYf76H mNdrNHmuTEJVpkTcl1rXT8hmgdrQ+iHdcXhNOBM6CsFLvbez1yYhxVYCX2txVaW1 Q4x7Bm0JjkpqbLHkdA2m =LFEw -----END PGP SIGNATURE-----