mirror of
https://github.com/M66B/FairEmail.git
synced 2024-12-27 18:27:43 +00:00
Updated FAQ
This commit is contained in:
parent
b8c6ab850d
commit
d55d0ac0c9
1 changed files with 4 additions and 8 deletions
12
FAQ.md
12
FAQ.md
|
@ -143,15 +143,11 @@ This IMAP extension is required to implement two way synchronization, which is n
|
||||||
So, unless your provider can enable this extension, you cannot use FairEmail for this provider.
|
So, unless your provider can enable this extension, you cannot use FairEmail for this provider.
|
||||||
|
|
||||||
<a name="FAQ11"></a>
|
<a name="FAQ11"></a>
|
||||||
~~**(11) Why is STARTTLS for IMAP not supported?**~~
|
**(11) Why is POP not supported?**
|
||||||
|
|
||||||
~~STARTTLS starts with a not encrypted connection and is therefore not secure.~~
|
Besides that any decent email provider supports [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol) these days,
|
||||||
~~All well known IMAP servers support IMAP with a plain SSL connection, so there is no need to support STARTTLS for IMAP.~~
|
using [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol) will result in unnecessary battery usage and delayed new message notifications.
|
||||||
~~If you encounter an IMAP server that requires STARTTLS, please let me know.~~
|
Moreover, POP is unsuitable for two way synchronization and more often than not people read email on different devices.
|
||||||
|
|
||||||
~~For more background information, please see [this article](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery).~~
|
|
||||||
|
|
||||||
~~tl;dr; "*Additionally, even if you configure STARTTLS perfectly and use a valid certificate, there’s still no guarantee your communication will be encrypted.*"~~
|
|
||||||
|
|
||||||
<a name="FAQ12"></a>
|
<a name="FAQ12"></a>
|
||||||
**(12) How does encryption/decryption work?**
|
**(12) How does encryption/decryption work?**
|
||||||
|
|
Loading…
Reference in a new issue