[nail-devel] Announcing S-nail v13.3

[Steffen D. N. <sd...@gm...>]

Hmhm, hi list,

deepest apologies -- this release will finally work even for users
which use a MTA gateway and have *record* set!

That fix is the main reason why i spent some more time and did yet
another release, S-nail(1) v13.3; but please read on.
The release tarball for S-nail(1) v13.3 can be downloaded from

  http://sourceforge.net/projects/s-nail/files/s-nailv13.3.tar.gz/download
  http://sourceforge.net/projects/s-nail/files/s-nail.tar.gz/download

The latter is a symlink to the latest release.  The checksum of
the release tarball is:

  MD5(s-nailv13.3.tar.gz)= 5f0a82b487a62c76be46bcb63cfaaa45
  SHA1(s-nailv13.3.tar.gz)= 866375b87659d06507c3bddb6176d02735afc767
  SHA256(s-nailv13.3.tar.gz)= \
    f13f981a55ff61c00cd8987a112fee39d69072c2dfd38dbff1c6941456eb3b80

The full changelog of the commits in between s-nailv13.2 and
s-nailv13.3 can be inspected by issuing a

  $ git log --reverse --topo-order s-nailv13.2..s-nailv13.3

So thanks for using S-nail(1), the most feature rich but only
second best Berkeley Mail(1) of the world ... and improving!
Ciao from the one who is off for carneval now,

--steffen

S - n a i l  N e w s
====================

v13.3, 2012-11-11
-----------------

- Configuration on UnixWare 7.1.4 will succeed (shell issue fixed).

- Even on DragonFly BSD the IMAP GSSAPI is now found
  (in /usr/pkg/include/krb5/gssapi/gssapi.h).

- Support for pkgsrc(7) systems and automatic integration of
  C_INCLUDE_PATH and LD_LIBRARY_PATH path configurations.
  Please see INSTALL.

- Fixes a mortally embarassing regression that the current maintainer
  introduced before i really knew what i was doing, in (If *record* is
  set, avoid writing dead content twice.., 2012-09-14).
  It hit users that send through a MTA and have *record* set; in this
  combination data would not have reached the MTA.
  Interested parties may read the comment in savedeadletter() (part of
  the changeset) or the (Fix MTA/*record* descriptor clash..,
  2012-11-10) commit log.

  Deepest apologies to tortured users from the current maintainer!

- RFC 4155 compatible MBOX file handling has been introduced, and so
  S-nail is now on par with (at least) NetBSD Mail in respect to this.
  It can be turned off with the new *posix-mbox* variable, which you may
  need to use since not all MUAs are capable to dig those MBOX files.
  E.g., less cutting-edge (.-) MUAs fail for this:

   |From - Thu May 10 20:40:54 2012
   |Date: Wed, 07 Nov 2012 11:48:30 +0100
   |To: su...@du...
   |Subject: super1
   |
   |From me.
   |
   |From - Thu May 10 20:40:54 2012
   |Date: Wed, 07 Nov 2012 11:48:30 +0100
   |To: su...@du...
   |Subject: super2
   |
   |>From - Thu May 10 20:40:54 2012
   |From - Thu May 10 20:40:54 2012

  I'm not completely happy since S-nail *does* still quote those lines,
  how rare they may be -- it *does* modify message content.  mutt(1)
  implements something more clever and that is quoted-printable encoding
  of the "F" from "From", when seen at the beginning of a line.
  This, when applied to just *any* "^From", will be a non-modifying and
  all-compatible solution.

- SEND_MBOX handling has been changed to discard any Content-Length: and
  Lines: headers when it rewrites a message by default.
  I know that mutt(1) generates them (why, after
  http://www.jwz.org/doc/content-length.html?).
  Anyway, S-nail does neither use nor manage them, so that any
  modification renders those fields invalid, and then it seems best to
  discard them anyway.
  You may turn the new behaviour off with *keep-content-length*.