-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Feature request for Microsoft Exchange OAuth2 #1645
Comments
I was looking at it a few weeks ago, but had some trouble with it due to other changes Microsoft is making. Will document my draft code and see what can be done. |
I've added my draft code. |
Showstopper issue
Problem is Microsoft:
|
For experimental usage with SnappyMail v2.36.1+ (requires Apache AcceptPathInfo): This should be the most comprehensive "not working" draft code for anyone that wants to try using the most annoying OAuth implementer that exists. I always advice to stop using Microsoft products, but somehow too many "advisors" keep selling the crap that Microsoft produces. |
Hi! This workaround seem to introduce a new failure: under Apache 2.4+, without mod_access_compat, giving a 500 error when trying to connect. Maybe, a fix is to test the presence of mod_access_compat, and if not, use Require instead? |
@GregThib sorry, my bad. That rule shouldn't be in and i removed it. |
No problem, I use the in-dev version via git fetch, so these kinds of "bugs" are normal outside tagged versions. |
Ok, back to the drawing board. |
Microsoft are dropping support for app passwords in September.
With an extension similar to "GMail OAuth2" (where I enter my client id/secret provided by Microsoft) I can still use snappymail after September.
I've considered using DavMail (available in debian's default repositories) as a gateway between snappymail and Microsoft's exchange servers.
The text was updated successfully, but these errors were encountered: