Devs, mailx is a fantastic command line mailer, but the version for 15.4 is more than a DECADE out of date, e.g. $ mailx -V 12.5 7/5/10 Uhhh, that's July 2010 folks? Why are we not using the s-nail package which still enjoys active development? E.g. $ mailx -V mail v14.9.24, 2022-03-26 (built for Linux) At least that's only 11 months old, not 13 years... -- David C. Rankin, J.D.,P.E.
On 2023-02-10 10:28, David C. Rankin wrote:
Devs,
mailx is a fantastic command line mailer, but the version for 15.4 is more than a DECADE out of date, e.g.
$ mailx -V 12.5 7/5/10
Uhhh, that's July 2010 folks?
Why are we not using the s-nail package which still enjoys active development? E.g.
$ mailx -V mail v14.9.24, 2022-03-26 (built for Linux)
At least that's only 11 months old, not 13 years...
Is it compatible? A replacement? Meaning, same command line? That's an absolute need, there are many scripts and programs that use the ancient "mail" command line. Mailx is a direct replacement, no changes needed. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2/10/23 03:32, Carlos E. R. wrote:
Is it compatible? A replacement?
Meaning, same command line? That's an absolute need, there are many scripts and programs that use the ancient "mail" command line. Mailx is a direct replacement, no changes needed.
Yes, Same options, same -a attachment, etc... -- David C. Rankin, J.D.,P.E.
On 2023/02/10 03:28:40 -0600, David C. Rankin wrote:
Devs,
mailx is a fantastic command line mailer, but the version for 15.4 is more than a DECADE out of date, e.g.
$ mailx -V 12.5 7/5/10
Uhhh, that's July 2010 folks?
Does something not work?
Why are we not using the s-nail package which still enjoys active development? E.g.
$ mailx -V mail v14.9.24, 2022-03-26 (built for Linux)
At least that's only 11 months old, not 13 years...
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders. Btw: I had a lot of patches for missed features of both old nail as well s-nail: werner/mailx> ll total 396 -rw-r--r-- 1 werner suse 1708 Dec 10 2014 0001-outof-Introduce-expandaddr-flag.patch -rw-r--r-- 1 werner suse 2206 Dec 10 2014 0002-unpack-Disable-option-processing-for-email-addresses.patch -rw-r--r-- 1 werner suse 2479 Dec 11 2014 0003-fio.c-Unconditionally-require-wordexp-support.patch -rw-r--r-- 1 werner suse 652 Dec 10 2014 0004-globname-Invoke-wordexp-with-WRDE_NOCMD-CVE-2004-277.patch drwxr-xr-x 6 werner suse 73 Nov 23 2021 Updates drwxr-xr-x 6 werner suse 328 Feb 10 10:44 Upstream -rw-r--r-- 1 werner suse 362 Dec 25 2020 fix-sendmail-name.patch drwxr-xr-x 3 werner suse 8192 Nov 23 2021 mailx-12.5 -rw-r--r-- 1 werner suse 982 Apr 8 2016 mailx-12.5-ipv6.dif -rw-r--r-- 1 werner suse 9628 Apr 8 2016 mailx-12.5-mime.dif -rw-r--r-- 1 werner suse 3808 Nov 2 2018 mailx-12.5-openssl-1.1.0f.patch -rw-r--r-- 1 werner suse 13104 Apr 8 2016 mailx-12.5-parentheses.dif -rw-r--r-- 1 werner suse 6831 May 13 2011 mailx-12.5-replyto.patch -rw-r--r-- 1 werner suse 653 Nov 23 2021 mailx-12.5-systemd.patch -rw-r--r-- 1 werner suse 15422 Nov 23 2021 mailx-12.5.dif -rw-r--r-- 1 werner suse 261429 May 13 2011 mailx-12.5.tar.bz2 -rw-r--r-- 1 werner suse 1019 May 13 2011 mailx-fix-openssl.patch -rw-r--r-- 1 werner suse 16329 Jan 3 13:04 mailx.changes -rw-r--r-- 1 werner suse 7869 Dec 27 14:09 mailx.spec -rw-r--r-- 1 werner suse 7187 Sep 21 2021 nail-11.25-path.dif -rw-r--r-- 1 werner suse 1361 May 13 2011 nail-11.25-toaddr.dif -rw-r--r-- 1 werner suse 553 May 13 2011 nail-11.25-ttychar.dif here Upstream is the git tree of s-nail :) -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx. Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography. There have been a number of updates, tls several times and most recently in glibc 2.37. Just something to look at. I don't have a problem reading mail on Arch with s-nail, so we can look at any additional patches. But the version v14.9.24, from 2022-03-26 likely obsoletes most of the patches you have. -- David C. Rankin, J.D.,P.E.
On 2023/02/10 04:43:31 -0600, David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography. There have been a number of updates, tls several times and most recently in glibc 2.37.
Just something to look at. I don't have a problem reading mail on Arch with s-nail, so we can look at any additional patches. But the version v14.9.24, from 2022-03-26 likely obsoletes most of the patches you have.
Sow me how you set a Reply-To: entry within the command line or with an option at calling s-nail. Also does s-nail support autodetection of UTF-8 encoded attachments provided with the option -a at calling s-nail? -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On 2/10/23 06:55, Dr. Werner Fink wrote:
On 2023/02/10 04:43:31 -0600, David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography. There have been a number of updates, tls several times and most recently in glibc 2.37.
Just something to look at. I don't have a problem reading mail on Arch with s-nail, so we can look at any additional patches. But the version v14.9.24, from 2022-03-26 likely obsoletes most of the patches you have.
Sow me how you set a Reply-To: entry within the command line or with an option at calling s-nail. Also does s-nail support autodetection of UTF-8 encoded attachments provided with the option -a at calling s-nail?
reply-to: is handled through user config files, e.g. ~/.s-nail.rc ## Mbox settings: set from='SDF User <sdfuser@sdf.org>' set reply-to='SDF User <sdfuser@sdf.org>' Attachments can apply character set changes if needed, but presume the attachment is in the default system locale character set which is UTF-8. -- David C. Rankin, J.D.,P.E.
On 2023-02-11 10:14, David C. Rankin wrote:
On 2/10/23 06:55, Dr. Werner Fink wrote:
On 2023/02/10 04:43:31 -0600, David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography. There have been a number of updates, tls several times and most recently in glibc 2.37.
Just something to look at. I don't have a problem reading mail on Arch with s-nail, so we can look at any additional patches. But the version v14.9.24, from 2022-03-26 likely obsoletes most of the patches you have.
Sow me how you set a Reply-To: entry within the command line or with an option at calling s-nail. Also does s-nail support autodetection of UTF-8 encoded attachments provided with the option -a at calling s-nail?
reply-to: is handled through user config files, e.g. ~/.s-nail.rc
mailx: -R | -R address Without any argument any folders will be opened read-only. With argument an reply-to adress is specifed on command line. Only the first argument after the -R flag is used as the address. That's a difference, then.
## Mbox settings: set from='SDF User <sdfuser@sdf.org>' set reply-to='SDF User <sdfuser@sdf.org>'
Attachments can apply character set changes if needed, but presume the attachment is in the default system locale character set which is UTF-8.
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2/11/23 04:08, Carlos E. R. wrote:
mailx:
-R | -R address Without any argument any folders will be opened read-only. With argument an reply-to adress is specifed on command line. Only the first argument after the -R flag is used as the address.
That's a difference, then.
Yep, 13 year old mailx winds that round :) -- David C. Rankin, J.D.,P.E.
Hi, all -- I've been watching this with some interest. Sometimes old doesn't mean bad; it's possible to accomplish a refined design and not need any further tweaking. Not that I'm going to go looking at the moment, but for example I think bc has been stable for almost as long as I've been using it :-) ...and then David C. Rankin said... % On 2/11/23 04:08, Carlos E. R. wrote: % > mailx: % > % > -R | -R address ... % > Only the first argument after the -R flag is used as the address. % > % > That's a difference, then. % % Yep, % % 13 year old mailx winds that round :) I wonder, though ... Can one specify to s-nail an rc file via command flag? better yet, could that file be somehow encapsulated on the command line or perhaps redirected from another file descriptop to save the temp file? It would be a royal pain, but for someone who wanted s-nail a way to have the same functionality ... % % -- % David C. Rankin, J.D.,P.E. HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
On 2/12/23 09:25, David Thorburn-Gundlach wrote:
Hi, all --
I've been watching this with some interest. Sometimes old doesn't mean bad; it's possible to accomplish a refined design and not need any further tweaking. Not that I'm going to go looking at the moment, but for example I think bc has been stable for almost as long as I've been using it :-)
David, While s-nail incorporates several rc files, I think the answer here is it wouldn't be as convenient as the -R option in heirloom-mailx. It would likely be simpler to write a procmail rule to do a header rewrite. That also brings up the point it would also likely be simpler just to patch s-nail with a new -R option to insert the given reply-to address. That's less than a dozen lines of code in C. Dr. Werner Fink's concern is valid for the -R option. Which is a difference in the options. When Arch looked at the issue of changing the command line mailer in the 2011-2012 timeframe, they went with s-nail because heirloom (and other flavors) of mailx were no longer actively being developed (that provides an upstream for fixes as things are discovered) Granted, this is needed a bit more with Arch that remains current with upstream for its model. SUSE/openSUSE has always tweaked and backported a bit more -- and has always had the resources to use that model. (and thank goodness for that given my "choice" of desktop) It would at least be nice to have the "choice" of s-nail as a supported package if not a replacement. I'll pull the source and see what it would take to add a -R option. -- David C. Rankin, J.D.,P.E.
David C. Rankin wrote:
It would at least be nice to have the "choice" of s-nail as a supported package if not a replacement.
I haven't looked, but surely someone is already building it in a home repo? It wouldn't much to have it made "officially" available for TW. -- Per Jessen, Zürich (5.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2/14/23 06:31, Per Jessen wrote:
I haven't looked, but surely someone is already building it in a home repo? It wouldn't much to have it made "officially" available for TW.
Yes, but sans wep, the only way to search home is through buildservice :( -- David C. Rankin, J.D.,P.E.
David C. Rankin wrote:
On 2/14/23 06:31, Per Jessen wrote:
I haven't looked, but surely someone is already building it in a home repo? It wouldn't much to have it made "officially" available for TW.
Yes, but sans wep, the only way to search home is through buildservice :(
I don't know if obs-cli might help, but why would you not have web access? Fwiw, I searched for s-nail - nothing found. -- Per Jessen, Zürich (2.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2/15/23 02:58, David C. Rankin wrote:
On 2/14/23 06:31, Per Jessen wrote:
I haven't looked, but surely someone is already building it in a home repo? It wouldn't much to have it made "officially" available for TW.
Yes, but sans wep, the only way to search home is through buildservice :(
Last build of s-nail was 9-years ago, nothing even remotely current. But, beyond that, somebody delete my drankatty build service project so I can't even build it myself now. How the hell did that happen? I've had that build service project since Novell owned openSUSE and I use it occasionally for builds such as this. Why was it deleted when in response to the request I requested it NOT be deleted!!! I need my drankinatty build service project restored ASAP. -- David C. Rankin, J.D.,P.E.
On Wed, Feb 15, 2023 at 10:14 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On 2/15/23 02:58, David C. Rankin wrote:
On 2/14/23 06:31, Per Jessen wrote:
I haven't looked, but surely someone is already building it in a home repo? It wouldn't much to have it made "officially" available for TW.
Yes, but sans wep, the only way to search home is through buildservice :(
Last build of s-nail was 9-years ago, nothing even remotely current.
But, beyond that, somebody delete my drankatty build service project so I can't even build it myself now. How the hell did that happen? I've had that build service project since Novell owned openSUSE and I use it occasionally for builds such as this. Why was it deleted when in response to the request I requested it NOT be deleted!!!
I need my drankinatty build service project restored ASAP.
I have a little script that downloads all my OBS stuff to local storage. I even maintain that in our software's source repository. Just in case... What I really need to do is set up a local OBS as well. Also just in case... -- Roger Oberholtzer
On 2023/02/13 19:36:03 -0600, David C. Rankin wrote:
On 2/12/23 09:25, David Thorburn-Gundlach wrote:
Hi, all --
I've been watching this with some interest. Sometimes old doesn't mean bad; it's possible to accomplish a refined design and not need any further tweaking. Not that I'm going to go looking at the moment, but for example I think bc has been stable for almost as long as I've been using it :-)
David,
While s-nail incorporates several rc files, I think the answer here is it wouldn't be as convenient as the -R option in heirloom-mailx. It would likely be simpler to write a procmail rule to do a header rewrite.
That also brings up the point it would also likely be simpler just to patch s-nail with a new -R option to insert the given reply-to address. That's less than a dozen lines of code in C.
Dr. Werner Fink's concern is valid for the -R option. Which is a difference in the options.
See thread followed on https://www.mail-archive.com/s-mailx@lists.sdaoden.eu/msg00808.html some changes had been done but currently s-nail is not compatible with old mailx. I'm in doubt that it every will be. Also I'd like to avoid to fork s-nail to port my patches on every new version of s-nail. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography.
Is that really a problem for a command-line tool? Just being curious. For me, mailx is perfect for anything I want to do in batches, and occasionally when I want to send a mail without cranking up TB. -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-02-10 17:03, Per Jessen wrote:
David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography.
Is that really a problem for a command-line tool? Just being curious.
For me, mailx is perfect for anything I want to do in batches, and occasionally when I want to send a mail without cranking up TB.
It _might_ have problems connecting to some mail servers out there. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-02-10 17:03, Per Jessen wrote:
David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography.
Is that really a problem for a command-line tool? Just being curious.
For me, mailx is perfect for anything I want to do in batches, and occasionally when I want to send a mail without cranking up TB.
It _might_ have problems connecting to some mail servers out there.
Ah, again way too advanced usage for me :-) I only drop mails into the MTA queue. Anyway, to accommodate my simpleton needs and those of more advanced beings, surely we have room for both mailx and s-nail ? -- Per Jessen, Zürich (-0.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-02-11 09:30, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-02-10 17:03, Per Jessen wrote:
David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography.
Is that really a problem for a command-line tool? Just being curious.
For me, mailx is perfect for anything I want to do in batches, and occasionally when I want to send a mail without cranking up TB.
It _might_ have problems connecting to some mail servers out there.
Ah, again way too advanced usage for me :-) I only drop mails into the MTA queue.
Anyway, to accommodate my simpleton needs and those of more advanced beings, surely we have room for both mailx and s-nail ? But of course, we had the same thing long ago, when we had both the ancient "mail" and the new "mailx". The problem is if it is done as a replacement: mailx could directly replace mail and the scripts continued running without modification. When the same command line was assured
Me too, but some people use it (in scripts, crons, etc) to send email talking directly to an ISP MTA. Remember that there was talk, years ago, of removing the MTA from the default installation. then the command was replaced. Of course, the new mail can have new options. But has to accept the same old ones, with same behaviour. So far, "-R address" is different. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-02-11 09:30, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-02-10 17:03, Per Jessen wrote:
David C. Rankin wrote:
On 2/10/23 03:48, Dr. Werner Fink wrote:
Simply s-nail is not mailx aka Heirloom mailx/nail. I had tried s-nail and seen that I was not able to read my own mbox folders.
s-nail is a offshoot from BSD mail but is option compatible with hierloom mailx.
Everything works with the current mailx, but the lack of development means that still uses the 2010 cryptography.
Is that really a problem for a command-line tool? Just being curious.
For me, mailx is perfect for anything I want to do in batches, and occasionally when I want to send a mail without cranking up TB.
It _might_ have problems connecting to some mail servers out there.
Ah, again way too advanced usage for me :-) I only drop mails into the MTA queue.
Me too, but some people use it (in scripts, crons, etc)
That is virtually the only place I use it. Manually running it is maybe once a year.
to send email talking directly to an ISP MTA.
Yes, I understand that is the idea you are talking about.
Anyway, to accommodate my simpleton needs and those of more advanced beings, surely we have room for both mailx and s-nail ?
But of course
Good, end of thread me thinks :-) -- Per Jessen, Zürich (3.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Carlos E. R. wrote:
On 2023-02-11 09:30, Per Jessen wrote:
Anyway, to accommodate my simpleton needs and those of more advanced beings, surely we have room for both mailx and s-nail ?
But of course
Good, end of thread me thinks :-)
Just to elaborate - s-nail does not seem to be a drop-in replacement for mailx, so anyone who has need for more up-to-date cipher support may need to move to s-nail while the rest of us can remain with mailx. -- Per Jessen, Zürich (4.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-02-11 11:29, Per Jessen wrote:
Per Jessen wrote:
Carlos E. R. wrote:
On 2023-02-11 09:30, Per Jessen wrote:
Anyway, to accommodate my simpleton needs and those of more advanced beings, surely we have room for both mailx and s-nail ?
But of course
Good, end of thread me thinks :-)
Just to elaborate - s-nail does not seem to be a drop-in replacement for mailx, so anyone who has need for more up-to-date cipher support may need to move to s-nail while the rest of us can remain with mailx.
Yes, that was my meaning. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023/02/11 11:15:23 +0100, Carlos E. R. wrote:
So far, "-R address" is different.
My mailx-12.5-replyto.patch patch extends -R to can be able to do both open mbox readonly and with address set a REply-To address. But there is more echo test äöü test | ./.obj/s-nail werner@suse.de -s "test" s-nail: -s is an invalid alias name echo test äöü test | mailx werner@suse.de -s "test" allow to set recipient address as first ... ( unsetenv LANG LC_CTYPE ; ( setenv LC_CTYPE de_DE.UTF-8; echo test äöü test ) | ./.obj/s-nail werner@suse.de ) s-nail: Cannot find a usable character set to encode message: No such entry, file or directory /suse/werner/dead.letter 3/55 ( unsetenv LANG LC_CTYPE ; ( setenv LC_CTYPE de_DE.UTF-8; echo test äöü test ) | mailx werner@suse.de ) autodetect UTF-8 mail body on the fly even if outer locale does not set this. All those patches are used by customers which uses mailx within batch jobs and scripts. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On 2023-02-13 10:49, Dr. Werner Fink wrote:
On 2023/02/11 11:15:23 +0100, Carlos E. R. wrote:
So far, "-R address" is different.
My mailx-12.5-replyto.patch patch extends -R to can be able to do both open mbox readonly and with address set a REply-To address.
But there is more
echo test äöü test | ./.obj/s-nail werner@suse.de -s "test" s-nail: -s is an invalid alias name
echo test äöü test | mailx werner@suse.de -s "test"
allow to set recipient address as first ...
( unsetenv LANG LC_CTYPE ; ( setenv LC_CTYPE de_DE.UTF-8; echo test äöü test ) | ./.obj/s-nail werner@suse.de ) s-nail: Cannot find a usable character set to encode message: No such entry, file or directory /suse/werner/dead.letter 3/55
( unsetenv LANG LC_CTYPE ; ( setenv LC_CTYPE de_DE.UTF-8; echo test äöü test ) | mailx werner@suse.de )
autodetect UTF-8 mail body on the fly even if outer locale does not set this.
All those patches are used by customers which uses mailx within batch jobs and scripts.
That's a very good testing, thanks. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 10.02.23 17:03, Per Jessen wrote:
For me, mailx is perfect for anything I want to do in batches, and occasionally when I want to send a mail without cranking up TB.
There is another alternative: "mail" from GNU Mailutils. # mail -V mail (GNU Mailutils) 3.15 Copyright (C) 2007-2022 Free Software Foundation, inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. # mail --help Usage: mail [OPTION...] [address...] or: mail [OPTION...] [OPTION...] [file] or: mail [OPTION...] --file [OPTION...] [file] or: mail [OPTION...] --file=file [OPTION...] GNU mail -- process mail messages. If -f or --file is given, mail operates on the mailbox named by the first argument, or the user's mbox, if no argument given. -A, --attach=FILE attach FILE -a, --append=HEADER: VALUE append given header to the message being sent --[no-]alternative force multipart/alternative content type --attach-fd=FD attach from file descriptor FD --content-filename=NAME set the Content-Disposition filename parameter for the next --attach option --content-name=NAME set the Content-Type name parameter for the next --attach option --content-type=TYPE set content type for subsequent --attach options -E, --exec=COMMAND execute COMMAND -e, --exist return true if mail exists --encoding=NAME set encoding for subsequent --attach options -F, --byname save messages according to sender -H, --headers write a header summary and exit -i, --ignore ignore interrupts -M, --[no-]mime compose MIME messages -N, --nosum do not display initial header summary -n, --norc do not read the system mailrc file -p, --print, --read print all mail to standard output -q, --quit cause interrupts to terminate program -r, --return-address=ADDRESS use address as the return address when sending mail -s, --subject=SUBJ send a message with the given SUBJECT --[no-]skip-empty-attachments skip attachments with empty body -t, --to read recipients from the message header -u, --user=USER operate on USER's mailbox Global debugging settings --debug-level=LEVEL set Mailutils debugging level --[no-]debug-line-info show source info with debugging messages Configuration handling --config-file=FILE load this configuration file; implies --no-config --config-lint check configuration file syntax and exit --config-verbose verbosely log parsing of the configuration files --no-config do not load site and user configuration files --no-site-config do not load site-wide configuration file --no-user-config do not load user configuration file --set=PARAM=VALUE set configuration parameter Informational options --config-help show configuration file summary --show-config-options show compilation options -?, --help give this help list --usage give a short usage message -V, --version print program version Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. Report bugs to <bug-mailutils@gnu.org>. GNU Mailutils home page: <http://mailutils.org> General help using GNU software: <http://www.gnu.org/gethelp/> Björn
On 2023-03-15 20:37, Bjoern Voigt wrote:
On 10.02.23 17:03, Per Jessen wrote:
For me, mailx is perfect for anything I want to do in batches, and occasionally when I want to send a mail without cranking up TB.
There is another alternative: "mail" from GNU Mailutils.
If I remember correctly, that's what *SUSE used since ever, and was changed to mailx/nail because it offered improved functionality while being a drop in replacement. That was before 2007. Maybe mail from Mailutils has improved meanwhile, dunno. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (7)
-
Bjoern Voigt -
Carlos E. R. -
David C. Rankin -
David Thorburn-Gundlach -
Dr. Werner Fink -
Per Jessen -
Roger Oberholtzer