From d012eee73526a959ad01012daac4d36e30fafd9b Mon Sep 17 00:00:00 2001 From: Marcel Bokhorst Date: Tue, 3 Mar 2020 22:39:36 +0100 Subject: [PATCH] Update FAQ.md --- FAQ.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/FAQ.md b/FAQ.md index 7821e766e5..8127a4fdaf 100644 --- a/FAQ.md +++ b/FAQ.md @@ -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. -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. 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). -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. -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. -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.