-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello list,
hereby i announce S-nail v14.8.5, the «Hen Harrier». It is mostly a bug fixing release. There are three more major features that i want S-nail to be able to deal with before i finally turn away to S-roff and S-CText for many months, but i need some time for that. On the other hand serious bugs have been fixed and i didn't want those to linger around for seven or eight more weeks. (On october 25th it"ll be three years since the first S-nail release.) Credits John Dodson, Claudio Cappelli. We welcome Claudio Cappelli in THANKS. Number games and some nitpicking ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This message doesn't use S/MIME signing; unfortunately the German government didn't include signed S/MIME certificate and GPG key once they introduced the new electronical passport over ten years ago, and i must admit i don't like the other S/MIME possibilities which exist for me. Adding (basic) OpenPGP support is thus a major target for S-nail v14.8.6. The SHA1 hash of the tagged release commit is [dfb13ef]. The release git(1) tag and the release tarball have been OpenPGP signed with my key 95F382CE (on OpenPGP keyservers and my website) [email protected] = 232C 220B CB56 90A3 7BD2 2FFD EB66 0227 95F3 82CE I've followed Junio Hamano's example and embedded it in the repository as a blob, too, tagged "steffen-gpg-pub": $ git cat-file blob steffen-gpg-pub | gpg --import $ git tag -v/--verify TAGNAME *Note* that i have rotated my key (, operating system & hardware) compared to v14.8.4 -- after some examination it finally seems that was most likely unnecessary, but now the rotation was done and the new private data will never see commercial operating systems. Release tarball (s-nail-14_8_5.tar) identification: MD5 = 3212659bb530f1a101d3bb9d1c60070a SHA1 = 6d2f4ebfe71e10c87d167cd51c798e8b21484e83 SHA256 = 8ce3720d6ae932e974ac9042dfa5de68bdd9a700268e1206935597c79d199538 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABCgAGBQJV6wNlAAoJEOtmAieV84LO164P/jg/lj4xwg4WTDGHtyhsLQG1 vkeDrZJEWuiUePg9BOCvyJSNvZBCuwY4AnDT3QU9my/hMKrf5lE3wxaJZ4W0WsZH dRDSTOjuer1aYZg9nMUoe263PGGHi1u4t7o7LlFDN3N4BNWtlgg2TGsXg6kmuaDO mD1zRaKa813MTA5gED4qj3gdUxShcitFMNH02W2p6In9ndvohjFw6ooZT/mE/FHz VN3ngAetrsjYSWQSq8hzZMLX4sZ7i93iLXglPj3MfSdgz3JxooeyEyyyAye2KD+G lHUONysQixbNuo1Dlis3e5osA/Dgwh3UMZ0XaDymwUMvYWwXhxqHSEZSDJ/jSSwL LrFRxRZEl1bB0+6lsfN9XA8akWScsYvNKCVNjFwvW6xJJR/g/1pl5WIpHC122yKK Eor8BaM9xLJnXB8RESFXzS6yjodBxmBKLj2elo7YNFdcwnA6YKvNmoEfli09xkne MgHinnS1B1xmZNrdaTmIUKtzFmQ61c9nV19sEE20AF7RFWaQMh1NWJHRbTPlCT/m npW4hLJ2T5xdtBXlpIsmHtB46F/JdKZNHHxxiZJHtXiRVR71m2oP8v48nPGpp1Eg IkmP14JUD5GazANx+1JqMddHKSL/zERPd9CAGyiedfzeO/fELcaMzpOBA/PF4ZA/ /oj6hk7ZlXkEPd7WxPtO =gWK1 -----END PGP SIGNATURE----- The detached signature can be downloaded as well as the compressed versions of the release tarball (e.g., via "curl -vv -L"): <https://downloads.sourceforge.net/project/s-nail/s-nail-14_8_5.tar.asc> <https://downloads.sourceforge.net/project/s-nail/s-nail-14_8_5.tar.xz> <https://downloads.sourceforge.net/project/s-nail/s-nail-14_8_5.tar.gz> Online manual: <http://sdaoden.users.sourceforge.net/code-nail.html> [Web site : <http://sdaoden.users.sourceforge.net/code.html#s-nail>] git(1) repo.s: <git.code.sf.net/p/s-nail/code> (git:// or http://) <https://gitlab.com/sdaoden/s-nail.git> git(1) browse: <http://sourceforge.net/p/s-nail/code/> <https://gitlab.com/sdaoden/s-nail> In the following numbers in [] reference either the commit SHA1 hash or the name of a topic branch which relate to the NEWS entry; Likewise, numbers after an at-sign @ are mdocmx(7) manual anchor references which allow directly jumping to the given anchor. Note this is also true for the manual on the web, e.g., to jump to the table of contents: [1] http://sdaoden.users.sourceforge.net/code-nail.html#3 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. # 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 NOTES, ChangeLog (packager-affine) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ $ Since grohtml(1) (of groff(1)) is so broken that it took me two full $ days of manual adjustments to get code-nail.html as above into a good $ shape, i manually inserted all changes of v14.8.{3,4,5} into that file. $ This means that anchors for the new features are different to that $ of the real manual, denoted by (#_?ANCHOR) in the following. $ I.e., use @NUMBER on the terminal, and #_?NUMBER for the above page. $ Thanks for your understanding. - - I've forgotten to add obsoletion warning messages in v14.8.4, so running with enabled -d/*debug* -vv/2x*verbose* may be useful. Sorry! [b3e34db] - - A series of bug FIXes (which caused the "Hen Harrier" in the end): . v14.8.4 bug: macro content will be added to the history. [28672e5] . Fallout of massive not-yet-dead style and control flow change series in February 2014, I.: the close-on-exec bit of temporary file descriptors wasn't set. [8f58404] . Fallout of massive not-yet-dead style and control flow change series in February 2014, II.: temporary files were always created in the current directory. Aloha, heh. [edc12c8] . v14.8.4 bug: when `resend'ing messages a crash would happen when generating the Message-Id: (control flow messed up when hastily implementing extended -t parsing). [9e63ae6] (Hello, Bob Tennent: i finally have added at least a simple `resend' test. Don't your worry.) . v14.8.4 bug: plugged a file descriptor leak in the dotlock code (one side of the control pipe was leaked upon success; there you see how large ulimit(3) limits are by default today). [ed5c8cf] - - When using -t and a template message recipients given on the command line will now be joined into the message instead of being discarded. [9eb4cbf] ChangeLog ^^^^^^^^^ - - The `set' command will now mark out assembled variables if *debug* or 2x*verbose* is set. [2b6e64a] - - Added *smime-cipher* @433 (#429) option (i.e., generic variant of *smime-cipher-USER@HOST*). [58804ea] - - Messages will now _only_ be saved in *DEAD* if *save* is set (POSIX). [3fefac9] - - The (pretty useless for now) `pipe' command will now also print the overall message info (it printed MIME part infos already). [e0a8196] - - NAIL_FILENAME_GENERATED is now nothing but a random string. [36097df] - - *debug* now implies no*record* and no*save*. [ca9f512] - - After almost three years i've finally heard what John Dodson said and changed/restored behaviour of plain "address" message specifications to reflect the original intent (and a bit POSIX) so we now have A case-insensitive “any substring matches” search against the ‘From:’ header, which will match addresses (too) even if showname[339] is set [things are different if *allnet* is set] [44cec1f] (John Dodson) - - ..and therefore we need the possibility to somehow perform "exact boundary" matches: for this i've extended the "@" message specification with a header-name "~" prefix and header abbreviations: ‘f’, ‘t’, ‘c’, ‘b’ and ‘s’ will match ‘From’, ‘To’, ‘Cc’, ‘Bcc’ and ‘Subject’, respectively and case-insensitively. And: This message specification performs full text comparison, but even with regular expression support it is almost impossible to write a search expression that savely matches only a specific address domain. To request that the content of the header is treated as a list of addresses, and to strip those down to the plain email address which the search expression is to be matched against, pre‐ fix the header name (abbreviation) with a tilde ‘~’: '@~f@@a\.safe\.domain\.match$' [50c2816] - - New option: *sendmail-no-default-arguments* @426 (#_423) [d983036] (Claudio Cappelli) - - Do no longer make a difference in "no mail for user" and "missing system mailbox". The latter caused yet an annoying error message even with *emptystart*. [7abff87] - - New command `source_if' @187 (#_186) is like `source' but don't fails if the file cannot be loaded. That is to say, we do not yet support "-f FILE" tests nor `test -f FILE` shell commands for `if', sigh. [893bd5f] ChangeLog (purely technical) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - Unless Gunnar Ritter is directly affected the fourth clause of the BSD copyright has been dropped, as has been done for NetBSD Mail. [b9ea247] - - Quoted-printable encoding will avoid printing a soft newline if only a single character is about to follow. [6b31542] - - The configuration script now shows what it is doing at the beginning, to overcome those hangs that can be seen especially in VMs. [4c29cea] - - The configuration will do an automatic "make clean" when the configuration had been updated. [9706734] - - We no longer generate a MIME message unless that is necessary. I.e., a plain 7-bit (US-ASCII) message without attachments send from a system daemon is a plain RFC 822/2822/5322 message and doesn't require any MIME header. [824257a] - - To avoid that DNS resolver becomes unusable due to ^C interruption. Also fixes a possible leak in non-getaddrinfo(3) codepath (old boxes). [767897a] Note, FYI: it seems the GNU/Linux resolver has quite some more problems; e.g., i have a macro "gmane" that invokes a perl(1) script that downloads NTP messages, and, occasionally, if i call this macro before i perform a "normal" DNS lookup (by sending SMTP or reading POP3) then any further DNS lookup will fail, and i have to quit and restart S-nail. The v14.8.* announcements have been shortened at this point; to see the older entries please have a look at [1]. [1] http://permalink.gmane.org/gmane.mail.s-nail.user/283 - --steffen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJV6wPwAAoJEOtmAieV84LOAmgP/0Wo/SWfG7OQBJpgRZdzLzTF eIqlTWJCWj5lEYmpLxZvtWD3W4lo+D16zdXWre3RJIKeAk5eqvmqjZGZf13EofA1 K1Jeb9PVXX655RiENzkPIGijPeZPn/AnslZ15e462FavFfRzH/KBlsHxjBGkw9ur ZwUl4AtmUCi5FnEVwfKwC9G1sibkETN/IOt3S/E+C3noFwMAistXlmqa4OOzVsKE VwF0aw64fE89DJY/zJPG+/BC6TGwzl5Zb2AYfPERCbvPjW/Pg6z7ZA2Bt+QpXMfu ibGi3DRar/EJhRhNI7jIQferOpdzmp9yi8Vw2PWHWsr/FjRS2hAyT44Hl41ZQn2Q aVjHGb7shsOI6yF/FYZ90Oq5XhMZx1mwJmvesPoQ8mZ+My7QKrBue2LVOcMe2nWK GthH4bejPJxGArRzClT8s19ynxyR7CVdJaBPuyanvi8UbKndkZCbcB+biYk5zANE nrawLV4j2SZ9gveI9JxOUBf0uUrXAvb58LxdgPbXEU3LbN4czXMQxMxK0/oO1NTv qwAWQBSKze5H1QcRWmLQCaGhi+zp0doDrMxKzD5VG++hzm2EPgK5P/CI9cslfwGr 8xPwLdQYPZeVNAyZA6iSncq2567Fs1Kr7hDGyljJJ++xpbsqbWTui9Yz+aa9ECfF sinCOSHQsJVS4MhdVcAm =sr2i -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ S-nail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/s-nail-users
