msb-public
/
FairEmail
mirror of https://github.com/M66B/FairEmail.git
1
0
Code Issues Projects Releases Wiki Activity

Merge branch 'master' of github.com:M66B/FairEmail

Browse Source
pull/175/head
M66B 5 years ago
parent 7b9327d2d3 d012eee735
commit d0505e91cb
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File

8
FAQ.md
Unescape 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,12 +1260,14 @@ 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.
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.
There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something). There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).

Write Preview
Loading…
Cancel
Save