Announcing S-nail 14.3.1

Hello to S-nail 14.3.1.
S-nail(1) is a fork of Heirloom mailx(1), the former nail(1).

This is an update (bugfix) release and as such pretty unfortunate.
Programming is an iterative task -- you step on by fixing your new
errors ,)

The release tarball can be downloaded (e.g., via 'curl -vv -L')
from, and its checksums are:

  <https://sourceforge.net/projects/s-nail/files/latest/download?source=files>

  MD5    = a7b855d937dc5b1f9802d33bc3ba7ba0
  SHA1   = 7497e428d9dbae26a1cabccf8641e73a2d8a85a9
  SHA256 = 2f091198795e66cf183e4694fb23d878048c721a2609316a9e69ec293f4ac19b

  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(1) browse: <http://sourceforge.net/p/s-nail/code/>

The NEWS entries for 14.3* follow; the complete changelog of the
commits in between s-nail-14.2.2 and s-nail-14.3.1 can be
inspected by issuing the following git(1) command:

  $ git log --reverse --topo-order s-nail-14.2.2..s-nail-14.3.1

v14.3.1, 2013-06-08
-------------------

A working -N would also be a good thing

Ok, but this doesn't count as a second bug, since it belongs into
the same changeset that Juergen yet put his finger on.  Right?
It changes *header* into *noheader*!
Who can doubt that???

--steffen

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j

_______________________________________________
nail-devel mailing list
nail-devel@...
https://lists.sourceforge.net/lists/listinfo/nail-devel

Due to this ... bug, 14.3.1 has to happen -- on the weekend

Hello,
i'm really extremely disappointed about this newly introduced bug!
But it is for real, and so, here we go again.

In trying to make the best of it (i won't be long) i will spend
some time on extending the cc-test.sh test script and then on
making the *ask*/*asksub* options mutually inclusive, as is
required by POSIX.
When all this has been done i'll release s-nail-14.3.1.
I don't expect another newly introduced bug, that is.
Thank you.

--steffen

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j

Re: s-nail 14.3, set ask possibly broken

Hello Juergen!

I hope it's ok that i Cc: the list.

Juergen Daubert <jue@...> wrote:
 |Hi Steffen,
 |
 |first a big thanks for your work on nail, I really appreciate it.

Thank you; it'll take years until it rocks.. :)

 |However looks like I've found a small bug. s-nail 14.3 is ignoring the 

Indeed.  Please find the fix attached below; it, and a new test
case in cc-test.sh, have also been pushed to the *master* (and
*next*) branches of the git repo.

I am *very* sad about this.  Many thanks for the report!

 |'ask' or 'asksub' setting. I've tried to set it in my system config 

And i'll implement tracking of *ask* and *asksub* so that we will
be POSIX compliant in this area.  Thanks for pointing this out.

 |(/usr/etc/mailx.rc) and user config(~/.mailrc) with no success.

I think for v14.4 i'll rewrite the config/make system so that all
the variables are solely in user.conf, i.e., including the
Makefile variables $(SYSCONFRC) etc.; also for the purpose of
not compiling files that are not used etc.; these and..

Announcing S-nail 14.3

Welcome to S-nail 14.3.
S-nail(1) is a fork of Heirloom mailx(1), the former nail(1).

This is a-lot-of-fixes-yet-some-new-features release.

The release tarball can be downloaded (e.g., via 'curl -vv -L')
from, and its checksums are:

  <https://sourceforge.net/projects/s-nail/files/latest/download?source=files>

  MD5    = f11a496d186ed8bcad7af6b6ff221dae
  SHA1   = 8c637f2037419ee2a7b84447aa3e1dc59012647b
  SHA256 = 595dc004e47cb3d9d08cb26c76d2d6971bef3f637d0d1d9a5248ae25c0b641cc

  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(1) browse: <http://sourceforge.net/p/s-nail/code/>

The NEWS entry for 14.3 follows; the full changelog of the commits
in between s-nail-14.2.2 and s-nail-14.3 can be inspected by
issuing the following git(1) command:

  $ git log --reverse --topo-order s-nail-14.2.2..s-nail-14.3

v14.3, 2013-06-03
-----------------

Thanks to Gavin Troy (gavtroy AT gmail DOT com) who inspired the  <at>  and
 <at> & pipe-command prefixes.

S-nail has been coverity scanned (project 444)...

Heya,
filling the void i want to mention that i registered S-nail (it's
project 444) at coverity.com [1].  Out of curiosity...

And that was a good thing, since it responded with 104 issues for
the first build and five for the second, many of which were really
bugs, some even catastrophic!  Damn!!

So i've spent the last one and a half day to iterate through those
and can finally report that S-nail's *next* branch doesn't produce
coverity errors anymore (and as of today)!

The severity of some of the bugs made me think about releasing a
14.3, however, since it'll take quite a long time until the
original 14.3 issues will be addressed; i.e., spending this week
on IMAP / POP3 testing, doing reviews of the few things that have
been done development-wise on *next*, and release a 14.3 once this
is done.  Then, release a 14.4 with all the things that were
planned for 14.3, like fixed thread selection etc. at the end of
this summer.

Yep, so i'll come back to you in a few days with a 14.3!
Ciao,

[1] <http://scan2.coverity.com/projects/444>

--steffen

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt

First step to control pipe-MIMETYPE command execution

Hello,
i was kind of „impressed“ that the pipe-MIMETYPE mechanism as it
is today really gets used for anything else than preparation of
HTML MIME parts, because i personally felt much too insecure to
do so because of some **** mails which come through and contain
attachments of various sort, and i usually use 'p:n' to look into
my boxes…

So, whereas it is not really possible to offer as much control as,
e.g., mutt(1), or any other mailer that has a GUI, especially not
today with our recursive shared parser/sender (display
preparator), here is a patch that extends the pipe-MIMETYPE syntax
to offer at least a little bit of control.
The attached diff is for S-nail 14.2.2 and thus also the *master*
branch from the repo (patch -p1 < pipe-prefix.diff).

  (Of course you could also upgrade to the *next* branch instead,
  though i wouldn't recommend it; why not use a temporary branch as in
    git co -b experimental-pipe-control
    patch -p1 < pipe-prefix.diff
    git add --all
    git ci -m 'seems to work from somewhat shallow testing'
   instead?  It's git(1)…)

This new feature may really be of interest for all of you who use
the pipe- mechanism:  If you prepend a command with ` <at> ' then the
command will *not* be executed *unless* you explicitly display the
message alone and by itself -- i.e., it will not be executed if
you display multiple messages in one go.

Announcing S-nail 14.2.2

Sigh.
So here is S-nail 14.2.2.
S-nail(1) is a fork of Heirloom mailx(1), the former nail(1).

The release tarball can be downloaded (e.g., via 'curl -vv -L')
from, and its checksums are:

  <https://sourceforge.net/projects/s-nail/files/latest/download?source=files>

  MD5    = 8331beb5307c329e5b2c80a28e362b5e
  SHA1   = ec4aba4b26fcf2a60ef5b50c8aa27febd814d00b
  SHA256 = 602a31085573426d22f042b2a8dd6243e79450130de7bf5a4d8613c5c8d1314a

  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(1) browse: <http://sourceforge.net/p/s-nail/code/>

  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  ! NOTE:                                                           !
  ! the release tarball for 14.2.1 will be removed from the server! !
  ! While there, i'll also drop 13.3.                               !
  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

The NEWS entries for 14.2.2 and 14.2.1 follow; the full
changelog of the commits in between s-nail-14.2 and s-nail-14.2.2
can be inspected by issuing the following git(1) command:

  $ git log --reverse --topo-order s-nail-14.2..s-nail-14.2.2

Attachments not working

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1

_______________________________________________
nail-devel mailing list
nail-devel@...
https://lists.sourceforge.net/lists/listinfo/nail-devel

Re: ..on cherry-picked bugfixes

William Yodlowsky <william@...> wrote:
 |On 30 April 2013 at 18:46, Steffen "Daode" Nurpmeso
<sdaoden@...> \
 |wrote:
 |> jca+nail@... (J=C3=A9r=C3=A9mie Courr=C3=A8ges-Anglas) wrote:
 |>|I can think of three possibilities:
 |>|- 14.2.1
 |> 
 |> Yea, i've just released that.
 |
 |Thanks for doing that, because now...
 |
 |>|- you upload those two patches right next to your tarballs.  I don't
 |>|  know how sourceforge does that.  The OpenBSD ports tree comes with
 |>|  a nice way to handle this kind of upstream patches (PATCHFILES in
 |>|  bsd.port.mk).
 |> 
 |> .. uuh!  That would have been ugly!
 |> 
 |>|- we import those two patches inside the OpenBSD ports tree.
 |>|
 |>|I'll let William speak here, as he's the port maintainer and I don't
 |>|have a strong opinion. :)
 |> 
 |> :) Ciao!
 |
 |...we can just move the openbsd port to 14.2.1.

Fantastic!

--steffen

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1

Announcing S-nail 14.2.1

welcome to S-nail 14.2.1.
S-nail(1) is a fork of Heirloom mailx(1), the former nail(1).

The release tarball can be downloaded (e.g., via 'curl -vv -L')
from, and its checksums are:

  <https://sourceforge.net/projects/s-nail/files/latest/download?source=files>

  MD5    = 76cab492c9b15233171493dd125b71dd
  SHA1   = 9d0530a2b8a4276e19986ab0f57de85770bd55a2
  SHA256 = 9c87736973165c3b61a434ac18224bec05e6fc5fa2b0364273e0ed28e49bcaa5

  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(1) browse: <http://sourceforge.net/p/s-nail/code/>

It follows the NEWS entry for 14.2.1; the full changelog of the
commits in between s-nail-14.2 and s-nail-14.2.1 can be inspected by
issuing the following git(1) command:

  $ git log --reverse --topo-order s-nail-14.2..s-nail-14.2.1

v14.2.1, 2013-04-30
-------------------

An unplanned (minor) bugfix release after i've found two bugs today and
heard from Jérémie Courrèges-Anglas (jca+nail AT wxcvbn DOT org) that
there exists a S-nail OpenBSD package.

I want to give prominence to the following people that helped to
improve S-nail(1) during this development cycle, in order of
appearance: Dirk Peters (peters AT schwertfisch DOT de).

Thank you very much, and best from Germany!

- Some warnings of newer clang(1) versions were silenced, including yet
  another alloca(3) problem (see *memtracer* topic branch in v14.0
  series).  [6f846efe]

- Tweaking the MIME boundary detection left a little hole that could
  cause boundaries not to be detected, as has been shown by a Microsoft
  Word generated mail on the ICU list.  [11e5fb5b]

- A format string could overflow bounds if unrealistic
  (18446744073709551615) line numbers or message sizes would have been
  produced.  [faa65c40]

- An algorithmic error could cause overlong lines which wrapped around
  to the next display line.  [ade52660] 
  (Dirk Peters.)

--steffen

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
nail-devel mailing list
nail-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nail-devel