Hello and Bonjour, Erik.
Erik Weber TSI wrote in
<cafqqm0ht2db5pc+c_yph8sact9dmgn4fe6z8amo7kcha_c4...@mail.gmail.com>:
i .. say it, HTML mail is not loved on this list; but i think it
is hard to define per-recipient (domain) exceptions in the GMail
web interface, so ..
|Hi, I don’t know if you can help me but I have a small question about
|s-nail, before on Redhat 7.9 we used the mailx command.
|
|/usr/bin/mailx -v -S smtp=”${server}” -S ttycharset=utf-8 -S
|smtp-use-starttls -S nss-config-dir=/etc/pki/nssdb/ -S smtp-auth=login -S
|smtp-auth-user=”${exp}” -S smtp-auth-password=”${pwd}” -r “${exp}” -s
|“${suject}” -c “${LISTCC}” “${TO}”
|< mail.txt 1> mail.log 2>& 1
Lots of this no longer works, most importantly NSS support i had
removed as one of the very first things in February 2013. At the
moment only OpenSSL (-compatible; LibreSSL) are supported.
For the smtp= and smtp-auth* variables obsoletion messages should
be printed; there is a manual section "URL syntax and credential
lookup" for how to specify credentials. Sorry, some things
changed. I hope it gets better in the future.
(Off-topic but i admire Glenn Strauss who in a single rush added
support for a plethora of TLS implementations for his lighttpd web
server, and maintains that.)
|The string ${LISTCC} was containing mail1,mail2 and the string ${TO} was
|containing mail3,mail4
|
|With s-nail (Redhat 9.4) we changed the command to separate the string
|${TO} with space instead of ,
Why? Comma is email standard, better if this is undone.
(However it *may* be necessary for this MUA to continue to support
the space-separation for at least -t and -T; .. i still have to
integrate the standard compliant email parser i have written into
the codebase.)
...
|But what can we do for the string ${LISTCC}, we tested -c mail1 -c mail2 =>
|result not sending mail to mail1 and mail2.
We had certain such questions like this, the last being
https://lists.sdaoden.eu/pipermail/s-mailx/2024-December/001837.html
My answer was
Yet, what does not work like the above anymore is comma- or
space-separated lists, that is "a b" or "c,d". The old address
parser is foolable, and so -b etc treat their arguments as
^ (this being the reason, the old parser used can be fooled, it
can easily misinterpret data, except for simple cases, and
i want(ed) to get over this for clarity.)
..etc etc...
In short: the answer is to use the new (non-portable) -T option
-T "field: addr", --target=..
(Send mode) Add addr to the list of receivers targeted by field,
for now supported are only ‘bcc’, ‘cc’, ‘fcc’, and ‘to’. Field
and body (address) are separated by a colon ‘:’ and optionally
blank (space, tabulator) characters.
...
addr is parsed like a message header address line,
as if it would be part of a template message fed in via
-t†
...
This option may be used multiple times.
Comma-separation is actual email syntax, so, if you can, you
better revert to using comma instead of space.
...
|Thank you for helping me.
Well i hope it works out.
Greetings to beautiful France!
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
|
|During summer's humble, here's David Leonard's grumble
|
|The black bear, The black bear,
|blithely holds his own holds himself at leisure
|beating it, up and down tossing over his ups and downs with pleasure
|
|Farewell, dear collar bear
