Re: My typical .muttrc frustrations
On 22.04.17 14:33, Charles E Campbell wrote: > 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. Charles, I've just sent an email to myself via the ISP (the "Received:" header lines show it went via 3 of their servers), thus confirming that I don't have such an issue. (I'll freely admit that much of my mailx usage is to send myself a reminder after I've shut down mutt, and can't be bothered with entering the ISP password for fetchmail, and waiting for things to come up.) > 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. And that doesn't happen when mutt is used interactively, AIUI. The question seems to be: What does it do in that mode, to bring up the SSL connection, that neither mutt nor mail do in batch mode? > Regards and thank you for looking into this, > Chip Campbell No worries. Unfortunately, I haven't set up any SSL for mail, so can't shed the light of experience on the gremlins you're smoking out. Erik
Re: My typical .muttrc frustrations
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
Re: My typical .muttrc frustrations
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. Erik
Re: My typical .muttrc frustrations
lilydjwg wrote: On Sun, Apr 16, 2017 at 06:48:34PM -0400, Charles E Campbell wrote: Hello: It was tricky, but I got my .muttrc working so that I could send stuff out via the command line. Until about two weeks ago, where mutt suddenly stopped sending out email and started complaining instead. To shorten the story: this is what I use with Seamonkey. Works fine. Description : astronaut Server Name : outgoing.verizon.net Port : 465 Connection Security : SSL/TLS Authentication Method : Normal password User Name : astronaut Of course, there is a password involved and its stored in Seamonkey's passwords file. Now, on to .muttrc: [...] You can see my some of my attempts at getting mutt to talk via smtp and messing around with smtp authenticators. None of them work. Would someone please help? Try this one? set smtp_url="smtps://astron...@verizon.net@outgoing.verizon.net:465" Here's the result: cec/ fsp#06 djinni? tstmutt.cfb SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-GCM-SHA384) external authentication failed, trying next method anonymous authentication failed, trying next method plain authentication failed, trying next method Connection to outgoing.verizon.net closed digest-md5 authentication failed, trying next method No authenticators available Could not send the message. That's better than what I had been getting: (after a long pause) Connection to outgoing.verizon.net closed SMTP session failed: read error Could not send the message. Thank you, Chip Campbell
My typical .muttrc frustrations
Hello: It was tricky, but I got my .muttrc working so that I could send stuff out via the command line. Until about two weeks ago, where mutt suddenly stopped sending out email and started complaining instead. To shorten the story: this is what I use with Seamonkey. Works fine. Description : astronaut Server Name : outgoing.verizon.net Port : 465 Connection Security : SSL/TLS Authentication Method : Normal password User Name : astronaut Of course, there is a password involved and its stored in Seamonkey's passwords file. Now, on to .muttrc: #set smtp_url="smtp://smtp.verizon.net:465" #set smtp_url="smtps://astron...@smtp.verizon.net:465" #set smtp_url="smtps://astron...@outgoing.verizon.net:465" #set smtp_url="smtp://astron...@outgoing.verizon.net:465" #set smtp_url="smtp://outgoing.verizon.net:465" set smtp_url="smtp://outgoing.verizon.net:465/" set smtp_pass="ELIDED" set from="astron...@verizon.net" set realname="C Campbell" set editor="gvim" set move=no set smtp_authenticators="external:anonymous:plain:otp:skey:digest-md5:scram:ntlm:gssapi:browserid-aes128:eap-aes128" ignore "Authentication-Results:" ignore "DomainKey-Signature:" ignore "DKIM-Signature:" hdr_order Date From To Cc alternative_order text/plain text/html * set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies set certificate_file=~/.mutt/certificates set smart_wrap=yes set sort='threads' set sort_aux='last-date-received' # vim: ft=muttrc You can see my some of my attempts at getting mutt to talk via smtp and messing around with smtp authenticators. None of them work. Would someone please help? Thank you, Chip Campbell
