Updated FAQ

This commit is contained in:
M66B 2019-06-19 15:14:16 +02:00
parent 2c1a0155d5
commit fe7150674e
1 changed files with 12 additions and 12 deletions

24
FAQ.md
View File

@ -181,7 +181,7 @@ FairEmail follows all the best practices for an email client as decribed in [thi
* [(106) Which launchers can show the number of new messages?](#user-content-faq106)
* [(107) How do I used colored stars?](#user-content-faq107)
* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
* [(109) Why is 'select account' available in official versions only?](#user-content-faq109)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
[I have another question.](#support)
@ -1795,21 +1795,21 @@ Permanently delete messages from other folders would defeat the purpose of the t
<br />
<a name="faq109"></a>
**(109) Why is 'select account' available in official versions only?**
**~~(109) Why is 'select account' available in official versions only?~~**
Using *select account* to select and authorize Google accounts require special permission from Google for security and privacy reasons.
This special permission can only be acquired for apps a developer manages and is responsible for.
Third party builds, like the F-Droid builds, are managed by third parties and are the responsibility of these third parties.
So, only these third parties can acquire the required permission from Google.
Since these third parties do not actually support FairEmail, they are most likely not going to request the required permission.
~~Using *select account* to select and authorize Google accounts require special permission from Google for security and privacy reasons.~~
~~This special permission can only be acquired for apps a developer manages and is responsible for.~~
~~Third party builds, like the F-Droid builds, are managed by third parties and are the responsibility of these third parties.~~
~~So, only these third parties can acquire the required permission from Google.~~
~~Since these third parties do not actually support FairEmail, they are most likely not going to request the required permission.~~
You can solve this in two ways:
~~You can solve this in two ways:~~
* Switch to the official version of FairEmail, see [here](https://github.com/M66B/open-source-email/blob/master/README.md#downloads) for the options
* Use app specific passwords, see [this FAQ](#user-content-faq6)
* ~~Switch to the official version of FairEmail, see [here](https://github.com/M66B/open-source-email/blob/master/README.md#downloads) for the options~~
* ~~Use app specific passwords, see [this FAQ](#user-content-faq6)~~
Using *select account* in third party builds is not possible in recent versions anymore.
In older versions this was possible, but it will now result in the error *UNREGISTERED_ON_API_CONSOLE*.
~~Using *select account* in third party builds is not possible in recent versions anymore.~~
~~In older versions this was possible, but it will now result in the error *UNREGISTERED_ON_API_CONSOLE*.~~
<br />