Thanks for the explanation, Kevin.
Andy
On Thu, Jun 03, 2021 at 09:29:18AM -0700, Kevin J. McCarthy wrote:
> On Thu, Jun 03, 2021 at 11:42:25AM -0400, Andrew D. Arenson wrote:
> >Update:
> >
> >Setting both of the following solves the first problem: "Encrypted
> >connection unavailable"
On Thu, Jun 03, 2021 at 11:42:25AM -0400, Andrew D. Arenson wrote:
Update:
Setting both of the following solves the first problem: "Encrypted connection
unavailable"
set ssl_starttls=no
set ssl_force_tls=no
1.13.0 changed $ssl_force_tls to default set. This was backed out in
1.13.4. Howev
Update:
Setting both of the following solves the first problem: "Encrypted
connection unavailable"
set ssl_starttls=no
set ssl_force_tls=no
I'm guessing this is related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963107, but I don't know
exactly how. Perhaps m
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
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: "E
