Updated FAQ

master
M66B 3 weeks ago
parent 32517888df
commit cec0f908f2

@ -2381,6 +2381,11 @@ or by Android not supporting older protocols anymore, like SSLv3 and TLSv1.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' means that the email server and Android do not have a common SSL/TLS protocol or a common cipher. The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' means that the email server and Android do not have a common SSL/TLS protocol or a common cipher.
The cipher set the server offers might be limited or the server might support the old (and insecure) SSL protocols only. The cipher set the server offers might be limited or the server might support the old (and insecure) SSL protocols only.
The error '*... TLSV1_ALERT_ACCESS_DENIED ...*' means that the email server actively blocks the connection for some reason (only the email provider knows).
With mobile data: try enabling flight mode for 10-15 minutes.
With Wi-Fi: try turning off your modem/router for 15-20 minutes.
Mostly this results in a new network address, often solving issues like this.
The error '*javax.net.ssl.SSLHandshakeException: Read error: ... CERT_LENGTH_MISMATCH*' means that there is something wrong with the email server setup. The error '*javax.net.ssl.SSLHandshakeException: Read error: ... CERT_LENGTH_MISMATCH*' means that there is something wrong with the email server setup.
Try to switch to port 993 (IMAP) or 465 (SMTP) with SSL/TLS. Try to switch to port 993 (IMAP) or 465 (SMTP) with SSL/TLS.

@ -1355,6 +1355,7 @@ X-Google-Original-From: Somebody &lt;somebody+extra@example.org&gt;</code></pre>
<p>The error ‘<em>Handshake failed SSL handshake terminated … SSLV3_ALERT_HANDSHAKE_FAILURE … HANDSHAKE_FAILURE_ON_CLIENT_HELLO</em>’ can be caused by <a href="https://issuetracker.google.com/issues/37122132">this Android 7.0 bug</a>. This can unfortunately not be fixed by FairEmail.</p> <p>The error ‘<em>Handshake failed SSL handshake terminated … SSLV3_ALERT_HANDSHAKE_FAILURE … HANDSHAKE_FAILURE_ON_CLIENT_HELLO</em>’ can be caused by <a href="https://issuetracker.google.com/issues/37122132">this Android 7.0 bug</a>. This can unfortunately not be fixed by FairEmail.</p>
<p>The error ‘<em>Handshake failed … UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION or SSLV3_ALERT_HANDSHAKE_FAILURE …</em>’ might be caused by enabling <strong>hardening connections</strong> or <strong>Bouncy Castle</strong> in the connection settings tab page, or by Android not supporting older protocols anymore, like SSLv3 and TLSv1.</p> <p>The error ‘<em>Handshake failed … UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION or SSLV3_ALERT_HANDSHAKE_FAILURE …</em>’ might be caused by enabling <strong>hardening connections</strong> or <strong>Bouncy Castle</strong> in the connection settings tab page, or by Android not supporting older protocols anymore, like SSLv3 and TLSv1.</p>
<p>The error ‘<em>Handshake failed … UNSUPPORTED_PROTOCOL …</em>’ means that the email server and Android do not have a common SSL/TLS protocol or a common cipher. The cipher set the server offers might be limited or the server might support the old (and insecure) SSL protocols only.</p> <p>The error ‘<em>Handshake failed … UNSUPPORTED_PROTOCOL …</em>’ means that the email server and Android do not have a common SSL/TLS protocol or a common cipher. The cipher set the server offers might be limited or the server might support the old (and insecure) SSL protocols only.</p>
<p>The error ‘<em>… TLSV1_ALERT_ACCESS_DENIED …</em>’ means that the email server actively blocks the connection for some reason (only the email provider knows). With mobile data: try enabling flight mode for 10-15 minutes. With Wi-Fi: try turning off your modem/router for 15-20 minutes. Mostly this results in a new network address, often solving issues like this.</p>
<p>The error ‘<em>javax.net.ssl.SSLHandshakeException: Read error: … CERT_LENGTH_MISMATCH</em>’ means that there is something wrong with the email server setup. Try to switch to port 993 (IMAP) or 465 (SMTP) with SSL/TLS.</p> <p>The error ‘<em>javax.net.ssl.SSLHandshakeException: Read error: … CERT_LENGTH_MISMATCH</em>’ means that there is something wrong with the email server setup. Try to switch to port 993 (IMAP) or 465 (SMTP) with SSL/TLS.</p>
<p>Android 8 Oreo and later <a href="https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all">do not support</a> 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). Since version 1.2121 the Bouncy Castle secure socket provider (<a href="https://en.wikipedia.org/wiki/Java_Secure_Socket_Extension">JSSE</a>) is bundled. Enabling this socket provider in the connection-settings tab and enabling ‘<em>Allow insecure connections</em>’ in the account/identity settings <em>might</em> solve this problem.</p> <p>Android 8 Oreo and later <a href="https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all">do not support</a> 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). Since version 1.2121 the Bouncy Castle secure socket provider (<a href="https://en.wikipedia.org/wiki/Java_Secure_Socket_Extension">JSSE</a>) is bundled. Enabling this socket provider in the connection-settings tab and enabling ‘<em>Allow insecure connections</em>’ in the account/identity settings <em>might</em> solve this problem.</p>
<p>The error ‘<em>javax.net.ssl.SSLHandshakeException: Read error: … TLSV1_ALERT_INTERNAL_ERROR</em>’ means that Android and the email server share no common protocol versions and/or common ciphers.</p> <p>The error ‘<em>javax.net.ssl.SSLHandshakeException: Read error: … TLSV1_ALERT_INTERNAL_ERROR</em>’ means that Android and the email server share no common protocol versions and/or common ciphers.</p>

Loading…
Cancel
Save