YUUHH - HUUUUUUUUUUUUHHHHHHHH!!!! Hello list, yet another shock, this time a mail shock:
S-nail v14.7.7 just sprung into existence! Things settle down and -- tomorrow is Sunday! So this is almost exclusively a bugfix release. The release tarballs can be downloaded (e.g., via 'curl -vv -L') from, and their checksums are: <https://downloads.sourceforge.net/project/s-nail/s-nail-14_7_7.tar.xz> MD5 = 580abec6a5164e753b18270eb276213b SHA1 = c07f85db753f6cc0316ae5a28582ba27f1424d08 SHA256 = d7864d5c75bd98118fd0fba7a40e3681293721b9deddd0a25656b6528e8365dd <https://downloads.sourceforge.net/project/s-nail/s-nail-14_7_7.tar.gz> MD5 = 717b3dbf7c5de1a5ef1f9721245abf7c SHA1 = df63006ab1436e2c40f5ff1208cf88aacacbcaac SHA256 = 28370171ce0aa0d80dabf3c4711e0344050d68a798d225c6f55328f08e6b1b1e Online manual: <http://sdaoden.users.sourceforge.net/code-nail.html> [Web site : <http://sdaoden.users.sourceforge.net/code.html#s-nail>] git(1) repo : <git.code.sf.net/p/s-nail/code> (git:// or http://) git(1) browse: <http://sourceforge.net/p/s-nail/code/> The complete changelog of commits in between two versions can be inspected by using the git(1) `log' command as shown below, where `OLD' and `NEW' are the two versions to be compared, e.g., v14.7.1 and v14.7.7: # All commits: $ 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 ${c1} ^${c2}\n" "${c6}"; done v14.7.7, 2014-09-27 ------------------- Thanks to Jan Chaloupka, Frantisek Holop, Matthias Kilian and Peter Hofmann. We welcome Frantisek, Matthias and Peter in THANKS. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - 1. No need to change anything. 2.1. The build system has been reworked a bit, `conf.rc' has been renamed to `make.rc'. 2.2. It is now possible to say 1/yes/true 0/no/false, case-insensitive, e.g., "WANT_ICONV=yes". 2.3. Some options can be "require"d: a failure to fulfill the request causes the configuration step to fail, e.g., $ make WANT_ICONV=require WANT_SMTP=require WANT_SSL=require all Should fail unless all of iconv(3), BSD sockets and OpenSSL are available. 2.4. This can be improved. (E.g., there should be warnings if an option is required that doesn't support this mode. Or -- all options should be requireable. Hm.) [topic/mandconf] - The build system should now correctly auto-detect $MAILSPOOL and $SENDMAIL!?! [c1a51bb] P.S.: why are you guys setting those explicitly? It is a BUG if that doesn't work automatically! P.P.S.: Packager heroes! Packager heroes!! Packager heroes!!! P.P.P.S.: .. and a nice weekend ;) - "make test" will now regulary test S/MIME when available. (A few tests have been added, to test the QP issue and to test the RFC 2047 MIME rewrite; which is still intermediate though.) - 2014-09-27: add-on: you may see more warnings for format strings which use the "size_t" integer type, and in the future even more of these will happen -- please read `INSTALL' again for more on that, but be ensured that we still compile-time-assert that the format strings fits the type size. (Enable ISO C99 mode for your compiler will cause any warnings to vanish.) ChangeLog ^^^^^^^^^ - FIXES: Maildir folders will now display correct content even after `newmail'. (Matthias Kilian; Frantisek Holop for nudging!) [158cfb6] Also *newmail* was somewhat broken since introduction of `File' command (missed updating a function argument back then). [58017a8] And unfortunately the readonly state of a folder could be forgotten after `newmail', too. [0cd5c9e, 0679ee4] - *quote-fold*: fix faulty line length calculation when a line started with a lot of leading whitespace. [731b8c9] - Fix: calculation of required memory for quoted-printable encoding was faulty for very long input that forces soft newline insertions. (Peter Hofmann) [c299c45, b043cfc, d105d80] - `headers' was falsely documented. (Jan Chaloupka) [ee76a42] - Complete rewrite of RFC 2047 header encoding. (Credit to Peter Hofmann because he peeked shitty MIME handling) [0add96e] Remark: S-nail doesn't yet support RFC 2231 and thus our RFC 2047 support is incomplete; also stateful character encodings, like ISO-2022-JP, are still not supported and thus we're in fact non-compliant. The same that it ever was. Well, we're not alone, and e.g. mutt(1) offers a "rfc2047_parameters=yes" option to deal..., also with us. I really hate to say that. But of course we all know that the mail standards are inherently braindead anyway, right? O-ho, yes, they are like that. I hope S-nail isn't part of the problem no more in 2016. - Oh, the [topic/retrim] in v14.7.6 actually missed a single occurance of fixed Re: checking! [ed1c865] - Allow $USER to be set to the empty string and no longer abort(3) if the user is not known, but instead exit(3) with value 67 (BSD EX_NOUSER constant from /usr/include/sysexits.h). $ USER= LC_ALL=C s-nail ... [a846fdb] v14.7.6, 2014-08-15 ------------------- Thanks to Georg Schlisio. Several bugfixes: it's definitely more than enough now, v14.7.8 in mid 2015 will have to and will definetely ship with a test series. NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - The global default nail.rc file now sets *sendcharsets* to 'utf-8,iso-8859-1', i.e., the order has been reversed. (Georg Schlisio) Also *bsdflags* is no longer set by default. [e39679b] ChangeLog ^^^^^^^^^ - Fix: in some configurations a `resend' message would end up with two 'Resend-Date:', instead of one such and a 'Resend-Message-Id:' field. [21b9218] - The internal exit status of a `mail' command will now be 0 upon success and 1 on failure, not vice versa. [1112375] - FIX: dependend on the set of retained / ignored etc. headers a MIME part with a *pipe-CONTENT/SUBTYPE* set to the special '@' plain-text command would try to execute a command equal to the name of the last header of the MIME part, most often 'Content-Disposition:'. [dee1fed,686a383] - Detected that the `fwd' / `forward' command(s) used the false (imho) mode to strip the address from the command line, now it's possible to: ? fwd MSG-SPEC "my friend <his@addr>" [1c4e164] - New variable *reply-strings*. It's more unlikely now to end up with threads which read 'Re: Aw: Re: Aw:' etc. [topic/retrim] - Because of user inconvenience, introduce a temporary hack not to mince user input lines in history entries, even if this means that each and every line is first duplicated before it is used. So now the `fwd' command as above will enter history in the given form. [f1ded4c] ChangeLog (purely technical) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Fixed one missing IMAP / IMAP-cache string relaxation restore. (In about six weeks or so this condition hit me once). [66ef04f] P.S.: I still see an occasional IMAP-cache crash that occasionally happens after several connects and diconnects without intervening folder changes; after being bitten once by that even after commit [cf7f63d] it seems this is a deeper structural problem, but i'll try to track that down for v14.8. v14.7.5, 2014-08-01 ------------------- Jan Chaloupka (jchaloup AT redhat DOT com) reported on nail-devel@ that Heirloom mailx can be crashed by setting *smtp* in combination with with *from* effectively set to a NULL string. I first was optimistic, but it turns out S-nail can, too. v14.7.4, 2014-07-15 ------------------- Fixes maildir code which was broken in May (too). Readds auto-detection of compressed boxes (i.e., if `$ Fi mybox' is executed and `mybox' doesn't exist, but `mybox.bz2' does, then the name is automatically expanded and `mybox.bz2' is used instead). Sorry for the inconvience. v14.7.3, 2014-07-14 ------------------- Thanks to Mantas Mikulėnas (grawity AT gmail DOT com). This is a bugfix release which fixes a regression in the handling of user credentials when *v15-compat* is not set, introduced in v14.7.1, quoting Mantas: In other words, $folder *requires* the @ to be percent-encoded, but $password requires the *opposite*. And that is not valid when *v15-compat* is not set. v14.7.2, 2014-07-12 ------------------- Thank you: Gavin Troy, Bob Tennent (rdt AT cs DOT queensu DOT ca), Tarqi Kazan. NOTES: ^^^^^^ v14.7.2 brings incompatible credential lookup changes when *v15-compat* is set; the lookup order now is: - *user-HOST*, *user*, [.netrc] ... - *password-USER@HOST*, *password-HOST*, *password*, [.netrc] .. Changelog in reverse order, oldest first. ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - New configuration option WANT_AGENT to support *agent-shell-lookup* (, -HOST, -USER@HOST) lookups of potentially encrypted password storage (inspired by Gavin Troy) [b2d41d3,516a7f0] - MAILSPOOL is now automatically set to /var/spool/mail if that directory exists, only otherwise we use /var/mail [4a83018] - WANT_GSSAPI is again enabled by default - Tarqi Kazan has correctly pointed out that the system environment at compilation time is likely to reflect the politics and/or preferred configuration of packagers, and self-compilers have always the chance to configure themselves (Tarqi Kazan) [398eb29] ChangeLog ^^^^^^^^^ - `un{,save,fwd}{ignore,retain}': let '*' mean 'all fields' [a1f1da9] - Bugfix: `setenv' takes 1-1000 arguments, not exactly 2 [daf2ea8] - New command: `varedit' edits the value of an existing variable in $EDITOR [93070d2] - New commands: `File' (and `Folder') explicitly open a mailbox in readonly mode, thus finally offering the possibility to avoid flag updates etc. whenever so desired [b1f5f2d] - Bugfix: since May the header display would display tabulators in an UTF-8 environment as replacement characters [870b314] - *mime-counter-evidence* now is a valued option. Set bit two (value two) and the detected real MIME type is carried along with the MIME part so that it is used instead of `application/octet-stream' to lookup possibly registered *pipe-CONTENT/SUBCONTENT* handlers. (Bob Tennent) [81473f8] Also pipe handlers will now be passed several MIME informations via environment variables, please see the manual for more. (inspired by Bob Tennent) - Resource file loading now prints a diagnostic when loading was stopped due to a processing error. This behaviour is also required by POSIX. (Bob Tennent) [fd42684] - Incompatible changes in credential handling, as above. [25d7735,3cdb6a3] - *netrc-lookup* is now a real chain and has -HOST and -USER@HOST variants (though the latter only for password lookups) [59fc226] - .netrc machine names are now lowercased before use [28c6fee] - The manual has seen some reorderings, a TOC will be shown if you '-dWANT_TOC=1' when using *roff(1) (as has been done for the online manual) - There is a new file `THANKS' [6b5cb3e] ChangeLog (purely technical) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - IMAP and IMAP cache now use string relaxation which *drastically* reduces memory usage on large mailboxes [e5598ce] - Fixed compilation on old OpenBSD installations without wordexp(3) as well as with GSS-API and WANT_AMALGAMATION and now using #pragma's to get rid of some warnings [topic/ccstuff] --steffen ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ S-nail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/s-nail-users
