-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protocol: Mail: EWS #56
Comments
Given that Exchange 2013 is
we don't need to support it anymore in Mustang. I.e. Exchange 2016 is the oldest Exchange server that we support. We support Exchange 2016, 2019, 2022 and Office365. That said, if you would like to add support for Exchange 2013, you're free to do so :-) |
I've written some proof of concept code which I've pushed as branch Obviously the To try it out, you'll need to create the account preferences in the developer tools; you'll need values for If you're using Office 365 with OAuth then you'll get an error I added my own code to fetch from arbitrary hosts because I've only just read your comment on the issue #55 regarding fetching
Not true; Owl only has some workarounds for Exchange 2010 (SP1), and ExQuilla might even work on Exchange 2007. |
Oh, great. We can include Exchange 2013, then. But it remains low priority.
I'm very curious to see that. More options are better. Could you please push your code to a branch |
Happy to see that you're working on this and making progress! Congrats. |
I did say that I'd pushed to branch |
Merged to master
I've split up the files and commited that change. |
I've been looking at
As such, in branch
|
Thanks for your detailed report on
I had the exactly same though, after my commit. Thanks for doing that.
It used that data for the default error message. What do we now get for 404, 401, 403 etc? BTW, on a relatec topic: I see that you pass
Merged to master |
The problem is that we can get an OAuth2 error from the interactive login, where we just have the error parameters and no request. I pass |
I don't know whether it makes a difference, but |
Status update:
Contacts
Calendar
|
Implement EWS protocol for Microsoft Exchange on-premise and Office365.
Authentication via username and password (on prem) or OAuth2 (Office365).
The text was updated successfully, but these errors were encountered: