Gregory Anders <g...@gpanders.com> wrote: > On Fri, 11 Jun 2021 08:46 -0400, Ofer Inbar wrote: > >At past jobs I've always used mutt for internal email, but currently > >I'm at a company that uses Office 365 and will not enable IMAP on that > >service. Reading between the lines (the IT department is not very open), > >and based on some searches for information on the web, I strongly suspect > >this is because Office 365 + Okta, which we use for SSO, doesn't work > >well with IMAP. I'd still like to find some way to use mutt rather > >than rely on the horrible Outlook clients. > > > >Has anyone here found a workaround for this? > >Maybe you know of a way to actually enable IMAP and still require some > >short-lived token that can only be obtained from Okta? Something I > >could suggest to our IT department? > >Or maybe there's some way to wire up some proxy that can fetch using > >Exchange protocol, and is Okta-aware, and can leave the mail it > >fetches in local maildir or mbox? > >Or anything else, I'm just vaguely brainstorming. > > > >(My local machine is a MacBook, if that affects things) > > -- Cos > > You might look into DavMail, which provides a bridge between Office > 365/Exchange and IMAP. > > I am in a similar situation, but unfortunately I have not been able > to get DavMail to work. You might have better luck though.
I did find DavMail when I was doing some web searches about this last week, but got the impression from the summary that it would need our IT department to enable IMAP on Office 365. Is that not true? And do you know if it's supposed to work with Okta? I just went looking for it again, and... I cannot find documentation. Is it one of those "read the source" projects, or am I just missing some documentation that's in plain sight somewhere? -- Cos
