mirror of
https://github.com/M66B/FairEmail.git
synced 2025-01-19 05:38:31 +00:00
Updated FAQ
This commit is contained in:
parent
788e0ba301
commit
bbc8b8259c
1 changed files with 4 additions and 0 deletions
4
FAQ.md
4
FAQ.md
|
@ -321,6 +321,9 @@ See [here](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-
|
||||||
|
|
||||||
Unfortunately, Outlook doesn't properly support OAuth for IMAP/SMTP connections, so there is no other way.
|
Unfortunately, Outlook doesn't properly support OAuth for IMAP/SMTP connections, so there is no other way.
|
||||||
|
|
||||||
|
Technical background: [MSAL](https://github.com/AzureAD/microsoft-authentication-library-for-android) is supported for business accounts only
|
||||||
|
and OAuth requires embedding a client secret in the app.
|
||||||
|
|
||||||
<br />
|
<br />
|
||||||
|
|
||||||
<a name="faq15"></a>
|
<a name="faq15"></a>
|
||||||
|
@ -979,6 +982,7 @@ The following authentication methods are supported and used in this order:
|
||||||
|
|
||||||
SASL authentication methods, like CRAM-MD5, are not supported
|
SASL authentication methods, like CRAM-MD5, are not supported
|
||||||
because [JavaMail for Android](https://javaee.github.io/javamail/Android) does not support SASL authentication.
|
because [JavaMail for Android](https://javaee.github.io/javamail/Android) does not support SASL authentication.
|
||||||
|
If using secure connections, a must today, there is little value in using CRAM-MD5 anyway.
|
||||||
|
|
||||||
If your provider requires an unsupported authentication method, you'll likely get the error message *authentication failed*.
|
If your provider requires an unsupported authentication method, you'll likely get the error message *authentication failed*.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue