On Sat, Jun 27, 2020 at 07:49:14AM +0100, isdtor wrote:
> Andrew D. Arenson writes:
> > My organization is moving to Office365 and have decided, sadly, not to
> > support IMAP.
> >
> > Anyone have insight in how mutt might still be able to connect to
> > Office365?
> >
> > A co-worker has been investigating a project called davmail, which
> > provides a gateway that sort of translates from Office365's other protocols
> > to IMAP, as they use a (non-mutt) IMAP mail client.
>
> I was never able to get davmail to work in the past but now, preparing for a
> potential future like yours, I looked at it again and did get it to work. I
> tested it in conjunction with fetchmail and ran into two problems. One I was
> able to work around, the other not, but most importantly, the setup seems to
> download mails ok.
>
> That's for imaps access only. I don't need pop and haven't tested smtp or
> caldav and ldap.
>
Well, I got word today that my work inbox is being migrated by the 29th
of this month from local Exchange to Office365, so can't put this off any
longer.
I don't need caldav or ldap. Not sure if I'll need smtp in the future,
but I don't need it immediately.
I'm not familiar with fetchmail. Would you mind saying more about how
you use fetchmail and what you did to get davmail to work?
I'm using a very old version of mutt, the latest available on RHEL6:
Mutt 1.5.20 (2009-12-10)
My current .muttrc IMAP config:
set imap_pass="*************"
set spoolfile="{aaren...@imap.exchange.iu.edu/ssl}INBOX"
mailboxes !
mailboxes "{aaren...@imap.exchange.iu.edu/ssl}Junk E-mail"
set certificate_file=~/.mutt/certificates
set ssl_starttls=yes
set ssl_force_tls=yes
set imap_keepalive = 10
I don't really know what I'm doing with mutt. I've cobbled
things together over the years and they mostly work well enough. Just
trying to figure out how to keep it going.
Andy
--
Andrew D. Arenson (he/him) H 317.964.0493
arenson (at) spatzel.net C 317.679.4669
