mirror of https://github.com/M66B/FairEmail.git
Updated FAQ
This commit is contained in:
parent
87453a8748
commit
0146c35f6a
2
FAQ.md
2
FAQ.md
|
@ -1564,7 +1564,7 @@ Since folders are mostly not created, renamed and deleted very often, you can sa
|
|||
FairEmail will by default check if old messages were deleted from the server on each connection.
|
||||
If you don't mind that old messages that were delete from the server are still visible in FairEmail, you can save some network and battery usage by disabling this in the receive settings.
|
||||
|
||||
Some providers don't follow the IMAP standard and don't keep connections open long enough, forcing FairEmail to reconnect often, causing extra battery usage.
|
||||
Some providers don't follow the IMAP standard and [don't keep connections open](https://datatracker.ietf.org/doc/html/rfc3501#section-5.4) long enough, forcing FairEmail to reconnect often, causing extra battery usage.
|
||||
You can inspect the *Log* via the main navigation menu to check if there are frequent reconnects (connection closed/reset, read/write error/timeout, etc).
|
||||
You can workaround this by lowering the keep-alive interval in the advanced account settings to for example 9 or 15 minutes.
|
||||
Note that battery optimizations need to be disabled in setup step 3 to reliably keep connections alive.
|
||||
|
|
Loading…
Reference in New Issue