Moving from mutt 1.5 to 1.13.2

[Hokan]

Mutt is at version 2.0.7.  I don't know what you might be seeing that is 1.13.2.

I am not familiar with davmail but perhaps the trouble is there; maybe it can't get a secure connection to your Exchange server?


On Thu, Jun 03, 2021 at 11:29:08AM -0400, Andrew D. Arenson wrote:
> 	On a RHEL6 box, using mutt 1.5, I got mutt to work w/ davmail, enabling me to get email from my work Office365 account. 
> 
> 	I'm transitioning to Ubuntu 20.04, which provides mutt 1.13.2 and have run into a problem that I'd love to get advice on. When I start mutt I get an error: "Encrypted connection unavailable". When I attempt to send an email I get "Error sending message, child exited 127 (Exec error.)."
> 
> 	I'm not sure where to start with either of these errors or whether or not they are related to each other.
> 
> 	My .muttrc includes:
> 
> set spoolfile="{aarenson\@iu.edu at localhost:1143}INBOX"
> set imap_pass="REDACTED"
> set imap_keepalive = 10
> set certificate_file=~/.mutt/certificates
> source ~/.mutt/smime.rc
> set smime_sign_as=ab2ec3ec.0
> 
> 	Looking at the davmail log, on the working, RHEL workstation I see:
> 
> ... davmail  - Connection from /127.0.0.1 on port 1143
> ... davmail.connection  - CONNECT - 127.0.0.1:38394
> ... davmail.exchange.ExchangeSession  - Test configuration status: 401
> ... davmail  - > * OK [CAPABILITY IMAP4REV1 AUTH=LOGIN MOVE SPECIAL-USE] IMAP4rev1 DavMail 5.5.1-3299 server ready
> ... davmail  - < a0000 AUTHENTICATE LOGIN
> etc.
> 
> 	On the not working, Ubuntu workstation the first four lines are the same, but then:
> 
> ... davmail - < a0000 STARTTLS
> ... davmail - > a0000 BAD command and authentication required
> 
>     	I tried forcing STARTTLS to 'no' with:
> 
> set ssl_starttls=no
> 
> 	... but that had no effect.
> 
> 	Any ideas on where to look next?
 
-- 
Hokan
Bicyclist
Sysadmin