<stringname="title_advanced_unseen_hint">Some providers don\'t support this properly, which may cause synchronising none or all messages</string>
<stringname="title_advanced_sync_delay_hint">This will slow down synchronising messages</string>
<stringname="title_advanced_highlight_hint">The accent colour of the theme will be used for highlighting</string>
<stringname="title_advanced_autoclose_hint">Automatically close conversations when all messages are archived, sent or deleted</string>
<stringname="title_advanced_cleanup_attachments_hint">When manually cleaning, this will remove attachments from messages that are no longer synchronised</string>
<stringname="title_identity_color_hint">Identity colours take precedence over folder and account colours</string>
<stringname="title_advanced_subject_top">Afficher l’objet au dessus de l’expéditeur</string>
<stringname="title_advanced_subject_italic">Afficher l’objet en italique</string>
<stringname="title_advanced_subject_elipsed">Raccourcir l’objet si nécessaire</string>
<stringname="title_advanced_highlight_color">Couleur de surbrillance</string>
<stringname="title_advanced_keywords">Afficher les mots-clés dans l’en-tête du message</string>
<stringname="title_advanced_labels">Afficher les libellés Gmail dans l\'en-tête du message</string>
<stringname="title_advanced_flags">Afficher les étoiles de suivi</string>
@ -469,9 +470,9 @@
<stringname="title_advanced_date_hint">Les messages ne sont regroupés par date que s’ils sont triés par ordre chronologique</string>
<stringname="title_advanced_navbar_colorize_hint">Le fonctionnement dépend de la version et de la variante d’Android</string>
<stringname="title_advanced_threading_hint">Grouper les messages liés les uns aux autres</string>
<stringname="title_advanced_highlight_hint">La couleur d’accentuation du thème sera utilisée pour la mise en surbrillance</string>
<stringname="title_advanced_gravatars_hint">Cela pourrait présenter un risque pour la confidentialité</string>
<stringname="title_advanced_name_email_hint">Si désactivé, seuls les noms seront affichés si disponibles</string>
<stringname="title_advanced_highlight_color_hint">Couleur de surbrillance pour l\'expéditeur et l\'objet</string>
<stringname="title_advanced_preview_hint">Disponible uniquement lorsque le texte du message a été téléchargé</string>
<stringname="title_advanced_preview_issue">Le défilement peut être lent quand il y a plus d’une ligne en raison d’un bogue dans certaines versions d’Android</string>
<stringname="title_advanced_overview_mode_hint">Ceci peut afficher de très petites polices de caractères</string>
<stringname="title_advanced_subject_top">Afficher l’objet au-dessus de l’expéditeur</string>
<stringname="title_advanced_subject_italic">Afficher l’objet en italique</string>
<stringname="title_advanced_subject_elipsed">Raccourcir l\'objet si nécessaire</string>
<stringname="title_advanced_highlight_color">Couleur de surbrillance</string>
<stringname="title_advanced_keywords">Afficher les mots-clés dans l\'en-tête du message</string>
<stringname="title_advanced_labels">Afficher les libellés Gmail dans l\'en-tête du message</string>
<stringname="title_advanced_flags">Afficher les étoiles de suivi</string>
@ -469,9 +470,9 @@
<stringname="title_advanced_date_hint">Les messages ne sont regroupés par date que s\'ils sont triés par ordre chronologique</string>
<stringname="title_advanced_navbar_colorize_hint">Le fonctionnement dépend de la version et de la variante d’Android</string>
<stringname="title_advanced_threading_hint">Grouper les messages liés les uns aux autres</string>
<stringname="title_advanced_highlight_hint">La couleur d’accentuation du thème sera utilisée pour la mise en surbrillance</string>
<stringname="title_advanced_gravatars_hint">Ceci pourrait présenter un risque pour la confidentialité</string>
<stringname="title_advanced_name_email_hint">Si désactivé, seuls les noms seront affichés si disponibles</string>
<stringname="title_advanced_highlight_color_hint">Couleur de surbrillance pour l\'expéditeur et l\'objet</string>
<stringname="title_advanced_preview_hint">Disponible uniquement lorsque le texte du message a été téléchargé</string>
<stringname="title_advanced_preview_issue">Le défilement peut être lent lorsqu’il y a plus d’une ligne en raison d’un bogue dans certaines versions d’Android</string>
<stringname="title_advanced_overview_mode_hint">Ceci peut afficher de très petites polices de caractères</string>
<stringname="title_advanced_highlight_hint">De accentkleur van het thema wordt gebruikt voor markering</string>
<stringname="title_advanced_gravatars_hint">Er is mogelijk een privacyrisico</string>
<stringname="title_advanced_name_email_hint">Indien uitgeschakeld, worden alleen namen weergegeven als deze beschikbaar zijn</string>
<stringname="title_advanced_highlight_color_hint">De markeerkleur voor de afzender en het onderwerp</string>
<stringname="title_advanced_preview_hint">Alleen beschikbaar wanneer de berichttekst werd gedownload</string>
<stringname="title_advanced_preview_issue">Scrollen kan langzaam zijn vanwege een fout in sommige Android-versies wanneer het aantal regels meer dan één is</string>
<stringname="title_advanced_overview_mode_hint">Dit kan resulteren in zeer kleine lettertypen</string>
<stringname="title_advanced_protocol_hint">Toto výrazne ovplivní nároky na úložisko a využívanie batérie!</string>
<stringname="title_advanced_debug_hint">Povoliť rozšírené zaznamenávanie a zobrazovať ladiace informácie na rôznych miestach</string>
<stringname="title_advanced_cleanup_attachments_hint">Pri manuálnom čistení táto možnosť odstráni prílohy zo správ, ktoré už nie sú synchronizované</string>
<stringname="title_advanced_cleanup_hint">Toto odstráni všetky dočasné súbory</string>
<stringname="title_advanced_never_favorite">Nikdy nepovažovať za obľúbený</string>
@ -834,6 +838,10 @@ Nastavenie vždy toto kompenzuje neustálym sledovaním zmien.</string>
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
* A [bug in Android](https://issuetracker.google.com/issues/119872129) causes FairEmail to crash with "*... Bad notification posted ...*" on some devices once after updating FairEmail and tapping on a notification.
* A [bug in Android](https://issuetracker.google.com/issues/62427912) sometimes causes a crash with "*... ActivityRecord not found for ...*" after updating FairEmail. Reinstalling ([source](https://stackoverflow.com/questions/46309428/android-activitythread-reportsizeconfigurations-causes-app-to-freeze-with-black)) might fix the problem.
* A [bug in Android](https://issuetracker.google.com/issues/37018931) sometimes causes a crash with *... InputChannel is not initialized ...* on some devices.
* ~~A [bug in LineageOS](https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265273) sometimes causes a crash with *... java.lang.ArrayIndexOutOfBoundsException: length=...; index=... ...*.~~
* A bug in Nova Launcher on Android 5.x causes FairEmail to crash with a *java.lang.StackOverflowError* when Nova Launcher has access to the accessibility service.
* ~~A [bug in LineageOS](https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265273) sometimes causes a crash with *... java.lang.ArrayIndexOutOfBoundsException: length=...; index=... ...*.~~
* A bug in Nova Launcher on Android 5.x causes FairEmail to crash with a *java.lang.StackOverflowError* when Nova Launcher has access to the accessibility service.
* ~~The folder selector sometimes shows no folders for yet unknown reasons. This seems to be fixed.~~
* ~~A [bug in AndroidX](https://issuetracker.google.com/issues/64729576) makes it hard to grap the fast scroller. A workaround was added.~~
* ~~Encryption with YubiKey results into an infinite loop. This seems to be caused by a [bug in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
@ -326,7 +326,7 @@ FairEmail will keep a list of addresses you receive messages from and send messa
<aname="faq2"></a>
**(2) Why is there a permanent notification shown?**
A low priority permanent status bar notification with the number of accounts being monitored and the number of operations pending (see the next question) is shown to prevent Android from killing the service that takes care of continuous receiving email. This was [already necessary](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), but with the introduction of [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) in Android 6 Marshmallow this is more than ever necessary. Doze mode will stop all apps when the screen is off for some time, unless the app did start a foreground service, which requires showing a status bar notification.
A low priority permanent status bar notification with the number of accounts being monitored and the number of operations pending (see the next question) is shown to prevent Android from killing the service that takes care of continuous receiving email. This was [already necessary](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), but with the introduction of [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) in Android 6 Marshmallow this is more than ever necessary. Doze mode will stop all apps when the screen is off for some time, unless the app did start a foreground service, which requires showing a status bar notification.
Most, if not all, other email apps don't show a notification with the "side effect" that new messages are often not or late being reported and that messages are not or late being sent.
@ -392,7 +392,7 @@ Note that older Android versions might not recognize newer certification authori
*Trust anchor for certification path not found*
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found ...* means that the default Android trust manager was not able to verify the server certificate chain.
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found ...* means that the default Android trust manager was not able to verify the server certificate chain.
You should either fix the server configuration or accept the fingerprint shown below the error message.
@ -898,9 +898,9 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
The authorization of Gmail accounts setup with the quick wizard needs to be periodically refreshed via the [Android account manager](https://developer.android.com/reference/android/accounts/AccountManager). This requires contact/account permissions and internet connectivity.
The error *... Authentication failed ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
Authentication failed ... The error *... Account not found ...* means that a previously authorized Gmail account was removed from the device.
The errors *... Authentication failed ... No token on refresh ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
Authentication failed ... The errors *... No token on refresh ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
The error *... Authentication failed ... Invalid credentials ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
* A [bug in Android](https://issuetracker.google.com/issues/119872129) causes FairEmail to crash with "*... Bad notification posted ...*" on some devices once after updating FairEmail and tapping on a notification.
* A [bug in Android](https://issuetracker.google.com/issues/62427912) sometimes causes a crash with "*... ActivityRecord not found for ...*" after updating FairEmail. Reinstalling ([source](https://stackoverflow.com/questions/46309428/android-activitythread-reportsizeconfigurations-causes-app-to-freeze-with-black)) might fix the problem.
* A [bug in Android](https://issuetracker.google.com/issues/37018931) sometimes causes a crash with *... InputChannel is not initialized ...* on some devices.
* ~~A [bug in LineageOS](https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265273) sometimes causes a crash with *... java.lang.ArrayIndexOutOfBoundsException: length=...; index=... ...*.~~
* A bug in Nova Launcher on Android 5.x causes FairEmail to crash with a *java.lang.StackOverflowError* when Nova Launcher has access to the accessibility service.
* ~~A [bug in LineageOS](https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265273) sometimes causes a crash with *... java.lang.ArrayIndexOutOfBoundsException: length=...; index=... ...*.~~
* A bug in Nova Launcher on Android 5.x causes FairEmail to crash with a *java.lang.StackOverflowError* when Nova Launcher has access to the accessibility service.
* ~~The folder selector sometimes shows no folders for yet unknown reasons. This seems to be fixed.~~
* ~~A [bug in AndroidX](https://issuetracker.google.com/issues/64729576) makes it hard to grap the fast scroller. A workaround was added.~~
* ~~Encryption with YubiKey results into an infinite loop. This seems to be caused by a [bug in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
@ -326,7 +326,7 @@ FairEmail will keep a list of addresses you receive messages from and send messa
<aname="faq2"></a>
**(2) Why is there a permanent notification shown?**
A low priority permanent status bar notification with the number of accounts being monitored and the number of operations pending (see the next question) is shown to prevent Android from killing the service that takes care of continuous receiving email. This was [already necessary](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), but with the introduction of [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) in Android 6 Marshmallow this is more than ever necessary. Doze mode will stop all apps when the screen is off for some time, unless the app did start a foreground service, which requires showing a status bar notification.
A low priority permanent status bar notification with the number of accounts being monitored and the number of operations pending (see the next question) is shown to prevent Android from killing the service that takes care of continuous receiving email. This was [already necessary](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), but with the introduction of [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) in Android 6 Marshmallow this is more than ever necessary. Doze mode will stop all apps when the screen is off for some time, unless the app did start a foreground service, which requires showing a status bar notification.
Most, if not all, other email apps don't show a notification with the "side effect" that new messages are often not or late being reported and that messages are not or late being sent.
@ -392,7 +392,7 @@ Note that older Android versions might not recognize newer certification authori
*Trust anchor for certification path not found*
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found ...* means that the default Android trust manager was not able to verify the server certificate chain.
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found ...* means that the default Android trust manager was not able to verify the server certificate chain.
You should either fix the server configuration or accept the fingerprint shown below the error message.
@ -898,9 +898,9 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
The authorization of Gmail accounts setup with the quick wizard needs to be periodically refreshed via the [Android account manager](https://developer.android.com/reference/android/accounts/AccountManager). This requires contact/account permissions and internet connectivity.
The error *... Authentication failed ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
Authentication failed ... The error *... Account not found ...* means that a previously authorized Gmail account was removed from the device.
The errors *... Authentication failed ... No token on refresh ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
Authentication failed ... The errors *... No token on refresh ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
The error *... Authentication failed ... Invalid credentials ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
* A [bug in Android](https://issuetracker.google.com/issues/119872129) causes FairEmail to crash with "*... Bad notification posted ...*" on some devices once after updating FairEmail and tapping on a notification.
* A [bug in Android](https://issuetracker.google.com/issues/62427912) sometimes causes a crash with "*... ActivityRecord not found for ...*" after updating FairEmail. Reinstalling ([source](https://stackoverflow.com/questions/46309428/android-activitythread-reportsizeconfigurations-causes-app-to-freeze-with-black)) might fix the problem.
* A [bug in Android](https://issuetracker.google.com/issues/37018931) sometimes causes a crash with *... InputChannel is not initialized ...* on some devices.
* ~~A [bug in LineageOS](https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265273) sometimes causes a crash with *... java.lang.ArrayIndexOutOfBoundsException: length=...; index=... ...*.~~
* A bug in Nova Launcher on Android 5.x causes FairEmail to crash with a *java.lang.StackOverflowError* when Nova Launcher has access to the accessibility service.
* ~~A [bug in LineageOS](https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265273) sometimes causes a crash with *... java.lang.ArrayIndexOutOfBoundsException: length=...; index=... ...*.~~
* A bug in Nova Launcher on Android 5.x causes FairEmail to crash with a *java.lang.StackOverflowError* when Nova Launcher has access to the accessibility service.
* ~~The folder selector sometimes shows no folders for yet unknown reasons. This seems to be fixed.~~
* ~~A [bug in AndroidX](https://issuetracker.google.com/issues/64729576) makes it hard to grap the fast scroller. A workaround was added.~~
* ~~Encryption with YubiKey results into an infinite loop. This seems to be caused by a [bug in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
@ -326,7 +326,7 @@ FairEmail will keep a list of addresses you receive messages from and send messa
<aname="faq2"></a>
**(2) Why is there a permanent notification shown?**
A low priority permanent status bar notification with the number of accounts being monitored and the number of operations pending (see the next question) is shown to prevent Android from killing the service that takes care of continuous receiving email. This was [already necessary](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), but with the introduction of [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) in Android 6 Marshmallow this is more than ever necessary. Doze mode will stop all apps when the screen is off for some time, unless the app did start a foreground service, which requires showing a status bar notification.
A low priority permanent status bar notification with the number of accounts being monitored and the number of operations pending (see the next question) is shown to prevent Android from killing the service that takes care of continuous receiving email. This was [already necessary](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), but with the introduction of [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) in Android 6 Marshmallow this is more than ever necessary. Doze mode will stop all apps when the screen is off for some time, unless the app did start a foreground service, which requires showing a status bar notification.
Most, if not all, other email apps don't show a notification with the "side effect" that new messages are often not or late being reported and that messages are not or late being sent.
@ -392,7 +392,7 @@ Note that older Android versions might not recognize newer certification authori
*Trust anchor for certification path not found*
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found ...* means that the default Android trust manager was not able to verify the server certificate chain.
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found ...* means that the default Android trust manager was not able to verify the server certificate chain.
You should either fix the server configuration or accept the fingerprint shown below the error message.
@ -898,9 +898,9 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
The authorization of Gmail accounts setup with the quick wizard needs to be periodically refreshed via the [Android account manager](https://developer.android.com/reference/android/accounts/AccountManager). This requires contact/account permissions and internet connectivity.
The error *... Authentication failed ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
Authentication failed ... The error *... Account not found ...* means that a previously authorized Gmail account was removed from the device.
The errors *... Authentication failed ... No token on refresh ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
Authentication failed ... The errors *... No token on refresh ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
The error *... Authentication failed ... Invalid credentials ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
<br/>
<aname="faq40"></a>
@ -1215,7 +1217,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
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 eller TLSV1_ALERT_PROTOCOL_VERSION ...*' kan forårsages af aktivering af forbindelseshærdning i forbindelsesindstillingerne eller af, at Android ikke længere understøtter ældre protokoller såsom SSLv3.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) 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).
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
<br/>
<aname="faq40"></a>
@ -1209,13 +1211,13 @@ Most providers provide encrypted connections using different ports, typically po
If your provider doesn't support encrypted connections, you should ask to make this possible. If this isn't an option, you could enable *Allow insecure connections* both in the advanced settings AND the account/identity settings.
Siehe auch [diese F&A](#user-content-faq4).
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 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, 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 oder TLSV1_ALERT_PROTOCOL_VERSION ...*' kann durch das Aktivieren von abgehärteten Verbindungen in den Verbindungseinstellungen verursacht werden oder durch Android, das ältere Protokolle, wie SSLv3, nicht mehr unterstützt.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) 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).
@ -1224,11 +1226,11 @@ You can use [this website](https://ssl-tools.net/mailservers) or [this website](
<br/>
<aname="faq42"></a>
**(42) Könne Sie einen neuen Anbieter zur Liste der Anbieter hinzufügen?**
**(42) Can you add a new provider to the list of providers?**
Wenn der Anbieter von mehr als ein paar Leuten benutzt wird, ja, mit Freude.
If the provider is used by more than a few people, yes, with pleasure.
Folgende Informationen werden benötigt:
The following information is needed:
```
<provider
@ -1246,13 +1248,13 @@ Folgende Informationen werden benötigt:
</provider>
```
Das EFF [schreibt](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Zusätzlich, auch wenn Sie STARTTLS perfekt konfigurieren und ein gültiges Zertifikat verwenden, gibt es noch keine Garantie dafür, dass Ihre Kommunikation verschlüsselt wird.*"
The EFF [writes](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Additionally, even if you configure STARTTLS perfectly and use a valid certificate, there’s still no guarantee your communication will be encrypted.*"
Also sind reine SSL-Verbindungen sicherer als die Verwendung von [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) und daher bevorzugt.
So, pure SSL connections are safer than using [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) and therefore preferred.
Bitte stellen Sie sicher, dass das Empfangen und Senden von Nachrichten richtig funktioniert, bevor Sie mich kontaktieren, um einen Anbieter hinzuzufügen.
Please make sure receiving and sending messages works properly before contacting me to add a provider.
Sehen Sie weiter unten wie Sie mich kontaktieren können.
See below about how to contact me.
<br/>
@ -1311,14 +1313,14 @@ You likely selected or sent an attachment or image with an outdated file manager
You can fix this by switching to an up-to-date file manager or an app designed for recent Android versions. Alternatively, you can grant FairEmail read access to the storage space on your device in the Android app settings. Note that this workaround [won't work on Android Q](https://developer.android.com/preview/privacy/scoped-storage) anymore.
Siehe auch [Frage 25](#user-content-faq25) und [Was Google dazu schreibt](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
See also [question 25](#user-content-faq25) and [what Google writes about it](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
<br/>
<aname="faq50"></a>
**(50) Can you add an option to synchronize all messages?**
A synchronize all (download all) messages will not be added because it can easily result in out of memory errors and the available storage space filling up. It can also easily result in a lot of battery and data usage. Mobile devices are just not very suitable to download and store years of messages. Sie können bese die Serversuche nutzen (siehe [Frage 13](#user-content-faq13)), die schneller und effizienter ist. Note that searching through a lot of messages stored locally would only delay searching and use extra battery power.
A synchronize all (download all) messages will not be added because it can easily result in out of memory errors and the available storage space filling up. It can also easily result in a lot of battery and data usage. Mobile devices are just not very suitable to download and store years of messages. You can better use the search on server function (see [question 13](#user-content-faq13)), which is faster and more efficient. Note that searching through a lot of messages stored locally would only delay searching and use extra battery power.
<br/>
@ -1481,7 +1483,7 @@ If you want to resize images on a case-by-case basis, you can use [Send Reduced]
~~The most natural thing to do when swiping a list entry left or right is to remove the entry from the list.~~ ~~The most natural action in the context of an email app is moving the message out of the folder to another folder.~~ ~~You can select the folder to move to in the account settings.~~
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. Siehe auch [diese Frage](#user-content-faq55).~~
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. See also [this question](#user-content-faq55).~~
~~Swiping left or right to mark a message read or unread is unnatural because the message first goes away and later comes back in a different shape.~~ ~~Note that there is an advanced option to mark messages automatically read on moving,~~~~which is in most cases a perfect replacement for the sequence mark read and move to some folder.~~ ~~You can also mark messages read from new message notifications.~~
**(66) Is FairEmail available in the Google Play Family Library?**
Der Preis für FairEmail ist dafür zu niedrig, niedriger als bei fast allen ähnlichen Apps, und es müssen [zu viele Gebühren und Steuern](#user-content-faq19) entrichtet werden. Google kassiert alleine schon 30% dafür, dass FairEmail in der [Google Play-Familienmediathek](https://support.google.com/googleone/answer/7007852) zur Verfügung gestellt wird. Note that Google promotes the Family libray, but lets developers pay for it and doesn't contribute anything.
The price of FairEmail is too low, lower than that of most similar apps, and there are [too many fees and taxes](#user-content-faq19), Google alone already takes 30 %, to justify making FairEmail available in the [Google Play Family Library](https://support.google.com/googleone/answer/7007852). Note that Google promotes the Family libray, but lets developers pay for it and doesn't contribute anything.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
<br/>
<aname="faq40"></a>
@ -1209,13 +1211,13 @@ Most providers provide encrypted connections using different ports, typically po
If your provider doesn't support encrypted connections, you should ask to make this possible. If this isn't an option, you could enable *Allow insecure connections* both in the advanced settings AND the account/identity settings.
Siehe auch [diese F&A](#user-content-faq4).
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 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, 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 oder TLSV1_ALERT_PROTOCOL_VERSION ...*' kann durch das Aktivieren von abgehärteten Verbindungen in den Verbindungseinstellungen verursacht werden oder durch Android, das ältere Protokolle, wie SSLv3, nicht mehr unterstützt.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) 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).
@ -1224,11 +1226,11 @@ You can use [this website](https://ssl-tools.net/mailservers) or [this website](
<br/>
<aname="faq42"></a>
**(42) Könne Sie einen neuen Anbieter zur Liste der Anbieter hinzufügen?**
**(42) Can you add a new provider to the list of providers?**
Wenn der Anbieter von mehr als ein paar Leuten benutzt wird, ja, mit Freude.
If the provider is used by more than a few people, yes, with pleasure.
Folgende Informationen werden benötigt:
The following information is needed:
```
<provider
@ -1246,13 +1248,13 @@ Folgende Informationen werden benötigt:
</provider>
```
Das EFF [schreibt](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Zusätzlich, auch wenn Sie STARTTLS perfekt konfigurieren und ein gültiges Zertifikat verwenden, gibt es noch keine Garantie dafür, dass Ihre Kommunikation verschlüsselt wird.*"
The EFF [writes](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Additionally, even if you configure STARTTLS perfectly and use a valid certificate, there’s still no guarantee your communication will be encrypted.*"
Also sind reine SSL-Verbindungen sicherer als die Verwendung von [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) und daher bevorzugt.
So, pure SSL connections are safer than using [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) and therefore preferred.
Bitte stellen Sie sicher, dass das Empfangen und Senden von Nachrichten richtig funktioniert, bevor Sie mich kontaktieren, um einen Anbieter hinzuzufügen.
Please make sure receiving and sending messages works properly before contacting me to add a provider.
Sehen Sie weiter unten wie Sie mich kontaktieren können.
See below about how to contact me.
<br/>
@ -1311,14 +1313,14 @@ You likely selected or sent an attachment or image with an outdated file manager
You can fix this by switching to an up-to-date file manager or an app designed for recent Android versions. Alternatively, you can grant FairEmail read access to the storage space on your device in the Android app settings. Note that this workaround [won't work on Android Q](https://developer.android.com/preview/privacy/scoped-storage) anymore.
Siehe auch [Frage 25](#user-content-faq25) und [Was Google dazu schreibt](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
See also [question 25](#user-content-faq25) and [what Google writes about it](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
<br/>
<aname="faq50"></a>
**(50) Can you add an option to synchronize all messages?**
A synchronize all (download all) messages will not be added because it can easily result in out of memory errors and the available storage space filling up. It can also easily result in a lot of battery and data usage. Mobile devices are just not very suitable to download and store years of messages. Sie können bese die Serversuche nutzen (siehe [Frage 13](#user-content-faq13)), die schneller und effizienter ist. Note that searching through a lot of messages stored locally would only delay searching and use extra battery power.
A synchronize all (download all) messages will not be added because it can easily result in out of memory errors and the available storage space filling up. It can also easily result in a lot of battery and data usage. Mobile devices are just not very suitable to download and store years of messages. You can better use the search on server function (see [question 13](#user-content-faq13)), which is faster and more efficient. Note that searching through a lot of messages stored locally would only delay searching and use extra battery power.
<br/>
@ -1481,7 +1483,7 @@ If you want to resize images on a case-by-case basis, you can use [Send Reduced]
~~The most natural thing to do when swiping a list entry left or right is to remove the entry from the list.~~ ~~The most natural action in the context of an email app is moving the message out of the folder to another folder.~~ ~~You can select the folder to move to in the account settings.~~
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. Siehe auch [diese Frage](#user-content-faq55).~~
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. See also [this question](#user-content-faq55).~~
~~Swiping left or right to mark a message read or unread is unnatural because the message first goes away and later comes back in a different shape.~~ ~~Note that there is an advanced option to mark messages automatically read on moving,~~~~which is in most cases a perfect replacement for the sequence mark read and move to some folder.~~ ~~You can also mark messages read from new message notifications.~~
**(66) Is FairEmail available in the Google Play Family Library?**
Der Preis für FairEmail ist dafür zu niedrig, niedriger als bei fast allen ähnlichen Apps, und es müssen [zu viele Gebühren und Steuern](#user-content-faq19) entrichtet werden. Google kassiert alleine schon 30% dafür, dass FairEmail in der [Google Play-Familienmediathek](https://support.google.com/googleone/answer/7007852) zur Verfügung gestellt wird. Note that Google promotes the Family libray, but lets developers pay for it and doesn't contribute anything.
The price of FairEmail is too low, lower than that of most similar apps, and there are [too many fees and taxes](#user-content-faq19), Google alone already takes 30 %, to justify making FairEmail available in the [Google Play Family Library](https://support.google.com/googleone/answer/7007852). Note that Google promotes the Family libray, but lets developers pay for it and doesn't contribute anything.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
<br/>
<aname="faq40"></a>
@ -1209,13 +1211,13 @@ Most providers provide encrypted connections using different ports, typically po
If your provider doesn't support encrypted connections, you should ask to make this possible. If this isn't an option, you could enable *Allow insecure connections* both in the advanced settings AND the account/identity settings.
Siehe auch [diese F&A](#user-content-faq4).
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 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, 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 oder TLSV1_ALERT_PROTOCOL_VERSION ...*' kann durch das Aktivieren von abgehärteten Verbindungen in den Verbindungseinstellungen verursacht werden oder durch Android, das ältere Protokolle, wie SSLv3, nicht mehr unterstützt.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) 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).
@ -1224,11 +1226,11 @@ You can use [this website](https://ssl-tools.net/mailservers) or [this website](
<br/>
<aname="faq42"></a>
**(42) Könne Sie einen neuen Anbieter zur Liste der Anbieter hinzufügen?**
**(42) Can you add a new provider to the list of providers?**
Wenn der Anbieter von mehr als ein paar Leuten benutzt wird, ja, mit Freude.
If the provider is used by more than a few people, yes, with pleasure.
Folgende Informationen werden benötigt:
The following information is needed:
```
<provider
@ -1246,13 +1248,13 @@ Folgende Informationen werden benötigt:
</provider>
```
Das EFF [schreibt](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Zusätzlich, auch wenn Sie STARTTLS perfekt konfigurieren und ein gültiges Zertifikat verwenden, gibt es noch keine Garantie dafür, dass Ihre Kommunikation verschlüsselt wird.*"
The EFF [writes](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Additionally, even if you configure STARTTLS perfectly and use a valid certificate, there’s still no guarantee your communication will be encrypted.*"
Also sind reine SSL-Verbindungen sicherer als die Verwendung von [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) und daher bevorzugt.
So, pure SSL connections are safer than using [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) and therefore preferred.
Bitte stellen Sie sicher, dass das Empfangen und Senden von Nachrichten richtig funktioniert, bevor Sie mich kontaktieren, um einen Anbieter hinzuzufügen.
Please make sure receiving and sending messages works properly before contacting me to add a provider.
Sehen Sie weiter unten wie Sie mich kontaktieren können.
See below about how to contact me.
<br/>
@ -1311,14 +1313,14 @@ You likely selected or sent an attachment or image with an outdated file manager
You can fix this by switching to an up-to-date file manager or an app designed for recent Android versions. Alternatively, you can grant FairEmail read access to the storage space on your device in the Android app settings. Note that this workaround [won't work on Android Q](https://developer.android.com/preview/privacy/scoped-storage) anymore.
Siehe auch [Frage 25](#user-content-faq25) und [Was Google dazu schreibt](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
See also [question 25](#user-content-faq25) and [what Google writes about it](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
<br/>
<aname="faq50"></a>
**(50) Can you add an option to synchronize all messages?**
A synchronize all (download all) messages will not be added because it can easily result in out of memory errors and the available storage space filling up. It can also easily result in a lot of battery and data usage. Mobile devices are just not very suitable to download and store years of messages. Sie können bese die Serversuche nutzen (siehe [Frage 13](#user-content-faq13)), die schneller und effizienter ist. Note that searching through a lot of messages stored locally would only delay searching and use extra battery power.
A synchronize all (download all) messages will not be added because it can easily result in out of memory errors and the available storage space filling up. It can also easily result in a lot of battery and data usage. Mobile devices are just not very suitable to download and store years of messages. You can better use the search on server function (see [question 13](#user-content-faq13)), which is faster and more efficient. Note that searching through a lot of messages stored locally would only delay searching and use extra battery power.
<br/>
@ -1481,7 +1483,7 @@ If you want to resize images on a case-by-case basis, you can use [Send Reduced]
~~The most natural thing to do when swiping a list entry left or right is to remove the entry from the list.~~ ~~The most natural action in the context of an email app is moving the message out of the folder to another folder.~~ ~~You can select the folder to move to in the account settings.~~
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. Siehe auch [diese Frage](#user-content-faq55).~~
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. See also [this question](#user-content-faq55).~~
~~Swiping left or right to mark a message read or unread is unnatural because the message first goes away and later comes back in a different shape.~~ ~~Note that there is an advanced option to mark messages automatically read on moving,~~~~which is in most cases a perfect replacement for the sequence mark read and move to some folder.~~ ~~You can also mark messages read from new message notifications.~~
**(66) Is FairEmail available in the Google Play Family Library?**
Der Preis für FairEmail ist dafür zu niedrig, niedriger als bei fast allen ähnlichen Apps, und es müssen [zu viele Gebühren und Steuern](#user-content-faq19) entrichtet werden. Google kassiert alleine schon 30% dafür, dass FairEmail in der [Google Play-Familienmediathek](https://support.google.com/googleone/answer/7007852) zur Verfügung gestellt wird. Note that Google promotes the Family libray, but lets developers pay for it and doesn't contribute anything.
The price of FairEmail is too low, lower than that of most similar apps, and there are [too many fees and taxes](#user-content-faq19), Google alone already takes 30 %, to justify making FairEmail available in the [Google Play Family Library](https://support.google.com/googleone/answer/7007852). Note that Google promotes the Family libray, but lets developers pay for it and doesn't contribute anything.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
<br/>
<aname="faq40"></a>
@ -1215,7 +1217,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
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 ... UNPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ... * ' peut être provoqué par l'activation du durcissement des connexions dans les paramètres de connexion ou par Android qui ne prend plus en charge les protocoles plus anciens comme SSLv3.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) 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).
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
<br/>
<aname="faq40"></a>
@ -1215,7 +1217,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
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 или TLSV1_ALERT_PROTOCOL_VERSION ...*' может быть вызвано включением усиленных соединений в настройках подключения или тем, что Android больше не поддерживают устаревшие протоколы, например SSLv3.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) 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).
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
<br/>
<aname="faq40"></a>
@ -1215,7 +1217,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
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 eller TLSV1_ALERT_PROTOCOL_VERSION ...*' kan orsakas av aktivering av härdning av anslutningar i anslutningsinställningarna eller av Android som inte stödjer äldre protokoll längre, som SSLv3.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) 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).
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
@ -1181,12 +1181,14 @@ If you got the message *This provider does not support push messages* while conf
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
By default auto optimize in the receive settings is enabled, which will switch an account to periodically checking for new messages when the email server:
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
M66B
4 years ago