mirror/FairEmail
1
0
Fork 0
mirror of https://github.com/M66B/FairEmail.git synced 2024-12-23 08:14:45 +00:00
Code Issues Releases Wiki Activity

Update FAQ.md

Browse source
This commit is contained in:
Marcel Bokhorst 2020-03-03 22:39:36 +01:00 committed by GitHub
parent 836be18114
commit d012eee735
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
FAQ.md
View file

@ -1250,7 +1250,7 @@ You can change this in the connection settings.
There are several possible causes, so please read to the end of this answer. There are several possible causes, so please read to the end of this answer.
The error '*Handshake failed ... WRONG_VERSION_NUMBER*' might mean that you are trying to connect to an IMAP or SMTP server The error '*Handshake failed ... WRONG_VERSION_NUMBER ...*' might mean that you are trying to connect to an IMAP or SMTP server
without an encrypted connection, typically using port 143 (IMAP) and port 25 (SMTP), or that a wrong protocol (SSL/TLS or STARTTLS) is being used. without an encrypted connection, typically using port 143 (IMAP) and port 25 (SMTP), or that a wrong protocol (SSL/TLS or STARTTLS) is being used.
Most providers provide encrypted connections using different ports, typically port 993 (IMAP) and port 465/587 (SMTP). Most providers provide encrypted connections using different ports, typically port 993 (IMAP) and port 465/587 (SMTP).
@ -1260,13 +1260,13 @@ If this isn't an option, you could enable *Allow insecure connections* both in t
See also [this FAQ](#user-content-faq4). See also [this FAQ](#user-content-faq4).
The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER*' is either caused by a bug in the SSL protocol implementation The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either caused by a bug in the SSL protocol implementation
or by a too short DH key on the email server and can unfortunately not be fixed by FairEmail. or by a too short DH key on the email server and can unfortunately not be fixed by FairEmail.
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO*' might be caused by the provider still using RC4, The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4,
which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore. which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL* might be caused by enabling hardening connections in the connection settings. The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore.