[email protected] wrote in <[email protected]>:
 | I fetched 2 messages from my POP server.
 |
| S 1 John Smith 2018-11-27 90/4750 parasitic \
 | carnivora
|>R 2 Letters, NYT 2018-11-27 226/15863 Automated \ |>Reply Re: ' He Says He Got Away With 90 Murders. Now He's Confessing \
 |>to Them All.'
 |
 | I saved the first to JohnSmith (name changed to protect the
 |innocent):
 |
 | ? s1 JohnSmith [Appended] 4760 bytes
 |
 |which worked properly.  When I tried to save the second to nytimes
 |(real name!)  I got:
 |
 | ? s2 nytimes mailx: nytimes: Snorkeling on empty pipe
 | ERROR# ? errors
 |    1. nytimes: Snorkeling on empty pipe
 |
 |and it didn't save.  I could save it to a different file name.  I
 |could open that file with mail and save it to nytimes.  I could open
 |nytimes.  The error seems to require both messages.  The word
 |Snorkeling does not appear in either.  Snorkeling is in nytimes, but

What you see is the S-nail specific errno(3) EPIPE error string;

Maybe a missing user folder in /var/spool/mail ?
I don't know how heirloom-mailx handeld this. I use s-nail for sending cron/command-line mails,
i never used it as MUA.

 |not that phrase.  I switched from mailx 12.5 recently, when Slackware
 |upgraded to it.
 | mailx v14.9.11, 2018-08-08 (build for linux)
 | Slackware, latest; kernel 4.19.4

Where does the string "mailx v14.9.11, 2018-08-08 (build for linux)" come from?
Is this a prebuilt binary?
Or from slackbuilds.org, or from slackware-current?

Oh really!  Please let me assume it is only because of OpenSSL,
rather than because of the software as such, right?  :-)

I submitted the slackbuild, but aren't responsible for what or why something lands in slackware,
but i proposed to replace heirloom-mailx.
OpenSSL didn't make headache i think, until now heirloom could be patched. For me it seemed, that heirloom-mailx development is now at s-nail, so why not go with it.

The .SlackBuild script of Johannes Schöpfer is the most
complicated think i have ever seen!  I really had to think about
it, but luckily and successfully avoided that, then.

Well, it's basically the original slackware heirloom-mailx buildscript, adapted to s-nail.

We are at Slackware, too!  Thank you, this is really nice!!
I did not even know that Slackware is still truly alive, but
i think: good that it is.

:-)

Johannes

Reply via email to