mirror/FairEmail
1
0
Fork 0
mirror of https://github.com/M66B/FairEmail.git synced 2025-03-15 08:29:24 +00:00
Code Issues Releases Wiki Activity

Updated FAQ

Browse source
This commit is contained in:
M66B 2020-01-12 16:26:08 +01:00
parent 51e971bf41
commit d5a413dcbb
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
FAQ.md
View file

@ -1144,6 +1144,7 @@ because connecting to the server and comparing the local and remotes messages ar
Note that setting a different poll interval for different accounts is deliberately not possible
since this would result in extra, unnecessary battery usage because the device would need to wake up more often than needed.
Note that you can use [automation](#user-content-faq78) for custom poll schemes.
Most of the battery usage, not considering viewing messages, is due to synchronization (receiving and sending) of messages.
So, to reduce the battery usage, set the number of days to synchronize message for to a lower value,
@ -1164,7 +1165,7 @@ will result in less network traffic and thus less battery usage.
You could disable this option for example for the sent folder and the archive.
Synchronizing messages at night is mostly not useful, so you can save on battery usage by not synchronizing at night.
In the settings you can select a schedule for message synchronization (this is a pro feature). See also [this FAQ](#user-content-faq78).
In the settings you can select a schedule for message synchronization (this is a pro feature).
FairEmail will by default synchronize the folder list on each connection.
Since folders are mostly not created, renamed and deleted very often, you can save some network and battery usage by disabling this in the receive settings.
@ -1175,6 +1176,7 @@ If you don't mind that old messages that were delete from the server are still v
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.
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 4 to reliably keep connections alive.
Some providers send every two minutes something like '*Still there*' resulting in network traffic and your device to wake up and causing unnecessary extra battery usage.
You can inspect the *Log* via the main navigation menu to check if your provider is doing this.