mirror of
https://github.com/M66B/FairEmail.git
synced 2026-01-06 04:45:50 +01:00
Crowdin sync
This commit is contained in:
@@ -390,6 +390,8 @@ Operations are processed only when there is a connection to the email server or
|
||||
<br />
|
||||
*... Invalid security certificate (Can't verify identity of server) ...*
|
||||
|
||||
This can be caused by using an incorrect host name, so first double check the host name in the advanced identity/account settings (setup step 1/2). Please see the documentation of the email provider about the right host name.
|
||||
|
||||
You should try to fix this by contacting your provider or by getting a valid security certificate because invalid security certificates are insecure and allow [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). If money is an obstacle, you can get free security certificates from [Let’s Encrypt](https://letsencrypt.org).
|
||||
|
||||
Alternatively, you can accept the fingerprint of invalid server certificates like this:
|
||||
@@ -871,7 +873,7 @@ The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *...
|
||||
|
||||
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
|
||||
|
||||
The errors *... BYE Logging out ...*, *... Connection reset by peer ...* mean that the email server actively terminated an existing connection.
|
||||
The errors *... BYE Logging out ...*, *... Connection reset ...* mean that the email server actively terminated an existing connection.
|
||||
|
||||
The error *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user