Hello Kevin,
Thank you for your reply.
Perhaps, I have misunderstood the Microsoft statement regarding
support for IMAP with Exchange Online, which is our use case, not
on-premisis Exchange. The paragraph below clearly states that they plan
to drop certain types of access for Exchange Online.
Have I misunderstood their statement? Is there a form of IMAP that
uses something other than "Basic Authentication for Exchange Active Sync
(EAS)"?
Regards,
Gerry
"Today, we are announcing that on October 13th, 2020 we will stop
supporting and retire Basic Authentication for Exchange Active Sync
(EAS), Post Office Protocol (POP), Internet Message Access Protocol
(IMAP), and Remote PowerShell (RPS) in Exchange Online. This means that
new or existing applications using one or more of these API’s/protocols
will not be able to use Basic Authentication when connecting
to Office 365 mailboxes or endpoints and will need to update how
they authenticate."
On 11/02/2020 18:31, Kevin J. McCarthy wrote:
On Tue, Feb 11, 2020 at 06:46:32PM +0100, Steffen Nurpmeso wrote:
Gerry O'Brien wrote in
<69f8180c-40de-b7b5-880b-0f0e9f998...@scss.tcd.ie>:
Hello,
Do you have any plans to make mutt compatible with Microsoft's
Exchange Online after they discontinue support for IMAP
https://developer.microsoft.com/en-us/office/blogs/end-of-support-for-ba\
sic-authentication-access-to-exchange-online-apis-for-office-365-custome\
rs.
Don't they support XOAUTH2/OAUTHBEARER?
As Steffen notes, it looks like the article says basic authentication
is being discontinued, not IMAP. In theory, Mutt already has
OAUTHBEARER support: see <http://www.mutt.org/doc/manual/#oauth>, but
we do rely on an external script.
If such a script is available for Exchange, or becomes available,
please let me know and I'll be glad to reference it in the documentation.
In particular, do you plan to implement MAPI over HTTP?
To be honest, this isn't on my roadmap. I don't seen enough benefit
for the effort that would be required.
I wonder whether they won't adapt the new, standardized JMAP
protocol, which will finally cover much more than just "I"MAP, but
also calenders etc. And if it is for interoperability, and maybe the
possibility to use open source software instead of putting
development power into their own stuff. I think JMAP is the future,
and i would almost bet: also for Microsoft.
I've been aware of JMAP for a while, but haven't taken a serious look
at it yet. Is usage becoming widespread outside of Fastmail yet?
--
Gerry O'Brien
Systems Manager
School of Computer Science and Statistics
Trinity College Dublin
Dublin 2
Ireland
Tel: +353 1 896 1341
