Erik Christiansen wrote:
On 17.04.17 22:34, Charles E Campbell wrote:
Here's the result:
...
Could not send the message.
Well, it's never occurred to me to pause to figure out how to use mutt
to send email on the command line, because the MUA I used before mutt
was traditional unix "mail"¹, and it is infinitely easier to just
apt-get that. A "man mail" shows that it's:
bsd-mailx - simple mail user agent
that I'm using ATM. As /usr/bin/bsd-mailx is only 92 kB in size, it
doesn't add much ballast to mutt 1.8.0 at 2.46 MB.
Mind you, it may just be that running an MTA here (postfix these days)
is what avoids your problems. That was easy to set up after the first
effort, given that I keep a few notes to avoid excessive brow furrowing
next time round.
¹ It was what we had on HP-UX and Solaris boxes back in the 1980s, and
it still works the same.
Hello, Erik:
I tried both mail and mailx. Both fail silently when I attempt to send
an email off my machine (didn't try mailx, but mail will send email to
accounts on the same machine), although I suppose its possible they're
still re-trying somewhere in the background and won't get a failure
email for a few days. That's why I had been using mutt until recently.
I have two potential smtp(s) targets, but neither works with mutt. For
example, both smtp targets fail with:
SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-SHA)
digest-md5 authentication failed, trying next method
external authentication failed, trying next method
anonymous authentication failed, trying next method
SASL authentication failed
Could not send the message.
Regards and thank you for looking into this,
Chip Campbell
