diff --git a/app/src/main/res/values-ar-rBH/strings.xml b/app/src/main/res/values-ar-rBH/strings.xml
index a5c6dc5430..a4a754100d 100644
--- a/app/src/main/res/values-ar-rBH/strings.xml
+++ b/app/src/main/res/values-ar-rBH/strings.xml
@@ -318,7 +318,6 @@
مزامنة
جارٍ التنزيل
إغلاق
- في انتظار المزامنة اللاحقة
صندوق البريد الوارد
المسودات
الأرشيف
diff --git a/app/src/main/res/values-ar-rEG/strings.xml b/app/src/main/res/values-ar-rEG/strings.xml
index a5c6dc5430..a4a754100d 100644
--- a/app/src/main/res/values-ar-rEG/strings.xml
+++ b/app/src/main/res/values-ar-rEG/strings.xml
@@ -318,7 +318,6 @@
مزامنة
جارٍ التنزيل
إغلاق
- في انتظار المزامنة اللاحقة
صندوق البريد الوارد
المسودات
الأرشيف
diff --git a/app/src/main/res/values-ar-rYE/strings.xml b/app/src/main/res/values-ar-rYE/strings.xml
index 1c0b63fb17..dd1ea133bb 100644
--- a/app/src/main/res/values-ar-rYE/strings.xml
+++ b/app/src/main/res/values-ar-rYE/strings.xml
@@ -375,7 +375,6 @@
مزامنة
جارٍ التنزيل
إغلاق
- في انتظار المزامنة اللاحقة
صندوق البريد الوارد
المسودات
الأرشيف
diff --git a/app/src/main/res/values-bg-rBG/strings.xml b/app/src/main/res/values-bg-rBG/strings.xml
index 3dc25bc96f..d44b316001 100644
--- a/app/src/main/res/values-bg-rBG/strings.xml
+++ b/app/src/main/res/values-bg-rBG/strings.xml
@@ -949,7 +949,6 @@
Синхронизиране
Изтегляне
Затваряне
- Изчаква следваща синхронизация
Обединена входяща поща / главен профил
Входящи
Чернови
diff --git a/app/src/main/res/values-ca-rES/strings.xml b/app/src/main/res/values-ca-rES/strings.xml
index 0ea30a680a..e961d0ad56 100644
--- a/app/src/main/res/values-ca-rES/strings.xml
+++ b/app/src/main/res/values-ca-rES/strings.xml
@@ -945,7 +945,6 @@ La creació i l\'ús de regles és una característica professional. Sincronitzant
Descarregant
Tancant
- Esperant la propera sincronització
Safata d\'entrada unificada / Compre principal
Safata d\'entrada
Esborranys
diff --git a/app/src/main/res/values-cs-rCZ/strings.xml b/app/src/main/res/values-cs-rCZ/strings.xml
index b0a5a3e54d..ab897c482e 100644
--- a/app/src/main/res/values-cs-rCZ/strings.xml
+++ b/app/src/main/res/values-cs-rCZ/strings.xml
@@ -387,6 +387,7 @@
Spravovat oznámení
Výchozí kanál
Kanál „příjem“
+ Nejnovější oznámení zobrazit přednostně
Pro synchronizaci zpráv použít službu na pozadí
Služba na pozadí může být systémem Android kdykoli zastavena, ale nevyžaduje oznámení ve stavové liště
Zobrazit počet nových zpráv u ikony aplikace
@@ -514,6 +515,7 @@
Pro nositelná zařízení umějící zobrazit celý text (až 5,000 znaků)
Pozdrží zobrazení oznámení, dokud není stažen text zprávy
Oznámení jsou do nositelného zařízení odeslány teprve po stažení textu zprávy
+ Vyžadováno pro podporu Android Auto
Cílovou složku lze změnit v nastavení účtu
Tato verze Androidu nepodporuje seskupování oznámení
Tato verze Androidu nepodporuje kanály oznámení
@@ -1083,7 +1085,6 @@
Probíhá synchronizace
Stahování
Ukončování
- Čekání na další synchronizaci
Sjednocené doručené / hlavní účet
Doručené
Koncepty
diff --git a/app/src/main/res/values-da-rDK/strings.xml b/app/src/main/res/values-da-rDK/strings.xml
index 537c98d95b..8450e45adf 100644
--- a/app/src/main/res/values-da-rDK/strings.xml
+++ b/app/src/main/res/values-da-rDK/strings.xml
@@ -364,6 +364,7 @@
Håndtér notifikationer
Standardkanal
Modtagekanal
+ Vis seneste notifikationer først
Benyt baggrundstjeneste til beskedsynkronisering
En baggrundstjeneste kan til enhver tid stoppes af Android, men behøver ingen statusbjælkenotifikation
Vis launcher-ikon med antal nye beskeder
@@ -387,6 +388,7 @@
Fjern nye beskednotifikationer ved tryk på notifikationen
Fjern nye beskednotifikationer ved visning af beskedliste
Send kun notifikationer med en beskedforhåndsvisning til wearables
+ Benyt Android \'beskedstil\' notifikationsformat
Vis notifikationsindhold ved brug af biometrisk godkendelse
Benyt notifikations-LED
Vælg notifikationslyd
@@ -490,6 +492,7 @@
For wearables, som kan vise den fulde tekst (op til 5.000 tegn)
Dette forsinker visning af notifikationer indtil beskedteksten er downloadet
Notifikationer sendes kun til en wearable, når beskedteksten er blevet downloadet
+ Dette kræves til Android Auto-understøttelse
Målmappen kan opsættes i kontoindstillingerne
Denne Android-version understøtter ikke notifikationsgruppering
Denne Android-version understøtter ikke notifikationskanaler
@@ -1053,7 +1056,6 @@
Synkroniserer
Downloader
Lukker
- Afventer næste synkronisering
Samlet indbakke/primærkonto
Indbakke
Kladder
diff --git a/app/src/main/res/values-de-rAT/strings.xml b/app/src/main/res/values-de-rAT/strings.xml
index aaf673d50a..5e0f31c6d6 100644
--- a/app/src/main/res/values-de-rAT/strings.xml
+++ b/app/src/main/res/values-de-rAT/strings.xml
@@ -366,6 +366,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Benachrichtigungen verwalten
Standardkanal
Empfangskanal
+ Neueste Benachrichtigungen zuerst anzeigen
Hintergrunddienst verwenden, um Nachrichten zu synchronisieren
Ein Hintergrunddienst kann jederzeit von Android angehalten werden, erfordert aber keine Benachrichtigung in der Statusleiste
Startsymbol mit der Anzahl der neuen Nachrichten anzeigen
@@ -389,6 +390,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Benachrichtigung über neue Nachrichten durch Tippen auf die Benachrichtigung entfernen
Benachrichtigung über neue Nachrichten beim Anzeigen der Nachrichtenliste entfernen
Nur Benachrichtigungen mit einer Nachrichtenvorschau an tragbare Gerätschaften senden
+ Androids Benachrichtigungsformat »messaging style« verwenden
Benachrichtigungsinhalt bei Nutzung der biometrischen Authentifizierung anzeigen
Benachrichtigungslicht verwenden
Benachrichtigungston auswählen
@@ -493,6 +495,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Für Wearables, die den kompletten Text anzeigen können (bis zu 5.000 Zeichen)
Dadurch wird die Anzeige der Benachrichtigungen verzögert, bis der Nachrichtentext heruntergeladen wurde.
Benachrichtigungen werden nur nach dem Download des Nachrichtentextes an einen tragbaren Empfänger gesendet
+ Dies ist für die Unterstützung von Android Auto erforderlich
Der Zielordner kann in den Kontoeinstellungen konfiguriert werden
Diese Android-Version unterstützt keine gruppierten Benachrichtigungen
Diese Android-Version unterstützt keine Benachrichtigungskanäle
@@ -1052,6 +1055,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Nachrichteninhalt bei Bedarf herunterladen
Synchronisierung an
Synchronisierung aus
+ periodisch synchronisieren
nicht verbunden
wird verbunden
Verbunden
@@ -1059,7 +1063,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
wird synchronisiert
wird heruntergeladen
Schließen
- Warten auf Synchronisation
Sammeleingang / Hauptkonto
Posteingang
Entwürfe
diff --git a/app/src/main/res/values-de-rDE/strings.xml b/app/src/main/res/values-de-rDE/strings.xml
index aaf673d50a..5e0f31c6d6 100644
--- a/app/src/main/res/values-de-rDE/strings.xml
+++ b/app/src/main/res/values-de-rDE/strings.xml
@@ -366,6 +366,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Benachrichtigungen verwalten
Standardkanal
Empfangskanal
+ Neueste Benachrichtigungen zuerst anzeigen
Hintergrunddienst verwenden, um Nachrichten zu synchronisieren
Ein Hintergrunddienst kann jederzeit von Android angehalten werden, erfordert aber keine Benachrichtigung in der Statusleiste
Startsymbol mit der Anzahl der neuen Nachrichten anzeigen
@@ -389,6 +390,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Benachrichtigung über neue Nachrichten durch Tippen auf die Benachrichtigung entfernen
Benachrichtigung über neue Nachrichten beim Anzeigen der Nachrichtenliste entfernen
Nur Benachrichtigungen mit einer Nachrichtenvorschau an tragbare Gerätschaften senden
+ Androids Benachrichtigungsformat »messaging style« verwenden
Benachrichtigungsinhalt bei Nutzung der biometrischen Authentifizierung anzeigen
Benachrichtigungslicht verwenden
Benachrichtigungston auswählen
@@ -493,6 +495,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Für Wearables, die den kompletten Text anzeigen können (bis zu 5.000 Zeichen)
Dadurch wird die Anzeige der Benachrichtigungen verzögert, bis der Nachrichtentext heruntergeladen wurde.
Benachrichtigungen werden nur nach dem Download des Nachrichtentextes an einen tragbaren Empfänger gesendet
+ Dies ist für die Unterstützung von Android Auto erforderlich
Der Zielordner kann in den Kontoeinstellungen konfiguriert werden
Diese Android-Version unterstützt keine gruppierten Benachrichtigungen
Diese Android-Version unterstützt keine Benachrichtigungskanäle
@@ -1052,6 +1055,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Nachrichteninhalt bei Bedarf herunterladen
Synchronisierung an
Synchronisierung aus
+ periodisch synchronisieren
nicht verbunden
wird verbunden
Verbunden
@@ -1059,7 +1063,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
wird synchronisiert
wird heruntergeladen
Schließen
- Warten auf Synchronisation
Sammeleingang / Hauptkonto
Posteingang
Entwürfe
diff --git a/app/src/main/res/values-de-rLI/strings.xml b/app/src/main/res/values-de-rLI/strings.xml
index aaf673d50a..5e0f31c6d6 100644
--- a/app/src/main/res/values-de-rLI/strings.xml
+++ b/app/src/main/res/values-de-rLI/strings.xml
@@ -366,6 +366,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Benachrichtigungen verwalten
Standardkanal
Empfangskanal
+ Neueste Benachrichtigungen zuerst anzeigen
Hintergrunddienst verwenden, um Nachrichten zu synchronisieren
Ein Hintergrunddienst kann jederzeit von Android angehalten werden, erfordert aber keine Benachrichtigung in der Statusleiste
Startsymbol mit der Anzahl der neuen Nachrichten anzeigen
@@ -389,6 +390,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Benachrichtigung über neue Nachrichten durch Tippen auf die Benachrichtigung entfernen
Benachrichtigung über neue Nachrichten beim Anzeigen der Nachrichtenliste entfernen
Nur Benachrichtigungen mit einer Nachrichtenvorschau an tragbare Gerätschaften senden
+ Androids Benachrichtigungsformat »messaging style« verwenden
Benachrichtigungsinhalt bei Nutzung der biometrischen Authentifizierung anzeigen
Benachrichtigungslicht verwenden
Benachrichtigungston auswählen
@@ -493,6 +495,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Für Wearables, die den kompletten Text anzeigen können (bis zu 5.000 Zeichen)
Dadurch wird die Anzeige der Benachrichtigungen verzögert, bis der Nachrichtentext heruntergeladen wurde.
Benachrichtigungen werden nur nach dem Download des Nachrichtentextes an einen tragbaren Empfänger gesendet
+ Dies ist für die Unterstützung von Android Auto erforderlich
Der Zielordner kann in den Kontoeinstellungen konfiguriert werden
Diese Android-Version unterstützt keine gruppierten Benachrichtigungen
Diese Android-Version unterstützt keine Benachrichtigungskanäle
@@ -1052,6 +1055,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
Nachrichteninhalt bei Bedarf herunterladen
Synchronisierung an
Synchronisierung aus
+ periodisch synchronisieren
nicht verbunden
wird verbunden
Verbunden
@@ -1059,7 +1063,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
wird synchronisiert
wird heruntergeladen
Schließen
- Warten auf Synchronisation
Sammeleingang / Hauptkonto
Posteingang
Entwürfe
diff --git a/app/src/main/res/values-el-rGR/strings.xml b/app/src/main/res/values-el-rGR/strings.xml
index f96ae458af..502939b8a9 100644
--- a/app/src/main/res/values-el-rGR/strings.xml
+++ b/app/src/main/res/values-el-rGR/strings.xml
@@ -365,6 +365,7 @@
Διαχείριση ειδοποιήσεων
Προεπιλεγμένο κανάλι
Κανάλι λήψης
+ Να προβάλλονται πρώτα οι πιο πρόσφατες ειδοποιήσεις
Χρήση υπηρεσίας στο παρασκήνιο για το συγχρονισμό των μηνυμάτων
Μια υπηρεσία που εκτελείται στο παρασκήνιο αλλά δεν απαιτεί κάποια ειδοποίηση στη γραμμή κατάστασης, μπορεί να τερματιστεί από το Android οποιαδήποτε στιγμή
Προβολή του αριθμού των νέων μηνυμάτων πάνω στο εικονίδιο εκκίνησης
@@ -388,6 +389,7 @@
Να απομακρύνεται η ειδοποίηση για νέο μήνυμα με άγγιγμα στην ειδοποίηση
Να απομακρύνεται η ειδοποίηση για νέο μήνυμα με την προβολή της λίστας μηνυμάτων
Να αποστέλλονται ειδοποιήσεις μόνον με προεπισκόπηση του μηνύματος στις φορετές συσκευές
+ Χρήση της μορφής ειδοποιήσεων του Android \"στιλ μηνυμάτων\"
Προβολή του περιεχομένου των ειδοποιήσεων κατά τη βιομετρική ταυτοποίηση
Χρήση φωτεινής ένδειξης ειδοποιήσεων
Επιλογή ήχου ειδοποιήσεων
@@ -490,6 +492,7 @@
Για φορετές συσκευές που μπορούν να προβάλλουν ολόκληρο το κείμενο (μέχρι 5.000 χαρακτήρες)
Καθυστερεί την προβολή των ειδοποιήσεων μέχρι να έχει κατέβει το κείμενο
Οι ειδοποιήσεις αποστέλλονται σε μια φορετή συσκευή μόνον αφού το κείμενο του μηνύματος έχει κατέβει
+ Απαιτείται για την υποστήριξη του Android Auto
Μπορείτε να ρυθμίσετε τον φάκελο προορισμού στις ρυθμίσεις του λογαριασμού
Αυτή η έκδοση του Android δεν υποστηρίζει ομαδοποίηση ειδοποιήσεων
Αυτή η έκδοση του Android δεν υποστηρίζει κανάλια ειδοποιήσεων
@@ -1049,6 +1052,7 @@
Κατέβασμα του περιεχομένου του μηνύματος κατόπιν αιτήματος
Συγχρονισμός ενεργός
Συγχρονισμός ανενεργός
+ Περιοδικός συγχρονισμός
Αποσυνδέθηκε
Γίνεται σύνδεση
Συνδέθηκε
@@ -1056,7 +1060,6 @@
Γίνεται συγχρονισμός
Κατεβαίνει/-ουν
Κλείσιμο
- Αναμονή για επόμενο συγχρονισμό
Ενοποιημένα εισερχόμενα / κύριος λογαριασμός
Εισερχόμενα
Πρόχειρα
diff --git a/app/src/main/res/values-en-rGB/strings.xml b/app/src/main/res/values-en-rGB/strings.xml
index 5d1c4133de..2985dd5b6b 100644
--- a/app/src/main/res/values-en-rGB/strings.xml
+++ b/app/src/main/res/values-en-rGB/strings.xml
@@ -44,7 +44,6 @@
Synchronise on
Synchronise off
Synchronising
- Waiting for next synchronisation
Bin
Number of days to synchronise / to keep messages
Default colour
diff --git a/app/src/main/res/values-es-rES/strings.xml b/app/src/main/res/values-es-rES/strings.xml
index 23f2ff3b96..ab5a44f327 100644
--- a/app/src/main/res/values-es-rES/strings.xml
+++ b/app/src/main/res/values-es-rES/strings.xml
@@ -366,6 +366,7 @@
Administrar notificaciones
Canal por defecto
Canal de recepción
+ Mostrar notificaciones más recientes primero
Usar servicio en segundo plano para sincronizar mensajes
Un servicio en segundo plano puede ser detenido por Android en cualquier momento, pero no requiere una notificación de la barra de estado
Mostrar icono del lanzador con el número de mensajes nuevos
@@ -389,6 +390,7 @@
Eliminar notificación de nuevos mensajes al pulsar en la notificación
Eliminar notificaciones de mensajes nuevos al ver la lista de mensajes
Sólo enviar notificaciones con vista previa de mensaje a dispositivos wearables
+ Usar formato de notificación \'estilo de mensajería\' de Android
Mostrar contenido de notificación al usar autenticación biométrica
Usar luz de notificación
Seleccionar sonido de notificación
@@ -493,6 +495,7 @@
Para los wearables que pueden mostrar el texto completo (hasta 5.000 caracteres)
Esto retrasa la visualización de notificaciones hasta que el texto del mensaje haya sido descargado
Las notificaciones sólo se envian a dispositivos wearables luego de que el texto del mensaje haya sido descargado
+ Esto es necesario para el soporte de Android Auto
La carpeta destino puede establecerse en la configuración de la cuenta
Esta versión de Android no es compatible con la agrupación de notificaciones
Esta versión de Android no es compatible con canales de notificación
@@ -1062,7 +1065,6 @@
Sincronizando
Descargando
Cerrando
- Esperando a la próxima sincronización
Bandeja de entrada unificada / Cuenta principal
Bandeja de entrada
Borradores
diff --git a/app/src/main/res/values-eu-rES/strings.xml b/app/src/main/res/values-eu-rES/strings.xml
index 50df4cd661..9041e60e00 100644
--- a/app/src/main/res/values-eu-rES/strings.xml
+++ b/app/src/main/res/values-eu-rES/strings.xml
@@ -917,7 +917,6 @@
Sinkronizatzen
Deskargatzen
Ixten
- Hurrengo sinkronizazioaren zain
Sarrera ontzi bateratua / kontu nagusia
Sarrera ontzia
Zirriborroak
diff --git a/app/src/main/res/values-fa-rIR/strings.xml b/app/src/main/res/values-fa-rIR/strings.xml
index f2d0bac17f..777fe9a447 100644
--- a/app/src/main/res/values-fa-rIR/strings.xml
+++ b/app/src/main/res/values-fa-rIR/strings.xml
@@ -867,7 +867,6 @@
در حال همگامسازی
درحال بارگیری
در حال بسته شدن
- در انتظار همگام سازی بعدی
صندوق دریافت یکپارچه / حساب اصلی
صندوق دریافت
پيشنويسها
diff --git a/app/src/main/res/values-fi-rFI/strings.xml b/app/src/main/res/values-fi-rFI/strings.xml
index 8399524500..81de91536b 100644
--- a/app/src/main/res/values-fi-rFI/strings.xml
+++ b/app/src/main/res/values-fi-rFI/strings.xml
@@ -83,6 +83,7 @@
Palvelimen \'%1$s\' hälytys
Yrityksiä jäljellä: %1$d
Lähettäminen vastaanottajalle %1$s epäonnistui
+ Muokattu: biometrinen tai PIN-tunnistautuminen on käytössä
%1$d minuuttia
Poistu
Viestipohjat
@@ -127,6 +128,7 @@
Asetusvelhoa voidaan käyttää moneen kertaan useamman tilin asettamiseksi
Tarvitsen uuden sähköpostiosoitteen
Mene \'takaisin\' palataksesi saapuneet-kansioon
+ Sähköpostipalveluntarjoaja on hyväksynyt OAuthin vain virallisille sovellusversioille
Muu palveluntarjoaja
Google-tilien valtuutus toimii vain virallisissa versioissa, koska Android tarkistaa sovelluksen allekirjoituksen
Ole hyvä ja myönnä oikeudet tilin valitsemiseksi ja nimesi lukemiseksi
@@ -361,6 +363,7 @@
Hallinnoi ilmoituksia
Oletuskanava
Vastaanottokanava
+ Näytä uusimmat ilmoitukset ensin
Käytä taustapalvelua viestien synkronointiin
Android voi lopettaa taustapalvelun koska tahansa, mutta taustapalvelu ei tarvitse tilapalkki-ilmoitusta
Näytä käynnistinsovelluksen kuvakkeessa uusien viestien lukumäärä
@@ -869,6 +872,7 @@
Viesti on tyhjä
liite,liitteet,liitetty,liitetyt,sisällytetty,lisätty,liitin,sisällytin,lisäsin
Oliko tarkoituksenasi lisätä liite?
+ Kaikki muotoilut menetetään
Viesti (%1$s) on suurempi kuin palvelimen raja (%2$s)
Kaikkia liitteitä ei ole ladattu
Tämä valintaikkuna voidaan ottaa uudelleen käyttöön yläreunan toimintopalkin kolmen pisteen valikosta
@@ -1055,7 +1059,6 @@
Synkronoidaan
Ladataan
Suljetaan
- Odotetaan seuraavaa synkronointia
Yhdistetty saapuneet-kansio / ensisijainen tili
Saapuneet
Luonnokset
diff --git a/app/src/main/res/values-fr-rCA/strings.xml b/app/src/main/res/values-fr-rCA/strings.xml
index af089a15a2..125907f60c 100644
--- a/app/src/main/res/values-fr-rCA/strings.xml
+++ b/app/src/main/res/values-fr-rCA/strings.xml
@@ -365,6 +365,7 @@
Gérer les notifications
Canal par défaut
Canal « Réception »
+ Afficher les notifications les plus récentes en premier
Utiliser le service d\'arrière-plan pour synchroniser les messages
Un service en arrière-plan peut être arrêté par Android à tout moment, mais ne nécessite pas de notification dans la barre d\'état
Afficher le nombre de nouveaux messages sur l\'icône de lancement
@@ -388,6 +389,7 @@
Supprimer la notification de nouveau message en tapant dessus
Supprimer les notifications de nouveaux messages lors de l’affichage de la liste des messages
Envoyer uniquement des notifications avec un aperçu de message aux appareils connectés
+ Utiliser le format de notification Android « style message »
Afficher le contenu des notifications lors de l’utilisation de l’authentification biométrique
Utiliser le voyant de notification
Sélectionner le son pour les notifications
@@ -492,6 +494,7 @@
Pour les appareils connectés qui peuvent afficher le texte complet (jusqu\'à 5 000 caractères)
Ceci retarde l\'affichage des notifications jusqu\'à ce que le texte du message ait été téléchargé
Les notifications ne sont envoyées à un appareil connecté qu’après le téléchargement du texte du message
+ Ceci est nécessaire pour la prise en charge d\'Android Auto
Le dossier cible peut être configuré dans les paramètres du compte
Cette version d’Android ne prend pas en charge le regroupement de notifications
Cette version d’Android ne prend pas en charge les canaux de notification
@@ -1054,6 +1057,7 @@
Télécharger le contenu des messages sur demande
Synchronisation activée
Synchronisation désactivée
+ Synchroniser périodiquement
Déconnecté
Connexion en cours
Connecté
@@ -1061,7 +1065,6 @@
Synchronisation en cours
Téléchargement en cours
Fermeture en cours
- En attente de la prochaine synchronisation
Boîte de réception unifiée / compte principal
Boîte de réception
Brouillons
diff --git a/app/src/main/res/values-fr-rFR/strings.xml b/app/src/main/res/values-fr-rFR/strings.xml
index aa33562234..f74735f968 100644
--- a/app/src/main/res/values-fr-rFR/strings.xml
+++ b/app/src/main/res/values-fr-rFR/strings.xml
@@ -365,6 +365,7 @@
Gérer les notifications
Canal par défaut
Canal « Réception »
+ Afficher les notifications les plus récentes en premier
Utiliser le service d\'arrière-plan pour synchroniser les messages
Un service en arrière-plan peut être arrêté par Android à tout moment, mais ne nécessite pas de notification dans la barre d\'état
Afficher le nombre de nouveaux messages sur l’icône de lancement
@@ -387,7 +388,8 @@
Reporter
Supprimer les notifications de nouveaux messages en tapant dessus
Supprimer les notifications de nouveaux messages lors de la visualisation de la liste des messages
- Envoyer uniquement des notifications avec un aperçu de message aux appareils portables
+ Envoyer uniquement des notifications avec un aperçu de message aux objets connectés
+ Utiliser le format de notification Android « style message »
Afficher le contenu des notifications lors de l’utilisation de l’authentification biométrique
Utiliser le voyant lumineux pour les notifications
Sélectionner le son pour les notifications
@@ -492,6 +494,7 @@
Pour les appareils portables qui peuvent afficher le texte complet (jusqu\'à 5 000 caractères)
Ceci retarde l\'affichage des notifications jusqu\'à ce que le texte du message ait été téléchargé
Les notifications sont envoyées à un appareil portable seulement après le téléchargement du texte du message
+ Ceci est nécessaire pour la prise en charge d\'Android Auto
Le dossier de destination peut être configuré dans les paramètres du compte
Cette version d\'Android ne prend pas en charge le regroupement de notifications
Cette version d’Android ne prend pas en charge les canaux de notification
@@ -1054,6 +1057,7 @@
Télécharger le contenu des messages sur demande
Synchronisation activée
Synchronisation désactivée
+ Synchroniser périodiquement
Déconnecté
Connexion en cours
Connecté
@@ -1061,7 +1065,6 @@
Synchronisation en cours
Téléchargement en cours
Fermeture en cours
- En attente de la prochaine synchronisation
Boîte de réception unifiée / compte principal
Boîte de réception
Brouillons
diff --git a/app/src/main/res/values-gl-rES/strings.xml b/app/src/main/res/values-gl-rES/strings.xml
index 5de3d234d8..dba2e5b8a1 100644
--- a/app/src/main/res/values-gl-rES/strings.xml
+++ b/app/src/main/res/values-gl-rES/strings.xml
@@ -128,11 +128,13 @@
O asistente de instalación pódese empregar varias veces para configurar varias contas
Preciso un novo enderezo de email
Prema \'atrás\' para volver a caixa de entrada
+ O provedor de correo so permite OAuth para as aplicacións de versións oficiais
Outro provedor
Autorizar contas de Google só funcionará nas versións oficiais desta aplicación porque Android verifica a súa sinatura dixital
Por favor, conceda permisos para seleccionar unha conta e ler o seu nome
Google pedirá permisos para ler, redactar, enviar e borrar permanentemente todo o seu correo. FairEmail nunca eliminará as súas mensaxes sen o seu consentimento explícito.
Se o cartafol de borradores non é accesible por IMAP, isto pódese solucionar na configuración de etiquetas de Gmail
+ Microsoft non prove este tipo de autorización para as contas de Outlook, Live, Hotmail, etc
O erro \'AUTHENTICATE failed\' pode estar causado porque IMAP/SMTP estea desactivado polo administrador do sistema
Autorizar o acceso á súa conta %1$s
Autorizar
@@ -200,6 +202,7 @@
Negro
Branco e negro
Intercambiar cores
+ Claro
Escuro
Segundo o sistema
Fondo escuro
@@ -246,6 +249,7 @@
Ordenar enderezos suxeridos pola frecuencia de uso
Fonte predefinida
Só poñer un único prefixo no asunto cando se responde ou reenvía
+ Inserir unha liña horizontal antes dunha cabeceira de resposta ou reenvío
Usar cabeceira estendida de resposta/reenvío
Citar texto respondido
Cambiar o tamaño das imaxes no texto respondido
@@ -278,6 +282,7 @@
Mostrar o menú de navegación por defecto no modo horizontal
Mostrar na pantalla de inicio
Usar o estilo de carta no canto do estilo de lapelas
+ Usar unha cor de fondo beixe cando se estea a empregar o estilo de carta
Agrupar por data
Conversacións en fíos
Mostrar o número de mensaxes sen ler nas conversas
@@ -303,6 +308,7 @@
Mostrar o asunto sobre o remitente
Mostrar o asunto en cursiva
Abreviar o asunto se é preciso
+ Cor de realce
Mostrar as palabras chave nas cabeceiras das mensaxes
Mostrar as etiquetas de Gmail nas cabeceiras das mensaxes
Ver estrelas
@@ -321,6 +327,7 @@
Usar tamaños de texto
Usar fontes
Usar aliñamento de texto
+ Usar liñas de separación
Pregar o texto citado
Mostrar imaxes en liña automaticamente
Mostrar a posición relativa nunha conversa cun punto
@@ -387,6 +394,7 @@
Delegar a apertura de ligazóns a Android
Confirmar a mostra de imaxes
Mostrar por defecto as mensaxes reformatadas
+ Intentar recoñecer e desactivar as imaxes de rastrexo
Enviar mensaxes sen a información de fuso horario
Mostrar textos ocultos das mensaxes
Excluír da pantalla de aplicacións recentes e impedir a toma de capturas de pantalla
@@ -415,12 +423,15 @@
Detectar o idioma da mensaxe
Crear o índice de busca
%1$d / %2$d mensaxes no índice (%3$s)
+ Idioma
+ Sistema
Verificar periodicamente se FairEmail aínda está activo
Optimizar automaticamente
Comprobar actualizacións
Probar características experimentais
Limitar o acceso simultáneo á base de datos
Enviar informes de erros
+ Rexistros de protocolo
Modo de depuración
Borrar os anexos das mensaxes vellas
Limpeza
@@ -450,9 +461,11 @@
Coller máis mensaxes cando se baixe a lista
Pódese cambiar a unha representación máis compacta e cambiar o tamaño de letra das mensaxes na barra superior de menús na vista de mensaxes
Pulsación longa en calquera cartafol na lista de cartafoles para engadilo ou quitalo da lista unificada de cartafoles
+ So cores claras
As mensaxes soamente se agrupan por data se están ordenadas temporalmente
Se isto funciona ou non depende da versión e variante de Android
Agrupar mensaxes relacionadas
+ A cor de resalto do tema será empregada para salientar
Podería haber un risco de privacidade
Cando estea desactivado, só se mostrarán os nomes cando estean dispoñibles
Soamente estará dispoñible cando o texto da mensaxe estea baixado
@@ -473,6 +486,7 @@
As novas notificacións de mensaxes borraranse sempre cando se arrastren e cando se marquen as mensaxes como lidas
Premer no nome da canle para axustar as súas propiedades
Para configurar os sons predeterminados, etc
+ Para desactivar a notificación de \'monitorización\'
Para que os reloxos e similares poidan mostrar o texto completo (até 5.000 caracteres)
Isto adía a mostra de notificacións até que o texto da mensaxe sexa descargado
As notificacións só se envían ao reloxo ou similar despois de que o texto da mensaxe sexa descargado
@@ -483,9 +497,12 @@
Activar isto mellora o rendemento de procura, pero tamén incrementa o uso da batería de do espazo de almacenamento
Isto reiniciará a aplicación
Lista de características experimentais
+ Isto incrementará moito o uso da batería e do espazo de almacenaxe!
+ Activar rexistros extra e amosar información aburrida de depuración en varios lugares
Cando se limpe manualmente, isto eliminará os anexos de mensaxes que xa non estean sincronizadas
Isto eliminará todos os ficheiros temporais
Nunca favorito
+ Editar nome
Axustar accións ao esvarar
Isto axustará o esvarar á esquerda e á dereita para todas as contas IMAP
Selección …
@@ -551,6 +568,7 @@
Falta o nome
Falta o enderezo electrónico
Enderezo email non válido: \'%1$s\'
+ O enderezo \'%1$s\' está repetido
Enderezo \'%1$s\' non válido: %2$s
Falta conta
Falta nome do servidor
@@ -585,6 +603,7 @@
Mirar mensaxes no servidor
Marcar mensaxes como lidas ao expandir
Sincronizar agora
+ Sincronizar os cartafoles derivados
Sincronizar máis mensaxes
Sincronizar
Borrar mensaxes locais
@@ -697,6 +716,7 @@
Spam
Mover
Copiar
+ Palabras chave
Anular subscrición
Crear regra
Non é spam
@@ -708,7 +728,7 @@
Adiar …
Arquivar
Responder
- Responder o remitente
+ Responder ao remitente
Responder a todos
Responder á lista
Enviar confirmación de lectura
@@ -799,11 +819,17 @@
Mediano
Grande
Color …
+ Aliñar
+ Inicio
+ Centro
+ Fin
Lista
Viñetas
Numerada
Tipo de letra
Predefinido
+ Cita de parágrafo
+ Riscado
Eliminar formatado
Inserir ligazón
Engadir imaxe
@@ -811,6 +837,7 @@
Anexar
Redimensionar
Eliminar datos privados
+ Localización xeográfica, números de serie, etc
< %1$d puntos
Seleccionar ficheiro
Engadir ficheiro anexo
@@ -845,6 +872,7 @@
A mensaxe está baleira
attached,attachment,attachments,included,anexo,anexado,adxunto,adjunto
Tiña intención de engadir un anexo?
+ Perderase todo o formatado
A mesaxe (%1$s) é máis grande que o límite do servidor (%2$s)
Non se descargaron todos os anexos
Este diálogo poderase activar de novo a través do menú dos tres puntos na barra de acción de enriba
@@ -854,6 +882,7 @@
Enviando mensaxe
A mensaxe enviarase sobre as %1$s
Asinar
+ Verificar
Cifrar
Descifrar
Volver sincronizar
@@ -948,6 +977,7 @@
Patrón de resposta
Nome do patrón
Grupo de patróns (opcional)
+ Predefinido
Favorito
Agachar nos menús
Texto do patrón
@@ -1016,6 +1046,8 @@
Redactar
Teclado
Autorización OAuth
+ Cartafol conectado
+ Cartafol desconectado
Descargar contidos das mensaxes automaticamente
Descargar contidos das mensaxes manualmente
Sincronización activada
@@ -1027,7 +1059,6 @@
Sincronizando
Descargando
Pechando
- Agardando á próxima sincronización
Caixa de entrada unificada / conta principal
Caixa de entrada
Borradores
@@ -1061,6 +1092,7 @@
Foi reenviado
Só está en formato texto
Requiriuse acuse de recibo
+ Foi enviado automaticamente
Ten anexo
É favorito
Xestionar os contactos
@@ -1123,6 +1155,8 @@
Baixar mensaxes pode levar certo tempo, dependendo da velocidade do provedor, da conexión a internet, o dispositivo e o número de mensaxes. Mentres a aplicación estea baixando mensaxes, pode responder máis lentamente.
Como FairEmail sempre está a recibir mensaxes, Android considerará que sempre está activa. Polo tanto podería parecer que FairEmail está sempre a consumir batería cando en realidade non é así.
Por defecto, FairEmail reformata as mensaxes por razóns de privacidade e de seguridade. Para ver a mensaxe orixinal, prema na icona de \'pantalla completa\' sobre o texto da mensaxe.
+ O deseño pretende non distraer e aínda manterse altamente funcional. Hai moitas opcións para personalizar a aparencia, pero comprenda que non é posible contentar a todas as persoas ao mesmo tempo.
+ O filtrado de correo lixo debería facelo o servidor de correo e non é fiable facelo nun aparello a baterías con capacidades limitadas.
Manteña pulsado para ver as opcións
Este é un resumo do contido dunha mensaxe en cru. Garde o mensaxe en cru ca icona na barra de accións para ver todo o contido.
Abrir ligazón
diff --git a/app/src/main/res/values-hr-rHR/strings.xml b/app/src/main/res/values-hr-rHR/strings.xml
index ba88977ce1..02622641a6 100644
--- a/app/src/main/res/values-hr-rHR/strings.xml
+++ b/app/src/main/res/values-hr-rHR/strings.xml
@@ -807,7 +807,6 @@
Sinkroniziranje
Preuzimanje
Zatvaranje
- Čeka se sljedeća sinkronizacija
Objedinjeni spremnik / primarni račun
Ulazni spremnik
Skice
diff --git a/app/src/main/res/values-hu-rHU/strings.xml b/app/src/main/res/values-hu-rHU/strings.xml
index 4a8b05c865..648fd4765e 100644
--- a/app/src/main/res/values-hu-rHU/strings.xml
+++ b/app/src/main/res/values-hu-rHU/strings.xml
@@ -1042,7 +1042,6 @@
Szinkronizálás...
Letöltés...
Bezárás
- Szinkronizálásra várakozás
Egységes beérkező mappa / elsődleges fiók
Bejövő mappa
Piszkozatok
diff --git a/app/src/main/res/values-in-rID/strings.xml b/app/src/main/res/values-in-rID/strings.xml
index 4de628a057..07c5a5e5bf 100644
--- a/app/src/main/res/values-in-rID/strings.xml
+++ b/app/src/main/res/values-in-rID/strings.xml
@@ -114,11 +114,13 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Panduan penginstalan dapat digunakan beberapa kali untuk mengatur banyak akun
Saya perlu alamat email baru
Ketuk \'kembali\' untuk membuka kotak masuk
+ Pengelola surel ini telah menerima OAuth hanya untuk versi aplikasi yang resmi saja
Penyedia Lainnya
Memberi otorisasi pada akun Google hanya akan berfungsi dalam versi resminya karena Android memeriksa tanda tangan aplikasi.
Mohon berikan izin untuk memilih akun dan membaca nama Anda.
Google akan meminta izin untuk membaca, menulis, mengirim dan menghapus semua email Anda secara permanen. FairEmail tidak akan pernah menghapus pesan tanpa persetujuan tegas dari Anda.
Jika folder draf tidak dapat diakses oleh IMAP, hal ini dapat diperbaiki pada pengaturan label Gmail.
+ Microsoft tidak akan memberikan tipe otorisasi ini untuk akun Outlook, Live, Hotmail, dan lainnya
Kesalahan \'AUTHENTICATE Failed\' bisa disebabkan oleh IMAP/SMTP yang dinon-aktifkan oleh administrator sistem.
Izinkan akses ke akun %1$s Anda
Perizinan
@@ -186,6 +188,7 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Hitam
Hitam dan Putih
Tukar warna
+ Terang
Gelap
Ikuti setelan sistem
Latar belakang hitam
@@ -230,6 +233,7 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Urutkan alamat yang disarankan pada frekuensi penggunaan
Huruf Standar
Awali subjek hanya sekali saat membalas atau meneruskan
+ Tambahkan garis horizontal sebelum header balasan/teruskan
Gunakan header balasan/penerusan yang diperpanjang
Kutip teks balasan
Ubah ukuran gambar dalam teks balasan
@@ -262,6 +266,7 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Tampilkan menu navigasi dalam mode lanskap secara bawaan
Tampilkan pada layar terkunci
Pakai gaya kartu seperti gaya tabel
+ Gunakan latar belakang krem ketika menggunakan gaya kartu
Kelompokkan sesuai tanggal
Obrolan via email yang berlanjut
Tampilkan jumlah pesan yang belum dibaca dalam obrolan
@@ -287,6 +292,7 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Tampilkan subjek di atas pengirim
Tampilkan subjek dengan huruf miring
Ketika dibutuhkan, mempersingkat subjek
+ Sorot warna
Tampilkan kata kunci di header pesan
Tampilkan label Gmail di header pesan
Tampilkan bintang
@@ -305,6 +311,7 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Gunakan ukuran teks
Gunakan huruf
Gunakan perata teks
+ Gunakan garis pemisah
Ciutkan teks kutipan
Tampilkan gambar sebaris secara otomatis
Tunjukkan posisi percakapan relatif dengan titik
@@ -364,6 +371,7 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Hapus notifikasi pesan baru saat mengetuk notifikasi
Hapus pemberitahuan pesan baru saat melihat daftar pesan
Hanya kirim pemberitahuan dengan pratinjau pesan ke perangkat wearable (jam tangan Android)
+ Gunakan format notifikasi \'Gaya pesan\' Android
Tampilkan konten pemberitahuan ketika menggunakan otentikasi sidik jari
Pakai lampu pemberitahuan
Pilih suara pemberitahuan
@@ -371,6 +379,7 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Delegasikan ketika membuka tautan ke sistem Android
Minta konfirmasi ketika menampilkan gambar
Tampilkan pesan yang diformat ulang secara standar
+ Coba untuk mengenali dan nonaktifkan pelacakan gambar
Kirim pesan tanpa data zona waktu
Tampilkan teks pesan tersembunyi
Sembunyikan dari layar aplikasi terbaru dan cegah pengambilan tangkapan layar
@@ -397,6 +406,8 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Deteksi bahasa teks pesan
Membangun indeks pencarian
%1$d / %2$d pesan terindeks (%3$s)
+ Bahasa
+ Sistem
Periksa secara berkala apakah FairEmail masih aktif
Optimalkan secara otomatis
Periksa pembaruan
@@ -432,9 +443,11 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Ambil lebih banyak pesan saat menggulir ke bawah
Beralih ke tata letak yang lebih kompak dan mengubah ukuran teks, ukuran teks bisa dirubah pada menu bilah aksi atas di tampilan pesan
Tekan lama folder apa pun di daftar folder untuk menambah atau menghapusnya dari daftar folder terpadu
+ Hanya tema terang
Pesan hanya dikelompokkan berdasarkan tanggal jika mereka diurutkan berdasarkan waktu
Apakah karya ini tergantung pada versi Android dan variannya
Pesan grup terkait satu sama lain
+ Warna aksen untuk tema ini akan digunakan untuk menyorot
Mungkin ada risiko privasi
Ketika dinonaktifkan hanya akan menampilkan nama jika ada
Hanya tersedia jika teks pesan sudah diunduh
@@ -444,6 +457,74 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot
Ini akan lebih akurat menampilkan pesan, tapi mungkin dengan penundaan
Secara otomatis membuka pesan ketika hanya ada satu pesan atau hanya satu pesan yang belum dibaca dalam percakapan
Secara otomatis menandai pesan terbaca ketika memperluasnya, bisa dinonaktifkan pada pengaturan akun individu
+ Tutup percakapan secara otomatis ketika seluruh pesan terarsip, terkirim, atau terbuang
+ Kebanyakan penyedia tidak mengizinkan untuk mengubah alamat pengirim
+ Alamat tidak akan ditampilkan, namun akan ditambahkan ketika mengirim
+ Menonaktifkan opsi ini akan membahayakan privasi anda
+ Hasil ini akan terlihat aneh dan teks berganda
+ PIN memiliki hak lebih tinggi dibandungan autentikasi biometrik
+ Hanya tersedia di peluncur yang terdukung
+ Maksimal tiga aksi akan ditampilkan
+ Notifikasi pesan baru akan selalu dihapuskan ketika digeser dan ketika menandai pesan telah dibaca
+ Tekan nama channel untuk mengatur properti channel
+ Untuk mengatur suara standar, dll
+ Untuk menonaktifkan notifikasi \'pemantauan\'
+ Untuk perangkat yang dapat digunakan yang dapat memperlihatkan teks penuh (sampai dengan 5,000 karakter)
+ Hal ini akan menunda tampilan notifikasi sampai teks pesan tersebut telah diunduh
+ Notifikasi hanya akan dikirimkan ke perangkat yang dapat digunakan setelah pesan teks telah terunduh
+ Hal ini dibutuhkan untuk bantuan otomatis Andorid
+ Folder target dapat dikonfigurasi dalam pengaturan akun
+ Versi Android ini tidak mendukung pengelompokan notifikasi
+ Versi Android ini tidak mendukung notifikasi channel
+ Mengaktifkan hal ini akan menurunkan performa. Namun, pengaktifan diwajibkan untuk beberapa perangkat
+ Mengaktifkan hal ini akan meningkatkan performa pencarian, namun juga menurunkan penggunaan baterai dan ruang penyimpanan
+ Hal ini akan mengulang aplikasi kembali
+ Daftar fitur eksperimental yang sedang berjalan
+ Hal ini akan menurunkan penggunaan baterai dan ruang penyimpanan secara signifikan!
+ Hal ini akan menghapus berkas sementara
+ Tidak akan masuk favorit
+ Sunting nama
+ Tetapkan aksi geseran
+ Pilih …
+ Nama anda
+ Surel anda
+ Identitas warna memiliki hak lebih tinggi dari warna folder dan akun
+ Izinkan menyunting alamat pengirim
+ Balas ke alamat
+ Gunakan tanggal diterima (server)
+ Gunakan header \'Received\'
+ Gunakan header \'Date\' (waktu pengiriman)
+ Perubahan akan diterapkan hanya ke pesan baru saja
+ Tambahkan identitas terkait
+ Periksa
+ Tidak ada nama
+ Tidak ada alamat surel
+ Alamat surel tidak valid: \'%1$s\'
+ Alamat \'%1$s\' ganda
+ Alamat \'%1$s\' tidak valid: %2$s
+ Tidak ada akun
+ Tidak ada nama host
+ Tidak ada nama pengguna
+ Tidak ada kata sandi
+ Kotak masuk tidak ditemukan
+ Tidak ada folder draf
+ Tidak ada folder spam yang dipilih untuk akun ini
+ Mengirimkan surel memerlukan identitas untuk dikonfigurasi, dan folder draf yang dipilih untuk pengaturan akun
+ Penyedia ini menggunakan protokol surel hak milik dan maka dari itu penggunaan pihak ketiga untuk surel klien tidak memungkinkan
+ Penyedia ini tidak mendukung pesan push. Hal ini akan menunda penerimaan pesan baru dan meningkatkan penggunaan baterai.
+ Penyedia ini tidak mendukung UTF-8
+ Singkronisasi eror sejak %1$s
+ Domain pengirim (%1$s) dan balasan (%2$s) berbeda
+ Identitas diperlukan untuk mengirim surel
+ Folder draf diperlukan untuk mengirim surel
+ Mengirim surel memerlukan folder draf yang dipilih dalam pengaturan akun
+ Hapus akun ini secara permanen?
+ Hapus identitas ini secara permanen?
+ Sunting dalam HTML
+ Terakhir tersambung: %1$s
+ Penggunaan penyimpanan server: %1$s/%2$s
+ Tidak terdukung OAuth
+ Periksa
Judul Bawaan Diubah
diff --git a/app/src/main/res/values-it-rIT/strings.xml b/app/src/main/res/values-it-rIT/strings.xml
index 31fb2f905b..c9f2d6606f 100644
--- a/app/src/main/res/values-it-rIT/strings.xml
+++ b/app/src/main/res/values-it-rIT/strings.xml
@@ -365,6 +365,7 @@
Gestisci notifiche
Canale predefinito
Canal «Ricevi»
+ Mostra prima le notifiche più recenti
Usa un servizio in secondo piano per sincronizzare i messaggi
Un servizio in secondo piano può essere interrotto da Android in qualsiasi momento, ma non richiede una notifica nella barra di stato
Mostra icona launcher con numero di nuovi messaggi
@@ -388,6 +389,7 @@
Rimuovi la notifica di nuovo messaggio quando si tocca la notifica
Rimuovi le notifiche dei nuovi messaggi dalla lista dei messaggi
Invia notifiche con un\'anteprima del messaggio solo agli indossabili
+ Usa il formato di notifica «stile di messagistica» di Android
Mostra il contenuto delle notifiche quando si utilizza l\'autenticazione biometrica
Usa il led di notifica
Seleziona il suono di notifica
@@ -492,6 +494,7 @@
Per gli indossabili che possono mostrare il testo completo (fino a 5.000 caratteri)
Questo ritardo la visualizzazione delle notifiche fino allo scaricamento del testo del messaggio
Le notifiche sono inviate solo a un indossabile dopo che il testo del messaggio è stato scaricato
+ Questo è necessario per il supporto di Android Auto
La cartella di destinazione può essere configurata nelle impostazioni dell\'account
Questa versione Android non supporta il raggruppamento di notifiche
Questa versione Android non supporta i canali di notifica
@@ -1061,7 +1064,6 @@
Sincronizzazione
Scaricamento
Chiusura
- In attesa della prossima sincronizzazione
Posta in arrivo unificata / account principale
Posta in arrivo
Bozze
diff --git a/app/src/main/res/values-ja-rJP/strings.xml b/app/src/main/res/values-ja-rJP/strings.xml
index 1e1f3a6490..bc7d390caf 100644
--- a/app/src/main/res/values-ja-rJP/strings.xml
+++ b/app/src/main/res/values-ja-rJP/strings.xml
@@ -15,6 +15,9 @@
エラー
サーバアラート
連絡先
+ アカウントの同期と監視
+ メッセージの送信
+ 新しいメッセージ通知
- 会話
@@ -85,6 +88,7 @@
このアプリを評価
ようこそ
エンドユーザー使用許諾契約書
+ コントリビューター
同意する
同意しない
バージョン %1$s
@@ -155,6 +159,7 @@ back navigation
完了
実行中です
エラー
+ アカウントを設定しています …
設定をエクスポート
設定をインポート
インポートされたアカウントは既存のアカウントを上書きせずに追加されます
@@ -216,6 +221,7 @@ back navigation
古いメッセージがサーバから削除されたか確認
Gmailアカウント用のGmailメッセージグループ化
フォルダーリストの同期
+ 共有フォルダリストを同期
購読したフォルダーの管理
メッセージの同期時に送信者のメールアドレスを確認
メッセージ同期に関する返信メールアドレスを確認
@@ -224,6 +230,7 @@ back navigation
送信したメッセージで見つかったアドレスを提案
受信したメッセージで見つかったアドレスを提案
使用頻度で提案されたアドレスを並べ替える
+ デフォルトフォント
返信または転送時にプレフィックスを1回だけにします
拡張した返信/転送ヘッダーを使用
返信テキスト時に引用符を付ける
@@ -276,6 +283,7 @@ back navigation
送信者の上に件名を表示
件名を斜体で表示
必要に応じて件名を短くします
+ ハイライトカラー
メッセージヘッダーにキーワードを表示
スターを表示
色付きのスターの代わりに色付きの背景を表示
@@ -285,6 +293,9 @@ back navigation
デフォルトでアドレスの詳細を表示
メッセージテキストの後に添付ファイルを表示
メッセージテキストにハイコントラストを使用
+ テキストの色を使用する
+ テキストのサイズを使用する
+ フォントを使用する
引用テキストを折りたたむ
インライン画像を自動的に表示
ドットで相対的な会話の位置を表示
@@ -366,6 +377,8 @@ back navigation
メッセージのテキスト言語を検出
検索インデックスを作成
%1$d/%2$d個のメッセージがインデックス付けされました(%3$s)
+ 言語
+ システム
FairEmailがアクティブか定期的に確認
更新を確認
実験的な機能を試す
@@ -903,7 +916,6 @@ back navigation
同期する
ダウンロード中
閉じる
- 次の同期を待っています
統合受信トレイ/プライマリアカウント
受信トレイ
下書き
diff --git a/app/src/main/res/values-nl-rNL/strings.xml b/app/src/main/res/values-nl-rNL/strings.xml
index f70ada6ae5..9cbba655d4 100644
--- a/app/src/main/res/values-nl-rNL/strings.xml
+++ b/app/src/main/res/values-nl-rNL/strings.xml
@@ -189,7 +189,7 @@
Volgorde accounts
Volgorde mappen
Reset volgorde
- Verificatie
+ Authenticatie
Biometrische verificatie
Inschakelen
Uitschakelen
@@ -364,6 +364,7 @@
Beheer meldingen
Standaardkanaal
Ontvangstkanaal
+ Laat nieuwste meldingen eerst zien
Gebruik achtergrondservice om berichten te synchroniseren
Een achtergrondservice kan op elk gewenst moment worden gestopt door Android, maar vereist geen melding in de statusbalk
Toon opstartpictogram met aantal nieuwe berichten
@@ -387,6 +388,7 @@
Verwijder melding van nieuw bericht bij het tikken op melding
Verwijder meldingen van nieuwe berichten bij het bekijken van een berichtenlijst
Stuur alleen meldingen met een berichtvoorbeeld naar wearables
+ Gebruik Android \'messaging style\' notificatieformaat
Toon notificatie inhoud bij het gebruik van biometrische verificatie
Gebruik meldingslicht
Selecteer meldingsgeluid
@@ -491,6 +493,7 @@
Voor wearables die de volledige tekst kunnen weergeven (tot 5.000 tekens)
Dit vertraagt het tonen van meldingen totdat de berichttekst is gedownload
Meldingen worden alleen verzonden naar een wearable nadat de berichttekst is gedownload
+ Dit is vereist voor Android Auto ondersteuning
De doelmap kan worden geconfigureerd in de accountinstellingen
Deze Android-versie ondersteunt geen meldingsgroepering
Deze Android-versie ondersteunt geen meldingskanalen
@@ -1053,6 +1056,7 @@
Inhoud van berichten op aanvraag downloaden
Synchronisatie aan
Synchronisatie uit
+ Periodiek synchroniseren
Verbinding verbroken
Verbinding maken
Verbonden
@@ -1060,7 +1064,6 @@
Synchroniseren
Downloaden
Sluiten
- Wachten op volgende synchronisatie
Gecombineerd postvak in / primaire account
Postvak in
Concepten
diff --git a/app/src/main/res/values-nn-rNO/strings.xml b/app/src/main/res/values-nn-rNO/strings.xml
index 6543f4d6b5..ddb322f53b 100644
--- a/app/src/main/res/values-nn-rNO/strings.xml
+++ b/app/src/main/res/values-nn-rNO/strings.xml
@@ -866,7 +866,6 @@
Synkroniserer
Laster ned
Lukker
- Venter på neste synkronisering
Enhetlig innboks/primærkonto
Innboks
Utkast
diff --git a/app/src/main/res/values-no-rNO/strings.xml b/app/src/main/res/values-no-rNO/strings.xml
index 6543f4d6b5..ddb322f53b 100644
--- a/app/src/main/res/values-no-rNO/strings.xml
+++ b/app/src/main/res/values-no-rNO/strings.xml
@@ -866,7 +866,6 @@
Synkroniserer
Laster ned
Lukker
- Venter på neste synkronisering
Enhetlig innboks/primærkonto
Innboks
Utkast
diff --git a/app/src/main/res/values-pl-rPL/strings.xml b/app/src/main/res/values-pl-rPL/strings.xml
index 5f62a19e47..a848efe39c 100644
--- a/app/src/main/res/values-pl-rPL/strings.xml
+++ b/app/src/main/res/values-pl-rPL/strings.xml
@@ -386,6 +386,7 @@
Zarządzaj powiadomieniami
Domyślny kanał
Kanał odbioru
+ Pokaż najpierw najnowsze powiadomienia
Użyj usługi w tle do synchronizacji wiadomości
Usługa w tle może być w dowolnym momencie zatrzymana przez Androida, ale nie wymaga powiadomienia na pasku stanu
Pokaż liczbę nowych wiadomości na ikonie launchera
@@ -409,6 +410,7 @@
Usuń powiadomienie o nowej wiadomości po dotknięciu powiadomienia
Usuń powiadomienia o nowych wiadomościach podczas przeglądania listy wiadomości
Powiadomienia z podglądem wiadomości wysyłaj tylko do urządzeń do noszenia
+ Użyj formatu powiadomień w stylu wiadomości systemu Android
Pokaż treść powiadomienia podczas korzystania z uwierzytelniania biometrycznego
Użyj diody powiadomień
Wybierz dźwięk powiadomienia
@@ -513,6 +515,7 @@
Dla urządzeń do noszenia, które mogą wyświetlać pełny tekst (do 5000 znaków)
Opóźnia to wyświetlanie powiadomień do momentu pobrania tekstu wiadomości
Powiadomienia są wysyłane na urządzenie do noszenia tylko po pobraniu treści wiadomości
+ Jest to wymagane dla wsparcia Android Auto
Folder docelowy można skonfigurować w ustawieniach konta
Ta wersja Androida nie obsługuje grupowania powiadomień
Ta wersja Androida nie obsługuje kanałów powiadomień
@@ -1075,6 +1078,7 @@
Pobierz treść wiadomości na żądanie
Synchronizacja włączona
Synchronizacja wyłączona
+ Synchronizuj okresowo
Rozłączony
Łączenie
Połączony
@@ -1082,7 +1086,6 @@
Synchronizowanie
Pobieranie
Zamykanie
- Oczekiwanie na następną synchronizację
Wspólna skrzynka / konto podstawowe
Odebrane
Szkice
diff --git a/app/src/main/res/values-pt-rBR/strings.xml b/app/src/main/res/values-pt-rBR/strings.xml
index 07dfcc055f..a930a3ad2f 100644
--- a/app/src/main/res/values-pt-rBR/strings.xml
+++ b/app/src/main/res/values-pt-rBR/strings.xml
@@ -1040,7 +1040,6 @@
Sincronizando
Baixando
Fechando
- Aguardando a próxima sincronização
Caixa de entrada unificada / conta principal
Caixa de entrada
Rascunhos
diff --git a/app/src/main/res/values-ro-rRO/strings.xml b/app/src/main/res/values-ro-rRO/strings.xml
index 3b7f1c6889..97521d80d8 100644
--- a/app/src/main/res/values-ro-rRO/strings.xml
+++ b/app/src/main/res/values-ro-rRO/strings.xml
@@ -1071,7 +1071,6 @@
Sincronizare în curs
Descărcare în curs
Închidere
- Așteptă următoarea sincronizare
Inbox unificat / cont primar
Primite
Ciorne
diff --git a/app/src/main/res/values-ru-rRU/strings.xml b/app/src/main/res/values-ru-rRU/strings.xml
index bf153ae57c..093c0eb310 100644
--- a/app/src/main/res/values-ru-rRU/strings.xml
+++ b/app/src/main/res/values-ru-rRU/strings.xml
@@ -103,7 +103,7 @@
Ожидание подходящего соединения
Низкий
\"%1$s\" не удалось
- \'%1$s\' предупреждение сервера
+ \"%1$s\" предупреждение сервера
Оставшиеся попытки: %1$d
Отправка для %1$s не удалась
Отредактировано: включена биометрическая аутентификация или PIN-код
@@ -163,7 +163,7 @@
Авторизироваться
Выбрать учётную запись
Инструкция по установке
- Не найдено настроек для домена %1$s
+ Не найдено настроек для домена \"%1$s\"
Пожалуйста, попробуйте настроить учётную запись и идентификатор в шагах 1 и 2, используя настройки, предоставленные вашим провайдером электронной почты
Пожалуйста, проверьте свой адрес электронной почты и пароль и убедитесь, что внешний доступ (IMAP/SMTP) включён для вашей учётной записи
Данный провайдер требует пароль для приложения вместо пароля от учётной записи, пожалуйста, ознакомьтесь с его инструкциями
@@ -387,6 +387,7 @@
Настроить уведомления
Канал по умолчанию
Канал получения
+ Сначала показывать новые уведомления
Использовать фоновую службу для синхронизации сообщений
Фоновая служба может быть остановлена Android в любое время, но не требует уведомления в статусной строке
Показывать значок запуска с количеством новых сообщений
@@ -410,6 +411,7 @@
Удалять уведомление о новом сообщении при нажатии на уведомление
Удалять уведомления о новых сообщениях при просмотре списка сообщений
Отправлять уведомления на носимые устройства только с предпросмотром
+ Использовать Android-стиль уведомления о сообщении
Показывать содержимое уведомлений при использовании биометрической аутентификации
Использовать индикатор уведомлений
Выбрать звук уведомления
@@ -514,6 +516,7 @@
Для носимых устройств, которые могут показывать полный текст (до 5000 символов)
Это задержит отображения уведомлений до тех пор, пока текст сообщения не будет загружен
Уведомления на носимое устройство отправляются только после загрузки текста сообщения
+ Требуется поддержка Android Auto
Целевая папка может быть указана в настройках учётной записи
Эта версия Android не поддерживает группировку уведомлений
Эта версия Android не поддерживает каналы уведомлений
@@ -593,7 +596,7 @@
Отсутствует адрес электронной почты
Неправильный адрес электронной почты: \"%1$s\"
Адрес \"%1$s\" дублируется
- Адрес \'%1$s\' неверный: %2$s
+ Адрес \"%1$s\" неправильный: %2$s
Отсутствует учётная запись
Отсутствует имя хоста
Отсутствует имя пользователя
@@ -833,7 +836,7 @@
Отправить в…
Шифрование
Приоритет
- Сервер не найден на \'%1$s\'
+ Сервер не найден на \"%1$s\"
Стиль
Жирный
Курсив
@@ -1076,6 +1079,7 @@
Загрузка содержимого сообщения по требованию
Синхронизация включена
Синхронизация отключена
+ Периодическая синхронизация
Отключено
Подключение
Подключено
@@ -1083,7 +1087,6 @@
Синхронизация
Загрузка
Закрытие
- Ожидание следующей синхронизации
Единый почтовый ящик / основная учётная запись
Входящие
Черновики
@@ -1234,7 +1237,7 @@
Загрузка…
Заново загружаем сообщения с сервера
Действия
- Ответить на: \'%1$s\'
+ Ответить на: \"%1$s\"
Копировать: \"%1$s\"
Принять
Отклонить
diff --git a/app/src/main/res/values-sk-rSK/strings.xml b/app/src/main/res/values-sk-rSK/strings.xml
index 9caad7c330..546581d16c 100644
--- a/app/src/main/res/values-sk-rSK/strings.xml
+++ b/app/src/main/res/values-sk-rSK/strings.xml
@@ -1078,7 +1078,6 @@ Nastavenie vždy toto kompenzuje neustálym sledovaním zmien.
Synchronizácia
Preberanie
Zatváranie
- Čakanie na ďalšiu synchronizáciu
Spoločná doručená pošta / primárny účet
Doručené
Koncepty
diff --git a/app/src/main/res/values-sl-rSI/strings.xml b/app/src/main/res/values-sl-rSI/strings.xml
index 39ebbbf146..b7d130c2bc 100644
--- a/app/src/main/res/values-sl-rSI/strings.xml
+++ b/app/src/main/res/values-sl-rSI/strings.xml
@@ -901,7 +901,6 @@
Sinhroniziranje
Prejemanje
Zapiranje
- Čakanje na naslednjo sinhronizacijo
Poenotena mapa \'Prejeto\'/Glavni račun
Prejeto
Osnutki
diff --git a/app/src/main/res/values-sr-rSP/strings.xml b/app/src/main/res/values-sr-rSP/strings.xml
index b793f26c7d..3739b1a97b 100644
--- a/app/src/main/res/values-sr-rSP/strings.xml
+++ b/app/src/main/res/values-sr-rSP/strings.xml
@@ -743,7 +743,6 @@
Синхронизујем
Преузимам
Затварам
- Чекање на следећу синхронизацију
Обједињено пријемно сандуче / главни налог
Пријемно сандуче
Нацрти
diff --git a/app/src/main/res/values-sv-rSE/strings.xml b/app/src/main/res/values-sv-rSE/strings.xml
index 479b7f0664..30fbdcf487 100644
--- a/app/src/main/res/values-sv-rSE/strings.xml
+++ b/app/src/main/res/values-sv-rSE/strings.xml
@@ -364,6 +364,7 @@
Hantera aviseringar
Standard kanal
Mottagningskanal
+ Visa nyaste aviseringar först
Använd en bakgrundstjänst för att synkronisera meddelanden
En bakgrundstjänst kan stoppas av Android när som helst, men kräver inte ett meddelande i statusfältet
Visa programstartarikon med antal nya meddelanden
@@ -387,6 +388,7 @@
Ta bort aviseringar för nya meddelanden när du trycker på meddelandet
Ta bort nya meddelandeaviseringar vid visning av meddelandelistan
Skicka endast aviseringar med en förhandsgranskning av meddelanden till bärbara enheter
+ Använd Android \'meddelandestil\' aviseringsformat
Visa aviseringsinnehåll när du använder biometrisk autentisering
Använda aviseringslampan
Välj aviseringsljud
@@ -491,6 +493,7 @@
För handburna enheter som kan visa fulltext (upp till 5000 tecken)
Denna försening visar aviseringar tills meddelandet har laddats ner
Aviseringar skickas endast till en bärbar enhet efter att meddelandet har laddats ner
+ Detta krävs för Android Auto-stöd
Målmappen kan konfigureras i kontoinställningarna
Den här Android-versionen stödjer inte notifikationsgruppering
Den här Android-versionen stödjer inte notifikationsgruppering
@@ -1053,6 +1056,7 @@
Hämta meddelandeinnehåll på begäran
Synkronisera nu
Synkronisera av
+ Synkronisera periodiskt
Frånkopplad
Ansluter
Ansluten
@@ -1060,7 +1064,6 @@
Synkroniserar
Hämtar
Stänger
- Väntar på nästa synkronisering
Samlad inkorg / primärt konto
Inkorg
Utkast
diff --git a/app/src/main/res/values-tr-rTR/strings.xml b/app/src/main/res/values-tr-rTR/strings.xml
index 3075b428d1..75bc249538 100644
--- a/app/src/main/res/values-tr-rTR/strings.xml
+++ b/app/src/main/res/values-tr-rTR/strings.xml
@@ -1004,7 +1004,6 @@
Eşzamanlama yapılıyor
İndiriliyor
Kapatılıyor
- Sonraki eşzamanlama için bekleniyor
Birleşik gelen kutusu / birincil hesap
Gelen kutusu
Taslaklar
diff --git a/app/src/main/res/values-zh-rCN/strings.xml b/app/src/main/res/values-zh-rCN/strings.xml
index d971d9fb0c..b24f589e7f 100644
--- a/app/src/main/res/values-zh-rCN/strings.xml
+++ b/app/src/main/res/values-zh-rCN/strings.xml
@@ -353,6 +353,7 @@
管理通知
默认频道
接收频道
+ 最新通知显示在前
使用后台服务来同步消息
后台服务不会显示状态栏通知，但随时可能会被 Android 终止
在启动器图标上显示新消息数目
@@ -376,6 +377,7 @@
点击通知时移除新的消息通知
查看消息列表时移除新消息通知
只向可穿戴设备发送有消息预览的通知
+ 使用安卓 \'消息样式\' 通知格式
使用生物认证时显示通知内容
使用指示灯
选择通知提示音
@@ -480,6 +482,7 @@
为可穿戴设备显示完整文本(最多5,000个字符)
这会延迟通知的显示直到消息文本下载完成
通知仅在消息文本下载后发送到可穿戴设备
+ 这是支持 Android Auto 所必需的
可在账户设定中配置目标文件夹
此Android版本不支持通知分组
此Android版本不支持通知通道
@@ -1042,6 +1045,7 @@
按需下载邮件内容
同步开启
同步关闭
+ 定期同步
未连接
正在连接
已连接
@@ -1049,7 +1053,6 @@
正在同步
下载中
正在结束
- 等待下次同步
聚合收件箱/主账户
收件箱
草稿
diff --git a/app/src/main/res/values-zh-rTW/strings.xml b/app/src/main/res/values-zh-rTW/strings.xml
index 89bf754f49..2d357270e7 100644
--- a/app/src/main/res/values-zh-rTW/strings.xml
+++ b/app/src/main/res/values-zh-rTW/strings.xml
@@ -1010,7 +1010,6 @@
正在同步
正在下載
關閉中
- 等待下一次同步
全域的收件匣/主要帳戶
收件箱
草稿
diff --git a/docs/FAQ-af-rZA.md b/docs/FAQ-af-rZA.md
index a29b7ff650..5428f60b9c 100644
--- a/docs/FAQ-af-rZA.md
+++ b/docs/FAQ-af-rZA.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ar-rBH.md b/docs/FAQ-ar-rBH.md
index ff5462fae3..70582435bc 100644
--- a/docs/FAQ-ar-rBH.md
+++ b/docs/FAQ-ar-rBH.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ar-rEG.md b/docs/FAQ-ar-rEG.md
index a94712c550..1cfc2e214f 100644
--- a/docs/FAQ-ar-rEG.md
+++ b/docs/FAQ-ar-rEG.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ar-rYE.md b/docs/FAQ-ar-rYE.md
index a94712c550..1cfc2e214f 100644
--- a/docs/FAQ-ar-rYE.md
+++ b/docs/FAQ-ar-rYE.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-az-rAZ.md b/docs/FAQ-az-rAZ.md
index 6194c94571..97ebaee6b4 100644
--- a/docs/FAQ-az-rAZ.md
+++ b/docs/FAQ-az-rAZ.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-bg-rBG.md b/docs/FAQ-bg-rBG.md
index b2a8448e4b..a89f41cd0b 100644
--- a/docs/FAQ-bg-rBG.md
+++ b/docs/FAQ-bg-rBG.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-bn-rBD.md b/docs/FAQ-bn-rBD.md
index b7c74e8d2c..7b9b51498f 100644
--- a/docs/FAQ-bn-rBD.md
+++ b/docs/FAQ-bn-rBD.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-bn-rIN.md b/docs/FAQ-bn-rIN.md
index b7c74e8d2c..7b9b51498f 100644
--- a/docs/FAQ-bn-rIN.md
+++ b/docs/FAQ-bn-rIN.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ca-rES.md b/docs/FAQ-ca-rES.md
index dcdf70db1a..3cc57031c0 100644
--- a/docs/FAQ-ca-rES.md
+++ b/docs/FAQ-ca-rES.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-cs-rCZ.md b/docs/FAQ-cs-rCZ.md
index 42c26e0c20..aa32ec6a35 100644
--- a/docs/FAQ-cs-rCZ.md
+++ b/docs/FAQ-cs-rCZ.md
@@ -75,7 +75,7 @@ Související dotazy:
* ~~[Chyba v AndroidX](https://issuetracker.google.com/issues/64729576) ztěžuje uchopení posuvníku pro rychlý posun. Bylo přidáno provizorní řešení.~~
* ~~Šifrování s YubiKey vyústí v nekonečnou smyčku. Toto je zdá se způsobeno [chybou v OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Posun na interně odkazovanou pozici v původních zprávách nefunguje. Toto nelze opravit, protože zobrazení původní zprávy je uvnitř posuvného náhledu.
-* Náhled textu zprávy se na Samsung hodinkách někdy (nikdy) nezobrazí, protože [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) se zdá být ignorován. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. Viz také [tento nejčastější dotaz](#user-content-faq126).
+* Náhled textu zprávy se na Samsung hodinkách někdy (nikdy) nezobrazí, protože [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) se zdá být ignorován. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP wearables. Viz také [tento nejčastější dotaz](#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.
@@ -175,7 +175,7 @@ Design je založen na mnoha diskuzích a pokud chcete, můžete se do diskuze za
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Věděl jste, že ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ Design je založen na mnoha diskuzích a pokud chcete, můžete se do diskuze za
* [(105) Jak funguje volba roaming jako doma (RLAH)?](#user-content-faq105)
* [(106) Které spouštěče aplikací umí zobrazit odznáček s počtem nepřečtených zpráv?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Je podporován OAuth?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-da-rDK.md b/docs/FAQ-da-rDK.md
index 5014581b56..bfe83249cf 100644
--- a/docs/FAQ-da-rDK.md
+++ b/docs/FAQ-da-rDK.md
@@ -75,7 +75,7 @@ Relaterede spørgsmål:
* ~~En [fejl i AndroidX](https://issuetracker.google.com/issues/64729576) gør det svært at gribe fat i hurtig-rulningsobjektet. En løsning blev tilføjet.~~
* ~~Kryptering med YubiKey resulterer i en uendelig løkke. Dette synes forårsaget at en [fejl i OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Rulning ned til en internt linket position i originalbeskeder fungerer ikke. Dette kan ikke rettes, da originalbeskedvisningen udgør en del af selve rulningsvisningen.
-* En forhåndsvisning af en beskedtekst vises ikke (altid) på Samsung-ure, da [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean))-parameteren synes at blive ignoreret. Beskedforhåndsvisningstekster bliver vist korrekt på Pebble- 2, Fitbit Charge 3- og Mi band 3-wearables. Se også [denne FAQ](#user-content-faq126).
+* En forhåndsvisning af en beskedtekst vises ikke (altid) på Samsung-ure, da [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean))-parameteren synes at blive ignoreret. Beskedforhåndsvisningstekster fremgår korrekt på Pebble 2-, Fitbit Charge 3- og Mi band 3-wearables. Se også [denne FAQ](#user-content-faq126).
* En [fejl i Android](https://issuetracker.google.com/issues/37068143) medfører af og til et nedbrud med "*... Ugyldig forskydning... Gyldigt område er ...* når tekst er valgt og der trykkes uden for den valgte tekst. Denne fejl er rettet i Android 6.0.1.
* Interne (anker-) links vil ikke fungere, da de oprindelige beskeder vises i et indlejret WebView i en rullevisning (samtalelisten). Dette er en Android-begrænsning, der ikke kan rettes eller omgås.
@@ -175,7 +175,7 @@ Designet er baseret på mange debatter, og er du interesseret, kan du også deba
* [~~(54) Hvodan bruges et navneområdepræfiks?~~](#user-content-faq54)
* [(55) Hvordan kan alle beskeder markeres som læst, flyttes eller slettes?](#user-content-faq55)
* [(56) Kan der tilføjes understøttelse af JMAP?](#user-content-faq56)
-* [~~(57) Kan HTML anvendes i signaturer?~~](#user-content-faq57)
+* [(57) Kan HTML benyttes i signaturer?](#user-content-faq57)
* [(58) Hvad betyder et åbent/lukket e-mail ikon?](#user-content-faq58)
* [(59) Kan originalbeskeder åbnes i browseren?](#user-content-faq59)
* [(60) Vidste du, at...?](#user-content-faq60)
@@ -225,7 +225,7 @@ Designet er baseret på mange debatter, og er du interesseret, kan du også deba
* [(105) Hvordan fungere indstillingen roam-som-på-hjemadressen?](#user-content-faq105)
* [(106) Hvilke launchere kan vise et badge-tal for antallet af ulæste beskeder?](#user-content-faq106)
* [(107) Hvordan anvendes farvede stjerner?](#user-content-faq107)
-* [(108) Kan der tilføjes permanent slettede beskeder fra enhver mappe?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Hvorfor er 'vælg konto' kun tilgængelig i officielle versioner?~~](#user-content-faq109)
* [(110) Hvorfor er (nogle) beskeder tomme og/eller vedhæftninger ødelagte?](#user-content-faq110)
* [(111) Er OAuth understøttet?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operationer behandles kun, såfremt en forbindelse til e-mailserveren findes, el
Du bør forsøge at løse dette ved at kontakte din udbyder eller ved at få et gyldigt sikkerhedscertifikat, da ugyldige sikkerhedscertifikater er usikre og tillader [mand-i-midten-angreb](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Er penge en hindring, kan du få gratis sikkerhedscertifikater fra [Let's Encrypt](https://letsencrypt.org).
-Alternativt kan du acceptere fingeraftrykket vist under fejlmeddelelsen, hvis du opsætter kontoen og/eller identiteten i opsætningstrin 1 og 2 (dette er ikke muligt, når du benytter hurtigopsætningsguiden). Bemærk, at du bør sikre dig, at den anvendte Internetforbindelse er sikker.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Bemærk, at ældre Android-versioner muligvis ikke genkender nyere certificeringsmyndigheder såsom Let’s Encrypt, hvorfor forbindelser kan blive betragtet som usikre, se også [hér](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Visse e-mailservere afslutter også ikke-aktive forbindelser for tidligt, selvom [standarden](https://tools.ietf.org/html/rfc2177) dikterer, at en ikke-aktiv forbindelse bør holdes åben i 29 minutter. I sådanne tilfælde vil du måske kun synkronisere periodisk, f.eks. hver time, i stedet for kontinuerligt. Bemærk, at hyppig polling (udover hvert ca. 30.-60. min) antageligt vil forbruge mere strøm end kontinuerlig synkronisering, da serverforbindelsesoprettelsen samt lokal-/fjernbeskeds matchning kræver ressourcer.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+Det er [på visse enheder](https://dontkillmyapp.com/) nødvendigt at *deaktivere* batterioptimering (opsætningstrin 4) for at holde e-mailserverforbinndelser åbne. Faktisk kan aktiv batterioptimering resultere i ekstra strømforbrug på alle enheder, selvom det lyder selvmodsigende!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Kan HTML benyttes i signaturer?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Ja, [HTML](https://en.wikipedia.org/wiki/HTML) kan benyttes. I signaturredigeringsværktøjet kan du via trepriksmenuen skifte til HTML-tilstand.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Bemærk, at skifter du tilbage til teksredigeringsværktøjet, vil alt HTML måske fremstå korrekt, da Android-teksredigeringsværktøjet ikke kan håndtere alt HTML. Tilsvarende, hvis du bruger tekstredigerinsværktøjet, kan HTML blive ændret på uventede måder.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+Ønsker su at bruge præformateret tekst, såsom [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), bør du ombryde teksten i et *præelement* således:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -1739,16 +1749,16 @@ Note that disabling an account will hide the account and all associated folders
You can automatically send commands with for example [Tasker](https://tasker.joaoapps.com/userguide/en/intents.html):
```
-New task: Something recognizable
-Action Category: Misc/Send Intent
-Action: eu.faircode.email.ENABLE
-Target: Service
+Ny opgave: En genkendelig
+Handlingskategori: Div./Send-
+hensigtshandling: eu.faircode.email.ENABLE
+Mål: Tjeneste
```
To enable/disable an account with the name *Gmail*:
```
-Extras: account:Gmail
+Ekstra: konto:Gmail
```
Account names are case sensitive.
@@ -1873,9 +1883,9 @@ Note that Yahoo, AOL, and Sky do not support standard push messages. The Yahoo e
Push messages require [IMAP IDLE](https://en.wikipedia.org/wiki/IMAP_IDLE) and the Yahoo email server does not report IDLE as capability:
```
-Y1 CAPABILITY
-* CAPABILITY IMAP4rev1 ID MOVE NAMESPACE XYMHIGHESTMODSEQ UIDPLUS LITERAL+ CHILDREN X-MSG-EXT UNSELECT OBJECTID
-Y1 OK CAPABILITY completed
+Y1-EVNE
+* MULIGHED FOR IMAP4rev1 ID FLYT NAVNEOMRÅDE XYMHIGHESTMODSEQ UIDPLUS LITERAL+ CHILDREN X-MSG-EXT AFMARKÉR OBJEKTID
+Y1 OK MULIGHED fuldført
```
@@ -2213,19 +2223,21 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
-* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
-* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
+* Sørg for, at Play Butik-appen er opdateret, [tjek hér](https://support.google.com/googleplay/answer/1050566?hl=en)
+* Åbn Play Butik-appen, og vent mindst ét minut for at give den tid til at synkronisere med Google-serverne
+* Åbn FairEmail og gå til Pro-funktionssiden for at lade FairEmail tjekke købene
You can also try to clear the cache of the Play store app via the Android apps settings. Restarting the device might be necessary to let the Play store recognize the purchase correctly.
Note that:
-* Purchases are stored in the Google cloud and cannot get lost
-* There is no time limit on purchases, so they cannot expire
-* Google does not expose details (name, e-mail, etc) about buyers to developers
-* An app like FairEmail cannot select which Google account to use
-* It may take a while until the Play store app has synchronized a purchase to another device
-* Play Store purchases cannot be used without the Play Store, which is also not allowed by Play Store rules
+* Ser du *VARE ALLEREDE KØBT*, skal Play Butik-appen sandsynligvis opdateres, [tjek hér](https://support.google.com/googleplay/answer/1050566?hl=en)
+* Køb gemmes i Google-skyen og kan ikke gå tabt
+* Der er ingen tidsbegrænsning på køb, hvorfor de aldrig udløber
+* Google afslører ikke oplysninger (navn, e-mail mv.) om købere til udviklere
+* En app såsom FairEmail kan ikke vælge, hvilken Google-konto, der skal benyttes
+* Der kan gå et stykke tid, før Play Butik-appen har synkroniseret et køb til en anden enhed
+* Play Butik-køb kan ikke anvendes uden Play Butik, hvilket heller ikke er tilladt jf. Play Butik-reglerne
If you cannot solve the problem with the purchase, you will have to contact Google about it.
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Mener du, at dette er tilstrækkeligt, du kan aktivere notifikationsindstillingen *Send kun notifikationer med beskedforhåndsvisning til wearables*, og fungerer dette ikke, du kan prøve at aktivere notifikationsindstillingen *Vis kun notifikationer med forhåndsvisningstekst*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2477,7 +2489,7 @@ The error *User is authenticated but not connected* might occur if:
The shared mailbox alias will mostly be the email address of the shared account, like this:
```
-you@example.com\shared@example.com
+dig@eksempel.dk\delt@eksempel.dk
```
Note that it should be a backslash and not a forward slash.
diff --git a/docs/FAQ-de-rAT.md b/docs/FAQ-de-rAT.md
index b1ecdeb69d..50918b8021 100644
--- a/docs/FAQ-de-rAT.md
+++ b/docs/FAQ-de-rAT.md
@@ -75,7 +75,7 @@ Verwandte Fragen:
* ~~Ein [Bug in AndroidX](https://issuetracker.google.com/issues/64729576) macht es schwer, den Schnellscroller zu fassen. Ein Workaround wurde hinzugefügt.~~
* ~~Die Verschlüsselung mit YubiKey führt zu einer Endlosschleife. Dies scheint durch einen [Fehler in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507) verursacht zu werden.~~
* Der Bildlauf zu einer intern verknüpften Stelle in Originalnachrichten funktioniert nicht. Dies kann nicht behoben werden, da die Original-Nachrichten-Ansicht in einer Scroll-Ansicht enthalten ist.
-* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3” und „Mi Band 3” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
+* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3”, „Mi Band 3” und „Xiaomi Amazfit BIP” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
* Ein [Fehler in Android 6.0](https://issuetracker.google.com/issues/37068143) verursacht einen Absturz mit * … Ungültiger Offset: ... Der gültige Bereich ist …* wenn Text ausgewählt ist und außerhalb des ausgewählten Textes angetippt wird. Dieser Fehler wurde in Android 6.0.1 behoben.
* Interne (Anker-)Links funktionieren nicht, da die Originalnachrichten in einer eingebetteten Web-Ansicht in einer scrollenden Ansicht (der Konversationsliste) angezeigt werden. Dies ist eine Einschränkung von Android, die nicht behoben oder umgangen werden kann.
@@ -175,7 +175,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [~~(54) Wie benutze ich ein Namensraumpräfix?~~](#user-content-faq54)
* [(55) Wie kann ich alle Nachrichten als gelesen markieren, verschieben oder löschen?](#user-content-faq55)
* [(56) Können Sie Unterstützung für JMAP hinzufügen?](#user-content-faq56)
-* [~~(57) Kann ich HTML in Signaturen verwenden?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) Was bedeutet ein geöffnetes/geschlossenes E-Mail-Symbol?](#user-content-faq58)
* [(59) Können Original-Nachrichten im Browser geöffnet werden?](#user-content-faq59)
* [(60) Wussten Sie …?](#user-content-faq60)
@@ -225,7 +225,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [(105) Wie funktioniert die »Roaming wie zu Hause«-Option?](#user-content-faq105)
* [(106) Welche Launcher können die Anzahl der ungelesenen Nachrichten als Plakette anzeigen?](#user-content-faq106)
* [(107) Wie verwende ich farbige Sterne?](#user-content-faq107)
-* [(108) Kann man Nachrichten aus beliebigen Ordnern dauerhaft löschen?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Warum ist »Konto auswählen« nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
* [(110) Warum sind (einige) Nachrichten leer und/oder Anhänge beschädigt?](#user-content-faq110)
* [(111) Wird OAuth unterstützt?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operationen werden nur bearbeitet, wenn eine Verbindung zum E-Mail-Server besteh
Kontaktieren Sie Ihren Provider, um dieses Problem zu beheben oder besorgen Sie sich ein gültiges Sicherheitszertifikat, da ungültige und dadurch unsichere Sicherheitszertifikate [Man-in-the-Middle-Angriffe](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) ermöglichen. Falls Sie die Kosten hierfür scheuen, dann können Sie kostenlose Sicherheitszertifikate von [Let's Encrypt](https://letsencrypt.org) beziehen.
-Alternativ Sie können den unten angezeigten Fingerabdruck der Fehlermeldung akzeptieren, wenn Sie das Konto und/oder die Identität in Schritt 1 und 2 einrichten (dies ist nicht möglich, wenn Sie den Schnelleinstellungsassistenten verwenden). Beachten Sie, dass Sie sicherstellen sollten, dass die von Ihnen verwendete Internetverbindung sicher ist.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Beachten Sie, dass ältere Android-Versionen neuere Zertifizierungsbehörden wie Let’s Encrypt möglicherweise nicht akzeptieren, wodurch Internetverbindungen als unsicher eingestuft werden können, siehe auch [hier](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Sofern das für Sie ausreichend ist, können Sie die Benachrichtigungsoption *Nur Benachrichtigungen mit einer Nachrichtenvorschau an Wearables senden* aktivieren, und falls dies nicht funktioniert, versuchen Sie die Benachrichtigungsoption *Benachrichtigungen nur mit einem Vorschautext anzeigen*. Beachten Sie, dass dies auch für Wearables gilt, die keinen Vorschautext anzeigen, selbst wenn die Android Wear App angibt, dass die Benachrichtigung gesendet (überbrückt) wurde.
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. Das bedeutet, dass alle Funktionen auch in der F-Droid-Version verfügbar sind, mit Ausnahme der Verwendung des Assistenten zur schnellen Einrichtung von Google Mail, da Google nur eine Signatur erlaubt (und zulässt). Für alle anderen E-Mail-Anbieter ist der OAuth-Zugang nur in Play-Store-Versionen und Github-Versionen verfügbar, da E-Mail-Anbieter nur offiziellen Builds die Nutzung von OAuth erlaubt haben.
+The F-Droid version is built from the same source code, but signed differently. Das bedeutet, dass alle Funktionen auch in der F-Droid-Version verfügbar sind, mit Ausnahme der Verwendung des Assistenten zur schnellen Einrichtung von Google Mail, da Google nur eine Signatur erlaubt (und zulässt). For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-de-rDE.md b/docs/FAQ-de-rDE.md
index b1ecdeb69d..50918b8021 100644
--- a/docs/FAQ-de-rDE.md
+++ b/docs/FAQ-de-rDE.md
@@ -75,7 +75,7 @@ Verwandte Fragen:
* ~~Ein [Bug in AndroidX](https://issuetracker.google.com/issues/64729576) macht es schwer, den Schnellscroller zu fassen. Ein Workaround wurde hinzugefügt.~~
* ~~Die Verschlüsselung mit YubiKey führt zu einer Endlosschleife. Dies scheint durch einen [Fehler in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507) verursacht zu werden.~~
* Der Bildlauf zu einer intern verknüpften Stelle in Originalnachrichten funktioniert nicht. Dies kann nicht behoben werden, da die Original-Nachrichten-Ansicht in einer Scroll-Ansicht enthalten ist.
-* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3” und „Mi Band 3” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
+* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3”, „Mi Band 3” und „Xiaomi Amazfit BIP” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
* Ein [Fehler in Android 6.0](https://issuetracker.google.com/issues/37068143) verursacht einen Absturz mit * … Ungültiger Offset: ... Der gültige Bereich ist …* wenn Text ausgewählt ist und außerhalb des ausgewählten Textes angetippt wird. Dieser Fehler wurde in Android 6.0.1 behoben.
* Interne (Anker-)Links funktionieren nicht, da die Originalnachrichten in einer eingebetteten Web-Ansicht in einer scrollenden Ansicht (der Konversationsliste) angezeigt werden. Dies ist eine Einschränkung von Android, die nicht behoben oder umgangen werden kann.
@@ -175,7 +175,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [~~(54) Wie benutze ich ein Namensraumpräfix?~~](#user-content-faq54)
* [(55) Wie kann ich alle Nachrichten als gelesen markieren, verschieben oder löschen?](#user-content-faq55)
* [(56) Können Sie Unterstützung für JMAP hinzufügen?](#user-content-faq56)
-* [~~(57) Kann ich HTML in Signaturen verwenden?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) Was bedeutet ein geöffnetes/geschlossenes E-Mail-Symbol?](#user-content-faq58)
* [(59) Können Original-Nachrichten im Browser geöffnet werden?](#user-content-faq59)
* [(60) Wussten Sie …?](#user-content-faq60)
@@ -225,7 +225,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [(105) Wie funktioniert die »Roaming wie zu Hause«-Option?](#user-content-faq105)
* [(106) Welche Launcher können die Anzahl der ungelesenen Nachrichten als Plakette anzeigen?](#user-content-faq106)
* [(107) Wie verwende ich farbige Sterne?](#user-content-faq107)
-* [(108) Kann man Nachrichten aus beliebigen Ordnern dauerhaft löschen?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Warum ist »Konto auswählen« nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
* [(110) Warum sind (einige) Nachrichten leer und/oder Anhänge beschädigt?](#user-content-faq110)
* [(111) Wird OAuth unterstützt?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operationen werden nur bearbeitet, wenn eine Verbindung zum E-Mail-Server besteh
Kontaktieren Sie Ihren Provider, um dieses Problem zu beheben oder besorgen Sie sich ein gültiges Sicherheitszertifikat, da ungültige und dadurch unsichere Sicherheitszertifikate [Man-in-the-Middle-Angriffe](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) ermöglichen. Falls Sie die Kosten hierfür scheuen, dann können Sie kostenlose Sicherheitszertifikate von [Let's Encrypt](https://letsencrypt.org) beziehen.
-Alternativ Sie können den unten angezeigten Fingerabdruck der Fehlermeldung akzeptieren, wenn Sie das Konto und/oder die Identität in Schritt 1 und 2 einrichten (dies ist nicht möglich, wenn Sie den Schnelleinstellungsassistenten verwenden). Beachten Sie, dass Sie sicherstellen sollten, dass die von Ihnen verwendete Internetverbindung sicher ist.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Beachten Sie, dass ältere Android-Versionen neuere Zertifizierungsbehörden wie Let’s Encrypt möglicherweise nicht akzeptieren, wodurch Internetverbindungen als unsicher eingestuft werden können, siehe auch [hier](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Sofern das für Sie ausreichend ist, können Sie die Benachrichtigungsoption *Nur Benachrichtigungen mit einer Nachrichtenvorschau an Wearables senden* aktivieren, und falls dies nicht funktioniert, versuchen Sie die Benachrichtigungsoption *Benachrichtigungen nur mit einem Vorschautext anzeigen*. Beachten Sie, dass dies auch für Wearables gilt, die keinen Vorschautext anzeigen, selbst wenn die Android Wear App angibt, dass die Benachrichtigung gesendet (überbrückt) wurde.
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. Das bedeutet, dass alle Funktionen auch in der F-Droid-Version verfügbar sind, mit Ausnahme der Verwendung des Assistenten zur schnellen Einrichtung von Google Mail, da Google nur eine Signatur erlaubt (und zulässt). Für alle anderen E-Mail-Anbieter ist der OAuth-Zugang nur in Play-Store-Versionen und Github-Versionen verfügbar, da E-Mail-Anbieter nur offiziellen Builds die Nutzung von OAuth erlaubt haben.
+The F-Droid version is built from the same source code, but signed differently. Das bedeutet, dass alle Funktionen auch in der F-Droid-Version verfügbar sind, mit Ausnahme der Verwendung des Assistenten zur schnellen Einrichtung von Google Mail, da Google nur eine Signatur erlaubt (und zulässt). For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-de-rLI.md b/docs/FAQ-de-rLI.md
index b1ecdeb69d..50918b8021 100644
--- a/docs/FAQ-de-rLI.md
+++ b/docs/FAQ-de-rLI.md
@@ -75,7 +75,7 @@ Verwandte Fragen:
* ~~Ein [Bug in AndroidX](https://issuetracker.google.com/issues/64729576) macht es schwer, den Schnellscroller zu fassen. Ein Workaround wurde hinzugefügt.~~
* ~~Die Verschlüsselung mit YubiKey führt zu einer Endlosschleife. Dies scheint durch einen [Fehler in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507) verursacht zu werden.~~
* Der Bildlauf zu einer intern verknüpften Stelle in Originalnachrichten funktioniert nicht. Dies kann nicht behoben werden, da die Original-Nachrichten-Ansicht in einer Scroll-Ansicht enthalten ist.
-* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3” und „Mi Band 3” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
+* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3”, „Mi Band 3” und „Xiaomi Amazfit BIP” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
* Ein [Fehler in Android 6.0](https://issuetracker.google.com/issues/37068143) verursacht einen Absturz mit * … Ungültiger Offset: ... Der gültige Bereich ist …* wenn Text ausgewählt ist und außerhalb des ausgewählten Textes angetippt wird. Dieser Fehler wurde in Android 6.0.1 behoben.
* Interne (Anker-)Links funktionieren nicht, da die Originalnachrichten in einer eingebetteten Web-Ansicht in einer scrollenden Ansicht (der Konversationsliste) angezeigt werden. Dies ist eine Einschränkung von Android, die nicht behoben oder umgangen werden kann.
@@ -175,7 +175,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [~~(54) Wie benutze ich ein Namensraumpräfix?~~](#user-content-faq54)
* [(55) Wie kann ich alle Nachrichten als gelesen markieren, verschieben oder löschen?](#user-content-faq55)
* [(56) Können Sie Unterstützung für JMAP hinzufügen?](#user-content-faq56)
-* [~~(57) Kann ich HTML in Signaturen verwenden?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) Was bedeutet ein geöffnetes/geschlossenes E-Mail-Symbol?](#user-content-faq58)
* [(59) Können Original-Nachrichten im Browser geöffnet werden?](#user-content-faq59)
* [(60) Wussten Sie …?](#user-content-faq60)
@@ -225,7 +225,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [(105) Wie funktioniert die »Roaming wie zu Hause«-Option?](#user-content-faq105)
* [(106) Welche Launcher können die Anzahl der ungelesenen Nachrichten als Plakette anzeigen?](#user-content-faq106)
* [(107) Wie verwende ich farbige Sterne?](#user-content-faq107)
-* [(108) Kann man Nachrichten aus beliebigen Ordnern dauerhaft löschen?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Warum ist »Konto auswählen« nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
* [(110) Warum sind (einige) Nachrichten leer und/oder Anhänge beschädigt?](#user-content-faq110)
* [(111) Wird OAuth unterstützt?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operationen werden nur bearbeitet, wenn eine Verbindung zum E-Mail-Server besteh
Kontaktieren Sie Ihren Provider, um dieses Problem zu beheben oder besorgen Sie sich ein gültiges Sicherheitszertifikat, da ungültige und dadurch unsichere Sicherheitszertifikate [Man-in-the-Middle-Angriffe](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) ermöglichen. Falls Sie die Kosten hierfür scheuen, dann können Sie kostenlose Sicherheitszertifikate von [Let's Encrypt](https://letsencrypt.org) beziehen.
-Alternativ Sie können den unten angezeigten Fingerabdruck der Fehlermeldung akzeptieren, wenn Sie das Konto und/oder die Identität in Schritt 1 und 2 einrichten (dies ist nicht möglich, wenn Sie den Schnelleinstellungsassistenten verwenden). Beachten Sie, dass Sie sicherstellen sollten, dass die von Ihnen verwendete Internetverbindung sicher ist.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Beachten Sie, dass ältere Android-Versionen neuere Zertifizierungsbehörden wie Let’s Encrypt möglicherweise nicht akzeptieren, wodurch Internetverbindungen als unsicher eingestuft werden können, siehe auch [hier](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Sofern das für Sie ausreichend ist, können Sie die Benachrichtigungsoption *Nur Benachrichtigungen mit einer Nachrichtenvorschau an Wearables senden* aktivieren, und falls dies nicht funktioniert, versuchen Sie die Benachrichtigungsoption *Benachrichtigungen nur mit einem Vorschautext anzeigen*. Beachten Sie, dass dies auch für Wearables gilt, die keinen Vorschautext anzeigen, selbst wenn die Android Wear App angibt, dass die Benachrichtigung gesendet (überbrückt) wurde.
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. Das bedeutet, dass alle Funktionen auch in der F-Droid-Version verfügbar sind, mit Ausnahme der Verwendung des Assistenten zur schnellen Einrichtung von Google Mail, da Google nur eine Signatur erlaubt (und zulässt). Für alle anderen E-Mail-Anbieter ist der OAuth-Zugang nur in Play-Store-Versionen und Github-Versionen verfügbar, da E-Mail-Anbieter nur offiziellen Builds die Nutzung von OAuth erlaubt haben.
+The F-Droid version is built from the same source code, but signed differently. Das bedeutet, dass alle Funktionen auch in der F-Droid-Version verfügbar sind, mit Ausnahme der Verwendung des Assistenten zur schnellen Einrichtung von Google Mail, da Google nur eine Signatur erlaubt (und zulässt). For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-el-rGR.md b/docs/FAQ-el-rGR.md
index 7a32f0f1e1..3336a2bdca 100644
--- a/docs/FAQ-el-rGR.md
+++ b/docs/FAQ-el-rGR.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-en-rGB.md b/docs/FAQ-en-rGB.md
index 07324c32cb..465ed803c3 100644
--- a/docs/FAQ-en-rGB.md
+++ b/docs/FAQ-en-rGB.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-es-rES.md b/docs/FAQ-es-rES.md
index 447b66511b..31e5153d9d 100644
--- a/docs/FAQ-es-rES.md
+++ b/docs/FAQ-es-rES.md
@@ -75,7 +75,7 @@ Preguntas relacionadas:
* ~~Un [error en AndroidX](https://issuetracker.google.com/issues/64729576) hace difícil agarrar el desplazamiento rápido. Una solución fue añadida.~~
* ~~El cifrado con YubiKey resulta en un bucle infinito. Esto parece ser causado por un [error en OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Desplazar a una ubicación vinculada internamente en mensajes originales no funciona. Esto no se puede arreglar porque la vista original del mensaje está contenida en una vista de desplazamiento.
-* La vista previa del texto de los mensajes no aparece (siempre) en los relojes de Samsung porque [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) parece ser ignorado. El texto de vista previa de los mensajes se muestra correctamente en Pebble 2, Fitbit Charge 3 y Mi band 3. Ver también [estas Preguntas Frecuentes](#user-content-faq126).
+* La vista previa del texto de los mensajes no aparece (siempre) en los relojes de Samsung porque [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) parece ser ignorado. Se sabe que los textos de vista previa de los mensajes se muestran correctamente en los wearables Pebble 2, Fitbit Charge 3, Mi band 3 y Xiaomi Amazfit BIP. Ver también [estas Preguntas Frecuentes](#user-content-faq126).
* Un [error en Android 6.0](https://issuetracker.google.com/issues/37068143) causa un error con *... Offset inválido: ... El rango válido es ...* cuando el texto está seleccionado y se toca fuera del texto seleccionado. Este error ha sido corregido en Android 6.0.1.
* Los enlaces internos (anchor) no funcionarán porque los mensajes originales se muestran en una WebView embebida en una vista de desplazamiento (la lista de conversaciones). Esta es una limitación de Android que no se puede arreglar o eludir.
@@ -175,7 +175,7 @@ El diseño está basado en muchas discusiones y si lo deseas puedes unirte a la
* [~~(54) ¿Cómo uso un prefijo de espacio de nombres?~~](#user-content-faq54)
* [(55) ¿Cómo puedo marcar todos los mensajes como leídos / moverlos o borrarlos?](#user-content-faq55)
* [(56) ¿Puedes añadir soporte para JMAP?](#user-content-faq56)
-* [~~(57) ¿Puedo usar HTML en firmas?~~](#user-content-faq57)
+* [(57) ¿Puedo usar HTML en firmas?](#user-content-faq57)
* [(58) ¿Qué significa un icono de correo electrónico abierto/cerrado?](#user-content-faq58)
* [(59) ¿Pueden abrirse mensajes originales en el navegador?](#user-content-faq59)
* [(60) ¿Sabía que ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ El diseño está basado en muchas discusiones y si lo deseas puedes unirte a la
* [(105) ¿Cómo funciona la opción de roam-como-en-casa?](#user-content-faq105)
* [(106) ¿Qué lanzadores pueden mostrar un contador con el número de mensajes no leídos?](#user-content-faq106)
* [(107) ¿Cómo utilizo estrellas de colores?](#user-content-faq107)
-* [(108) ¿Puedes añadir eliminar mensajes permanentemente desde cualquier carpeta?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) ¿Por qué 'seleccionar cuenta' está disponible sólo en versiones oficiales?~~](#user-content-faq109)
* [(110) ¿Por qué hay (algunos) mensajes vacíos y/o adjuntos corruptos?](#user-content-faq110)
* [(111) ¿Es compatible OAuth?](#user-content-faq111)
@@ -388,7 +388,7 @@ Las operaciones sólo se procesan cuando hay una conexión al servidor de correo
Debería intentar arreglar esto poniéndose en contacto con su proveedor u obteniendo un certificado de seguridad válido porque los certificados de seguridad inválidos no son seguros y permiten [ataques man-in-the-middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Si el dinero es un obstáculo, puede obtener certificados de seguridad gratuitos de [Let’s Encrypt](https://letsencrypt.org).
-Alternativamente, puede aceptar la huella digital mostrada a continuación del mensaje de error si configura la cuenta y/o identidad en los pasos de configuración 1 y 2 (esto no es posible cuando utiliza el asistente de configuración rápido). Tenga en cuenta que debe asegurarse de que la conexión a Internet que está utilizando es segura.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Tenga en cuenta que las versiones antiguas de Android podrían no reconocer las nuevas autoridades de certificación como Let’s Encrypt que causan que las conexiones se consideren inseguras, vea también [aquí](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ La autorización de las cuentas de Gmail configuradas con el asistente rápido d
El error *... La autenticación falló ... Cuenta no encontrada ...* significa que una cuenta de Gmail previamente autorizada fue eliminada del dispositivo.
-Los errores *... La autenticación falló ... Ningún token al actualizar...* significa que el administrador de cuentas de Android no pudo actualizar la autorización de una cuenta de Gmail.
+Los errores *... La autenticación falló ... No token ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
El error *... La autenticación falló ... Credenciales inválidas... error de red...* significa que el administrador de cuentas de Android no pudo actualizar la autorización de una cuenta de Gmail debido a problemas con la conexión a Internet
@@ -1168,9 +1168,9 @@ Es inevitable que sincronizar mensajes use energía de batería porque requiere
Si está comparando el uso de la batería de FairEmail con otro cliente de correo electrónico, por favor asegúrese de que el otro cliente de correo esté configurado de forma similar. Por ejemplo, comparar sincronizar siempre (mensajes push) y la comprobación periódica (poco frecuente) de nuevos mensajes no es una comparación justa.
-Reconectar a un servidor de correo electrónico consumirá energía extra de la batería, por lo que una conexión a internet inestable resultará en un uso adicional de la batería. En este caso puede que quiera sincronizar periódicamente, por ejemplo cada hora, en lugar de continuamente. Tenga en cuenta que sondear con frecuencia (más que cada 30-60 minutos) probablemente usará más energía de batería que sincronizar siempre porque conectarse al servidor y comparar los mensajes locales y remotos son operaciones costosas.
+Reconectar a un servidor de correo electrónico consumirá energía extra de la batería, por lo que una conexión a internet inestable resultará en un uso adicional de la batería. Además, algunos servidores de correo electrónico terminan las conexiones inactivas prematuramente, mientras que [el estándar](https://tools.ietf.org/html/rfc2177) dice que una conexión inactiva debe mantenerse abierta durante 29 minutos. En estos casos puede que desee sincronizar periódicamente, por ejemplo cada hora, en lugar de continuamente. Tenga en cuenta que sondear con frecuencia (más de 30-60 minutos) probablemente usará más energía de batería que sincronizar siempre porque conectarse al servidor y comparar los mensajes locales y remotos son operaciones costosas.
-[En algunos dispositivos](https://dontkillmyapp.com/) es necesario *desactivar* optimizaciones de batería (configuración paso 4) para mantener las conexiones a los servidores de correo electrónico abiertos.
+[En algunos dispositivos](https://dontkillmyapp.com/) es necesario *desactivar* optimizaciones de batería (configuración paso 4) para mantener las conexiones a los servidores de correo electrónico abiertos. De hecho, dejar habilitadas las optimizaciones de la batería puede resultar en un uso extra de la batería para todos los dispositivos, ¡aunque esto suene contradictorio!
La mayor parte del uso de la batería, sin considerar la visualización de mensajes, se debe a la sincronización (recepción y envío) de mensajes. Por lo tanto, para reducir el uso de la batería, establezca el número de días para sincronizar el mensaje a un valor más bajo, especialmente si hay muchos mensajes recientes en una carpeta. Mantenga presionado el nombre de carpeta en la lista de carpetas y seleccione *Editar propiedades* para acceder a esta configuración.
@@ -1402,13 +1402,23 @@ Casi no hay proveedores que ofrezcan el protocolo [JMAP](https://jmap.io/), por
-**(57) ~~¿Puedo usar HTML en firmas?~~**
+**(57) ¿Puedo usar HTML en firmas?**
-~~Sí, puede usar HTML en firmas si pega texto formateado en el campo de firma o usa el menú *Editar como HTML* para introducir HTML manualmente.~~
+Sí, puede usar [HTML](https://en.wikipedia.org/wiki/HTML). En el editor de firmas se puede cambiar al modo HTML a través del menú de tres puntos.
-~~Tenga en cuenta que incluir enlaces e imágenes en los mensajes aumentará la probabilidad de que un mensaje sea visto como spam,~~ ~~especialmente cuando envía un mensaje a alguien por primera vez.~~
+Tenga en cuenta que si vuelve al editor de texto no todo el HTML puede ser renderizado tal como es porque el editor de texto de Android no es capaz de renderizar todo el HTML. De la misma manera, si utiliza el editor de texto, el HTML podría ser alterado de maneras inesperadas.
-~~Vea [aquí](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) para ver qué etiquetas HTML son soportadas.~~
+Si desea utilizar texto preformateado, como [arte ASCII](https://en.wikipedia.org/wiki/ASCII_art), debe envolver el texto en un elemento *pre*, así:
+
+```
+
+ |\_/|
+ / @ @ \
+( > o < )
+ `>>x<<́
+ / O \
+
+```
@@ -2213,13 +2223,15 @@ Google gestiona todas las compras, por lo que como desarrollador tengo poco cont
* Asegúrese de tener una conexión activa a internet
* Asegúrese de que ha iniciado sesión con la cuenta de Google correcta y de que no hay ningún problema con su cuenta de Google
* Asegúrese de instalar FairEmail a través de la cuenta de Google correcta si configuró varias cuentas de Google en su dispositivo
+* Asegúrese de que la aplicación Play Store está actualizada, por favor [ver aquí](https://support.google.com/googleplay/answer/1050566?hl=en)
* Abra la aplicación Play Store y espere al menos un minuto para darle tiempo para sincronizar con los servidores de Google
-* Abrir FairEmail y navegar a la pantalla de características pro para permitir que FairEmail compruebe las compras
+* Abra FairEmail y navegue a la pantalla de características pro para permitir que FairEmail compruebe las compras
También puede intentar limpiar la caché de la aplicación Play Store a través de los ajustes de las aplicaciones de Android. Reiniciar el dispositivo puede ser necesario para que la Play Store reconozca la compra correctamente.
Tenga en cuenta que:
+* Si obtiene *ITEM_ALREADY_OWNED*, la aplicación Play Store probablemente necesite ser actualizada, por favor [vea aquí](https://support.google.com/googleplay/answer/1050566?hl=en)
* Las compras se almacenan en la nube de Google y no se pueden perder
* No hay límite de tiempo en las compras, por lo que no pueden expirar
* Google no expone detalles (nombre, correo electrónico, etc.) sobre los compradores a los desarrolladores
@@ -2317,7 +2329,7 @@ Justo después del primer paso se notificarán nuevos mensajes. Sin embargo, só
Dado que no hay garantía de que un texto del mensaje se obtenga siempre después de un encabezado del mensaje, no es posible garantizar que una notificación de nuevo mensaje con un texto de vista previa se enviará siempre a un wearable.
-Si usted piensa que esto es suficientemente bueno, puede activar la opción de notificación *Sólo enviar notificaciones con vista previa de mensaje a dispositivos wearables* y si esto no funciona, puede intentar activar la opción de notificación *Mostrar notificaciones sólo con un texto de vista previa*.
+Si usted piensa que esto es suficientemente bueno, puede activar la opción de notificación *Sólo enviar notificaciones con vista previa de mensaje a dispositivos wearables* y si esto no funciona, puede intentar activar la opción de notificación *Mostrar notificaciones sólo con un texto de vista previa*. Tenga en cuenta que esto se aplica también a los wearables que no muestran un texto de vista previa, incluso cuando la aplicación Android Wear dice que la notificación ha sido enviada (bridged).
Si desea que se le envíe el mensaje completo a su wearable, puede activar la opción de notificación *Vista previa de todo el texto*. Tenga en cuenta que se sabe que algunos wearables fallan con esta opción habilitada.
@@ -2592,7 +2604,7 @@ Probablemente llegó aquí porque está usando una versión de terceros de FairE
F-Droid compila de forma irregular, lo que puede ser problemático cuando hay una actualización importante. Por lo tanto se le aconseja cambiar a la versión de GitHub.
-La versión de F-Droid se compila con el mismo código fuente, pero se firma de forma diferente. Esto significa que todas las características están disponibles también en la versión de F-Droid excepto para usar el asistente de configuración rápida de Gmail porque Google aprueba (y permite) una sola firma de la aplicación. Para todos los demás proveedores de correo electrónico, el acceso OAuth sólo está disponible en las versiones de Play Store y en las versiones de Github, dado que los proveedores de correo electrónico sólo han permitido que las compilaciones oficiales usen OAuth.
+La versión de F-Droid se compila con el mismo código fuente, pero se firma de forma diferente. Esto significa que todas las características están disponibles también en la versión de F-Droid excepto para usar el asistente de configuración rápida de Gmail porque Google aprueba (y permite) una sola firma de la aplicación. Para todos los demás proveedores de correo electrónico, el acceso OAuth sólo está disponible en las versiones de Play Store y en las versiones de Github, dado que los proveedores de correo electrónico sólo permiten el uso de OAuth para versiones oficiales.
Tenga en cuenta que primero tendrá que desinstalar la compilación de F-Droid antes de instalar una versión de GitHub porque Android se niega a instalar la misma aplicación con una firma diferente por razones de seguridad.
diff --git a/docs/FAQ-eu-rES.md b/docs/FAQ-eu-rES.md
index 65597be9f6..d689a850cc 100644
--- a/docs/FAQ-eu-rES.md
+++ b/docs/FAQ-eu-rES.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-fa-rIR.md b/docs/FAQ-fa-rIR.md
index a85a031433..936a53c235 100644
--- a/docs/FAQ-fa-rIR.md
+++ b/docs/FAQ-fa-rIR.md
@@ -75,7 +75,7 @@ Please see [here](#user-content-faq22) for common error messages and solutions.
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-fi-rFI.md b/docs/FAQ-fi-rFI.md
index 51937d4371..8e721ae77d 100644
--- a/docs/FAQ-fi-rFI.md
+++ b/docs/FAQ-fi-rFI.md
@@ -20,7 +20,7 @@ Jos nopea asennus epäonnistuu, sinun on määritettävä tili manuaalisesti (s
Hakemalla *IMAP* ja palveluntarjoajan nimi riittää useimmiten oikean dokumentaation löytämiseen.
-Joissakin tapauksissa sinun on otettava käyttöön ulkoinen pääsy tilillesi ja/tai käytettävä erityistä (sovelluksen) salasanaa, esimerkiksi silloin, kun kaksivaiheinen todennus on käytössä.
+Joissakin tapauksissa sinun on otettava käyttöön ulkoinen pääsy tilillesi ja/tai käytettävä erityistä (sovelluksen) salasanaa, kuten silloin, kun kaksivaiheinen tunnistautuminen on käytössä.
Valtuutukseen:
@@ -44,9 +44,9 @@ Aiheeseen liittyvät kysymykset:
## Kuinka ...?
* Vaihda tilin nimi: Asetukset, vaihe 1, Muokkaa, napauta tiliä
-* Change the swipe left/right target: Setup, Behavior, Set swipe actions
-* Change password: Setup, step 1, Manage, tap account, change password
-* Set a signature: Setup, step 2, Manage, tap identity, Edit signature.
+* Vaihda vasemmalle/oikealle pyyhkäisyn kohdetta: Asetukset, Toiminnot, Aseta pyyhkäisytoiminnot
+* Vaihda salasana: Asetukset, kohta 1, Muokkaa, napauta tiliä, vaihda salasana
+* Aseta allekirjoitus: Asetukset, kohta 2, Muokkaa, napauta identiteettiä, Muokkaa allekirjoitusta.
* Add CC and BCC addresses: tap the people's icon at the end of the subject
* Go to the next/previous message on archive/delete: in the behavior settings disable *Automatically close conversations* and select *Go to next/previous conversation* for *On closing a conversation*
* Add a folder to the unified inbox: long press the folder in the folder list and tick *Show in unified inbox*
@@ -75,7 +75,7 @@ Aiheeseen liittyvät kysymykset:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-fr-rCA.md b/docs/FAQ-fr-rCA.md
index 5005561396..d3489e7afd 100644
--- a/docs/FAQ-fr-rCA.md
+++ b/docs/FAQ-fr-rCA.md
@@ -75,7 +75,7 @@ Questions connexes :
* ~~Un [bug dans AndroidX](https://issuetracker.google.com/issues/64729576) rend difficile le défilement rapide. Une solution de contournement a été ajoutée.~~
* ~~Le chiffrement avec YubiKey se traduit par une boucle infinie. Cela semble être causé par un [bug dans OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Le défilement vers un emplacement lié en interne dans les messages originaux ne fonctionne pas. Ceci ne peut pas être corrigé car la vue du message d'origine est contenue dans une vue déroulante.
-* Un aperçu d'un message texte n'apparaît pas (toujours) sur les montres Samsung car [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) semble être ignoré. Les textes de prévisualisation du message sont connus pour être affichés correctement sur Pebble 2, Fitbit Charge 3 et Mi band 3. Voir aussi [cette FAQ](#user-content-faq126).
+* Un aperçu d'un message texte n'apparaît pas (toujours) sur les montres Samsung car [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) semble être ignoré. Les textes de prévisualisation des messages sont censés être affichés correctement sur les objets connectés Pebble 2, Fitbit Charge 3, Mi band 3 et Xiaomi Amazfit BIP. Voir aussi [cette FAQ](#user-content-faq126).
* Un [bug sur Android 6.0](https://issuetracker.google.com/issues/37068143) provoque un plantage *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. Ce bogue a été corrigé dans Android 6.0.1.
* Les liens internes (ancrés) ne fonctionneront pas parce que les messages originaux sont affichés dans une WebView intégrée dans une vue défilante (la liste des conversations). Il s'agit d'une limitation Android qui ne peut être ni corrigée ni contournée.
@@ -175,7 +175,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
* [~~(54) Comment utiliser un préfixe d'espace de noms ?~~](#user-content-faq54)
* [(55) Comment puis-je marquer tous les messages comme lus / déplacer ou supprimer tous les messages ?](#user-content-faq55)
* [(56) Pouvez-vous ajouter un support pour JMAP?](#user-content-faq56)
-* [~~(57) Puis-je utiliser du HTML dans les signatures ?~~](#user-content-faq57)
+* [(57) Puis-je utiliser HTML dans les signatures ?](#user-content-faq57)
* [(58) Que signifie une icône de courriel ouverte/fermée?](#user-content-faq58)
* [(59) Peut-on ouvrir des messages originaux dans le navigateur?](#user-content-faq59)
* [(60) Saviez-vous ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
* [(105) Comment fonctionne l’option itinérance à domicile?](#user-content-faq105)
* [(106) Quels lanceurs peuvent afficher un nombre de badges avec le nombre de messages non lus ?](#user-content-faq106)
* [(107) Comment utiliser les étoiles colorées ?](#user-content-faq107)
-* [(108) Pouvez-vous ajouter des messages de façon permanente à partir de n'importe quel dossier ?](#user-content-faq108)
+* [~~(108) Pouvez-vous ajouter la suppression des messages de façon définitive à partir de n'importe quel dossier ?~~](#user-content-faq108)
* [~~(109) Pourquoi 'sélectionner le compte' est-il uniquement disponible dans les versions officielles ?~~](#user-content-faq109)
* [(110) Pourquoi (certains) les messages sont-ils vides et/ou les pièces jointes corrompues?](#user-content-faq110)
* [(111) OAuth est-il pris en charge ?](#user-content-faq111)
@@ -388,7 +388,7 @@ Les opérations ne sont traitées que lorsqu'il y a une connexion au serveur de
Vous devriez essayer de résoudre ce problème en contactant votre fournisseur ou en obtenant un certificat de sécurité valide car les certificats de sécurité non valides sont non sécurisés et autorisent [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Si l'argent est un obstacle, vous pouvez obtenir des certificats de sécurité gratuits auprès de [Crypt](https://letsencrypt.org).
-Alternativement, vous pouvez accepter l'empreinte digitale affichée sous le message d'erreur si vous configurez le compte et/ou l'identité lors de l'étape de configuration 1 et 2 (ce n'est pas possible lorsque vous utilisez l'assistant d'installation rapide). Notez que vous devez vous assurer que la connexion Internet que vous utilisez est sûre.
+Vous pouvez également accepter l'empreinte du certificat de serveur non valide comme indiqué sous le message d'erreur en cochant une case à cocher. En cas de compte existant (IMAP, recevoir) et/ou d'identité (SMTP, envoyer) vous aurez besoin de le vérifier/sauvegarder via les étapes 1 et 2 de configuration pour recevoir le message d'erreur. Ceci va "épingler" le certificat du serveur pour éviter les attaques de man-in-the-middle. Notez que vous devez vous assurer que la connexion Internet que vous utilisez est sûre si vous faites cela.
Notez que les anciennes versions d'Android peuvent ne pas reconnaître de nouvelles autorités de certification comme Let's Encrypt qui peuvent considérer les connexions comme non sécurisées, voir aussi [ici](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... Aucun jeton ...* signifie que le gestionnaire de comptes Android n'a pas réussi à actualiser l'autorisation d'un compte Gmail.
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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. De plus, certains serveurs de messagerie terminent prématurément les connexions inactives, tandis que [la norme](https://tools.ietf.org/html/rfc2177) indique qu'une connexion inactive doit rester ouverte pendant 29 minutes. Dans ces cas, vous pouvez synchroniser périodiquement, par exemple chaque heure au lieu de en continu. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Si vous pensez que c'est suffisant, vous pouvez activer l'option de notification *Envoyer uniquement des notifications avec un aperçu de message aux objets connectés* et si cela ne fonctionne pas, vous pouvez essayer d'activer l'option de notification *Afficher les notifications avec un texte de prévisualisation uniquement*. Notez que ceci s'applique aux objets connectés n'affichant pas de texte de prévisualisation non plus, même lorsque l'application Android Wear indique que la notification a été envoyée (pont).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. Ceci signifie que toutes les fonctionnalités sont également disponibles dans la version F-Droid, à l'exception de l'utilisation de l'assistant de configuration rapide Gmail parce que Google a approuvé (et autorisé) une seule signature d'application. Pour tous les autres fournisseurs de messagerie, l'accès OAuth n'est disponible que dans les versions du Play Store et dans les versions de Github, étant donné que les fournisseurs de messagerie n'ont autorisé que les versions officielles à utiliser OAuth.
+The F-Droid version is built from the same source code, but signed differently. Ceci signifie que toutes les fonctionnalités sont également disponibles dans la version F-Droid, à l'exception de l'utilisation de l'assistant de configuration rapide Gmail parce que Google a approuvé (et autorisé) une seule signature d'application. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-fr-rFR.md b/docs/FAQ-fr-rFR.md
index 58f5b09ba4..c09b7a4107 100644
--- a/docs/FAQ-fr-rFR.md
+++ b/docs/FAQ-fr-rFR.md
@@ -75,7 +75,7 @@ Questions connexes :
* ~~Un [bug dans AndroidX](https://issuetracker.google.com/issues/64729576) rend difficile le défilement rapide. Une solution de contournement a été ajoutée.~~
* ~~Le chiffrement avec YubiKey se traduit par une boucle infinie. Cela semble être causé par un [bug dans OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Le défilement vers un emplacement lié en interne dans les messages originaux ne fonctionne pas. Ceci ne peut pas être corrigé car la vue du message d'origine est contenue dans une vue déroulante.
-* Un aperçu d'un message texte n'apparaît pas (toujours) sur les montres Samsung car [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) semble être ignoré. Les textes de prévisualisation du message sont connus pour être affichés correctement sur Pebble 2, Fitbit Charge 3 et Mi band 3. Voir aussi [cette FAQ](#user-content-faq126).
+* Un aperçu d'un message texte n'apparaît pas (toujours) sur les montres Samsung car [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) semble être ignoré. Les textes de prévisualisation des messages sont censés être affichés correctement sur les objets connectés Pebble 2, Fitbit Charge 3, Mi band 3 et Xiaomi Amazfit BIP. Voir aussi [cette FAQ](#user-content-faq126).
* Un [bug sur Android 6.0](https://issuetracker.google.com/issues/37068143) provoque un plantage *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. Ce bogue a été corrigé dans 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). Il s'agit d'une limitation Android qui ne peut pas être réparée ou contournée.
@@ -175,7 +175,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
* [~~(54) Comment utiliser un préfixe d'espace de noms ?~~](#user-content-faq54)
* [(55) Comment puis-je marquer tous les messages comme lus / déplacer ou supprimer tous les messages ?](#user-content-faq55)
* [(56) Pouvez-vous ajouter un support pour JMAP?](#user-content-faq56)
-* [~~(57) Puis-je utiliser du HTML dans les signatures ?~~](#user-content-faq57)
+* [(57) Puis-je utiliser HTML dans les signatures ?](#user-content-faq57)
* [(58) Que signifie une icône de courriel ouverte/fermée?](#user-content-faq58)
* [(59) Peut-on ouvrir des messages originaux dans le navigateur?](#user-content-faq59)
* [(60) Saviez-vous ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
* [(105) Comment fonctionne l’option itinérance à domicile?](#user-content-faq105)
* [(106) Quels lanceurs peuvent afficher un nombre de badges avec le nombre de messages non lus ?](#user-content-faq106)
* [(107) Comment utiliser les étoiles colorées ?](#user-content-faq107)
-* [(108) Pouvez-vous ajouter des messages de façon permanente à partir de n'importe quel dossier ?](#user-content-faq108)
+* [~~(108) Pouvez-vous ajouter la suppression des messages de façon définitive à partir de n'importe quel dossier ?~~](#user-content-faq108)
* [~~(109) Pourquoi 'sélectionner le compte' est-il uniquement disponible dans les versions officielles ?~~](#user-content-faq109)
* [(110) Pourquoi (certains) les messages sont-ils vides et/ou les pièces jointes corrompues?](#user-content-faq110)
* [(111) OAuth est-il pris en charge ?](#user-content-faq111)
@@ -388,7 +388,7 @@ Les opérations ne sont traitées que lorsqu'il y a une connexion au serveur de
Vous devriez essayer de résoudre ce problème en contactant votre fournisseur ou en obtenant un certificat de sécurité valide car les certificats de sécurité non valides sont non sécurisés et autorisent [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Si l'argent est un obstacle, vous pouvez obtenir des certificats de sécurité gratuits auprès de [Crypt](https://letsencrypt.org).
-Alternativement, vous pouvez accepter l'empreinte digitale affichée sous le message d'erreur si vous configurez le compte et/ou l'identité lors de l'étape de configuration 1 et 2 (ce n'est pas possible lorsque vous utilisez l'assistant d'installation rapide). Notez que vous devez vous assurer que la connexion Internet que vous utilisez est sûre.
+Vous pouvez également accepter l'empreinte du certificat de serveur non valide comme indiqué sous le message d'erreur en cochant une case à cocher. En cas de compte existant (IMAP, recevoir) et/ou d'identité (SMTP, envoyer) vous aurez besoin de le vérifier/sauvegarder via les étapes 1 et 2 de configuration pour recevoir le message d'erreur. Ceci va "épingler" le certificat du serveur pour éviter les attaques de man-in-the-middle. Notez que vous devez vous assurer que la connexion Internet que vous utilisez est sûre si vous faites cela.
Notez que les anciennes versions d'Android peuvent ne pas reconnaître de nouvelles autorités de certification comme Let's Encrypt qui peuvent considérer les connexions comme non sécurisées, voir aussi [ici](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... Aucun jeton ...* signifie que le gestionnaire de comptes Android n'a pas réussi à actualiser l'autorisation d'un compte Gmail.
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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. De plus, certains serveurs de messagerie terminent prématurément les connexions inactives, tandis que [la norme](https://tools.ietf.org/html/rfc2177) indique qu'une connexion inactive doit rester ouverte pendant 29 minutes. Dans ces cas, vous pouvez synchroniser périodiquement, par exemple chaque heure au lieu de en continu. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Si vous pensez que c'est suffisant, vous pouvez activer l'option de notification *Envoyer uniquement des notifications avec un aperçu de message aux objets connectés* et si cela ne fonctionne pas, vous pouvez essayer d'activer l'option de notification *Afficher les notifications avec un texte de prévisualisation uniquement*. Notez que ceci s'applique aux objets connectés n'affichant pas de texte de prévisualisation non plus, même lorsque l'application Android Wear indique que la notification a été envoyée (pont).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. Ceci signifie que toutes les fonctionnalités sont également disponibles dans la version F-Droid, à l'exception de l'utilisation de l'assistant de configuration rapide Gmail parce que Google a approuvé (et autorisé) une seule signature d'application. Pour tous les autres fournisseurs de messagerie, l'accès OAuth n'est disponible que dans les versions du Play Store et dans les versions de Github, étant donné que les fournisseurs de messagerie n'ont autorisé que les versions officielles à utiliser OAuth.
+The F-Droid version is built from the same source code, but signed differently. Ceci signifie que toutes les fonctionnalités sont également disponibles dans la version F-Droid, à l'exception de l'utilisation de l'assistant de configuration rapide Gmail parce que Google a approuvé (et autorisé) une seule signature d'application. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-fy-rNL.md b/docs/FAQ-fy-rNL.md
index 03ec1d43d0..ecb662dceb 100644
--- a/docs/FAQ-fy-rNL.md
+++ b/docs/FAQ-fy-rNL.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-gl-rES.md b/docs/FAQ-gl-rES.md
index 8718b3a9d9..01db675d78 100644
--- a/docs/FAQ-gl-rES.md
+++ b/docs/FAQ-gl-rES.md
@@ -75,7 +75,7 @@ Preguntas relacionadas:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
@@ -2764,21 +2776,21 @@ If I could, I would add a setting to select the primary and accent color right a
-## Support
+## Asistencia Técnica
-Only the latest Play store version and latest GitHub release are supported. This also means that downgrading is not supported.
+So se soportan as derradeiras versións da Play store e de Github. Isto significa tamén que non se soporta volver a versións antigas.
-Requested features should:
+As características que se pidan deberían:
-* be useful to most people
-* not complicate the usage of FairEmail
-* fit within the philosophy of FairEmail (privacy oriented, security minded)
-* comply with common standards (IMAP, SMTP, etc)
+* ser de utilidade para a maioría da xente
+* non complicar o uso de FairEmail
+* encaixar na filosofía de FairEmail (orientado á privacidade e coa seguridade en mente)
+* cumprir cos estándares comúns (IMAP, SMTP, etc)
-Features not fulfilling these requirements will likely be rejected. This is also to keep maintenance and support in the long run feasible.
+As características que non cumpran con estes requirimentos van ser probablemente rexeitadas. Isto tamén é para facer posible o mantemento e a asistencia técnica posibles ao longo prazo.
-If you have a question, want to request a feature or report a bug, please use [this form](https://contact.faircode.eu/?product=fairemailsupport).
+Se ten algunha dúbida, quere pedir unha característica ou avisar dun fallo, use [este formulario](https://contact.faircode.eu/?product=fairemailsupport).
-GitHub issues are disabled due to frequent misusage.
+O seguimento de fallos de GitHub desactivouse porque non se estaba a usar correctamente de maneira habitual.
Copyright © 2018-2020 Marcel Bokhorst.
diff --git a/docs/FAQ-hi-rIN.md b/docs/FAQ-hi-rIN.md
index a29b7ff650..5428f60b9c 100644
--- a/docs/FAQ-hi-rIN.md
+++ b/docs/FAQ-hi-rIN.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-hr-rHR.md b/docs/FAQ-hr-rHR.md
index 550021d50e..456b5c721e 100644
--- a/docs/FAQ-hr-rHR.md
+++ b/docs/FAQ-hr-rHR.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-hu-rHU.md b/docs/FAQ-hu-rHU.md
index fd6651f801..b1b5e92896 100644
--- a/docs/FAQ-hu-rHU.md
+++ b/docs/FAQ-hu-rHU.md
@@ -75,7 +75,7 @@ Kapcsolódó kérdések:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-in-rID.md b/docs/FAQ-in-rID.md
index d792c6b840..4472cd148f 100644
--- a/docs/FAQ-in-rID.md
+++ b/docs/FAQ-in-rID.md
@@ -1,4 +1,4 @@
-# Dukungan FairEmail
+# Bantuan FairEmail
Jika Anda memiliki pertanyaan, silakan periksa pertanyaan yang sering diajukan di bawah ini terlebih dahulu. Di bagian bawah, Anda dapat mengetahui cara mengajukan pertanyaan lain, meminta fitur, dan melaporkan bug.
@@ -52,7 +52,7 @@ Pertanyaan terkait:
* Add a folder to the unified inbox: long press the folder in the folder list and tick *Show in unified inbox*
* Menambahkan berkas di menu navigasi: tekan berkas dengan lama di dalam daftar berkan dan berikan tanda di *Tampilkan di menu navigasi*
* Memuat pesan lainnya: tekan berkas dengan lama di dalam daftar berkas, pilih *Singkronisasikan pesan lainnya*
-* Delete a message, skipping trash: in the 3-dots menu just above the message text *Delete* or alternatively, unselect the trash folder in the account settings
+* Menghapus pesan, loncati sampah: dalam menu titik 3 diatas *Hapus* teks pesan atau secara alternatif tidak memilih folder sampah di pengaturan akun
* Menghapus akun/identitas: Pengaturan langkah 1/2, Pengelolaan, menu titik 3, Hapus
* Menghapus berkas: tekan berkas dengan lama di dalam daftar berkas, Sunting properti, menu tiga titik, Hapus
* Mengurungkan pesan: Kotak keluar, tekan pesan, tekan tombol ikon urungkan
@@ -75,30 +75,30 @@ Pertanyaan terkait:
* ~~[Bug di AndroidX](https://issuetracker.google.com/issues/64729576) menyebabkan kesulitan untuk menekan scroll cepat. Solusi telah ditambahkan.~~
* ~~Enkripsi menggunakan YubiKey mengakibaykan putaran yang terus menerus. Hal ini disebabkan karena sebuah [bug di 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.
-* Tampilan teks pesan tidak (selalu) terlihat pada jam Samsung karena [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) sepertinya dihindari. Tampilan teks pesan diketahui terlihat dengan benar pada perangkat jam Pebble 2, Fitbit Charge 3, dan Mi band 3. Lihat juga [FAQ ini](#user-content-faq126).
+* Tampilan teks pesan tidak (selalu) terlihat pada jam Samsung karena [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) sepertinya dihindari. Tampilan teks pesan diketahui dapat ditampilkan dengan benar pada perangkat wearable Pebble 2, Fitbit Charge 3, Mi band 3, dan Xiaomi Amazfit BIP. Lihat juga [FAQ ini](#user-content-faq126).
* [Bug idi Android 6.0](https://issuetracker.google.com/issues/37068143) menyebabkan crash dengan *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. Bug ini telah diperbaiki dalam 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). Hal ini merupakan limitasi Android yang tidak dapat diperbaiki atau di buat bekerja.
## Fitur yang Direncanakan
-* ~~Synchronize on demand (manual)~~
+* ~~Singkronisasi secara manual~~
* ~~Enkripsi semi otomatis~~
* ~~Salinan pesan~~
-* ~~Colored stars~~
+* ~~Bintang berwarna~~
* ~~Pengaturan notifikasi per berkas~~
* ~~Pilih gambar lokal untuk tanda tangan~~ (hal ini belum ditambahkan karena memerlukan manajemen berkas gambar dan karena bagaimanapun gambar tidak ditampilkan secara default pada sebagian besar surel klien)
-* ~~Show messages matched by a rule~~
+* ~~Tampilkan pesan yang cocok dengan pengaturan~~
* ~~[ManageSieve](https://tools.ietf.org/html/rfc5804)~~ (there are no maintained Java libraries with a suitable license and without dependencies and besides that, FairEmail has its own filter rules)
* ~~Cari pesan menggunakan/tanpa lampiran~~ (hal ini belum ditambahkan karena IMAP tidak mendukung perncarian lampiran)
-* ~~Search for a folder~~ (filtering a hierarchical folder list is problematic)
+* ~~Mencari folder~~ (susah sekali menyaring folder hirarki)
* ~~Penyaranan pencarian~~
* ~~[Autocrypt Setup Message](https://autocrypt.org/autocrypt-spec-1.0.0.pdf) (section 4.4)~~ (IMO it is not a good idea to let an email client handle sensitive encryption keys for an exceptional use case while OpenKeychain can export keys too)
* ~~Generic unified folders~~
-* ~~New per account message notification schedules~~ (implemented by adding a time condition to rules so messages can be snoozed during selected periods)
+* ~~Jadwal notifikasi pesan per akun baru~~ (diterapkan dengan menambahkan waktu untuk mengatur sehingga pesan dapat disnooze selama periode yang ditentukan)
* ~~Salin akun dan identitas~~
* ~~Pinch zoom~~ (not reliably possible in a scrolling list; the full message view can be zoomed instead)
* ~~Tampilan berkas yang lebih sederhana~~
-* ~~Compose lists and tables~~ (this requires a rich text editor, see [this FAQ](#user-content-faq99))
+* ~~Buat daftar dan tabel~~ (hal ini memerlukan penyusun rich text, lihat [FAQ ini](#user-content-faq99))
* ~~Pinch zoom text size~~
* ~~Tampilan GIF~~
* ~~Tema~~ (tema abu-abu muda dan gelap telah ditambahkan karena tema ini yang paling banyak disukai orang)
@@ -109,7 +109,7 @@ Pertanyaan terkait:
* ~~Select domains to show images for~~ (this will be too complicated to use)
* ~~Unified starred messages view~~ (there is already a special search for this)
* ~~Memindahkan aksi notifikasi~~
-* ~~S/MIME support~~
+* ~~Dukungan S/MIME~~
* ~~Pencarian untuk pengaturan~~
Apapun yang ada dalam daftar ini disusun secara acak dan *mungkin* akan ditambahkan pada waktu yang akan datang.
@@ -139,7 +139,7 @@ Desain ini bersadarkan dari banyak diskusi dan anda dapat mendiskusikannya [di f
* [~~(17) Mengapa singkronisasi manual tidak bekerja~~](#user-content-faq17)
* [(18) Mengapa tampilan pesan tidak selalu terlihat?](#user-content-faq18)
* [(19) Mengapa fitur pro sangat mahal?](#user-content-faq19)
-* [(20) Apakah dapat mengembalikan dana saya?](#user-content-faq20)
+* [(20) Apakah dana saya dapat dikembalikan?](#user-content-faq20)
* [(21) Bagaimana cara saya mengaktifkan lampu notifikasi?](#user-content-faq21)
* [(22) Apa yang dimaksud dengan akun/folder eror ... ?](#user-content-faq22)
* [(23) Mengapa saya mendapatkan tanda .. ?](#user-content-faq23)
@@ -165,8 +165,8 @@ Desain ini bersadarkan dari banyak diskusi dan anda dapat mendiskusikannya [di f
* [(44) Apakah saya dapat menampilkan foto / ikon identitas kontak dari folder terkirim?](#user-content-faq44)
* [(45) How can I fix 'This key is not available. To use it, you must import it as one of your own!' ?](#user-content-faq45)
* [(46) Mengapa daftar pesan saya selalu segarkan?](#user-content-faq46)
-* [(47) How do I solve the error 'No primary account or no drafts folder' ?](#user-content-faq47)
-* [~~(48) How do I solve the error 'No primary account or no archive folder' ?~~](#user-content-faq48)
+* [(47) Bagaimana cara saya memperbaiki eror 'Tidak ada akun utama atau tidak ada folder draf' ?](#user-content-faq47)
+* [~~(48) Bagaimana cara saya memperbaiki eror 'Tidak ada akun utama atau tidak ada folder arsip' ?~~](#user-content-faq48)
* [(49) How do I fix 'An outdated app sent a file path instead of a file stream' ?](#user-content-faq49)
* [(50) Apakah saya dapat menambahkan opsi singkronisasikan seluruh pesan?](#user-content-faq50)
* [(51) Bagaimana folder disusun?](#user-content-faq51)
@@ -174,15 +174,15 @@ Desain ini bersadarkan dari banyak diskusi dan anda dapat mendiskusikannya [di f
* [(53) Apakah saya dapat menempelkan bilah aksi pesan ke paling atas/paling bawah?](#user-content-faq53)
* [~~(54) Bagaimana cara saya menggunakan bagian prefiks nama?~~](#user-content-faq54)
* [(55) Bagaimana cara saya menandai semua pesan telah dibaca / memindahkan atau menghapus seluruh pesan?](#user-content-faq55)
-* [(56) Apakah saya dapat menambahkan dukungan untuk JMAP?](#user-content-faq56)
-* [~~(57) Apakah saya dapat menggunakan HTML di tanda tangan?~~](#user-content-faq57)
+* [(56) Apakah anda dapat menambahkan dukungan untuk JMAP?](#user-content-faq56)
+* [(57) Apakah saya dapat menggunakan HTML di tanda tangan?](#user-content-faq57)
* [(58) Apa yang dimaksud dengan ikon surel buka/tutup?](#user-content-faq58)
* [(59) Apakah pesan orisinil dapat dibuka di browser?](#user-content-faq59)
-* [(60) Apakah anda mengetahui ...?](#user-content-faq60)
+* [(60) Tahukah anda ...?](#user-content-faq60)
* [(61) Mengapa terdapat beberapa pesan yang terlihat redup?](#user-content-faq61)
* [(62) Metode autentikasi apa yang didukung?](#user-content-faq62)
* [(63) Bagaimana cara mengubah ukuran gambar untuk ditampilkan di layar?](#user-content-faq63)
-* [~~(64) Apakah saya dapat menambah aksi tambahan untuk geser kiri/kanan?~~](#user-content-faq64)
+* [~~(64) Apakah anda dapat menambahkan aksi tambahan untuk geser kiri/kanan?~~](#user-content-faq64)
* [(65) Mengapa terdapat beberapa lampiran yang terlihat redup?](#user-content-faq65)
* [(66) Apakah FairEmail tersedia di Google Play Family Library?](#user-content-faq66)
* [(67) Bagaimana cara saya snooze percakapan?](#user-content-faq67)
@@ -210,99 +210,99 @@ Desain ini bersadarkan dari banyak diskusi dan anda dapat mendiskusikannya [di f
* [(90) Why are some texts linked while not being a link?](#user-content-faq90)
* [~~(91) Apakah anda dapat menambahkan singkronisasi periodik untuk menghemat tenaga baterai?~~](#user-content-faq91)
* [(92) Can you add spam filtering, verification of the DKIM signature and SPF authorization?](#user-content-faq92)
-* [(93) Apakah anda dapat mengizinkan instalasi/penyimpanan data di media penyimpanan eksternal?](#user-content-faq93)
+* [(93) Apakah anda dapat mengizinkan instalasi/penyimpanan data di media penyimpanan eksternal (sdcard)?](#user-content-faq93)
* [(94) Apa yang dimaksud dari garis yang berwarna merah/oranye diakhir header?](#user-content-faq94)
* [(95) Mengapa tidak semua aplikasi terlihat saat memilih lampiran atau gambar?](#user-content-faq95)
* [(96) Dimana saya dapat menemukan pengaturan IMAP dan SMTP?](#user-content-faq96)
* [(97) What is 'cleanup' ?](#user-content-faq97)
-* [(98) Why can I still pick contacts after revoking contacts permissions?](#user-content-faq98)
+* [(98) Menngapa saya tetap bisa memilih kontak setelah membatalkan izin kontak?](#user-content-faq98)
* [(99) Can you add a rich text or markdown editor?](#user-content-faq99)
-* [(100) How can I synchronize Gmail categories?](#user-content-faq100)
-* [(101) What does the blue/orange dot at the bottom of the conversations mean?](#user-content-faq101)
-* [(102) How can I enable auto rotation of images?](#user-content-faq102)
-* [(103) How can I record audio?](#user-content-faq103)
-* [(104) What do I need to know about error reporting?](#user-content-faq104)
+* [(100) Bagaimana cara saya mensingkronisasikan kategori Gmail?](#user-content-faq100)
+* [(101) Apa yang dimaksud dengan titik yang berwarna biru/oranye yang berada dibawah percakapan?](#user-content-faq101)
+* [(102) Bagaimana cara saya mengaktifkan rotasi otomatis untuk gambar?](#user-content-faq102)
+* [(103) Bagaimana cara saya merekam audio?](#user-content-faq103)
+* [(104) Apa yang harus saya ketahui tentang pelaporan eror?](#user-content-faq104)
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
-* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
-* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
-* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
-* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
-* [(111) Is OAuth supported?](#user-content-faq111)
-* [(112) Which email provider do you recommend?](#user-content-faq112)
-* [(113) How does biometric authentication work?](#user-content-faq113)
-* [(114) Can you add an import for the settings of other email apps?](#user-content-faq114)
+* [(106) Peluncur mana yang dapat menampilkan lencana hitungan dengan jumlah pesan yang belum dibaca?](#user-content-faq106)
+* [(107) Bagaimana cara saya menggunakan bintang berwarna?](#user-content-faq107)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
+* [~~(109) Mengapa 'pilih akun' hanya tersedia di versi resmi saja?~~](#user-content-faq109)
+* [(110) Mengapa terdapat (beberapa) pesan kosong dan/atau lampiran yang rusak?](#user-content-faq110)
+* [(111) Apakah OAuth tersedia?](#user-content-faq111)
+* [(112) Penyedia surel apa yang anda rekomendasikan?](#user-content-faq112)
+* [(113) Bagaimana cara kerja autentikasi biometrik?](#user-content-faq113)
+* [(114) Apakah anda dapat menambahkan impor untuk pengaturan aplikasi surel lain?](#user-content-faq114)
* [(115) Can you add email address chips?](#user-content-faq115)
-* [~~(116) How can I show images in messages from trusted senders by default?~~](#user-content-faq116)
-* [(117) Can you help me restore my purchase?](#user-content-faq117)
-* [(118) What does 'Remove tracking parameters' exactly?](#user-content-faq118)
-* [~~(119) Can you add colors to the unified inbox widget?~~](#user-content-faq119)
-* [(120) Why are new message notifications not removed on opening the app?](#user-content-faq120)
-* [(121) How are messages grouped into a conversation?](#user-content-faq121)
-* [~~(122) Why is the recipient name/email address show with a warning color?~~](#user-content-faq122)
-* [(123) What will happen when FairEmail cannot connect to an email server?](#user-content-faq123)
-* [(124) Why do I get 'Message too large or too complex to display'?](#user-content-faq124)
-* [(125) What are the current experimental features?](#user-content-faq125)
-* [(126) Can message previews be sent to my wearable?](#user-content-faq126)
+* [~~(116) Bagaimana caranya saya dapat menampilkan gambar dari pengirim yang saya percaya secara otomatis?~~](#user-content-faq116)
+* [(117) Apakah anda dapat membantu saya memulihkan pembelian saya?](#user-content-faq117)
+* [(118) Apa sebenarnya yang dimaksud dengan 'Hapus parameter pelacakan'?](#user-content-faq118)
+* [~~(119) Apakah anda dapat menambahkan warna ke dalam widget pesan masuk terpadu?~~](#user-content-faq119)
+* [(120) Mengapa notifikasi pesan baru tidak terhapus ketika membuka aplikasi?](#user-content-faq120)
+* [(121) Bagaimana pesan dikelompokan kedalam sebuah percakapan?](#user-content-faq121)
+* [~~(122) Mengapa nama/alamat surel penerima memiliki warna peringatan?~~](#user-content-faq122)
+* [(123) Apa yang terjadi ketika FairEmail tidak dapat terhubung dengan server surel?](#user-content-faq123)
+* [(124) Mengapa saya mendapatkan 'Pesan terlalu besar atau terlalu kompleks untuk ditampilkan'?](#user-content-faq124)
+* [(125) Apa saja fitur eksperimental terbaru?](#user-content-faq125)
+* [(126) Apakah tampilan pesan dapat dikirimkan ke perangkat yang dapat saya pakai?](#user-content-faq126)
* [(127) How can I fix 'Syntactically invalid HELO argument(s)'?](#user-content-faq127)
-* [(128) How can I reset asked questions, for example to show images?](#user-content-faq128)
-* [(129) Are ProtonMail, Tutanota supported?](#user-content-faq129)
-* [(130) What does message error ... mean?](#user-content-faq130)
-* [(131) Can you change the direction for swiping to previous/next message?](#user-content-faq131)
-* [(132) Why are new message notifications silent?](#user-content-faq132)
-* [(133) Why is ActiveSync not supported?](#user-content-faq133)
-* [(134) Can you add deleting local messages?](#user-content-faq134)
-* [(135) Why are trashed messages and drafts shown in conversations?](#user-content-faq135)
-* [(136) How can I delete an account/identity/folder?](#user-content-faq136)
-* [(137) How can I reset 'Don't ask again'?](#user-content-faq137)
-* [(138) Can you add calendar/contact management/synchronizing?](#user-content-faq138)
-* [(139) How do I fix 'User is authenticated but not connected'?](#user-content-faq139)
-* [(140) Why does the message text contain strange characters?](#user-content-faq140)
-* [(141) How can I fix 'A drafts folder is required to send messages'?](#user-content-faq141)
-* [(142) How can I store sent messages in the inbox?](#user-content-faq142)
-* [~~(143) Can you add a trash folder for POP3 accounts?~~](#user-content-faq143)
-* [(144) How can I record voice notes?](#user-content-faq144)
-* [(145) How can I set a notification sound for an account, folder or sender?](#user-content-faq145)
-* [(146) How can I fix incorrect message times?](#user-content-faq146)
-* [(147) What should I know about third party versions?](#user-content-faq147)
-* [(148) How can I use an Apple iCloud account?](#user-content-faq148)
-* [(149) How does the unread message count widget work?](#user-content-faq149)
-* [(150) Can you add cancelling calendar invites?](#user-content-faq150)
-* [(151) Can you add backup/restore of messages?](#user-content-faq151)
-* [(152) How can I insert a contact group?](#user-content-faq152)
-* [(153) Why does permanently deleting Gmail message not work?](#user-content-faq153)
-* [~~(154) Can you add favicons as contact photos?~~](#user-content-faq154)
-* [(155) What is a winmail.dat file?](#user-content-faq155)
-* [(156) How can I set up an Office 365 account?](#user-content-faq156)
-* [(157) How can I set up an Free.fr account?](#user-content-faq157)
-* [(158) Which camera / audio recorder do you recommend?](#user-content-faq158)
+* [(128) Bagaimana cara saya mengulang pertanyaan yang ditanyakan, seperti untuk menampilkan gambar?](#user-content-faq128)
+* [(129) Apakah ProtonMail terdukung Tutanota?](#user-content-faq129)
+* [(130) Apakah yang dimaksud dengan pesan eror ... ?](#user-content-faq130)
+* [(131) Apakah anda dapat mengubah arah geser untuk pesan sebelumnya/selanjutnya?](#user-content-faq131)
+* [(132) Mengapa notifikasi pesan baru tidak berbunyi?](#user-content-faq132)
+* [(133) Mengapa tidak terdukung ActiveSync?](#user-content-faq133)
+* [(134) Apakah anda dapat menambahkan hapus pesan lokal?](#user-content-faq134)
+* [(135) Mengapa pesan dan draf yang telah dibuang ditampilkan di percakapan?](#user-content-faq135)
+* [(136) Bagaimana cara saya menghapus akun/identitas/folder?](#user-content-faq136)
+* [(137) Bagaimana cara saya mengulang 'Jangan bertanya lagi'?](#user-content-faq137)
+* [(138) Apakah anda dapat menambahkan kalender/manajemen kontak/singkronisasi?](#user-content-faq138)
+* [(139) Bagaimana cara saya memperbaiki 'Pengguna telah terotentikasi namun tidak terkoneksi'?](#user-content-faq139)
+* [(140) Mengapa teks pesan terdapat karakter yang aneh?](#user-content-faq140)
+* [(141) Bagaimana cara saya memperbaiki 'Folder draf diperlukan untuk mengirim pesan'?](#user-content-faq141)
+* [(142) Bagaimana cara saya menyimpan pesan yang terkirim di pesan masuk?](#user-content-faq142)
+* [~~(143) Apakah anda dapat menambahkan folder untuk akun POP3?~~](#user-content-faq143)
+* [(144) Bagaimana cara saya merekam catatan suara?](#user-content-faq144)
+* [(145) Bagaimana cara saya menyetel suara notifikasi untuk akun, folder dan pengirim?](#user-content-faq145)
+* [(146) Bagaimana cara saya memperbaiki waktu pesan yang salah?](#user-content-faq146)
+* [(147) Apa yang harus saya ketahui tentang versi pihak ketiga?](#user-content-faq147)
+* [(148) Bagaimana cara saya menggunakan akun Apple iCloud?](#user-content-faq148)
+* [(149) Bagaimana cara kerja widget penghitung pesan yang belum dibaca?](#user-content-faq149)
+* [(150) Apakah anda dapat menambahkan pembatalan undangan kalender?](#user-content-faq150)
+* [(151) Apakah anda dapat menambahkan backup/restore pesan?](#user-content-faq151)
+* [(152) Bagaimana cara saya memasukan kontak ke grup?](#user-content-faq152)
+* [(153) Mengapa hapus pesan Gmail secara permanen tidak bekerja?](#user-content-faq153)
+* [~~(154) Apakah anda dapat menambahkan favicons sebagai foto kontak?~~](#user-content-faq154)
+* [(155) Apa itu berkas winmail.dat?](#user-content-faq155)
+* [(156) Bagaimana cara saya mengatur akun Office 365?](#user-content-faq156)
+* [(157) Bagaimana cara saya mengatur akun Free.fr?](#user-content-faq157)
+* [(158) Kamera / perekam audio apa yang anda sarankan?](#user-content-faq158)
* [(159) What are Disconnect's tracker protection lists?](#user-content-faq159)
-* [(160) Can you add permanent deletion of messages without confirmation?](#user-content-faq160)
-* [(161) Can you add a setting to change the primary and accent color?](#user-content-faq161)
+* [(160) Apakah anda dapat menambahkan penghapusan permanen dari pesan tanpa konfirmasi?](#user-content-faq160)
+* [(161) Apakah anda dapat menambahkan pengaturan untuk mengubah warna utama dan aksen?](#user-content-faq161)
-[I have another question.](#user-content-support)
+[Saya memiliki pertanyaan lain.](#user-content-support)
-**(1) Which permissions are needed and why?**
+**(1) Izin apa yang diperlukan dan mengapa?**
-The following Android permissions are needed:
+Dibawah ini adalah izin Android yang diperlukan:
-* *have full network access* (INTERNET): to send and receive email
-* *view network connections* (ACCESS_NETWORK_STATE): to monitor internet connectivity changes
-* *run at startup* (RECEIVE_BOOT_COMPLETED): to start monitoring on device start
-* *foreground service* (FOREGROUND_SERVICE): to run a foreground service on Android 9 Pie and later, see also the next question
-* *prevent device from sleeping* (WAKE_LOCK): to keep the device awake while synchronizing messages
-* *in-app billing* (BILLING): to allow in-app purchases
-* Optional: *read your contacts* (READ_CONTACTS): to autocomplete addresses and to show photos
-* Optional: *read the contents of your SD card* (READ_EXTERNAL_STORAGE): to accept files from other, outdated apps, see also [this FAQ](#user-content-faq49)
-* Optional: *use fingerprint hardware* (USE_FINGERPRINT) and use *biometric hardware* (USE_BIOMETRIC): to use biometric authentication
-* Optional: *find accounts on the device* (GET_ACCOUNTS): to select an account when using the Gmail quick setup
-* Android 5.1 Lollipop and before: *use accounts on the device* (USE_CREDENTIALS): to select an account when using the Gmail quick setup (not requested on later Android versions)
-* Android 5.1 Lollipop and before: *Read profile* (READ_PROFILE): to read your name when using the Gmail quick setup (not requested on later Android versions)
+* *memiliki akses internet penuh* (INTERNET): untuk mengirimkan dan menerima pesan
+* *tampilkan koneksi network* (ACCESS_NETWORK_STATE): untuk memonitor perubahan konektivitas internet
+* *berjalan saat memulai*(RECEIVE_BOOT_COMPLETED): untuk memulai pemantauan perangkat saat memulai
+* *servis latar depan* (FOREGROUND_SERVICE): untuk menjalankan servis latar depan pada Android 9 Pie dan sebelumnya, lihat juga pertanyaan selanjutnya
+* *mencegah perangkat untuk tidur* (WAKE_LOCK): untuk membuat perangkat tetap terbangun saat mensingkronisasi pesan
+* *penagihan dalam aplikasi* (BILLING): untuk mengizinkan pembelian di dalam aplikasi
+* Opsional: *membaca kontak anda* (READ_CONTACTS): untuk mengisi alamat secara otomatis dan menampilkan foto
+* Opsional: *membaca isi dari kartu SD anda* (READ_EXTERNAL_STORAGE): untuk meneruma berkas dari yang lain, aplikasi yang telah kadauwarsa, lihat juga [FAQ ini](#user-content-faq49)
+* Opsional: *gunakan perangkat sidik jari* (USE_FINGERPRINT) dan gunakan *perangkat biometrik* (USE_BIOMETRIC): untuk menggunakan autentikasi biometrik
+* Opsional: *cari akun di perangkat* (GET_ACCOUNTS): untuk memilih akun ketika menggunakan pengaturan cepat Gmail
+* Android 5.1 Lollipop dan sebelumnya: *gunakan akun di perangkat* (USE_CREDENTIALS): untuk memilih akun saat menggunakan pengaturan cepat Gmail (tidak dapat digunakan dalam versi Android yang lebih lama)
+* Android 5.1 Lollipop dan sebelumnya: *membaca profil* (READ_PROFILE): untuk membaca nama saat menggunakan saat menggunakan pengaturan cepat Gmail (tidak dapat digunakan dalam versi Android yang lebih lama)
-[Optional permissions](https://developer.android.com/training/permissions/requesting) are supported on Android 6 Marshmallow and later only. On earlier Android versions you will be asked to grant the optional permissions on installing FairEmail.
+[Izin opsional](https://developer.android.com/training/permissions/requesting) hanya terdapat di Android 6 Marshmallow dan sebelumnya. Pada versi Android terbaru, anda akan diminta untuk memberikan izin opsinal untuk menginstal FairEmail.
-The following permissions are needed to show the count of unread messages as a badge (see also [this FAQ](#user-content-faq106)):
+Izin dibawah ini diperlukan untuk menampilkan perhitungan pesan yang belum dibaca sebagai lencana (lihat juga [FAQ ini](#user-content-faq106)):
* *com.sec.android.provider.badge.permission.READ*
* *com.sec.android.provider.badge.permission.WRITE*
@@ -321,223 +321,223 @@ The following permissions are needed to show the count of unread messages as a b
* *me.everything.badger.permission.BADGE_COUNT_READ*
* *me.everything.badger.permission.BADGE_COUNT_WRITE*
-FairEmail will keep a list of addresses you receive messages from and send messages to and will use this list for contact suggestions when no contacts permissions is granted to FairEmail. This means you can use FairEmail without the Android contacts provider (address book). Note that you can still pick contacts without granting contacts permissions to FairEmail, only suggesting contacts won't work without contacts permissions.
+FairEmail akan menyimpan daftar alamat dari pesan yang anda terima dan pesan yang anda kirim, serta akan menggunakan daftar ini untuk penyaranan kontak ketika tidak ada perizinan kontak yang diberikan untuk FairEmail. Artinya, anda dapat menggunakan FairEmail tanpa adanya penyedia kontak Android (buku alamat). Perhatikan bahwa anda masih tetap dapat memilih kontak tanpa anda memberikan izin kontak ke FairEmail, hanya memberikan saran kontak tidak bekerja tanpa mengizinkan kontak.
-**(2) Why is there a permanent notification shown?**
+**(2) mengapa terdapat notifikasi yang permanen yang terlihat?**
-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.
+Bilah status notifkasi permanen yang berprioritas rendah dengan jumlah akun yang sedang dalam pantauan dan jumlah operasi yang tertunda (lihat pertanyaan selanjutnya) ditampilkan untuk mengindari Android mematikan layanan yang mengerjakan penerimaan surel yang terus menerus. Hal ini [telah menjadi penting](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), namun dengan adanya pengenalan dari [mode doze](https://developer.android.com/training/monitoring-device-state/doze-standby) dalam Android 6 Marshmallow hal in menjadi lebih penting dibandingkan sebelumnya. Mode doze akan menghentikan seluruh aplikasi ketika layar sedang dalam keadaan mati beberapa saat, kecuali ketika aplikasi telah menjalankan layanan latar depan, yang membutuhkan tampilan bilah status notifikasi.
-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.
+Kebanyakan, namun tidak semua, aplikasi surel lainnya tidak menampilkan notifikasi dengan "efek samping" yaitu pesan baru akan sering tidak atau terlambat diberitahukan dan pesan tersebut tidak atau terlambat dikirimkan.
-Android shows icons of high priority status bar notifications first and will hide the icon of FairEmail's notification if there is no space to show icons anymore. In practice this means that the status bar notification doesn't take space in the status bar, unless there is space available.
+Android menampilkan ikon bilah status notifikasi dengan prioritas tinggi terlebih dahulu dan akan menyembunyikan ikon notifikasi FairEmail jika tidak ada tempat untuk menampilkan ikon lagi. Secara praktis, hal ini berarti bilah status notifikasi tidak mengambil tempat di bilah status kecuali memang ada tempat tersedia.
-The status bar notification can be disabled via the notification settings of FairEmail:
+Bilah status notifikasi dapat dinonaktifkan lewat pengaturan notifikasi FairEmail:
-* Android 8 Oreo and later: tap the *Receive channel* button and disable the channel via the Android settings (this won't disable new message notifications)
-* Android 7 Nougat and before: enabled *Use background service to synchronize messages*, but be sure to read the remark below the setting
+* Android 8 Oreo sampai yang terbaru: tekan tombol *Penerimaan channel* dan matikan channel tersebut lewat pengaturan Android (hal ini tidak akan menonaktifkan notifikasi pesan baru)
+* Android 7 Nougat dan sebelumnya: aktifkan *Gunakan layanan latar untuk mensingkroniasikan pesan*, namun harap membaca catatan dibawah pengaturan
-You can switch to periodically synchronization of messages in the receive settings to remove the notification, but be aware that this might use more battery power. See [here](#user-content-faq39) for more details about battery usage.
+Anda dapat mengubah ke singkronisasi pesan secara perodik dalam pengaturan penerimaan untuk menghapus notifikasi, namun waspadalah bahwa hal ini dapat menggunakan daya baterai yang lebih banyak. Lihat [di sini](#user-content-faq39) untuk rincian lebih anjut tentang penggunaan baterai.
-Android 8 Oreo might also show a status bar notification with the text *Apps are running in the background*. Please see [here](https://www.reddit.com/r/Android/comments/7vw7l4/psa_turn_off_background_apps_notification/) about how you can disable this notification.
+Android 8 Oreo mungkin akan juga menampilkan bilah status notifikasi dengan tulisan *Aplikasi berjalan di background*. Sila lihat [di sini](https://www.reddit.com/r/Android/comments/7vw7l4/psa_turn_off_background_apps_notification/) tentang bagaimana cara anda untuk mematikan notifikasi ini.
-Some people suggested to use [Firebase Cloud Messaging](https://firebase.google.com/docs/cloud-messaging/) (FCM) instead of an Android service with a status bar notification, but this would require email providers to send FCM messages or a central server where all messages are collected sending FCM messages. The first is not going to happen and the last would have significant privacy implications.
+Beberapa orang memberikan saran untuk menggunakan [Firebase Cloud Messaging](https://firebase.google.com/docs/cloud-messaging/) (FCM) dibandingkan layanan Android dengan bilah status notifikasi, namun hal ini membutuhkan surel penyedia untuk mengirimkan pesan FCM atau server pusat di mana seluruh pesan dikumpulkan untuk mengirim pesan FCM. Hal yang pertama tidak akan terjadi dan hal yang kedua akan berdampak ke impikasi privasi yang signifikan.
-If you came here by clicking on the notification, you should know that the next click will open the unified inbox.
+Jika anda datang ke sini dengan menekan notifikasi, anda harus tahu bahwa jika anda tekan berikutnya akan membuka kotak masuk terpadu.
-**(3) What are operations and why are they pending?**
-
-The low priority status bar notification shows the number of pending operations, which can be:
-
-* *add*: add message to remote folder
-* *move*: move message to another remote folder
-* *copy*: copy message to another remote folder
-* *fetch*: fetch changed (pushed) message
-* *delete*: delete message from remote folder
-* *seen*: mark message as read/unread in remote folder
-* *answered*: mark message as answered in remote folder
-* *flag*: add/remove star in remote folder
+**(3) Apa itu operasi dan mengapa mereka tertunda?**
+
+Bilah status notifikasi prioritas rendah menampilkan sejumlah operasi yang tertunda, yaitu:
+
+* *tambah*: menambahkan pesan ke folder remot
+* *pindah*: memindahkan pesan ke folder remot lainnya
+* *salin*: menyalin pesan ke folder remot lainnya
+* *ambil*: memperoleh perubahan pesan (push)
+* *hapus*: menghapus pesan dari folder remot
+* *terlihat*: tandai pesan terbaca/belum terbaca di folder remot
+* *terbalas*: tandai pesan telah terbalas di folder remot
+* *tandai*: menambahkan/menghapus bintang di folder remot
* *keyword*: add/remove IMAP flag in remote folder
-* *label*: set/reset Gmail label in remote folder
-* *headers*: download message headers
+* *label*: atur/atur ulang label Gmail di folder remot
+* *header*: unduh header pesan
* *raw*: download raw message
-* *body*: download message text
-* *attachment*: download attachment
-* *sync*: synchronize local and remote messages
+* *isi*: unduh teks pesan
+* *lampiran*: unduh lampiran
+* *sync*: sinkronisasi pesan lokal dan remot
* *subscribe*: subscribe to remote folder
* *purge*: delete all messages from remote folder
-* *send*: send message
+* *kirim*: mengirim pesan
* *exists*: check if message exists
* *rule*: execute rule on body text
-Operations are processed only when there is a connection to the email server or when manually synchronizing. See also [this FAQ](#user-content-faq16).
+Operasi diproses hanya ketika ada koneksi ke servel surel atau tersingkronisasi secara manual. Lihat juga [FAQ ini](#user-content-faq16).
-**(4) How can I use an invalid security certificate / empty password / plain text connection?**
+**(4) Bagaimana cara saya menggunakan sertifikat keamanan yang tidak valid / kata sandi kosong / koneksi teks kosong?**
*... Untrusted ... not in certificate ...*
*... Invalid security certificate (Can't verify identity of server) ...*
-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).
+Anda harus mencoba memperbaiki hal ini dengan menghubungu penyedia atau dengan mendapatkan sertifikat keamanan yang valid karena sertifikat keamanan yang tidak valid tersebut tidak aman dan memberikan [ serangan man-in-the-middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Jika dana menjadi kendala, anda dapat mengambil sertifikat keamanan gratis dari [Let’s Encrypt](https://letsencrypt.org).
-Alternatively, you can accept the fingerprint shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
-Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
+Perhatikan juga bahwa versi Android yang lama mungkin tidak mengenal otoritas sertifikasi yang lebih baru seperti Let’s Encrypt akan membuat koneksi dianggap sebagai tidak aman, lihat juga [di sini](https://developer.android.com/training/articles/security-ssl).
*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.
-You should either fix the server configuration or accept the fingerprint shown below the error message.
+Anda harus memperbaiki konfigurasi server atau menyetujui sidik jari yang ditampilkan dibawah pesan eror.
-Note that this problem can be caused by the server not sending all intermediate certificates too.
+Perhatikan bahwa masalah ini dapat juga disebabkan oleh server yang tidak mengirimkan seluruh sertifikat yang penting.
-*Empty password*
+*Kata sandoi kosong*
-Your username is likely easily guessed, so this is insecure.
+Nama pengguna anda kemungkinan akan mudah ditebak, maka hal ini tidak aman.
*Plain text connection*
-Your username and password and all messages will be sent and received unencrypted, which is **very insecure** because a [man-in-the-middle attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) is very simple on an unencrypted connection.
+Nama pengguna dan kata sandi anda serta seluruh pesan yang akan dikirimkan dan diteriima tidak terenkripsi, hal tersebut **sangat tidak aman** karena mudah [terserang man-in-the-middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) dalam koneksi yang tidak terenkripsi.
-If you still want to use an invalid security certificate, an empty password or a plain text connection you'll need to enable insecure connections in the account and/or identity settings. STARTTLS should be selected for plain text connections. If you enable insecure connections, you should connect via private, trusted networks only and never via public networks, like offered in hotels, airports, etc.
+If you still want to use an invalid security certificate, an empty password or a plain text connection you'll need to enable insecure connections in the account and/or identity settings. STARTTLS should be selected for plain text connections. Jika anda mengaktifkan koneksi yang tidak aman, anda harus terkoneksi melalui jaringan yang privat dan terpercaya dan jangan pernah terkoneksi melalui jaringan publik seperti yang ditawarkan hotel, bandara, dll.
-**(5) How can I customize the message view?**
+**(5) Bagaimana cara saya mengatur tampilan pesan?**
-In the three dot overflow menu you can enable or disable or select:
+Pada menu overflow titik tiga anda dapat mengaktifkan atau menonaktifkan atau memilih:
-* *text size*: for three different font sizes
-* *compact view*: for more condensed message items and a smaller message text font
+* *ukuran teks*: untuk tiga ukuran font yang berbeda
+* *tampilan sederhana*: untuk item pesan yang lebih padat dan ukuran font teks pesan yang kecil
-In the display section of the settings you can enable or disable:
+Pada baguan tampilan pengaturan anda dapat mengaktifkan atau menonaktifkan:
* *Unified inbox*: to disable the unified inbox and to list the folders selected for the unified inbox instead
-* *Group by date*: show date header above messages with the same date
+* *Kelompokan berdasarkan tanggal*: tampilkan header tanggal diatas pesan yang memiliki tanggal yang sama
* *Conversation threading*: to disable conversation threading and to show individual messages instead
-* *Show contact photos*: to hide contact photos
-* *Show identicons*: to show generated contact avatars
-* *Show names and email addresses*: to show names or to show names and email addresses
-* *Show subject italic*: to show the message subject as normal text
-* *Show stars*: to hide stars (favorites)
-* *Show message preview*: to show two lines of the message text
-* *Show address details by default*: to expand the addresses section by default
-* *Use monospaced font for message text*: to use a fixed width typeface for message texts
-* *Automatically show original message for known contacts*: to automatically show original messages for contacts on your device, please read [this FAQ](#user-content-faq35)
-* *Automatically show images for known contacts*: to automatically show images for contacts on your device, please read [this FAQ](#user-content-faq35)
-* *Conversation action bar*: to disable the bottom navigation bar
+* *Tampilkan foto kontak*: untuk menyembunyikan foto kontak
+* *Tampilkan identicons*: untuk menampilkan avatar kontak yang dibuat
+* *Tampilkan nama dan alamat surel*: untuk menampilkan nama atau menampilkan nama beserta alamat surel
+* *Tampilkan judul dalam cetak miring*: untuk menampilkan judul pesan sebagai teks normal
+* *Tampilkan bintang*: untuk menyembunyikan bintang (favorit)
+* *Lihat tampilan pesan*: untuk melihat dua garis dari teks pesan
+* *Tampilkan rincian alamat secara standar*: untuk memperluas bagian alamat secara standar
+* *Gunakan font spasi tunggal untuk teks pesan*: untuk menggunakan jenis huruf dengan lebar pasti untuk teks pesan
+* *Tampilkan pesan orisinil secara otomatis untuk kontak yang telah diketahui*: untuk menampilkan pesan orisinil secara otomatis untuk kontak yang ada di perangkat anda, sila baca [FAQ ini](#user-content-faq35)
+* *Tampilkan gambar secara otomatis untuk kontak yang diketahui*: untuk menampilkan gambar secara otomatis bagi kontak yang dalam perangkat anda, sila baca [FAQ ini](#user-content-faq35)
+* *Bilah aksi percakapan*: untuk menonaktifkan bilah navigasi bawah
-Note that messages can be previewed only when the message text was downloaded. Larger message texts are not downloaded by default on metered (generally mobile) networks. You can change this in the settings.
+Perhatikan bahwa pesan dapat ditampilkan hanya ketika teks pesan telah diunduh. Teks pesan yang lebih besar tidak terunduh secara otomatis pada jaringan terukur (biasanya perangkat seluler). Anda dapat mengubahnya dalam pengaturan.
-If the list of addresses is long, you can collapse the addresses section with the *less* icon at the top of the addresses section.
+Jika daftar alamat terlalu panjang, anda dapat memendekkan bagian alamat dengan ikon *kurangi* yang terletak diatas bagian alamat.
-Some people ask:
+Beberapa orang bertanya:
-* to show the subject bold, but bold is already being used to highlight unread messages
-* to show the address or subject larger/smaller, but this would interfere with the text size option
-* to move the star to the left, but it is much easier to operate the star on the right side
+* untuk menampilkan judul yang dicetak tebal, namun cetak tebal telah digunakan untuk menyoroti pesan yang belum dibaca
+* untuk menampilkan alamat atau judul lebih kecil/lebih besar, namun hal ini dapat mengganggu opsi ukuran teks
+* untuk memindahkan bintang ke kiri, namun lebih mudah untuk mengoperasikan bintang di bagian kanan
-Unfortunately, it is impossible to make everybody happy and adding lots of settings would not only be confusing, but also never be sufficient.
+Sayangnya, tidak mungkin bisa untuk membuat seluruh orang senang dan menambahkan banyak pengaturan juga tidak hanya akan membuat bingung, namun juga tidak akan cukup.
-**(6) How can I login to Gmail / G suite?**
+**(6) Bagaimana cara saya masuk ke Gmail / G suite?**
-You can use the quick setup wizard to easily setup a Gmail account and identity.
+Anda dapat menggunakan wizard pengaturan cepat untuk mengatur akun Gmail dan identitas dengan mudah.
-If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to setup an account and identity via setup step 1 and 2 instead of via the quick setup wizard.
+Jika anda tidak ingin menggunakan akun Gmail yang ada di perangkat anda, anda dapat mengizinkan akses untuk "aplikasi yang kurang aman" dan gunakan kata sandi akun anda (tidak disarankan) atau anda dapat menonaktifkan autentikasi dua faktor dan gunakan kata sandi khusus aplikasi. Untuk menggunakan kata sandi, anda harus mengatur akun dan identitas melalui langah pengaturan 1 dan 2 dari pada melalui wizard pengaturan cepat.
-Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
+Sila lihat [FAQ ini](#user-content-faq111) untuk mengetahui mengapa hanya akun yang terdapat pada perangkat saja yang dapat digunakan.
-Note that an app specific password is required when two factor authentication is enabled.
+Perhatikan bahwa kata sandi khusus aplikasi diharuskan ketika otentikasi dua faktor diaktifkan.
-*App specific password*
+*Kata sandi khusus aplikasi*
-See [here](https://support.google.com/accounts/answer/185833) about how to generate an app specific password.
+Lihat [disini](https://support.google.com/accounts/answer/185833) tentang bagaimana cara membuat kata sandi khusus aplikasi.
-*Enable "Less secure apps"*
+*Aktifkan "Aplikasi yang kurang aman"*
-**Important**: using this method is not recommended because it is less reliable.
+**Penting**: penggunaan metode ini tidak direkomendasikan karena kurang diandalkan.
-**Important**: Gsuite accounts authorized with a username/password will stop working [in the near future](https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html).
+**Penting**: Akun Gsuite yang diotorisasikan dengan nama pengguna/kata sandi akan berkenti bekerja [dalam masa yang akan datang](https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html).
-See [here](https://support.google.com/accounts/answer/6010255) about how to enable "less secure apps" or go [directy to the setting](https://www.google.com/settings/security/lesssecureapps).
+Lihat [di sini](https://support.google.com/accounts/answer/6010255) untuk mengetahui cara mengaktifkan "aplikasi yang kurang aman" atau kunjungi [langsung ke bagian pengaturan](https://www.google.com/settings/security/lesssecureapps).
-If you use multiple Gmail accounts, make sure you change the "less secure apps" setting of the right account(s).
+Jika anda menggunakan akun Gmail lebih dari satu, pastikan anda mengubah pengaturan "aplikasi yang kurang aman" pada akun yang benar.
-Be aware that you need to leave the "less secure apps" settings screen by using the back arrow to apply the setting.
+Pastikan bahwa anda harus meninggalkan pengaturan "aplikasi yang kurang aman" dengan menggunakan tanda panah kembali untuk mengaplikasikan pengaturan tersebut.
-If you use this method, you should use a [strong password](https://en.wikipedia.org/wiki/Password_strength) for your Gmail account, which is a good idea anyway. Note that using the [standard](https://tools.ietf.org/html/rfc3501) IMAP protocol in itself is not less secure.
+Jika anda menggunakan metode ini, anda harus menggunakan [kata sandi yang kuat](https://en.wikipedia.org/wiki/Password_strength) untuk akun Gmail anda, lagipula itu ide yang bagus. Pastikan bahwa dengan menggunakan protokol IMAP [standar](https://tools.ietf.org/html/rfc3501) dengan sendirinya itu kurang aman.
-When "less secure apps" is not enabled, you'll get the error *Authentication failed - invalid credentials* for accounts (IMAP) and *Username and Password not accepted* for identities (SMTP).
+Jika "aplikasi yang kurang aman" tidak diaktifkan, anda akan mendapatkan eror *Otentikasi gagal - kredensial yang tidak valid* untuk akun (IMAP) dan *Nama pengguna dan Kata sandi tidak diterima* untuk identitas (SMTP).
-*General*
+*Umum*
-You might get the alert "*Please log in via your web browser*". This happens when Google considers the network that connects you to the internet (this could be a VPN) to be unsafe. This can be prevented by using the Gmail quick setup wizard or an app specific password.
+Anda mungkin mendapatkan peringatan "*Suila masuk lewat web browser anda*". Hal ini terjadi ketika Google menganggap jaringan yang menghubungkan anda ke internet (hal ini bisa jadi VPN) tidak aman. Peringatan ini dapat dicegah dengan menggunakan wizard pengaturan cepat atau kata sandi khusus aplikasi.
-See [here](https://support.google.com/mail/answer/7126229) for Google's instructions and [here](https://support.google.com/mail/accounts/answer/78754) for troubleshooting.
+Lihat [di sini](https://support.google.com/mail/answer/7126229) untuk instruksi dari Google dan [di sini](https://support.google.com/mail/accounts/answer/78754) untuk penyelesaian masalah.
-**(7) Why are sent messages not appearing (directly) in the sent folder?**
+**(7) Mengapa pesan yang terkirimkan tidak nampak (secara langsung) dalam folder terkirim?**
-Sent messages are normally moved from the outbox to the sent folder as soon as your provider adds sent messages to the sent folder. This requires a sent folder to be selected in the account settings and the sent folder to be set to synchronizing.
+Pesan yang terkirim normalnya dipindahkan dari pesan keluar ke folder terkirim langsung setelah penyedia anda menambahkan pesan yang terkirim ke folder terkirim. Hal ini membutuhkan folder terkirim yang dipilih dalam pengaturan akun dan folser kirim yang diatur untuk singkronisasi.
-Some providers do not keep track of sent messages or the used SMTP server might not be related to the provider. In these cases FairEmail, will automatically add sent messages to the sent folder on synchronizing the sent folder, which will happen after a message have been sent. Note that this will result in extra internet traffic.
+Beberapa penyedia tidak melacak pesan yang terkirim atau server SMTP yang telah digunakan bisa jadi tidak berhubungan dengan penyedia tersebut. Dalam kasus ini, FairEmail akan menambahkan pesan yang telah terkirim ke folder terkirim secara otomatis dalam mensingkronisasikan folder tersebut, yang akan terjadi setelah pesan telah dikirimkan. Perhatikan bahwa hal ini akan mengakibatkan traffic internet tambahan.
-~~If this doesn't happen, your provider might not keep track of sent messages or you might be using an SMTP server not related to the provider.~~ ~~In these cases you can enable the advanced identity setting *Store sent messages* to let FairEmail add sent messages to the sent folder right after sending a message.~~ ~~Note that enabling this setting might result in duplicate messages if your provider adds sent messages to the sent folder too.~~ ~~Also beware that enabling this setting will result in extra data usage, especially when when sending messages with large attachments.~~
+~~Jika hal ini tidak terjadi, penyedia anda mungkin tidak melacak pesan yang terkirim atau anda mungkin menggunakan server SMTP yang tidak berhubungan dengan penyedia.~~ ~~Dalam kasus ini, anda dapat mengaktifkan pengaturan identitas tingkat lanjut *Simpan pesan yang terkirim* agar FairEmail dapat menambahkan pesan yang terkirim ke dalam folder terkirim langsung setelah anda mengirim pesan.~~ ~~Perhatikan bahwa mengaktifkan pengaturan ini dapat mengaktibatkan pesan ganda jika penyedia anda juga menambahkan pesan yang terkirim ke dalam folder terkirim.~~ ~~Serta, berhati-hatilah bahwa dengan anda mengaktifkan pengaturan ini akan mengakibatkan penggunaan data ekstra, terutama saat mengirimkan pesan dengan lampiran yang besar.~~
-~~If sent messages in the outbox are not found in the sent folder on a full synchronize, they will be moved from the outbox to the sent folder too.~~ ~~A full synchronize happens when reconnecting to the server or when synchronizing periodically or manually.~~ ~~You'll likely want to enable the advanced setting *Store sent messages* instead to move messages to the sent folder sooner.~~
+~~Jika pesan yang terkirim di dalam pesan keluar tidak dapat ditemukan di dalam folder terkirim dalam singkronisasi penuh, pesan tersebut akan dipindahkan juga dari pesan keluar ke folser terkirim.~~ ~~Singkronisasi penuh terjadi ketika sedang menyambungkan kembali ke server atau ketika singkronisasi periodik atau manual.~~ ~~Anda mungkin akan perlu untuk mengaktifkan pengaturan tingkat lanjut *Simpan pesan yang terkirim* dibandingkan dengan memindahkan pesan ke dalam folder terkirim sekarang.~~
-**(8) Can I use a Microsoft Exchange account?**
+**(8) Apakah saya dapat menggunakan akun Microsoft Exchange?**
-You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
+Anda dapat menggunakan akun Microsoft Exchange jika, selalu dalam kasus ini, dapat diakses melalui IMAP. Lihat [di sini](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) untuk informasi lebih lanjut.
-Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
+Sila lihat [di sini](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) untuk dokumentasi Microsoft mengenai konfigurasi surel klien. Terdapat juga bagian mengenai eror koneksi yang sering terjadi dan solusinya.
-Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
+Sebagian versi server Exchange yang lama memiliki bug yang akan mengakibatkan pesan kosong dan lampiran yang rusak. Sila lihat [FAQ ini](#user-content-faq110) untuk solusinya.
-Please see [this FAQ](#user-content-faq133) about ActiveSync support.
+Sila lihat [FAQ ini](#user-content-faq133) tentang bantuan ActiveSync.
-Please see [this FAQ](#user-content-faq111) about OAuth support.
+Sila lihat [FAQ ini](#user-content-faq111) tentang bantuan OAuth.
-**(9) What are identities / how do I add an alias?**
+**(9) Apa itu identitas / bagaimana cara saya menambahkan alias?**
-Identities represent email addresses you are sending *from* via an email (SMTP) server.
+Identitas merepresentasikan alamat surel *dari* yang anda kirim melalui server surel (SMTP).
-Some providers allow you to have multiple aliases. You can configure these by setting the email address field of an additional identity to the alias address and setting the user name field to your main email address.
+Sebagian penyedia mengizinkan anda untuk memiliki alias lebih dari satu. Anda dapat mengkonfigurasi hal ini dengan mengatur bagian alamat surel dari identitas tambahan ke dalam alamat alias dan atur bagian nama pengguna dengan alamat surel utama anda.
-Note that you can copy an identity by long pressing it.
+Perhatikan bahwa anda dapat menyalin identitas dengan menekannya dengan lama.
-Alternatively, you can enable *Allow editing sender address* in the advanced settings of an existing identity to edit the username when composing a new message, if your provider allows this.
+Secara alternatif, anda dapat mengaktifkan *Izinkan penyuntingan alamat pengirim* di pengaturan tingkat lanjut dari identitas yang telah ada untuk menyunting nama pengguna ketika menulis pesan baru, jika penyedia anda mengizinkannya.
-FairEmail will automatically update the passwords of related identities when you update the password of the associated account or a related identity.
+FairEmail akan memperbarui kata sandi dari identitas terkait secara otomatis ketika anda memperbarui kata sandi dari akun yang terasosiasi atau identitas yang terkait.
-See [this FAQ](#user-content-faq33) on editing the username of email addresses.
+Lihat [FAQ ini](#user-content-faq33) untuk cara menyunting nama pengguna dari alamat surel.
@@ -549,46 +549,46 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
-**~~(11) Why is POP not supported?~~**
+**~~(11) Mengapa POP tidak terdukung?~~**
-~~Besides that any decent email provider supports [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol) these days,~~ ~~using [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol) will result in unnecessary extra battery usage and delayed new message notifications.~~ ~~Moreover, POP is unsuitable for two way synchronization and more often than not people read and write messages on different devices these days.~~
+~~Selain penyedia surel yang mendukung [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol) belakangan ini,~~ ~~menggunakan [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol) akan mengakibatkan penggunaan baterai ekstra yang tidak penting dan notifikasi pesan baru yang terhambat.~~ ~~Ditambah lagi POP tidak cocok untuk singkronisasi dua arah dan sering kali orang membaca dan menulis pesan di perangkat yang berbeda belakangan ini.~~
-~~Basically, POP supports only downloading and deleting messages from the inbox.~~ ~~So, common operations like setting message attributes (read, starred, answered, etc), adding (backing up) and moving messages is not possible.~~
+~~Secara singkat, POP hanya mendukung mengunduh dan mengahpus pesan dari kotak masuk.~~ ~~Maka, operasi yang biasa dilakukan seperti mengatur atribut pesan (baca, bintang, balas, dll), menambahkan (back up) dan memindahkan pesan tidak memungkinkan.~~
-~~See also [what Google writes about it](https://support.google.com/mail/answer/7104828).~~
+~~Lihat juga [apa yang Google tulis tentang POP](https://support.google.com/mail/answer/7104828).~~
-~~For example [Gmail can import messages](https://support.google.com/mail/answer/21289) from another POP account,~~ ~~which can be used as a workaround for when your provider doesn't support IMAP.~~
+~~Contohnya, [Gmail dapat mengimpor pesan](https://support.google.com/mail/answer/21289) dari akun POP lainnya,~~ ~~yang dapat digunakan sebagai solusi jika penyedia anda tidak mendukung IMAP.~~
-~~tl;dr; consider to switch to IMAP.~~
+~~tl;dr; menyarankan untuk pindah ke IMAP.~~
-**(12) How does encryption/decryption work?**
+**(12) Bagaimana cara kerja enkripsi / dekripsi?**
-*General*
+*Umum*
-Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
+Sila lihat [di sini](https://en.wikipedia.org/wiki/Public-key_cryptography) tentang bagaimana cara kerja enskripsi kunci.
-Encryption in short:
+Enkripsi secara singkat:
-* **Outgoing** messages are encrypted with the **public key** of the recipient
-* **Incoming** messages are decrypted with the **private key** of the recipient
+* Pesan **keluar** terenkripsi dengan **kunci publik** dari penerima
+* Pesan **masuk** terdekripsi dengan **kunci privat** dari penerima
-Signing in short:
+Membuat sign secara singkat:
-* **Outgoing** messages are signed with the **private key** of the sender
-* **Incoming** messages are verified with the **public key** of the sender
+* Pesan **keluar** tersign dengan **kunci privat** dari pengirim
+* Pesan **masuk** diverifikasi dengan **kunci publik** dari pengirim
-To sign/encrypt a message, just select the appropriate method in the send dialog. You can always open the send dialog using the three-dots overflow menu in case you selected *Don't show again* before.
+Untuk membuat sign/enkripsi sebuah pesan, anda tinggal memilih metode yang cocok dalam dialog kirim. Anda dapat selalu membuka dialog pengiriman dengan menggunakan menu overflow tiga titik jika anda telah memilik *Jangan tampilkan lagi* sebelumnya.
-To verify a signature or to decrypt a received message, open the message and just tap the gesture or padlock icon just below the message action bar.
+Untuk memverifikasi signature atau mendekripsi pesan yang diterima, buka pesan tersebut dan klik gestur atau ikon gembok yang terletak dibawah bilah aksi pesan.
-The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
+Pertama kali anda mengirim pesan tersign/enkripsi, anda mungkin akan ditanyakan mengenai kunci sign. Untuk berikutnya, FairEmail akan menyimpan secara otomatis kunci sign yang telah dipilih di dalam identitas yang telah digunakan. Jika anda perlu mengatur ulang kunci sign, anda tinggal menyimpan identitas atau tekan lama pada identitas di dalam daftar identitas dan pilih *Atur ulang kunci sign*. Kunci sign yang telah dipilih akan terlihat di daftar identitas. Jika anda perlu untuk memilih kunci berdasarkan kasus per kasus, anda dapat membuat identitas lebih dari satu untuk akun yang sama dengan alamat surel yang sama.
-In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
+Pada bagian pengaturan privasi anda dapat memilih metode standar enkripsi (PGP or S/MIME), aktifkan *Sign dengan standar*, *Enkripsi dengan standar* dan *Dekripsi pesan secara otomatis*. Namun berhati-hatilah bahwa dekripsi secara otomatis tidak akan memungkinkan jika mengharuskan interaksi pengguna, seperti memilih kunci atau membaca token keamanan.
-The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
+The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. Jika anda ingin mengurungkan dekripsi, anda dapat menggunakan menu *singkronisasi ulang* di dalam menu titik tiga dari bilah aksi pesan.
*PGP*
@@ -677,67 +677,67 @@ S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations ar
-**(13) How does search on device/server work?**
+**(13) Bagaimana cara kerja pencarian dalam perangkat/server?**
-You can start searching for messages on sender (from), recipient (to, cc, bcc), subject, keywords or message text by using the magnify glass in the action bar of a folder. You can also search from any app by selecting *Search email* in the copy/paste popup menu.
+Anda dapat memulai pencarian pesan dalam pengirim (dari), penerima (untuk, cc, bcc), judul, kata kunci atau teks pesandengan menggunakan kaca pembesar di bilah aksi dari folder. Anda juga dapat mencari aplikasi apapun dengan memilik *Cari surel* dalam menu popup salin/unggah.
Searching in the unified inbox will search in all folders of all accounts, searching in the folder list will search in the associated account only and searching in a folder will search in that folder only.
-Messages will be searched for on the device first. There will be an action button with a search again icon at the bottom to continue searching on the server. You can select in which folder to continue the search.
+Pesan akan dicari dalam perangkat terlebih dahulu. Akan ada tombol aksi dengan ikon cari lagi di paling bawah untuk meneruskan pencarian di server. Anda dapat memilih folder mana untuk meneruskan pencarian tersebut.
-The IMAP protocol doesn't support searching in more than one folder at the same time. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
+The IMAP protocol doesn't support searching in more than one folder at the same time. Pencarian dalam server merupakan operasi yang mahal, maka dari itu tidak mungkin bisa memilih lebih dari satu folder.
-Searching local messages is case insensitive and on partial text. The message text of local messages will not be searched if the message text was not downloaded yet. Searching on the server might be case sensitive or case insensitive and might be on partial text or whole words, depending on the provider.
+Searching local messages is case insensitive and on partial text. Teks pesan dari pesan lokal tidak akan dicari jika teks tersebut belum terlebih dahulu diunduh. Pencarian di server mungkin akan menyebabkan sensitif akan kata atau tidak dan mungkin akan pada sebagian teks atau seluruh kata, tergantung dari penyedia.
-Some servers cannot handle searching in the message text when there are a large number of messages. For this case there is an option to disable searching in the message text.
+Sebagian server tidak dapat menangani pencarian dalam teks pesan jika terdapat pesan dalam jumlah yang banyak. Untuk hal ini, terdapat opsi untuk menonaktifkan pencarian di dalam teks pesan.
-It is possible to use Gmail search operators by prefixing a search command with *raw:*. If you configured just one Gmail account, you can start a raw search directly on the server by searching from the unified inbox. If you configured multiple Gmail accounts, you'll first need to navigate to the folder list or the archive (all messages) folder of the Gmail account you want to search in. Please [see here](https://support.google.com/mail/answer/7190) for the possible search operators. For example:
+It is possible to use Gmail search operators by prefixing a search command with *raw:*. If you configured just one Gmail account, you can start a raw search directly on the server by searching from the unified inbox. If you configured multiple Gmail accounts, you'll first need to navigate to the folder list or the archive (all messages) folder of the Gmail account you want to search in. Sila [lihat di sini](https://support.google.com/mail/answer/7190) untuk operator pencarian yang memungkinkan. Sebagai contoh:
`
raw:larger:10M`
-Searching through a large number of messages on the device is not very fast because of two limitations:
+Pencarian diantara pesan dengan jumlah yang banyak di dalam perangkat akan memakan waktu yang lama karena dua limitasi:
-* [sqlite](https://www.sqlite.org/), the database engine of Android has a record size limit, preventing message texts from being stored in the database
-* Android apps get only limited memory to work with, even if the device has plenty memory available
+* [sqlite](https://www.sqlite.org/), mesin database Android memiliki batasan ukuran rekaman yang mencegaj teks pesan disimpan di dalam database
+* Aplikasi Andorid hanya mendapatkan memori yang terbatas untuk bekerja, bahkan ketika peangkat tersebut memiliki banyak memori yang masih tersedia
-This means that searching for a message text requires that files containing the message texts need to be opened one by one to check if the searched text is contained in the file, which is a relatively expensive process.
+Hal ini berarti pencarian pesan teks memerlukan berkas tersebut yang memiliki pesan teks harus dibuka satu per satu untuk memeriksa apakah teks yang dicari terdapat di dalam berkas, yang secara relatif merupakan proses yang mahal.
-In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
+Dalam *pengaturan lainnya* anda dapat mengaktifkan *Buat indeks pencarian* untuk meningkatkan kecepatan pencarian dalam perangkat secara signifikan, namun berhati-hatilah bahwa hal ini akan meningkatkan penggunaan bateraidan kapasitas penyimpanan. Pencarian indeks didasarkan oleh kata, maka pencarian untuk sebagian teks tidak memungkinkan. Mencari dengan menggunakan indeks pencarian dilakukan dengan DAN standar, maka pencarian untuk *apel jeruk* akan menghasilkan pencarian untuk apel DAN jeruk. Kata yang dipisahkan dengan koma akan menghasilkan pencarian untuk ATAU, maka contohnya seperti *apel, jeruk* akan menghasilkan pencarian untuk apel ATAU jeruk. Keduanya dapat digabungkan, maka pencarian untuk *apel, jeruk pisang* akan mengahsilkan pencarian untuk apel ATAU (jeruk DAN pisang). Penggunaan indeks pencarian merupakan fitur yang dimiliki pro.
-From version 1.1315 it is possible to use search expressions like this:
+Dari versi 1.1315, hal ini memungkinkan untuk menggunakan ekspresi pencarian seperti:
```
-apple +banana -cherry ?nuts
+apel +pisang -ceri ?kacang
```
-This will result in searching like this:
+Hal ini akan menghasilkan pencarian seperti:
```
-("apple" AND "banana" AND NOT "cherry") OR "nuts"
+("apel" DAN "pisang" DAN TIDAK "ceri") ATAU "kacang"
```
-Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
+Ekspresi pencarian dapat digunakan untuk mencari dalam perangkat melalui pencarian indeks dan untuk pencarian dalam server surel, namun tidak untuk pencarian dalam perangkat tanpa indeks pencarian untuk alasan performa.
-Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
+Pencarian dalam perangkat adalah fitur gratis, menggunakan indeks pencarian dan mencari dalam server adalah fitur yang dimiliki pro.
-**(14) How can I set up an Outlook / Live / Hotmail account?**
+**(14) Bagaimana cara saya mengatur akun Outlook / Live / Hotmail?**
-An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
+Akun Outlook / Live / Hotmail dapat diatur melalui wizard pengaturan cepat dan pilih *Outlook*.
-To use an Outlook, Live or Hotmail account with two factor authentication enabled, you need to create an app password. See [here](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-passwords-two-step-verification) for the details.
+Untu menggunakan akun Outlook, Live atau Hotmail dengan autentikasi dua faktor yang aktif, anda perlu membuat kata sandi aplikasi. Lihat [di sini](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-passwords-two-step-verification) untuk lebih lanjut.
-See [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for Microsoft's instructions.
+Lihat [di sini](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) untuk instruksi dari Microsoft.
-For setting up an Office 365 account, please see [this FAQ](#user-content-faq156).
+Untuk mengatur akun Office 365, sila lihat [FAQ ini](#user-content-faq156).
-**(15) Why does the message text keep loading?**
+**(15) Mengapa teks pesan terus menerus dimuat?**
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and will be fetched on demand on expanding a message. The message text will keep loading if there is no connection to the account, see also the next question, or if there other operations, like synchronizing messages, are being executed.
@@ -752,110 +752,110 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
-**(16) Why are messages not being synchronized?**
+**(16) Mengapa pesan tidak tersingkronisasi?**
-Possible causes of messages not being synchronized (sent or received) are:
+Kemungkinan penyebab yang membuat pesan tidak tersingkronisasi (terkirim atau diterima) adalah:
-* The account or folder(s) are not set to synchronize
-* The number of days to synchronize message for is set too low
-* There is no usable internet connection
-* The email server is temporarily not available
-* Android stopped the synchronization service
+* Kaun atau folder tidak diatur untuk singkronisasi
+* Jumlah hari untuk mensingkronisasi pesan ditetapkan teralu pendek
+* Tidak ada koneksi internet yang dapat digunakan
+* Server surel yang tidak tersedia pada saat itu
+* Android memberhentikan pelayanan singkronisasi
-So, check your account and folder settings and check if the accounts/folders are connected (see the legend in the navigation menu for the meaning of the icons).
+Maka, peruka akun dan pengaturan folder anda dan periksa juga apakah folder akun anda terkoneksi (lihat legenda di menu navigasi untuk arti dari ikon-ikon).
-If there are any error messages, please see [this FAQ](#user-content-faq22).
+Jika ada pesan eror, sila lihat [FAQ ini](#user-content-faq22).
-On some devices, where there are lots of applications competing for memory, Android may stop the synchronization service as a last resort.
+Dalam beberapa perangkat, yang terdapat banyak aplikasi yang bersaing untuk menggunakan memori, Android akan memberhentikan pelayanan singkronisasi sebagai langkah terakhir.
-Some Android versions stop apps and services too aggressively. See [this dedicated website](https://dontkillmyapp.com/) and [this Android issue](https://issuetracker.google.com/issues/122098785) for more information.
+Sebagian versi Andorid mematikan aplikasi dan pelayanan secra agresif. Lihat [situs web khusus ini](https://dontkillmyapp.com/) dan [isu Android ini](https://issuetracker.google.com/issues/122098785) untuk informasi lebih lanjut.
-Disabling battery optimizations (setup step 4) reduces the chance Android will stop the synchronization service.
+Menonaktifkan optimisasi baterai (pengaturan langkah 4) akan mengurangi kesempakan Android yang akan memberhentikan layanan singkronisasi.
-**~~(17) Why does manual synchronize not work?~~**
+**~~(17) Mengapa singkronisasi manual tidak bekerja?~~**
-~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
+~~Jika menu *Singkronisasi sekarang* terlihat redup, maka tidak terdapat koneksi ke akun.~~
-~~See the previous question for more information.~~
+~~Sila lihat pertanyaan sebelumnya untuk informasi lebih lanjut.~~
-**(18) Why is the message preview not always shown?**
+**(18) Mengapa tampilan pesan tidak selalu terlihat?**
-The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
+Tampilan teks pesan tidak dapat ditampilkan jika isi pesan tersebut belum diunduh. Lihat juga [FAQ ini](#user-content-faq15).
-**(19) Why are the pro features so expensive?**
+**(19) Mengapa fitur pro sangat mahal?**
-The right question is "*why are there so many taxes and fees?*":
+Pertanyaan yang benar adalah '*mengapa terdapat banyak pajak dan biaya?*":
-* VAT: 25 % (depending on your country)
-* Google fee: 30 %
-* Income tax: 50 %
-* Paypal fee: 5-10 % depending on the country/amount
+* PPN: 25% (tergantung masing-masing negara)
+* Biaya Google: 30 %
+* Pajak penghasilan: 50 %
+* Biaya PayPal: 5-10 % tergantung dari masing-masing negara/jumlah
-So, what is left for the developer is just a fraction of what you pay.
+Maka, yang tersisa untuk developer hanya sebagian dari yang anda bayar.
-Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
+Perhatikan bahwa hanya sebagian fitur yang nyaman dan canggih harus dibeli, artinya FairEmail sebenarnya gratis untuk digunakan.
-Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
+Perhatikan juga bahwa sebagian besar aplikasi yang gratis akan terlihat tidak berkelanjutan di akhir, sedangkan FairEmail dikelola dan didukung dengan benar, dan aplikasi gratis tersebut mungkin tidak aman, seperti megirimkan informasi sensitif ke internet.
-I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
+Saya telah mengerjakan FairEmail hampir setiap hai selama lebih dari dua tahun, maka menurut saya harga tersebut masih masuk akal. Untuk alasan ini juga tidak akan ada diskon.
-**(20) Can I get a refund?**
+**(20) Apakah dana saya dapat dikembalikan?**
-If a purchased pro feature doesn't work as intended and this isn't caused by a problem in the free features and I cannot fix the problem in a timely manner, you can get a refund. In all other cases there is no refund possible. In no circumstances there is a refund possible for any problem related to the free features, since there wasn't paid anything for them and because they can be evaluated without any limitation. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
+Jika fitur pro yang telah dibeli tidak bekerja seperti yang seharusnya dan hal ini tidak disebabkan oleh masalah yang ada di fitur gratis dan saya tidak dapat memperbaiki masalah tersebut secepat mungkin, dana anda akan dikembalikan. Dalam kasus lainnya, mungkin tidak akan ada pengembalian dana. Dalam keadaan apa pun, tidak ada pengembalian dana untuk masalah apa pun yang terkait dengan fitur gratis, karena fitur tersebut tidak memiliki bayaran apa pun dan dapat dievaluasi tanpa batasan apa pun. Saya bertanggung jawab sebagai penjual untuk memberikan apa yang telah saya janjikan dan saya harap anda bertanggung jawab untu mengetahui dengan jelas apa yang anda beli.
-**(21) How do I enable the notification light?**
+**(21) Bagaimana cara saya mengaktifkan lampu notifikasi?**
-Before Android 8 Oreo: there is an advanced option in the setup for this.
+Sebelum Android 8 Oreo: terdapat opsi tingkat lanjut dalam pengaturan untuk hal terkait.
-Android 8 Oreo and later: see [here](https://developer.android.com/training/notify-user/channels) about how to configure notification channels. You can use the button *Manage notifications* in the setup to directly go to the Android notification settings. Note that apps cannot change notification settings, including the notification light setting, on Android 8 Oreo and later anymore. Apps designed and targeting older Android versions might still be able to control the contents of notifications, but such apps cannot be updated anymore and recent Android versions will show a warning that such apps are outdated.
+Android 8 Oreo sampai yang terbaru: lihat [di sini](https://developer.android.com/training/notify-user/channels) untuk mengetahui tentang mengkonfigurasi channel notifikasi. Anda dapat menggunakan tombom *Kelola notifikasi* pada bagian pengaturan untuk langsung menuju ke pengaturan notifikasi Andorid. Perhatikan bahwa aplikasi sudah tidak dapat mengubah pengaturan notifikasi, termasuk pengaturan lampu notifikasi, dalam Android 8 Oreo sampai yang terbaru lagi. Aplikasi yang didesain dan ditargetkan ke versi Android yang lebih lama mungkin dapat mengkontrol isi dari notifikasi, namun aplikasi tersebut tidak dapat diperbarui lagi dan versi Android yang terbaru akan menampilkan peringatan bahwa aplikasi tersebut telah kadaluwarsa.
-Sometimes it is necessary to disable the setting *Show message preview in notifications* or to enable the settings *Show notifications with a preview text only* to workaround a bug in Android. This might apply to notification sounds and vibrations too.
+Beberapa kali, penting halnya untuk menonaktifkan pengaturan *Lihat tampilan pesan di notifikasi* atau mengaktifkan pengaturan *Tampilkan notifikasi hanya adengan tampilan pesan saja* untuk memperbaiki bug di Android. Hal ini juga akan diterapkan ke suara dan getaran notifikasi.
-Setting a light color before Android 8 is not supported and on Android 8 and later not possible.
+Pengaturan warna lampu tidak terdukung di versi Andorid sebelum Android 8 dan tidak memungkinkan pada versi Andorid 8 sampai yang terbaru.
-**(22) What does account/folder error ... mean?**
+**(22) Apa yang dimaksud dengan akun/folder eror ... ?**
-FairEmail does not hide errors like similar apps often do, so it is easier to diagnose problems.
+FairEmail tidak menyembunyikan eror seperti aplikasi sejenis lainnya, maka mudah untuk anda mendiagnosa masalah yang terjadi.
-FairEmail will automatically try to connect again after a delay. This delay will be doubled after each failed attempt to prevent draining the battery and to prevent from being locked out permanently.
+FairEmail akan secara otomatis mencoba untuk menyambungkan lagi setelah menunda. Penundaan ini akan digandakan setelah setiap usaha yang gagal untuk menghindari menghabiskan baterai dan terkunci secara permanen.
-There are general errors and errors specific to Gmail accounts (see below).
+Terdapat eror umum dan spesifik untuk akun Gmail (lihat dibawah).
-**General errors**
+**Eror Umum**
-The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
+The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Sebagian penyedia mengharapkan nama pengguna anda hanyalah *nama pengguna* dan lainnya adalah alamat surel lengkap anda *namapengguna@contoh.com*. Ketika menyalin/menempel untuk mengisi nama pengguna atau kata sandi, karakter yang tidak terlihat dapat juga tersalin yang akan mengakibatkan masalah ini juga. Beberapa pengelola kata sandi juga terkenal untuk memiliki kesalahan ini. Nama pengguna mungkin sensitif dengan penggunaan huruf, maka coba hanya gunakan huruf kecil saja. Kata sandi hampir selalu sensitif drngan penggunaan huruf. Sebagian penyedia memerlukan pengunaan aplikasi kata sandi dibandingkan dengan kata sandi akun, maka sila periksa dokumentasi dari penyedia tersebut. Terkadang, mengaktifkan akses eksternal (IMAP/SMTP) dalam situs web dari penyedia tersebut terlebih dahulu merupakan hal yang penting. Penyebab lainnya yang mungkin terjadi adalah akun terblokir atau anda telah dilarang secara administratif untuk masuk dalam beberapa hal, seperti contoh ketika hanya mengizinkan untuk masuk dari jaringan / alamat IP tertentu.
-The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
+The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Sila lihat [FAQ ini](#user-content-faq88) tentang bagaimana caranya untuk mengatur akun Yahoo.
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
The errors *... invalid greeting ...*, *... requires valid address ...* and *... Parameter to HELO does not conform to RFC syntax ...* can likely be solved by changing the advanced identity setting *Use local IP address instead of host name*.
-The error *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
+The error *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Seringkali menandakan adanya masalah sambungan internet, mungkin disebabkan oleh VPN atau aplikasi firewall. Anda dapat meningkatkan waktu habis koneksi pada bagian pengaturan koneksi dari FairEmail, untuk ketika server surel sangat lambat.
The error *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
The error *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
-The error *... Host is unresolved ...* or "*... Unable to resolve host ...* means that the address of the email server could not be resolved. This might be caused by ad blocking or an unreachable or not properly working [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
+The error *... Host is unresolved ...* or "*... Unable to resolve host ...* means that the address of the email server could not be resolved. Hal ini dapat diakibatkan oleh blokir iklan atau server [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) yang tidak terhubung atau tidak bekerja dengan baik.
-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 error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. Hal ini dapat terjadi, contohnya, jika sambungan telah tersesat. Contoh yang sering terjadi adalah menyalakan mode pesawat.
The errors *... BYE Logging out ...*, *... Connection reset by peer ...* mean that the email server actively terminated an existing connection.
@@ -867,7 +867,7 @@ The error *... Unexpected end of zlib input stream ...* means that not all data
The error *... connection failure ...* could indicate [Too many simultaneous connections](#user-content-faq23).
-The warning *... Unsupported encoding ...* means that the character set of the message is unknown or not supported. FairEmail will assume ISO-8859-1 (Latin1), which will in most cases result in showing the message correctly.
+The warning *... Unsupported encoding ...* means that the character set of the message is unknown or not supported. FairEmail akan mengasumsikan ISO-8859-1 (Latin1), yang sering kali akan menghasilkan tampilan pesan dengan benar.
Please [see here](#user-content-faq4) for the errors *... Untrusted ... not in certificate ...*, *... Invalid security certificate (Can't verify identity of server) ...* or *... Trust anchor for certification path not found ...*
@@ -877,215 +877,215 @@ Please [see here](#user-content-faq41) for the error *... Handshake failed ...*.
See [here](https://linux.die.net/man/3/connect) for what error codes like EHOSTUNREACH and ETIMEDOUT mean.
-Possible causes are:
+Kemungkinan disebabkan karena:
-* A firewall or router is blocking connections to the server
-* The host name or port number is invalid
-* Ada masalah dengan koneksi internet
-* Ada masalah dengan menyelesaikan nama domain (Yandex: coba nonaktifkan DNS pribadi di pengaturan Android)
+* Firewall atau router memblok koneksi ke server
+* Nama host atau nomor port yang tidak valid
+* Terdapat masalah dengan koneksi internet
+* Terdapat masalah dengan menyelesaikan nama domain (Yandex: coba nonaktifkan DNS pribadi di pengaturan Android)
* Server email menolak untuk menerima koneksi (eksternal)
* Server email menolak untuk menerima pesan, misalnya karena terlalu besar atau berisi tautan yang tidak dapat diterima
* Ada terlalu banyak koneksi ke server, lihat juga pertanyaan berikutnya
-Many public Wi-Fi networks block outgoing email to prevent spam. Sometimes you can workaround this by using another SMTP port. See the documentation of the provider for the usable port numbers.
+Banyak jaringan Wi-Fi publik memblokir surel yang keluar untuk mencegah spam. Terkadang anda dapat menyelesaikan masalah ini dengan menggunakan pory SMTP lainnya. Lihat dokumentasi dari penyedia untuk melihat nomor port yang dapat digunakan.
-If you are using a [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), the VPN provider might block the connection because it is too aggressively trying to prevent spam. Note that [Google Fi](https://fi.google.com/) is using a VPN too.
+Jika anda menggunakan [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), penyedia VPN tersebut mungkin memblokir koneksi karena hal tersebut mencoba untuk mengurangi spam secara agresif. Perhatikan bahwa [Google Fi](https://fi.google.com/) juga menggunakan VPN.
-**Send errors**
+**Eror Pengiriman**
-SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes). Too large messages and triggering the spam filter of an email server are the most common reasons.
+Server SMTP dapat menolak pesan karena [berbagai alasan](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes). Pesan yang telalu besar dan memicu saringan spam dari server surel adalah alasan yang paling sering ditemukan.
-* The attachment size limit for Gmail [is 25 MB](https://support.google.com/mail/answer/6584)
-* The attachment size limit for Outlook and Office 365 [is 20 MB](https://support.microsoft.com/en-us/help/2813269/attachment-size-exceeds-the-allowable-limit-error-when-you-add-a-large)
-* The attachment size limit for Yahoo [is 25 MB](https://help.yahoo.com/kb/SLN5673.html)
+* Batas ukuran lampiran untuk Gmail adalah [25 MB](https://support.google.com/mail/answer/6584)
+* Bata ukuran lampiran untuk Outlook dan Office 365 [adalah 20 MB](https://support.microsoft.com/en-us/help/2813269/attachment-size-exceeds-the-allowable-limit-error-when-you-add-a-large)
+* Batas ukuran lampiran untuk Yahoo [adalah 25MB](https://help.yahoo.com/kb/SLN5673.html)
* *554 5.7.1 Service unavailable; Client host xxx.xxx.xxx.xxx blocked*, please [see here](https://docs.gandi.net/en/gandimail/faq/error_types/554_5_7_1_service_unavailable.html)
* *501 Syntax error - line too long* is often caused by using a long Autocrypt header
* *503 5.5.0 Recipient already specified* mostly means that an address is being used both as TO and CC address
-* *554 5.7.1 ... not permitted to relay* means that the email server does not recognize the username/email address. Please double check the host name and username/email address in the identity settings.
+* *554 5.7.1 ... not permitted to relay* means that the email server does not recognize the username/email address. Sila periksa lagi nama host dan nama pengguna/alamat surel pada pengaturan identitas.
-**Gmail errors**
+**Eror Gmail**
-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.
+Pengaturan otorisasi akun Gmail dengan wizard cepat perlu disegarkan secara periodik melalui [pengelola akun Andorid](https://developer.android.com/reference/android/accounts/AccountManager). Hal ini memerlukan izin kontak/akun dan jaringan internet.
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
-The error *... Authentication failed ... Invalid credentials ...* could be caused by having revoked the required account/contacts permissions. Just start the wizard (but do not select an account) to grant the required permissions again.
+The error *... Authentication failed ... Invalid credentials ...* could be caused by having revoked the required account/contacts permissions. Hanya perlu memulai wizard lagi (maun jangan pilih akun) untuk memberikan izin yang diperlukan.
The eror *... ServiceDisabled ...* might be caused by enrolling in the [Advanced Protection Program](https://landing.google.com/advancedprotection/): "*To read your email, you can (must) use Gmail - You won’t be able to use your Google Account with some (all) apps & services that require access to sensitive data like your emails*", see [here](https://support.google.com/accounts/answer/7519408?hl=en&ref_topic=9264881).
-When in doubt, you can ask for [support](#user-content-support).
+Jika anda ragu, anda dapat bertanya di [bantuan](#user-content-support).
-**(23) Why do I get alert ... ?**
+**(23) Mengapa saya mendapatkan tanda ..?**
-*General*
+*Umum*
-Alerts are warning messages sent by email servers.
+Alert adalah pesan peringatan yang dikirimkan oleh server surel.
-*Too many simultaneous connections* or *Maximum number of connections exceeded*
+*Terlalu banyak koneksi secara serentak* atau *Koneksi maksimum terlampaui*
-This alert will be sent when there are too many folder connections for the same email account at the same time.
+Alert ini akan terkirim ketika terdapat terlalu banyak koneksi folder untuk akun surel yang sama secara bersamaan.
-Possible causes are:
+Kemungkinan disebabkan karena:
-* There are multiple email clients connected to the same account
-* The same email client is connected multiple times to the same account
-* Previous connections were terminated abruptly for example by abruptly losing internet connectivity
+* Terdapat lebih dari satu surel klien yang terhubung dengan akun yang sama
+* Surel klien yang sama terkoneksi lebih dari satu kali ke akun yang sama
+* Koneksi sebelumnya telah diberhentikan secara tiba-tiba karena contohnya tiba-tiba kehilangan jaringan internet
-First try to wait some time to see if the problem resolves itself, else:
+Pertama, coba tunggu beberap saat untuk melihat apakah masalah tersebut akan selesai dengan sendirinya, atau:
-* either switch to periodically checking for messages in the receive settings, which will result in opening folders one at a time
-* or set some folders to poll instead of synchronize (long press folder in the folder list, edit properties)
+* pindah ke pemeriksaan secara periodik untuk pesan salam pengaturan penerimaan, yang akan menghasilkan folder untuk terbuka satu per satu
+* atau atur beberapa folder untuk pilihan dibandingkan dengan sinkronisasi (tekan dengan lama pada folder dalam daftar folder, sunting properti)
-The maximum number of simultaneous folder connections for Gmail is 15, so you can synchronize at most 15 folders simultaneously on *all* your devices at the same time. For this reason Gmail *user* folders are set to poll by default instead of synchronize always. When needed or desired, you can change this by long pressing a folder in the folder list and selecting *Edit properties*. See [here](https://support.google.com/mail/answer/7126229) for details.
+Jumlah maksimal koneksi folder secara bersamaan untuk Gmail adalah 15, maka anda dapat mengsingkronkan 15 folder paling banyak secara sekaligus ke *seluruh* perangkat anda dalam waktu yang bersamaan. Karena alasan ini maka folder *pengguna* Gmail telah diatur sebagai pilihan secara otomatis dibandingkan dengan selalu disingkronasi. Jika diperlukan atau diinginkan, anda dapat mengubahnya dengan menekan lama pada folder ddi daftar folder dan pilih *Sunting properti*. Lihat [di sini](https://support.google.com/mail/answer/7126229) untuk lebih lanjut.
When using a Dovecot server, you might want to change the setting [mail_max_userip_connections](https://doc.dovecot.org/settings/dovecot_core_settings/#mail-max-userip-connections).
-**(24) What is browse messages on the server?**
+**(24) Apa itu telusuri pesan di server?**
-Browse messages on the server will fetch messages from the email server in real time when you reach the end of the list of synchronized messages, even when the folder is set to not synchronize. You can disable this feature in the advanced account settings.
+Browse messages on the server will fetch messages from the email server in real time when you reach the end of the list of synchronized messages, even when the folder is set to not synchronize. Anda dapat menonaktifkan fitur ini dalam pengaturan akun tingkat lanjut.
-**(25) Why can't I select/open/save an image, attachment or a file?**
+**(25) Mengapa saya tidak dapat memilih/membuka/menyimpan gambar, lampiran atau berkas?**
-When a menu item to select/open/save a file is disabled (dimmed) or when you get the message *Storage access framework not available*, the [storage access framework](https://developer.android.com/guide/topics/providers/document-provider), a standard Android component, is probably not present. This might be because your custom ROM does not include it or because it was actively removed (debloated).
+Ketika menu item untuk memilih/membuka/menyimpan berkas tidak diaktifkan (redup) atau ketika anda mendapatkan pesan *Framework akses penyimpanan tidak tersedia*, [Framework akses penyimpanan](https://developer.android.com/guide/topics/providers/document-provider), komponen standar dari Andorid, mungkin tidak ada. Hal ini dapat disebabkan karena tidak termasuk ke dalam kustom ROM anda atau karena telah dihapus (dimatikan).
-FairEmail does not request storage permissions, so this framework is required to select files and folders. No app, except maybe file managers, targeting Android 4.4 KitKat or later should ask for storage permissions because it would allow access to *all* files.
+FairEmail tidak meminta izin penyimpanan, maka framework ini akan membutuhkan untuk memilih berkas dan folder. Tidak ada aplikasi, kecuali mungkin pengelola berkas, yang ditargetkan ke Android 4.4 KitKat sampai dengan yang terbaru bertanya yentang izin penyimpanan karena hal ini akan mengizinkan akses ke *seluruh* berkas.
The storage access framework is provided by the package *com.android.documentsui*, which is visible as *Files* app on some Android versions (notable OxygenOS).
-You can enable the storage access framework (again) with this adb command:
+Anda dapat mengaktifkan framework akses penyimpanan (kembali) dengan perintah adb:
```
pm install -k --user 0 com.android.documentsui
```
-Alternatively, you might be able to enable the *Files* app again using the Android app settings.
+Secara alternatif, anda dapat mengaktifkan aplikasi *Berkas* kembali menggunakan pengaturan aplikasi Android.
-**(26) Can I help to translate FairEmail in my own language?**
+**(26) Apakah saya dapat membantu menerjemahkan FairEmail ke dalam bahasa saya?**
-Yes, you can translate the texts of FairEmail in your own language [on Crowdin](https://crowdin.com/project/open-source-email). Registration is free.
+Iya, anda dapat menerjemahkan teks FairEmail ke dalam bahasa anda [di Crowdin](https://crowdin.com/project/open-source-email). Pendaftaran gratis.
-If you would like your name or alias to be included in the list of contributors in *About* the app, please [contact me](https://contact.faircode.eu/?product=fairemailsupport).
+Jika anda menginginkan nama atau alias anda ingin dimasukkan ke dalam daftar kontribusi dalam *Tentang* di aplikasi, sila [hubungi saya](https://contact.faircode.eu/?product=fairemailsupport).
-**(27) How can I distinguish between embedded and external images?**
+**(27) Bagaimana cara saya membedakan gambar yang tertanam dan eksternal?**
-External image:
+Gambar eksternal:
-
+
-Embedded image:
+Gambar tersemat:
-
+
-Broken image:
+Gambar rusak:
-
+
-Note that downloading external images from a remote server can be used to record you did see a message, which you likely don't want if the message is spam or malicious.
+Perhatikan bahwa gambar eksternal yang diunduh dari server jarak jauh dapat digunakan untuk merekam dalam pesan anda lihat, yang anda akan tidak mau jika pesan tersebut adalah spam atau berbahaya.
-**(28) How can I manage status bar notifications?**
+**(28) Bagaimana cara saya mengelola status bilah notifikasi?**
-In the setup you'll find a button *Manage notifications* to directly navigate to the Android notifications settings for FairEmail.
+Dalam pengaturan anda akan menemukan tombol *Kelola notifikasi* untuk menavigasi secara langsung ke pengaturan notifikasi Android untuk FairEmail.
-On Android 8.0 Oreo and later you can manage the properties of the individual notification channels, for example to set a specific notification sound or to show notifications on the lock screen.
+Pada Android 8.0 Oreo sampai yang terbaru, anda dapat mengelola properti dari channel notifikasi secara individual, sebagai contoh untuk mengatur suara notifikasi secara spesifik atau untuk menampilkan notifikasi di layar kunci.
-FairEmail has the following notification channels:
+FairEmail memiliki channel notifikasi seperti dibawah ini:
-* Service: used for the notification of the synchronize service, see also [this FAQ](#user-content-faq2)
-* Send: used for the notification of the send service
-* Notifications: used for new message notifications
-* Warning: used for warning notifications
-* Error: used for error notifications
+* Layanan: digunakan untuk notifikasi dari layanan singkronisasi, lihat juga [FAQ ini](#user-content-faq2)
+* Kirim: digunakan untuk notifikasi untuk layanan pengiriman
+* Notifikasi: digunakan untuk notifikasi pesan baru
+* Peringatan: digunakan untuk notifikasi peringatan
+* Eror: digunakan untuk notifikasi eror
-See [here](https://developer.android.com/guide/topics/ui/notifiers/notifications#ManageChannels) for details on notification channels. In short: tap on the notification channel name to access the channel settings.
+Lihat [di sini](https://developer.android.com/guide/topics/ui/notifiers/notifications#ManageChannels) untuk rincian channel notifikasi. Secara singkat: tekan nama notifikasi channel untuk mengakes pengaturan channel.
-On Android before Android 8 Oreo you can set the notification sound in the settings.
+Pada Andorid sebelum Android 8 Oreo anda dapat mengatur suara notifikasi di pengaturan.
-See [this FAQ](#user-content-faq21) if your device has a notification light.
+Lihat [FAQ ini](#user-content-faq21) jika perangkat anda memiliki lampu notifikasi.
-**(29) How can I get new message notifications for other folders?**
+**(29) Bagaiman cara saya mendapatkan notifikasi pesan baru dari folder lainnya?**
-Just long press a folder, select *Edit properties*, and enable either *Show in unified inbox* or *Notify new messages* (available on Android 7 Nougat and later only) and tap *Save*.
+Hanya perlu menekan folder dengan lama, pilih *Sunting properti*, dan aktifkan *Tampilkan kotak masuk terpadu* atau *Notifikasi pesan baru* (hanya tersedia di Android 7 Nougat sampai yang terbaru) dan tekan *Simpan*.
-**(30) How can I use the provided quick settings?**
+**(30) bagaimana cara saya menggunakan pengaturan cepat yang tersedia?**
-There are quick settings (settings tiles) available to:
+Terdapat pengaturan cepat (menu tile) yang tersedia untuk:
-* globally enable/disable synchronization
-* show the number of new messages and marking them as seen (not read)
+* mengaktifkan/menonaktifkan singkronisasi secara global
+* menampilkan jumlah pesan baru dan menandai pesan tersebut sebagai terlihat (bukan dibaca)
-Quick settings require Android 7.0 Nougat or later. The usage of settings tiles is explained [here](https://support.google.com/android/answer/9083864).
+Pengaturan cepat membutuhkan Android 7.0 Nougat sampai yang terbaru. Penggunaan pengaturan tiles dijelaskan [di sini](https://support.google.com/android/answer/9083864).
-**(31) How can I use the provided shortcuts?**
+**(31) Bagaimana cara saya menggunakan shortcut yang tersedia?**
-There are shortcuts available to:
+Terdapat jalan pintas yang tersedia untuk:
-* compose a new message to a favorite contact
-* setup accounts, identities, etc
+* membuat pesan baru untuk kontak favorit
+* mengatur akun, identitas, dll
-Shortcuts require Android 7.1 Nougat or later. The usage of shortcuts is explained [here](https://support.google.com/android/answer/2781850).
+Jalan pintas membutuhkan Android 7.1 Nougat sampai dengan yang terbaru. Penggunaan jalan pintas dijelaskan [di sini](https://support.google.com/android/answer/2781850).
-**(32) How can I check if reading email is really safe?**
+**(32) Bagaimana cara saya memeriksa jika membaca pesan ini aman?**
-You can use the [Email Privacy Tester](https://www.emailprivacytester.com/) for this.
+Anda dapat menggunakan [Penguji Privasi Surel](https://www.emailprivacytester.com/) untuk hal ini.
-**(33) Why are edited sender addresses not working?**
+**(33) Mengapa alamat pengirim yang telah disunting tidak dapat bekerja?**
-Most providers accept validated addresses only when sending messages to prevent spam.
+Kebanyakan provider menerima alamat yang valid hanya ketika megirimkan pesan untuk menghindari spam.
-For example Google modifies the message headers like this for *unverified* addresses:
+Contohnya Google memodifikasi header pesan seperti ini untuk alamat *yang tidak terverifikasi*:
```
-From: Somebody
-X-Google-Original-From: Somebody
+Dari: Seseorang
+X-Google-Orisinal-Dari: Seseorang
```
-This means that the edited sender address was automatically replaced by a verified address before sending the message.
+Hal ini berarti alamat pengirim yang telah tersunting telah digantkan secara otomatis dengan alamat yang diverifikasi sebelum mengirim pesan.
-Note that this is independent of receiving messages.
+Perhatikan bahwa ini adalah cara menerima pesan yang independen.
-**(34) How are identities matched?**
+**(34) Bagaimana identitas cocok?**
-Identities are as expected matched by account. For incoming messages the *to*, *cc*, *bcc*, *from* and *(X-)delivered/envelope/original-to* addresses will be checked (in this order) and for outgoing messages (drafts, outbox and sent) only the *from* addresses will be checked.
+Indentitas dapat dicocokan seperti yang diharapkan dengan akun. Untuk pesan yang masuk *kepada*, *cc*, *bcc*, *dari* dan *(X-)dikirimkan/pesan/orisinal-ke* alamat akan diperiksa (dengan urutan yang telah disebutkan) dan untuk pesan keluar (draf, pesan keluar dan terkirim) hanya dalam *bentuk* alamat yang akan diperiksa.
The matched address will be shown as *via* in the addresses section of received messages (between the message header and message text).
@@ -1114,7 +1114,7 @@ Matched identities can be used to color code messages. The identity color takes
-**(35) Why should I be careful with viewing images, attachments, and the original message?**
+**(35) Mengapa saya harus berhati-hati dalam melihat gambar, lampiran dan pesan orisinil?**
Viewing remotely stored images (see also [this FAQ](#user-content-faq27)) might not only tell the sender that you have seen the message, but will also leak your IP address.
@@ -1135,7 +1135,7 @@ If you want to reset the default *Open with* apps, please [see here](https://www
-**(36) How are settings files encrypted?**
+**(36) Bagaimana pegaturan berkas terenkripsi?**
Short version: AES 256 bit
@@ -1147,7 +1147,7 @@ Long version:
-**(37) How are passwords stored?**
+**(37) Bagaimana kata sandi disimpan?**
All supported Android versions [encrypt all user data](https://source.android.com/security/encryption), so all data, including usernames, passwords, messages, etc, is stored encrypted.
@@ -1156,7 +1156,7 @@ If the device is secured with a PIN, pattern or password, you can make the accou
-**(39) How can I reduce the battery usage of FairEmail?**
+**(39) Bagaimana cara saya mereduksi penggunaan baterai dari FairEmail?**
Recent Android versions by default report *app usage* as a percentage in the Android battery settings screen. **Confusingly, *app usage* is not the same as *battery usage* and is not even directly related to battery usage!** The app usage (while in use) will be very high because FairEmail is using a foreground service which is considered as constant app usage by Android. However, this doesn't mean that FairEmail is constantly using battery power. The real battery usage can be seen by navigating to this screen:
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1207,7 +1207,7 @@ In addition, the trash and spam folders will be automatically set to checking fo
-**(40) How can I reduce the data usage of FairEmail?**
+**(40) Bagaimana cara saya mereduksi penggunaan data dari FairEmail?**
You can reduce the data usage basically in the same way as reducing battery usage, see the previous question for suggestions.
@@ -1245,7 +1245,7 @@ You can use [this website](https://ssl-tools.net/mailservers) or [this website](
-**(42) Can you add a new provider to the list of providers?**
+**(42) Apakah saya dapat menambahkan provider baru dalam daftar provider?**
If the provider is used by more than a few people, yes, with pleasure.
@@ -1278,14 +1278,14 @@ See below about how to contact me.
-**(43) Can you show the original ... ?**
+**(43) Apakah anda dapat menampilkan yang orisinil ... ?**
Show original, shows the original message as the sender has sent it, including original fonts, colors, margins, etc. FairEmail does and will not alter this in any way, except for requesting [TEXT_AUTOSIZING](https://developer.android.com/reference/android/webkit/WebSettings.LayoutAlgorithm), which will *attempt* to make small text more readable.
-**~~(44) Can you show contact photos / identicons in the sent folder?~~**
+**~~(44) Apakah saya dapat menampilkan foto / ikon identitas kontak dari folder terkirim?~~**
~~Contact photos and identicons are always shown for the sender because this is necessary for conversation threads.~~ ~~Getting contact photos for both the sender and receiver is not really an option because getting contact photo is an expensive operation.~~
@@ -1299,7 +1299,7 @@ You'll get the message *This key is not available. To use it, you must import it
-**(46) Why does the message list keep refreshing?**
+**(46) Mengapa daftar pesan saya selalu segarkan?**
If you see a 'spinner' at the top of the message list, the folder is still being synchronized with the remote server. You can see the progress of the synchronization in the folder list. See the legend about what the icons and numbers mean.
@@ -1308,7 +1308,7 @@ The speed of your device and internet connection and the number of days to synch
-**(47) How do I solve the error 'No primary account or no drafts folder' ?**
+**(47) Bagaimana cara saya memperbaiki eror 'Tidak ada akun utama atau tidak ada folder draf' ?**
You'll get the error message *No primary account or no drafts folder* when trying to compose a message while there is no account set to be the primary account or when there is no drafts folder selected for the primary account. This can happen for example when you start FairEmail to compose a message from another app. FairEmail needs to know where to store the draft, so you'll need to select one account to be the primary account and/or you'll need to select a drafts folder for the primary account.
@@ -1319,7 +1319,7 @@ Please see [this FAQ](#user-content-faq141) for some more information.
-**~~(48) How do I solve the error 'No primary account or no archive folder' ?~~**
+**~~(48) Bagaimana cara saya memperbaiki eror 'Tidak ada akun utama atau tidak ada folder arsip' ?~~**
~~You'll get the error message *No primary account or no archive folder* when searching for messages from another app. FairEmail needs to know where to search, so you'll need to select one account to be the primary account and/or you'll need to select a archive folder for the primary account.~~
@@ -1337,14 +1337,14 @@ See also [question 25](#user-content-faq25) and [what Google writes about it](ht
-**(50) Can you add an option to synchronize all messages?**
+**(50) Apakah saya dapat menambahkan opsi singkronisasikan seluruh pesan?**
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.
-**(51) How are folders sorted?**
+**(51) Bagaimana folder disusun?**
Folders are first sorted on account order (by default on account name) and within an account with special, system folders on top, followed by folders set to synchronize. Within each category the folders are sorted on (display) name. You can set the display name by long pressing a folder in the folder list and selecting *Edit properties*.
@@ -1353,7 +1353,7 @@ The navigation (hamburger) menu item *Order folders* in the setup can be used to
-**(52) Why does it take some time to reconnect to an account?**
+**(52) Mengapa membutuhkan beberapa waktu untuk menghubungkan kembali ke akun?**
There is no reliable way to know if an account connection was terminated gracefully or forcefully. Trying to reconnect to an account while the account connection was terminated forcefully too often can result in problems like [too many simultaneous connections](#user-content-faq23) or even the account being blocked. To prevent such problems, FairEmail waits 90 seconds until trying to reconnect again.
@@ -1362,7 +1362,7 @@ You can long press *Settings* in the navigation menu to reconnect immediately.
-**(53) Can you stick the message action bar to the top/bottom?**
+**(53) Apakah saya dapat menempelkan bilah aksi pesan ke paling atas/paling bawah?**
The message action bar works on a single message and the bottom action bar works on all the messages in the conversation. Since there is often more than one message in a conversation, this is not possible. Moreover, there are quite some message specific actions, like forwarding.
@@ -1373,7 +1373,7 @@ Note that there are not many, if any, email apps that display a conversation as
-**~~(54) How do I use a namespace prefix?~~**
+**~~(54) Bagaimana cara saya menggunakan bagian prefiks nama?~~**
~~A namespace prefix is used to automatically remove the prefix providers sometimes add to folder names.~~
@@ -1388,54 +1388,64 @@ Note that there are not many, if any, email apps that display a conversation as
-**(55) How can I mark all messages as read / move or delete all messages?**
+**(55) Bagaimana cara saya menandai semua pesan telah dibaca / memindahkan atau menghapus seluruh pesan?**
You can use multiple select for this. Long press the first message, don't lift your finger and slide down to the last message. Then use the three dot action button to execute the desired action.
-**(56) Can you add support for JMAP?**
+**(56) Apakah anda dapat menambahkan dukungan untuk JMAP?**
There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so it is not worth a lot of effort to add support for this to FairEmail.
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
+
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
-**(58) What does an open/closed email icon mean?**
+**(58) Apa yang dimaksud dengan ikon surel buka/tutup?**
The email icon in the folder list can be open (outlined) or closed (solid):
-
+
Message bodies and attachments are not downloaded by default.
-
+
Message bodies and attachments are downloaded by default.
-**(59) Can original messages be opened in the browser?**
+**(59) Apakah pesan orisinil dapat dibuka di browser?**
For security reasons the files with the original message texts are not accessible to other apps, so this is not possible. In theory the [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider) could be used to share these files, but even Google's Chrome cannot handle this.
-**(60) Did you know ... ?**
+**(60) Tahukah anda ...?**
* Did you know that starred messages can be synchronized/kept always? (this can be enabled in the receive settings)
* Did you know that you can long press the 'write message' icon to go to the drafts folder?
@@ -1457,7 +1467,7 @@ For security reasons the files with the original message texts are not accessibl
-**(61) Why are some messages shown dimmed?**
+**(61) Mengapa terdapat beberapa pesan yang terlihat redup?**
Messages shown dimmed (grayed) are locally moved messages for which the move is not confirmed by the server yet. This can happen when there is no connection to the server or the account (yet). These messages will be synchronized after a connection to the server and the account has been made or, if this never happens, will be deleted if they are too old to be synchronized.
@@ -1489,7 +1499,7 @@ If your provider requires an unsupported authentication method, you'll likely ge
-**(63) How are images resized for displaying on screens?**
+**(63) Bagaimana cara mengubah ukuran gambar untuk ditampilkan di layar?**
Large inline or attached [PNG](https://en.wikipedia.org/wiki/Portable_Network_Graphics) and [JPEG](https://en.wikipedia.org/wiki/JPEG) images will automatically be resized for displaying on screens. This is because email messages are limited in size, depending on the provider mostly between 10 and 50 MB. Images will by default be resized to a maximum width and height of about 1440 pixels and saved with a compression ratio of 90 %. Images are scaled down using whole number factors to reduce memory usage and to retain image quality. Automatically resizing of inline and/or attached images and the maximum target image size can be configured in the send settings.
@@ -1498,7 +1508,7 @@ If you want to resize images on a case-by-case basis, you can use [Send Reduced]
-**~~(64) Can you add custom actions for swipe left/right?~~**
+**~~(64) Apakah anda dapat menambahkan aksi tambahan untuk geser kiri/kanan?~~**
~~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.~~
@@ -1511,21 +1521,21 @@ If you want to resize images on a case-by-case basis, you can use [Send Reduced]
-**(65) Why are some attachments shown dimmed?**
+**(65) Mengapa terdapat beberapa lampiran yang terlihat redup?**
Inline (image) attachments are shown dimmed. [Inline attachments](https://tools.ietf.org/html/rfc2183) are supposed to be downloaded and shown automatically, but since FairEmail doesn't always download attachments automatically, see also [this FAQ](#user-content-faq40), FairEmail shows all attachment types. To distinguish inline and regular attachments, inline attachments are shown dimmed.
-**(66) Is FairEmail available in the Google Play Family Library?**
+**(66) Apakah FairEmail tersedia di Google Play Family Library?**
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.
-**(67) How can I snooze conversations?**
+**(67) Bagaimana cara saya snooze percakapan?**
Multiple select one of more conversations (long press to start multiple selecting), tap the three dot button and select *Snooze ...*. Alternatively, in the expanded message view use *Snooze ...* in the message three-dots 'more' menu or the timelapse action in the bottom action bar. Select the time the conversation(s) should snooze and confirm by tapping OK. The conversations will be hidden for the selected time and shown again afterwards. You will receive a new message notification as reminder.
@@ -1540,7 +1550,7 @@ By selecting a zero snooze duration you can cancel snoozing.
-**~~(68) Why can Adobe Acrobat reader not open PDF attachments / Microsoft apps not open attached documents?~~**
+**~~(68) Mengapa Adobe Acrobat reader tidak membuka lampiran PDF / aplikasi Microsoft tidak membuka dokumen yang dilampirkan?~~**
~~Adobe Acrobat reader and Microsoft apps still expects full access to all stored files,~~ ~~while apps should use the [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider) since Android KitKat (2013)~~ ~~to have access to actively shared files only. This is for privacy and security reasons.~~
@@ -1549,14 +1559,14 @@ By selecting a zero snooze duration you can cancel snoozing.
-**(69) Can you add auto scroll up on new message?**
+**(69) Apakah saya dapat menambahkan scroll ke atas otomatis di pesan baru?**
The message list is automatically scrolled up when navigating from a new message notification or after a manual refresh. Always automatically scrolling up on arrival of new messages would interfere with your own scrolling, but if you like you can enable this in the settings.
-**(70) When will messages be auto expanded?**
+**(70) Kapan pesan akan diperluas secara otomatis?**
When navigation to a conversation one message will be expanded if:
@@ -1572,7 +1582,7 @@ Messages will automatically be marked read on expanding, unless this was disable
-**(71) How do I use filter rules?**
+**(71) Bagaimana cara saya menggunakan aturan penyaringan?**
You can edit filter rules by long pressing a folder in the folder list.
@@ -1646,7 +1656,7 @@ Using rules is a pro feature.
-**(72) What are primary accounts/identities?**
+**(72) Apa itu akun/identitas utama?**
The primary account is used when the account is ambiguous, for example when starting a new draft from the unified inbox.
@@ -1657,7 +1667,7 @@ There can be just one primary account and there can be just one primary identity
-**(73) Is moving messages across accounts safe/efficient?**
+**(73) Apakah memindahkan pesan ke berbagai akun aman/efisien?**
Moving messages across accounts is safe because the raw, original messages will be downloaded and moved and because the source messages will be deleted only after the target messages have been added
@@ -1675,21 +1685,21 @@ Gmail allows one message to have multiple labels, which are presented to FairEma
-**(75) Can you make an iOS, Windows, Linux, etc version?**
+**(75) Apakah anda dapat membuat versi iOS, Windows, Linux, dan sebagainya?**
A lot of knowledge and experience is required to successfully develop an app for a specific platform, which is why I develop apps for Android only.
-**(76) What does 'Clear local messages' do?**
+**(76) Apa itu 'Hapus pesan lokal'?**
The folder menu *Clear local messages* removes messages from the device which are present on the server too. It does not delete messages from the server. This can be useful after changing the folder settings to not download the message content (text and attachments), for example to save space.
-**(77) Why are messages sometimes shown with a small delay?**
+**(77) Mengapa pesan sering ditampilkan sedikit tertunda?**
Depending on the speed of your device (processor speed and maybe even more memory speed) messages might be displayed with a small delay. FairEmail is designed to dynamically handle a large number of messages without running out of memory. This means that messages needs to be read from a database and that this database needs to be watched for changes, both of which might cause small delays.
@@ -1702,7 +1712,7 @@ FairEmail is based on the state-of-the-art [Android architecture components](htt
-**(78) How do I use schedules?**
+**(78) Bagaimana cara saya menggunakan jadwal?**
In the receive settings you can enable scheduling and set the time period and the day of weeks when messages should be received.
@@ -1765,7 +1775,7 @@ Scheduling is a pro feature.
-**(79) How do I use synchronize on demand (manual)?**
+**(79) Bagaimana cara sama mensinkronisasikan dengan manual?**
Normally, FairEmail maintains a connection to the configured email servers whenever possible to receive messages in real-time. If you don't want this, for example to be not disturbed or to save on battery usage, just disable receiving in the receive settings. This will stop the background service which takes care of automatic synchronization and will remove the associated status bar notification.
@@ -1789,27 +1799,27 @@ You'll likely want to disabled [browse on server](#user-content-faq24) too.
-**~~(81) Can you make the background of the original message dark in the dark theme?~~**
+**~~(81) Apakah saya dapat membuat latar belakang pesan orisinal menjadi gelap di tema gelap?~~**
~~The original message is shown as the sender has sent it, including all colors.~~ ~~Changing the background color would not only make the original view not original anymore, it can also result in unreadable messages.~~
-**(82) What is a tracking image?**
+**(82) Apa itu pelacakan gambar?**
Please see [here](https://en.wikipedia.org/wiki/Web_beacon) about what a tracking image exactly is. In short tracking images keep track if you opened a message.
FairEmail will in most cases automatically recognize tracking images and replace them by this icon:
-
+
Automatic recognition of tracking images can be disabled in the privacy settings.
-**(84) What are local contacts for?**
+**(84) Apakah fungsi dari kontak lokal?**
Local contact information is based on names and addresses found in incoming and outgoing messages.
@@ -1824,7 +1834,7 @@ By default only names and addresses to whom you send messages to will be recorde
-**(85) Why is an identity not available?**
+**(85) Mengapa identitas tidak tersedia?**
An identity is available for sending a new message or replying or forwarding an existing message only if:
@@ -1837,7 +1847,7 @@ FairEmail will try to select the best identity based on the *to* address of the
-**~~(86) What are 'extra privacy features'?~~**
+**~~(86) Apa itu 'fitur privasi tambahan'?~~**
~~The advanced option *extra privacy features* enables:~~
@@ -1847,7 +1857,7 @@ FairEmail will try to select the best identity based on the *to* address of the
-**(87) What does 'invalid credentials' mean?**
+**(87) Apa yang dimaksud dengan 'kredensial tidak valid'?**
The error message *invalid credentials* means either that the user name and/or password is incorrect, for example because the password was changed or expired, or that the account authorization has expired.
@@ -1858,7 +1868,7 @@ If the account authorization has expired, you will have to select the account ag
-**(88) How can I use a Yahoo, AOL or Sky account?**
+**(88) Bagaimana cara saya menggunakan akun Yahoo, AOL or Sky?**
To authorize a Yahoo, AOL, or Sky account you will need to create an app password. For instructions, please see here:
@@ -1881,7 +1891,7 @@ Y1 OK CAPABILITY completed
-**(89) How can I send plain text only messages?**
+**(89) Bagaimana cara saya mengirim pesan hanya teks?**
By default FairEmail sends each message both as plain text and as HTML formatted text because almost every receiver expects formatted messages these days. If you want/need to send plain text messages only, you can enable this in the advanced identity options. You might want to create a new identity for this if you want/need to select sending plain text messages on a case-by-case basis.
@@ -1895,7 +1905,7 @@ FairEmail will automatically link not linked web links (http and https) and not
Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but links for less usual or less safe protocols like telnet and ftp will not be recognized.
-**~~(91) Can you add periodical synchronization to save battery power?~~**
+**~~(91) Apakah anda dapat menambahkan singkronisasi periodik untuk menghemat tenaga baterai?~~**
~~Synchronizing messages is an expensive proces because the local and remote messages need to be compared,~~ ~~so periodically synchronizing messages will not result in saving battery power, more likely the contrary.~~
@@ -1924,7 +1934,7 @@ If legitimate messages are failing authentication, you should notify the sender
-**(93) Can you allow installation/data storage on external storage media (sdcard)?**
+**(93) Apakah anda dapat mengizinkan instalasi/penyimpanan data di media penyimpanan eksternal (sdcard)?**
FairEmail uses services and alarms, provides widgets and listens for the boot completed event to be started on device start, so it is not possible to store the app on external storage media, like an sdcard. See also [here](https://developer.android.com/guide/topics/data/install-location).
@@ -1937,14 +1947,14 @@ If you need to save on storage space, you can limit the number of days messages
-**(94) What does the red/orange stripe at the end of the header mean?**
+**(94) Apa yang dimaksud dari garis yang berwarna merah/oranye diakhir header?**
The red/orange stripe at the left side of the header means that the DKIM, SPF or DMARC authentication failed. See also [this FAQ](#user-content-faq92).
-**(95) Why are not all apps shown when selecting an attachment or image?**
+**(95) Mengapa tidak semua aplikasi terlihat saat memilih lampiran atau gambar?**
For privacy and security reasons FairEmail does not have permissions to directly access files, instead the Storage Access Framework, available and recommended since Android 4.4 KitKat (released in 2013), is used to select files.
@@ -1955,7 +1965,7 @@ Android Q will make it harder and maybe even impossible to directly access files
-**(96) Where can I find the IMAP and SMTP settings?**
+**(96) Dimana saya dapat menemukan pengaturan IMAP dan SMTP?**
The IMAP settings are part of the (custom) account settings and the SMTP settings are part of the identity settings.
@@ -1977,7 +1987,7 @@ Note that the cleanup job will only run when the synchronize service is active.
-**(98) Why can I still pick contacts after revoking contacts permissions?**
+**(98) Menngapa saya tetap bisa memilih kontak setelah membatalkan izin kontak?**
After revoking contacts permissions Android does not allow FairEmail access to your contacts anymore. However, picking contacts is delegated to and done by Android and not by FairEmail, so this will still be possible without contacts permissions.
@@ -1993,7 +2003,7 @@ A [Rich text](https://en.wikipedia.org/wiki/Formatted_text) or [Markdown](https:
-**(100) How can I synchronize Gmail categories?**
+**(100) Bagaimana cara saya mensingkronisasikan kategori Gmail?**
You can synchronize Gmail categories by creating filters to label categorized messages:
@@ -2017,7 +2027,7 @@ You can use *Force sync* in the three-dots menu of the unified inbox to let Fair
-**(101) What does the blue/orange dot at the bottom of the conversations mean?**
+**(101) Apa yang dimaksud dengan titik yang berwarna biru/oranye yang berada dibawah percakapan?**
The dot shows the relative position of the conversation in the message list. The dot will be show orange when the conversation is the first or last in the message list, else it will be blue. The dot is meant as an aid when swiping left/right to go to the previous/next conversation.
@@ -2026,7 +2036,7 @@ The dot is disabled by default and can be enabled with the display settings *Sho
-**(102) How can I enable auto rotation of images?**
+**(102) Bagaimana cara saya mengaktifkan rotasi otomatis untuk gambar?**
Images will automatically be rotated when automatic resizing of images is enabled in the settings (enabled by default). However, automatic rotating depends on the [Exif](https://en.wikipedia.org/wiki/Exif) information to be present and to be correct, which is not always the case. Particularly not when taking a photo with a camara app from FairEmail.
@@ -2035,7 +2045,7 @@ Note that only [JPEG](https://en.wikipedia.org/wiki/JPEG) and [PNG](https://en.w
-**(103) How can I record audio?**
+**(103) Bagaimana cara saya merekam audio?**
You can record audio if you have a recording app installed which supports the [RECORD_SOUND_ACTION](https://developer.android.com/reference/android/provider/MediaStore.Audio.Media#RECORD_SOUND_ACTION) intent. If no supported app is installed, FairEmail will not show a record audio action/icon.
@@ -2044,7 +2054,7 @@ Unfortunately and surprisingly, most recording apps do not seem to support this
-**(104) What do I need to know about error reporting?**
+**(104) Apa yang harus saya ketahui tentang pelaporan eror?**
* Error reports will help improve FairEmail
* Error reporting is optional and opt-in
@@ -2067,7 +2077,7 @@ So, you don't have to disable this option if you don't have an EU SIM or are not
-**(106) Which launchers can show a badge count with the number of unread messages?**
+**(106) Peluncur mana yang dapat menampilkan lencana hitungan dengan jumlah pesan yang belum dibaca?**
Please [see here](https://github.com/leolin310148/ShortcutBadger#supported-launchers) for a list of launchers which can show the number of unread messages.
@@ -2094,7 +2104,7 @@ The number of new, unread messages will be in an integer "*count*" parameter.
-**(107) How do I use colored stars?**
+**(107) Bagaimana cara saya menggunakan bintang berwarna?**
You can set a colored star via the *more* message menu, via multiple selection (started by long pressing a message), by long pressing a star in a conversation or automatically by using [rules](#user-content-faq71).
@@ -2105,14 +2115,14 @@ Some email clients use IMAP keywords for colors. However, not all servers suppor
-**~~(108) Can you add permanently delete messages from any folder?~~**
+**~~(108) Apakah anda dapat menghapus pesan secara permanen dari folder apapun?~~**
~~When you delete messages from a folder the messages will be moved to the trash folder, so you have a chance to restore the messages.~~ ~~You can permanently delete messages from the trash folder.~~ ~~Permanently delete messages from other folders would defeat the purpose of the trash folder, so this will not be added.~~
-**~~(109) Why is 'select account' available in official versions only?~~**
+**~~(109) Mengapa 'pilih akun' hanya tersedia di versi resmi saja?~~**
~~Using *select account* to select and authorize Google accounts require special permission from Google for security and privacy reasons.~~ ~~This special permission can only be acquired for apps a developer manages and is responsible for.~~ ~~Third party builds, like the F-Droid builds, are managed by third parties and are the responsibility of these third parties.~~ ~~So, only these third parties can acquire the required permission from Google.~~ ~~Since these third parties do not actually support FairEmail, they are most likely not going to request the required permission.~~
@@ -2126,7 +2136,7 @@ Some email clients use IMAP keywords for colors. However, not all servers suppor
-**(110) Why are (some) messages empty and/or attachments corrupt?**
+**(110) Mengapa terdapat (beberapa) pesan kosong dan/atau lampiran yang rusak?**
Empty messages and/or corrupt attachments are probably being caused by a bug in the server software. Older Microsoft Exchange software is known to cause this problem. Mostly you can workaround this by disabling *Partial fetch* in the advanced account settings:
@@ -2139,7 +2149,7 @@ Disabling *Partial fetch* will result in more memory usage.
-**(111) Is OAuth supported?**
+**(111) Apakah OAuth tersedia?**
OAuth for Gmail is supported via the quick setup wizard. The Android account manager will be used to fetch and refresh OAuth tokens for selected on-device accounts. OAuth for non on-device accounts is not supported because Google requires a [yearly security audit](https://support.google.com/cloud/answer/9110914) ($15,000 to $75,000) for this.
@@ -2152,7 +2162,7 @@ OAuth access for Yahoo was requested, but Yahoo never responded to the request.
-**(112) Which email provider do you recommend?**
+**(112) Penyedia surel apa yang anda rekomendasikan?**
FairEmail is an email client only, so you need to bring your own email address.
@@ -2165,7 +2175,7 @@ Using your own (custom) domain name, which is supported by most email providers,
-**(113) How does biometric authentication work?**
+**(113) Bagaimana cara kerja autentikasi biometrik?**
If your device has a biometric sensor, for example a fingerprint sensor, you can enable/disable biometric authentication in the navigation (hamburger) menu of the setup screen. When enabled FairEmail will require biometric authentication after a period of inactivity or after the screen has been turned off while FairEmail was running. Activity is navigation within FairEmail, for example opening a conversation thread. The inactivity period duration can be configured in the miscellaneous settings. When biometric authentication is enabled new message notifications will not show any content and FairEmail won't be visible on the Android recents screen.
@@ -2176,7 +2186,7 @@ Biometric authentication is a pro feature.
-**(114) Can you add an import for the settings of other email apps?**
+**(114) Apakah anda dapat menambahkan impor untuk pengaturan aplikasi surel lain?**
The format of the settings files of most other email apps is not documented, so this is difficult. Sometimes it is possible to reverse engineer the format, but as soon as the settings format changes things will break. Also, settings are often incompatible. For example, FairEmail has unlike most other email apps settings for the number of days to synchronize messages for and for the number of days to keep messages for, mainly to save on battery usage. Moreover, setting up an account/identity with the quick setup is simple, so it is not really worth the effort.
@@ -2196,7 +2206,7 @@ Reverted [commit](https://github.com/M66B/FairEmail/commit/2c80c25b8aa75af2287f4
-**~~(116) How can I show images in messages from trusted senders by default?~~**
+**~~(116) Bagaimana caranya saya dapat menampilkan gambar dari pengirim yang saya percaya secara otomatis?~~**
~~You can show images in messages from trusted senders by default by enabled the display setting *Automatically show images for known contacts*.~~
@@ -2206,13 +2216,14 @@ Reverted [commit](https://github.com/M66B/FairEmail/commit/2c80c25b8aa75af2287f4
-**(117) Can you help me restore my purchase?**
+**(117) Apakah anda dapat membantu saya memulihkan pembelian saya?**
Google manages all purchases, so as a developer I have little control over purchases. So, basically the only thing I can do, is give some advice:
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2232,14 +2244,14 @@ If you cannot solve the problem with the purchase, you will have to contact Goog
-**(118) What does 'Remove tracking parameters' exactly?**
+**(118) Apa sebenarnya yang dimaksud dengan 'Hapus parameter pelacakan'?**
Checking *Remove tracking parameters* will remove all [UTM parameters](https://en.wikipedia.org/wiki/UTM_parameters) from a link.
-**~~(119) Can you add colors to the unified inbox widget?~~**
+**~~(119) Apakah anda dapat menambahkan warna ke dalam widget pesan masuk terpadu?~~**
~~The widget is designed to look good on most home/launcher screens by making it monochrome and by using a half transparent background.~~ ~~This way the widget will nicely blend in, while still being properly readable.~~
@@ -2250,7 +2262,7 @@ Due to Android limitations it is not possible to dynamically set the opacity of
-**(120) Why are new message notifications not removed on opening the app?**
+**(120) Mengapa notifikasi pesan baru tidak terhapus ketika membuka aplikasi?**
New message notifications will be removed on swiping notifications away or on marking the associated messages read. Opening the app will not remove new message notifications. This gives you a choice to leave new message notifications as a reminder that there are still unread messages.
@@ -2259,7 +2271,7 @@ On Android 7 Nougat and later new message notifications will be [grouped](https:
-**(121) How are messages grouped into a conversation?**
+**(121) Bagaimana pesan dikelompokan kedalam sebuah percakapan?**
By default FairEmail groups messages in conversations. This can be turned of in the display settings.
@@ -2268,14 +2280,14 @@ FairEmail groups messages based on the standard *Message-ID*, *In-Reply-To* and
-**~~(122) Why is the recipient name/email address show with a warning color?~~**
+**~~(122) Mengapa nama/alamat surel penerima memiliki warna peringatan?~~**
~~The recipient name and/or email address in the addresses section will be shown in a warning color~~ ~~when the sender domain name and the domain name of the *to* address do not match.~~ ~~Mostly this indicates that the message was received *via* an account with another email address.~~
-**(123) What will happen when FairEmail cannot connect to an email server?**
+**(123) Apa yang terjadi ketika FairEmail tidak dapat terhubung dengan server surel?**
When FairEmail cannot connect to an email server to receive messages, for example when the internet connection is bad or a firewall or a VPN is blocking the connection, FairEmail will wait 8, 16 and 32 seconds while keeping the device awake (=use battery power) and try again to connect. If this fails, FairEmail will schedule an alarm to retry after 15, 30 and 60 minutes and let the device sleep (=no battery usage).
@@ -2292,21 +2304,21 @@ Note that sending will not be retried in case of authentication problems and whe
-**(124) Why do I get 'Message too large or too complex to display'?**
+**(124) Mengapa saya mendapatkan 'Pesan terlalu besar atau terlalu kompleks untuk ditampilkan'?**
The message *Message too large or too complex to display* will be shown if there are more than 100,000 characters or more than 500 links in a message. Reformatting and displaying such messages will take too long. You can try to use the original message view, powered by the browser, instead.
-**(125) What are the current experimental features?**
+**(125) Apa saja fitur eksperimental terbaru?**
* ...
-**(126) Can message previews be sent to my wearable?**
+**(126) Apakah tampilan pesan dapat dikirimkan ke perangkat yang dapat saya pakai?**
FairEmail fetches a message in two steps:
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Jika anda rasa sudah cukup, anda dapat mengaktifkan opsi notifikasi *Hanya kirim notifikasi dengan tampilan pesan ke perangkat wearable* dan jika tidak berfungsi, anda dapat mencoba mengaktifkan opsi notifikasi *Tampilkan notifikasi hanya dengan tampilan teks saja*. Perhatikan bahwa hal ini akan diterapkan di perangkat wearable yang juga tidak akan menampilkan tampilan pesan, bahkan ketika aplikasi Android Wear menginformasikan bahwa notifikasi telah dikirimkan (dijembatani).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2333,14 +2345,14 @@ The error *... Syntactically invalid HELO argument(s) ...* means that the SMTP s
-**(128) How can I reset asked questions, for example to show images?**
+**(128) Bagaimana cara saya mengulang pertanyaan yang ditanyakan, seperti untuk menampilkan gambar?**
You can reset asked questions via the three dots overflow menu in the miscellaneous settings.
-**(129) Are ProtonMail, Tutanota supported?**
+**(129) Apakah ProtonMail terdukung Tutanota?**
ProtonMail uses a proprietary email protocol and [does not directly support IMAP](https://protonmail.com/support/knowledge-base/imap-smtp-and-pop3-setup/), so you cannot use FairEmail to access ProtonMail.
@@ -2349,7 +2361,7 @@ Tutanota uses a proprietary email protocol and [does not support IMAP](https://t
-**(130) What does message error ... mean?**
+**(130) Apakah yang dimaksud dengan pesan eror ... ?**
A series of lines with orangish or red texts with technical information means that debug mode was enabled in the miscellaneous settings.
@@ -2366,7 +2378,7 @@ Please see [here](#user-content-faq22) for other error messages in the outbox.
-**(131) Can you change the direction for swiping to previous/next message?**
+**(131) Apakah anda dapat mengubah arah geser untuk pesan sebelumnya/selanjutnya?**
If you read from left to right, swiping to the left will show the next message. Similarly, if you read from right to left, swiping to the right will show the next message.
@@ -2377,7 +2389,7 @@ Anyway, there is a behavior setting to reverse the swipe direction.
-**(132) Why are new message notifications silent?**
+**(132) Mengapa notifikasi pesan baru tidak berbunyi?**
Notifications are silent by default on some MIUI versions. Please see [here](http://en.miui.com/thread-3930694-1-1.html) how you can fix this.
@@ -2388,7 +2400,7 @@ Android might rate limit the notification sound, which can cause some new messag
-**(133) Why is ActiveSync not supported?**
+**(133) Mengapa tidak terdukung ActiveSync?**
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
@@ -2399,7 +2411,7 @@ Note that the desciption of FairEmail starts with the remark that non-standard p
-**(134) Can you add deleting local messages?**
+**(134) Apakah anda dapat menambahkan hapus pesan lokal?**
*POP3*
@@ -2416,7 +2428,7 @@ Note that it is possible to set the swipe left or right action to hide a message
-**(135) Why are trashed messages and drafts shown in conversations?**
+**(135) Mengapa pesan dan draf yang telah dibuang ditampilkan di percakapan?**
Individual messages will rarely be trashed and mostly this happens by accident. Showing trashed messages in conversations makes it easier to find them back.
@@ -2427,7 +2439,7 @@ Similarly, drafts are shown in conversations to find them back in the context wh
-**(136) How can I delete an account/identity/folder?**
+**(136) Bagaimana cara saya menghapus akun/identitas/folder?**
Deleting an account/identity/folder is a little bit hidden to prevent accidents.
@@ -2440,14 +2452,14 @@ In the three-dots overflow menu at the top right there is an item to delete the
-**(137) How can I reset 'Don't ask again'?**
+**(137) Bagaimana cara saya mengulang 'Jangan bertanya lagi'?**
You can reset all questions set to be not asked again in the miscellaneous settings.
-**(138) Can you add calendar/contact management/synchronizing?**
+**(138) Apakah anda dapat menambahkan kalender/manajemen kontak/singkronisasi?**
Calendar and contact management can better be done by a separate, specialized app. Note that FairEmail is a specialized email app, not an office suite.
@@ -2463,7 +2475,7 @@ Note that FairEmail does support replying to calendar invites (a pro feature) an
-**(139) How do I fix 'User is authenticated but not connected'?**
+**(139) Bagaimana cara saya memperbaiki 'Pengguna telah terotentikasi namun tidak terkoneksi'?**
In fact this Microsoft Exchange specific error is an incorrect error message caused by a bug in older Exchange server software.
@@ -2485,14 +2497,14 @@ Note that it should be a backslash and not a forward slash.
-**(140) Why does the message text contain strange characters?**
+**(140) Mengapa teks pesan terdapat karakter yang aneh?**
Displaying strange characters is almost always caused by specifying no or an invalid character encoding by the sending software. FairEmail will assume [ISO 8859-1](https://en.wikipedia.org/wiki/ISO/IEC_8859-1) when no character set or when [US-ASCII](https://en.wikipedia.org/wiki/ASCII) was specified. Other than that there is no way to reliably determine the correct character encoding automatically, so this cannot be fixed by FairEmail. The right action is to complain to the sender.
-**(141) How can I fix 'A drafts folder is required to send messages'?**
+**(141) Bagaimana cara saya memperbaiki 'Folder draf diperlukan untuk mengirim pesan'?**
To store draft messages a drafts folder is required. In most cases FairEmail will automatically select the drafts folders on adding an account based on [the attributes](https://www.iana.org/assignments/imap-mailbox-name-attributes/imap-mailbox-name-attributes.xhtml) the email server sends. However, some email servers are not configured properly and do not send these attributes. In this case FairEmail tries to identify the drafts folder by name, but this might fail if the drafts folder has an unusual name or is not present at all.
@@ -2505,7 +2517,7 @@ Quick link for Gmail: [https://mail.google.com/mail/u/0/#settings/labels](https:
-**(142) How can I store sent messages in the inbox?**
+**(142) Bagaimana cara saya menyimpan pesan yang terkirim di pesan masuk?**
Generally, it is not a good idea to store sent messages in the inbox because this is hard to undo and could be incompatible with other email clients.
@@ -2518,7 +2530,7 @@ If this is not an option, you can [create a rule](#user-content-faq71) to automa
-**~~(143) Can you add a trash folder for POP3 accounts?~~**
+**~~(143) Apakah anda dapat menambahkan folder untuk akun POP3?~~**
[POP3](https://en.wikipedia.org/wiki/Post_Office_Protocol) is a very limited protocol. Basically only messages can be downloaded and deleted from the inbox. It is not even possible to mark a message read.
@@ -2531,11 +2543,11 @@ Version 1.1082 added a local trash folder. Note that trashing a message will per
-**(144) How can I record voice notes?**
+**(144) Bagaimana cara saya merekam catatan suara?**
To record voice notes you can press this icon in the bottom action bar of the message composer:
-
+
This requires a compatible audio recorder app to be installed. In particular [this common intent](https://developer.android.com/reference/android/provider/MediaStore.Audio.Media.html#RECORD_SOUND_ACTION) needs to be supported.
@@ -2546,7 +2558,7 @@ Voice notes will automatically be attached.
-**(145) How can I set a notification sound for an account, folder or sender?**
+**(145) Bagaimana cara saya menyetel suara notifikasi untuk akun, folder dan pengirim?**
Account:
@@ -2571,7 +2583,7 @@ Setting a notification sound for an account, folder or sender requires Android 8
-**(146) How can I fix incorrect message times?**
+**(146) Bagaimana cara saya memperbaiki waktu pesan yang salah?**
Since the sent date/time is optional and can be manipulated by the sender, FairEmail uses the server received date/time by default.
@@ -2584,7 +2596,7 @@ This will not change the time of already synchronized messages. To solve this, l
-**(147) What should I know about third party versions?**
+**(147) Apa yang harus saya ketahui tentang versi pihak ketiga?**
You likely came here because you are using a third party build of FairEmail.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
@@ -2605,7 +2617,7 @@ If you have a problem with the F-Droid build, please check if there is a newer G
-**(148) How can I use an Apple iCloud account?**
+**(148) Bagaimana cara saya menggunakan akun Apple iCloud?**
There is a built-in profile for Apple iCloud, but if needed you can find the right settings [here](https://support.apple.com/en-us/HT202304).
@@ -2614,7 +2626,7 @@ When using two-factor authentication you might need to use an [app-specific pass
-**(149) How does the unread message count widget work?**
+**(149) Bagaimana cara kerja widget penghitung pesan yang belum dibaca?**
The unread message count widget shows the number of unread messages either for all accounts or for a selected account, but only for the folders for which new message notifications are enabled.
@@ -2627,7 +2639,7 @@ Tapping on the notification will synchronize all folders for which synchronizati
-**(150) Can you add cancelling calendar invites?**
+**(150) Apakah anda dapat menambahkan pembatalan undangan kalender?**
Cancelling calendar invites (removing calendar events) requires write calendar permission, which will result in effectively granting permission to read and write *all* calendar events of *all* calendars.
@@ -2638,7 +2650,7 @@ Inserting new calendar events can be done without permissions with special [inte
-**(151) Can you add backup/restore of messages?**
+**(151) Apakah anda dapat menambahkan backup/restore pesan?**
An email client is meant to read and write messages, not to backup and restore messages. Note that breaking or losing your device, means losing your messages!
@@ -2651,7 +2663,7 @@ If you want to import an mbox file to an existing email account, you can use Thu
-**(152) How can I insert a contact group?**
+**(152) Bagaimana cara saya memasukan kontak ke grup?**
You can insert the email addresses of all contacts in a contact group via the three dots menu of the message composer.
@@ -2660,7 +2672,7 @@ You can define contact groups with the Android contacts app, please see [here](h
-**(153) Why does permanently deleting Gmail message not work?**
+**(153) Mengapa hapus pesan Gmail secara permanen tidak bekerja?**
You might need to change [the Gmail IMAP settings](https://mail.google.com/mail/u/0/#settings/fwdandpop) on a desktop browser to make it work:
@@ -2674,14 +2686,14 @@ Some background: Gmail seems to have an additional message view for IMAP, which
-**~~(154) Can you add favicons as contact photos?~~**
+**~~(154) Apakah anda dapat menambahkan favicons sebagai foto kontak?~~**
~~Besides that a [favicon](https://en.wikipedia.org/wiki/Favicon) might be shared by many email addresses with the same domain name~~ ~~and therefore is not directly related to an email address, favicons can be used to track you.~~
-**(155) What is a winmail.dat file?**
+**(155) Apa itu berkas winmail.dat?**
A *winmail.dat* file is sent by an incorrectly configured Outlook client. It is a Microsoft specific file format ([TNEF](https://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format)) containing a message and possibly attachments.
@@ -2692,7 +2704,7 @@ You can view it with for example the Android app [Letter Opener](https://play.go
-**(156) How can I set up an Office 365 account?**
+**(156) Bagaimana cara saya mengatur akun Office 365?**
An Office 365 account can be set up via the quick setup wizard and selecting *Office 365 (OAuth)*.
@@ -2703,7 +2715,7 @@ If you've enabled *security defaults* in your organization, you might need to en
-**(157) How can I set up an Free.fr account?**
+**(157) Bagaimana cara saya mengatur akun Free.fr?**
Veuillez [voir ici](https://free.fr/assistance/597.html) pour les instructions.
@@ -2714,7 +2726,7 @@ Veuillez [voir ici](http://jc.etiemble.free.fr/abc/index.php/trucs-astuces/confi
-**(158) Which camera / audio recorder do you recommend?**
+**(158) Kamera / perekam audio apa yang anda sarankan?**
To take photos and to record audio a camera and an audio recorder app are needed. The following apps are open source cameras and audio recorders:
@@ -2750,35 +2762,35 @@ Updating once a week will probably be sufficient, please see [here](https://gith
-**(160) Can you add permanent deletion of messages without confirmation?**
+**(160) Apakah anda dapat menambahkan penghapusan permanen dari pesan tanpa konfirmasi?**
Permanent deletion means that messages will *irreversibly* be lost, and to prevent this from happening accidentally, this always needs to be confirmed. Even with a confirmation, some very angry people who lost some of their messages through their own fault contacted me, which was a rather unpleasant experience :-(
-**(161) Can you add a setting to change the primary and accent color?***
+**(161) Apakah anda dapat menambahkan pengaturan untuk mengubah warna utama dan aksen?***
If I could, I would add a setting to select the primary and accent color right away, but unfortunately Android themes are fixed, see for example [here](https://stackoverflow.com/a/26511725/1794097), so this is not possible.
-## Support
+## Bantuan
-Only the latest Play store version and latest GitHub release are supported. This also means that downgrading is not supported.
+Hanya versi Play store terbaru dan rilis GitHub terbaru yang terdukung. Hal ini juga berarti tidak dapat menurunkan peringkat.
-Requested features should:
+Fitur yang diminta harus:
-* be useful to most people
-* not complicate the usage of FairEmail
-* fit within the philosophy of FairEmail (privacy oriented, security minded)
-* comply with common standards (IMAP, SMTP, etc)
+* berguna untuk seluruh orang
+* tidak menyusahkan pengguna FairEmail
+* cocok dengan filosofi FairEmail (berorientasi dengan privasi, berfikir keamanan)
+* memenuhi standar umum (IMAP, SMTP, dll)
-Features not fulfilling these requirements will likely be rejected. This is also to keep maintenance and support in the long run feasible.
+Fitur yang tidak memenuhi persyaratan ini kemungkinan besar akan ditolak. Hal ini juga dapat menjaga pemeliharaan dan bantuan dalam jangka panjang dapat terpenuhi.
-If you have a question, want to request a feature or report a bug, please use [this form](https://contact.faircode.eu/?product=fairemailsupport).
+Jika anda memiliki pertanyaan, ingin meminta fitur, atau melaporkan bug, sila gunakan [formulir ini](https://contact.faircode.eu/?product=fairemailsupport).
-GitHub issues are disabled due to frequent misusage.
+Permasalahan GitHub dinonaktifkan karena sering disalahgunakan.
-Copyright © 2018-2020 Marcel Bokhorst.
+Hak cipta © 2018-2020 Marcel Bokhorst.
diff --git a/docs/FAQ-it-rIT.md b/docs/FAQ-it-rIT.md
index becf7c75ee..e28afca42f 100644
--- a/docs/FAQ-it-rIT.md
+++ b/docs/FAQ-it-rIT.md
@@ -75,7 +75,7 @@ Domande correlate:
* ~~Un [errore in AndroidX](https://issuetracker.google.com/issues/64729576) rende difficile toccare lo scroller rapido. È stato aggiunto un espediente.~~
* ~~La crittografia con YubiKey risulta in un ciclo infinito. Ciò sembra essere causato da un [errore in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Lo scorrimento verso una posizione collegata internamente nei messaggi originali non funziona. Ciò non può essere risolto perché la vista originale dei messaggi è contenuta in una vista a scorrimento.
-* Un'anteprima di un testo di un messaggio non (sempre) appare negli orologi Samsung perché [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) sembra venga ignorato. Le anteprime dei messaggi sono note per essere visualizzate correttamente su Pebble 2, Fitbit Charge 3 e Mi band 3. Vedi anche [queste domande frequenti](#user-content-faq126).
+* Un'anteprima di un testo di un messaggio non (sempre) appare negli orologi Samsung perché [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) sembra venga ignorato. I testi di anteprima del messaggio sono noti per essere visualizzati correttamente sugli indossabili Pebble 2, Fitbit Charge 3, Mi band 3 e Xiaomi Amazfit BIP. Vedi anche [queste domande frequenti](#user-content-faq126).
* Un [errore in Android](https://issuetracker.google.com/issues/37068143) a volte provoca un crash con *... Spostamento non valido: ... L'intervallo valido è ... quando il testo è selezionato e tocca all'esterno del testo selezionato. Questo bug è stato risolto in Android 6.0.1.
* I collegamenti interni (ancoraggi) non funzioneranno perché i messaggi originali sono mostrati in una WebView incorporata in una vista a scorrimento (l'elenco delle conversazioni). Questa è una limitazione di Android che non può essere fissata o lavorata.
@@ -175,7 +175,7 @@ Il design è basato su molte discussioni e se vuoi puoi discuterne anche tu [in
* [~~(54) Come uso un prefisso dello spazio del nome?~~](#user-content-faq54)
* [(55) Come posso contrassegnare tutti i messaggi come letti / spostati o eliminare tutti i messaggi?](#user-content-faq55)
* [(56) Puoi aggiungere il supporto per JMAP?](#user-content-faq56)
-* [~~(57) Posso usare HTML nelle firme?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) Cosa significa un'icona dell'email aperta/chiusa?](#user-content-faq58)
* [(59) I messaggi originali possono essere aperti nel browser?](#user-content-faq59)
* [(60) Lo sapevi ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ Il design è basato su molte discussioni e se vuoi puoi discuterne anche tu [in
* [(105) Come funziona l'opzione roam-like-at-home?](#user-content-faq105)
* [(106) Quali launcher possono mostrare un distintivo di conteggio con il numero di messaggi non letti?](#user-content-faq106)
* [(107) Come uso le stelle colorate?](#user-content-faq107)
-* [(108) Puoi aggiungere permanentemente l'eliminazione dei messaggi da ogni cartella?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Perché 'seleziona profilo' è disponibile solo nelle versioni ufficiali?~~](#user-content-faq109)
* [(110) Perché (alcuni) messaggi vuoti e/o allegati sono corrotti?](#user-content-faq110)
* [(111) OAuth è supportato?](#user-content-faq111)
@@ -388,7 +388,7 @@ Le operazioni sono elaborate solo quando esiste una connessione al server email
Dovresti provare a risolvere ciò contattando il tuo fornitore o ottenendo un certificato di sicurezza valido perché i certificati di sicurezza non validi non sono sicuri e consente gli [attacchi man-in-the-middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Se il denaro è un ostacolo, puoi ottenere dei certificati di sicurezza gratuiti da [Let's Encrypt](https://letsencrypt.org).
-In alternativa, puoi accettare le impronte digitali mostrate sotto il messaggio di errore se configuri il profilo e/o l'identità nei passaggi 1 e 2 della configurazione (non è possibile usando la procedura guidata di configurazione rapida). Nota che dovresti assicurarti che la connessione ad internet che stai usando sia sicura.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Nota che le versioni precedenti potrebbero non riconoscere le autorità di certificazione più nuove come Let's Encrypt, causando alle connessioni di essere considerate non sicure, vedi anche [qui](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Posso usare l'HTML nelle firme?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+Se pensi sia abbastanza buono, puoi abilitare l'opzione di notifica *Invia solo le notifiche con un'anteprima di messaggio agli indossabili* e se non funziona, puoi provare ad abilitare l'opzione di notifica *Mostra notifiche aventi solo un testo di anteprima*. Nota che ciò si applica agli indossabili che non mostrano anch'essi un testo di anteprima, anche quando l'app di Android Wear dice che la notifica è stata inviata (collegata).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-iw-rIL.md b/docs/FAQ-iw-rIL.md
index 708ce7257d..97ea895a16 100644
--- a/docs/FAQ-iw-rIL.md
+++ b/docs/FAQ-iw-rIL.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ja-rJP.md b/docs/FAQ-ja-rJP.md
index c19017c47d..d021883b5a 100644
--- a/docs/FAQ-ja-rJP.md
+++ b/docs/FAQ-ja-rJP.md
@@ -1,4 +1,4 @@
-# FairEmail support
+# FairEmail のサポート
If you have a question, please check the frequently asked questions below first. At the bottom, you can find out how to ask other questions, request features, and report bugs.
@@ -6,7 +6,7 @@ If you have a question, please check the frequently asked questions below first.
* [Authorizing accounts](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-authorizing-accounts)
* [How to ...?](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-howto)
-* [Known problems](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-known-problems)
+* [既知の問題](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-known-problems)
* [Planned features](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-planned-features)
* [Frequently requested features](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-frequently-requested-features)
* [Frequently Asked Questions](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-frequently-asked-questions)
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-kk-rKZ.md b/docs/FAQ-kk-rKZ.md
index a29b7ff650..5428f60b9c 100644
--- a/docs/FAQ-kk-rKZ.md
+++ b/docs/FAQ-kk-rKZ.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ko-rKR.md b/docs/FAQ-ko-rKR.md
index 906ab0872d..162293916a 100644
--- a/docs/FAQ-ko-rKR.md
+++ b/docs/FAQ-ko-rKR.md
@@ -75,7 +75,7 @@ Searching for *IMAP* and the name of the provider is mostly sufficient to find t
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-lt-rLT.md b/docs/FAQ-lt-rLT.md
index 2337061c5d..06341fd3e3 100644
--- a/docs/FAQ-lt-rLT.md
+++ b/docs/FAQ-lt-rLT.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-nl-rNL.md b/docs/FAQ-nl-rNL.md
index 432c1b8c27..07b65bbc72 100644
--- a/docs/FAQ-nl-rNL.md
+++ b/docs/FAQ-nl-rNL.md
@@ -75,7 +75,7 @@ Gerelateerde vragen:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-nn-rNO.md b/docs/FAQ-nn-rNO.md
index 312e9d0116..b7bffdfd7f 100644
--- a/docs/FAQ-nn-rNO.md
+++ b/docs/FAQ-nn-rNO.md
@@ -75,7 +75,7 @@ Relaterte spørsmål:
* ~~En [feil i AndroidX](https://issuetracker.google.com/issues/64729576) gjør det vanskelig å ta tak i hurtigrulleren. En løsning ble lagt til.~~
* ~~Kryptering med YubiKey resulterer i en uendelig loop. Dette ser ut til å være forårsaket av en [feil i OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Å rulle til et internt koblet sted i originale meldinger fungerer ikke. Dette kan ikke løses fordi den opprinnelige meldingsvisningen finnes i en rullende visning.
-* En forhåndsvisning av en meldingstekst vises ikke (alltid) på Samsung-klokker fordi [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) ser ut til å bli ignorert. Det er kjent at forhåndsvisningstekster for meldinger vises riktig på Pebble 2, Fitbit Charge 3 og Mi band 3 wearables. Se også [denne vanlige FAQ](#user-content-faq126).
+* En forhåndsvisning av en meldingstekst vises ikke (alltid) på Samsung-klokker fordi [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) ser ut til å bli ignorert. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP wearables. Se også [denne vanlige 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.
@@ -175,7 +175,7 @@ Designet er basert på mange diskusjoner, og hvis du vil, kan du diskutere om de
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ Designet er basert på mange diskusjoner, og hvis du vil, kan du diskutere om de
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-no-rNO.md b/docs/FAQ-no-rNO.md
index e8f99b9428..c16456bbd0 100644
--- a/docs/FAQ-no-rNO.md
+++ b/docs/FAQ-no-rNO.md
@@ -75,7 +75,7 @@ Relaterte spørsmål:
* ~~En [feil i AndroidX](https://issuetracker.google.com/issues/64729576) gjør det vanskelig å ta tak i hurtigrulleren. En løsning ble lagt til.~~
* ~~Kryptering med YubiKey resulterer i en uendelig loop. Dette ser ut til å være forårsaket av en [feil i OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Å rulle til et internt koblet sted i originale meldinger fungerer ikke. Dette kan ikke løses fordi den opprinnelige meldingsvisningen finnes i en rullende visning.
-* En forhåndsvisning av en meldingstekst vises ikke (alltid) på Samsung-klokker fordi [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) ser ut til å bli ignorert. Det er kjent at forhåndsvisningstekster for meldinger vises riktig på Pebble 2, Fitbit Charge 3 og Mi band 3 wearables. Se også [denne vanlige FAQ](#user-content-faq126).
+* En forhåndsvisning av en meldingstekst vises ikke (alltid) på Samsung-klokker fordi [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) ser ut til å bli ignorert. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP wearables. Se også [denne vanlige 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.
@@ -175,7 +175,7 @@ Designet er basert på mange diskusjoner, og hvis du vil, kan du diskutere om de
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ Designet er basert på mange diskusjoner, og hvis du vil, kan du diskutere om de
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-pl-rPL.md b/docs/FAQ-pl-rPL.md
index 662f5fba00..79e89b8b1e 100644
--- a/docs/FAQ-pl-rPL.md
+++ b/docs/FAQ-pl-rPL.md
@@ -75,7 +75,7 @@ Powiązane pytania:
* ~~A [błąd w AndroidX](https://issuetracker.google.com/issues/64729576) utrudnia przechwytywanie szybkiego przewijania. Dodano obejście. ~~
* ~~ Szyfrowanie za pomocą YubiKey skutkuje nieskończoną pętlą. Wydaje się, że jest to spowodowane błędem [w OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Przewijanie do wewnętrznie połączonej lokalizacji w oryginalnych wiadomościach nie działa. Nie można tego naprawić, ponieważ oryginalny widok wiadomości znajduje się w przewijanym widoku.
-* Podgląd tekstu wiadomości nie (zawsze) pojawia się na zegarku Samsung, ponieważ [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wydaje się być ignorowany. Wiadomo, że teksty podglądu wiadomości są wyświetlane poprawnie na Pebble 2, Fitbit Charge 3 i Mi band 3. Zobacz również [ten FAQ](#user-content-faq126).
+* Podgląd tekstu wiadomości nie (zawsze) pojawia się na zegarku Samsung, ponieważ [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wydaje się być ignorowany. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP wearables. Zobacz również [ten 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.
@@ -175,7 +175,7 @@ Projekt opiera się na wielu dyskusjach i jeśli chcesz, możesz o nim dyskutowa
* [~~ (54) Jak korzystać z prefiksu przestrzeni nazw? ~~](#user-content-faq54)
* [(55) Jak mogę oznaczyć wszystkie wiadomości jako przeczytane / przeniesione lub usunąć wszystkie wiadomości?](#user-content-faq55)
* [(56) Czy możesz dodać wsparcie dla JMAP?](#user-content-faq56)
-* [~~(57) Czy mogę użyć HTML w podpisach?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) Co oznacza otwarta/zamknięta ikona e-mail?](#user-content-faq58)
* [(59) Czy oryginalne wiadomości mogą być otwierane w przeglądarce?](#user-content-faq59)
* [(60) Czy wiesz...?](#user-content-faq60)
@@ -225,7 +225,7 @@ Projekt opiera się na wielu dyskusjach i jeśli chcesz, możesz o nim dyskutowa
* [(105) Jak działa opcja Roaming jak w domu?](#user-content-faq105)
* [(106) Które launchery mogą pokazać licznik z liczbą nieprzeczytanych wiadomości?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Czy można trwale usunąć wiadomości z dowolnego folderu?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~ (109) Dlaczego funkcja „wybierz konto” jest dostępna tylko w oficjalnych wersjach? ~~](#user-content-faq109)
* [(110) Dlaczego (niektóre) wiadomości są puste i / lub załączniki są uszkodzone?](#user-content-faq110)
* [(111) Czy OAuth jest wspierany?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operacje są przetwarzane tylko wtedy, gdy istnieje połączenie z serwerem e-ma
Powinieneś spróbować to naprawić, kontaktując się z dostawcą lub uzyskując ważny certyfikat bezpieczeństwa ponieważ nieprawidłowe certyfikaty bezpieczeństwa są niepewne i umożliwiają [ ataki typu man-in-the-middle ](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Jeśli pieniądze są przeszkodą, możesz otrzymać darmowe certyfikaty bezpieczeństwa od [Let’s Encrypt](https://letsencrypt.org).
-Alternatywnie możesz zaakceptować odcisk palca wyświetlony poniżej komunikatu o błędzie, jeśli skonfigurujesz konto i/lub tożsamość w kroku 1 i 2 konfiguracji (nie jest to możliwe w przypadku korzystania z kreatora szybkiej konfiguracji). Pamiętaj, że należy upewnić się, że połączenie z internetem jest bezpieczne.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Pamiętaj, że starsze wersje Androida mogą nie rozpoznawać nowszych urzędów certyfikacji, takich jak Let's Encrypt, powodując, że połączenia są uważane za niebezpieczne, patrz także [ tutaj ](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-pt-rBR.md b/docs/FAQ-pt-rBR.md
index 2cbfc160c2..1100b2b300 100644
--- a/docs/FAQ-pt-rBR.md
+++ b/docs/FAQ-pt-rBR.md
@@ -75,7 +75,7 @@ Perguntas relacionadas:
* ~~Um [problema no AndroidX](https://issuetracker.google.com/issues/64729576) torna difícil selecionar a rolagem rápida. Uma solução alternativa foi adicionada.~~
* ~~Criptografia com YubiKey resulta em um loop (ciclo) infinito. Isso parece ser causado por um [problema no OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Rolar para um local com link interno nas mensagens originais não funciona. Não é possível corrigir porque a visualização de mensagem original é limitada na visualização de rolagem.
-* A pré-visualização do texto de uma mensagem não aparece (sempre) nos relógios Samsung porque [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) parece ser ignorado. É sabido que a pré-visualização do texto de mensagens é exibida corretamente nos relógios Pebble 2, Fitbit Charge 3, e Mi band 3. Veja também [ esse FAQ](#user-content-faq126).
+* A pré-visualização do texto de uma mensagem não aparece (sempre) nos relógios Samsung porque [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) parece ser ignorado. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP wearables. Veja também [ esse FAQ](#user-content-faq126).
* Um [problema no Android 6.0](https://issuetracker.google.com/issues/37068143) às vezes causa um travamento com a mensagem *... Invalid offset: ... Valid range is ...* ao selecionar o texto e depois tocar fora do texto selecionado. Esse erro foi corrigido no 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.
@@ -175,7 +175,7 @@ O design é baseado em várias discussões e, se quiser, você pode discutir sob
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) Como posso marcar todas as mensagens como lidas / mover ou excluir todas as mensagens?](#user-content-faq55)
* [(56) Você pode adicionar suporte para JMAP?](#user-content-faq56)
-* [~~(57) Posso usar HTML em assinaturas?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) O que um ícone de e-mail aberto/fechado significa?](#user-content-faq58)
* [(59) Mensagens originais podem ser abertas no navegador?](#user-content-faq59)
* [(60) Você sabia ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ O design é baseado em várias discussões e, se quiser, você pode discutir sob
* [(105) Como a opção roam-like-at-home funciona?](#user-content-faq105)
* [(106) Quais launcher (inicializadores) podem mostrar um contador com o número de mensagens não lidas?](#user-content-faq106)
* [(107) Como eu utilizo estrelas coloridas?](#user-content-faq107)
-* [(108) Você pode configurar para apagar mensagens permanentemente de qualquer pasta?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Porque 'selecionar conta' está disponível apenas nas versões oficiais?~~](#user-content-faq109)
* [(110) Por que (algumas) mensagems estão vazias e/ou com anexos corrompidos?](#user-content-faq110)
* [(111) OAuth é suportado?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operações são processadas somente quando há uma conexão com o servidor de e
Você deve tentar corrigir isso entrando em contato com seu provedor ou obtendo um certificado de segurança válido porque certificados de segurança inválidos são inseguros e permitem os chamados [ ataques man-in-the-middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Se dinheiro for um obstáculo, você pode obter certificados de segurança gratuitos no [Let's Encrypt](https://letsencrypt.org).
-Alternativamente, você pode aceitar a impressão digital mostrada abaixo da mensagem de erro, se você configurou a conta e/ou identidade nas etapas de configuração 1 e 2 (isso não é possível ao utilizar o assistente de configuração rápida). Observe que você deve se certificar de que a conexão com a intertet que você está utilizando é segura.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Observe ainda que versões mais antigas do Android podem não reconhecer as autoridades de certificados mais recentes como o Encrypt, fazendo com que as conexões sejam consideradas inseguras, veja também [aqui](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-pt-rPT.md b/docs/FAQ-pt-rPT.md
index 96cc81d8bc..4d3293bf1a 100644
--- a/docs/FAQ-pt-rPT.md
+++ b/docs/FAQ-pt-rPT.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ro-rRO.md b/docs/FAQ-ro-rRO.md
index fca90b6ddc..3e236d38f4 100644
--- a/docs/FAQ-ro-rRO.md
+++ b/docs/FAQ-ro-rRO.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-ru-rRU.md b/docs/FAQ-ru-rRU.md
index fc2af42f78..3427219555 100644
--- a/docs/FAQ-ru-rRU.md
+++ b/docs/FAQ-ru-rRU.md
@@ -75,7 +75,7 @@
* ~~ [ошибка в AndroidX](https://issuetracker.google.com/issues/64729576) затрудняет захват быстрой прокрутки. Обходное решение было добавлено.~~
* ~~Шифрование с помощью YubiKey приводит к бесконечному циклу. Похоже, что это вызвано ошибкой [в OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Прокрутка к внутренне привязанному местоположению в оригинальных сообщениях не работает. Это не может быть исправлено, потому что исходный вид сообщения содержится в прокрутке.
-* Предпросмотр текста сообщения (всегда) не отображается на Samsung watch, потому что [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)), похоже, игнорируется. Известно, что текст предварительного просмотра сообщений правильно отображаются на экране Pebble 2, Fitbit Charge 3 и Mi band 3. См. также [этот FAQ](#user-content-faq126).
+* Предпросмотр текста сообщения (всегда) не отображается на Samsung watch, потому что [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)), похоже, игнорируется. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP wearables. См. также [этот 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.
* Внутренние (якорные) ссылки не будут работать, потому что оригинальные сообщения отображаются во встроенном WebView в виде прокрутки (список разговоров). Это ограничение Android, которое не может быть исправлено или обойдено.
@@ -175,7 +175,7 @@
* [~~(54) Как использовать префикс пространства имён?~~](#user-content-faq54)
* [(55) Как я могу пометить все сообщения как прочитанные / переместить или удалить все сообщения?](#user-content-faq55)
* [(56) Вы можете добавить поддержку JMAP?](#user-content-faq56)
-* [~~(57) Можно использовать HTML в подписях?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) Что означает иконка с открытым или закрытым письмом?](#user-content-faq58)
* [(59) Можно ли открыть оригинальные сообщения в браузере?](#user-content-faq59)
* [(60) Знали ли Вы ...?](#user-content-faq60)
@@ -225,7 +225,7 @@
* [(105) Как работает вариант «роуминг как дома»?](#user-content-faq105)
* [(106) Какие программы запуска могут показывать счетчик значков с количеством непрочитанных сообщений?](#user-content-faq106)
* [(107) Как пользоваться цветными звездами?](#user-content-faq107)
-* [(108) Можно ли добавлять сообщения, удаляемые навсегда из любой папки?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Почему 'select account' доступен только в официальных версиях?~~](#user-content-faq109)
* [(110) Почему (некоторые) сообщения пусты и / или повреждены вложения?](#user-content-faq110)
* [(111) Поддерживается ли авторизация?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. Это означает, что все функции доступны и в версии F-Droid, за исключением использования мастера быстрой настройки Gmail, так как Google одобрил (и позволяет) только одну подпись приложения. Для всех других поставщиков электронной почты OAuth доступен только в версиях Play Store и релизах Github, поскольку поставщики электронной почты разрешили использовать OAuth только в официальных сборках.
+The F-Droid version is built from the same source code, but signed differently. Это означает, что все функции доступны и в версии F-Droid, за исключением использования мастера быстрой настройки Gmail, так как Google одобрил (и позволяет) только одну подпись приложения. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-sk-rSK.md b/docs/FAQ-sk-rSK.md
index 04a50c12d6..81fe9fd5f8 100644
--- a/docs/FAQ-sk-rSK.md
+++ b/docs/FAQ-sk-rSK.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-sl-rSI.md b/docs/FAQ-sl-rSI.md
index 2d5a332fc6..669cd2a5d6 100644
--- a/docs/FAQ-sl-rSI.md
+++ b/docs/FAQ-sl-rSI.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-sr-rSP.md b/docs/FAQ-sr-rSP.md
index e74ed9b5f5..c6743cf46d 100644
--- a/docs/FAQ-sr-rSP.md
+++ b/docs/FAQ-sr-rSP.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-sv-rSE.md b/docs/FAQ-sv-rSE.md
index eefdb47c14..ef95a6049f 100644
--- a/docs/FAQ-sv-rSE.md
+++ b/docs/FAQ-sv-rSE.md
@@ -75,7 +75,7 @@ Relaterade frågor:
* ~~En [bugg i AndroidX](https://issuetracker.google.com/issues/64729576) gör det svårt att ta den snabba scrollern. En lösning lades till.~~
* ~~Kryptering med YubiKey resulterar i en oändlig loop. Detta verkar bero på ett [fel i OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
* Att bläddra till en internt länkad plats i originalmeddelanden fungerar inte. Detta kan inte rättas till eftersom den ursprungliga meddelandevyn finns i en rullande vy.
-* En förhandsvisning av ett meddelande visas inte (alltid) på Samsung klockor eftersom [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) verkar ignoreras. Meddelanden är kända för att visas korrekt på Pebble 2, Fitbit Charge 3 och Mi band 3 wearables. Se även [denna FAQ](#user-content-faq126).
+* En förhandsvisning av ett meddelande visas inte (alltid) på Samsung klockor eftersom [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) verkar ignoreras. Meddelande förhandsgranskningstexter är kända för att visas korrekt på Pebble 2, Fitbit Charge 3, Mi band 3 och Xiaomi Amazfit BIP wearables. Se även [denna FAQ](#user-content-faq126).
* En [bugg i Android 6.0](https://issuetracker.google.com/issues/37068143) orsakar en krasch med *... Ogiltig offset: ... Giltigt intervall är ...* när text är markerad och knackar utanför den valda texten. Detta fel har rättats i Android 6.0.1.
* Interna (ankare) länkar kommer inte att fungera eftersom ursprungliga meddelanden visas i en inbäddad WebView i en rullande vy (meddelandelistan). Detta är en Android-begränsning som inte kan lösas eller arbetas runt.
@@ -175,7 +175,7 @@ Designen bygger på många diskussioner och om du vill kan du diskutera det [i d
* [~~(54) Hur använder jag ett namnrymdsprefix?~~](#user-content-faq54)
* [(55) Hur kan jag markera alla meddelanden som lästa/flytta eller ta bort alla meddelanden?](#user-content-faq55)
* [(56) Kan du lägga till stöd för JMAP?](#user-content-faq56)
-* [~~(57) Kan jag använda HTML i signaturer?~~](#user-content-faq57)
+* [(57) Kan jag använda HTML i signaturer?](#user-content-faq57)
* [(58) Vad betyder en öppen/stängd e-postikon?](#user-content-faq58)
* [(59) Kan originalmeddelanden öppnas i webbläsaren?](#user-content-faq59)
* [(60) Kände du till ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ Designen bygger på många diskussioner och om du vill kan du diskutera det [i d
* [(105) Hur fungerar roaming som hemma?](#user-content-faq105)
* [(106) Vilken hemapp kan visa ett märke med antalet olästa meddelanden?](#user-content-faq106)
* [(107) Hur använder jag färgade stjärnor?](#user-content-faq107)
-* [(108) Kan du lägga till permanent ta bort meddelanden från valfri mapp?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Varför finns "välj konto" endast i officiella versioner?~~](#user-content-faq109)
* [(110) Varför är (vissa) meddelanden tomma och/eller bilagor korrumperade?](#user-content-faq110)
* [(111) Stöds OAuth?](#user-content-faq111)
@@ -388,7 +388,7 @@ Meddelandet med låg prioritet visar antalet pågående åtgärder, som kan vara
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. Detta innebär att alla funktioner är tillgängliga i F-Droid versionen också, förutom att använda Gmail snabbinstallationsguide eftersom Google är godkänt (och tillåter) endast en app-signatur. För alla andra e-postleverantörer är OAuth åtkomst endast tillgänglig i Play Store-versioner och Github utgåvor, som e-postleverantörer har endast tillåtelse för officiella byggen att använda OAuth.
+The F-Droid version is built from the same source code, but signed differently. Detta innebär att alla funktioner är tillgängliga i F-Droid versionen också, förutom att använda Gmail snabbinstallationsguide eftersom Google är godkänt (och tillåter) endast en app-signatur. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-tr-rTR.md b/docs/FAQ-tr-rTR.md
index 446faf728a..c75859ec87 100644
--- a/docs/FAQ-tr-rTR.md
+++ b/docs/FAQ-tr-rTR.md
@@ -75,7 +75,7 @@ Sıkça rastlanan hata iletileri ve çözümleri için [burayı](#user-content-f
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-uk-rUA.md b/docs/FAQ-uk-rUA.md
index 741cc38f10..dc80fd0978 100644
--- a/docs/FAQ-uk-rUA.md
+++ b/docs/FAQ-uk-rUA.md
@@ -75,7 +75,7 @@
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-vi-rVN.md b/docs/FAQ-vi-rVN.md
index 2770b27178..92f48b217c 100644
--- a/docs/FAQ-vi-rVN.md
+++ b/docs/FAQ-vi-rVN.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-zh-rCN.md b/docs/FAQ-zh-rCN.md
index 2fabf39c1e..111fabeca0 100644
--- a/docs/FAQ-zh-rCN.md
+++ b/docs/FAQ-zh-rCN.md
@@ -75,7 +75,7 @@
* ~~A [bug in AndroidX](https://issuetracker.google.com/issues/64729576) makes it hard to grap the fast scroller. A workaround was added.~~ A workaround was added.~~
* ~~Encryption with YubiKey results into an infinite loop. ~~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. 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). 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). Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP 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. 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. This is an Android limitation which cannot be fixed or worked around.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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). If money is an obstacle, you can get free security certificates from [Let’s Encrypt](https://letsencrypt.org).
-Alternatively, you can accept the fingerprint shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe. Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
diff --git a/docs/FAQ-zh-rTW.md b/docs/FAQ-zh-rTW.md
index a19e0f7f8b..7f40f01a1c 100644
--- a/docs/FAQ-zh-rTW.md
+++ b/docs/FAQ-zh-rTW.md
@@ -75,7 +75,7 @@ Related questions:
* ~~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, Mi band 3, and Xiaomi Amazfit BIP 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.
@@ -175,7 +175,7 @@ The design is based on many discussions and if you like you can discuss about it
* [~~(54) How do I use a namespace prefix?~~](#user-content-faq54)
* [(55) How can I mark all messages as read / move or delete all messages?](#user-content-faq55)
* [(56) Can you add support for JMAP?](#user-content-faq56)
-* [~~(57) Can I use HTML in signatures?~~](#user-content-faq57)
+* [(57) Can I use HTML in signatures?](#user-content-faq57)
* [(58) What does an open/closed email icon mean?](#user-content-faq58)
* [(59) Can original messages be opened in the browser?](#user-content-faq59)
* [(60) Did you known ...?](#user-content-faq60)
@@ -225,7 +225,7 @@ The design is based on many discussions and if you like you can discuss about it
* [(105) How does the roam-like-at-home option work?](#user-content-faq105)
* [(106) Which launchers can show a badge count with the number of unread messages?](#user-content-faq106)
* [(107) How do I use colored stars?](#user-content-faq107)
-* [(108) Can you add permanently delete messages from any folder?](#user-content-faq108)
+* [~~(108) Can you add permanently delete messages from any folder?~~](#user-content-faq108)
* [~~(109) Why is 'select account' available in official versions only?~~](#user-content-faq109)
* [(110) Why are (some) messages empty and/or attachments corrupted?](#user-content-faq110)
* [(111) Is OAuth supported?](#user-content-faq111)
@@ -388,7 +388,7 @@ Operations are processed only when there is a connection to the email server or
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 shown below the error message if you set up the account and/or identity in setup step 1 and 2 (this is not possible when using the quick setup wizard). Note that you should make sure the internet connection you are using is safe.
+Alternatively, you can accept the fingerprint of the invalid server certificate as shown below the error message by ticking a checkbox. In case of an existing account (IMAP, receive) and/or identity (SMTP, send) you will need check/save it via setup step 1 and 2 to get the error message. This will "pin" the server certificate to prevent man-in-the-middle attacks. Note that you should make sure the internet connection you are using is safe if you do this.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@@ -909,7 +909,7 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
The error *... Authentication failed ... 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.
+The errors *... Authentication failed ... No token ...* 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
@@ -1168,9 +1168,9 @@ It is inevitable that synchronizing messages will use battery power because it r
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
-Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. In this case you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remotes messages are expensive operations.
+Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
-[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open.
+[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 4) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
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, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
@@ -1402,13 +1402,23 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
-**(57) ~~Can I use HTML in signatures?~~**
+**(57) Can I use HTML in signatures?**
-~~Yes, you can use HTML in signatures if you paste formatted text into the signature field or use the *Edit as HTML* menu to enter HTML manually.~~
+Yes, you can use [HTML](https://en.wikipedia.org/wiki/HTML). In the signature editor you can switch to HTML mode via the three-dots menu.
-~~Note that including links and images in messages will increase the likelihood that a message will be seen as spam,~~ ~~especially when you send a message to someone for the first time.~~
+Note that if you switch back to the text editor that not all HTML might be rendered as-is because the Android text editor is not able to render all HTML. Similarly, if you use the text editor, the HTML might be altered in unexpected ways.
-~~See [here](https://stackoverflow.com/questions/44410675/supported-html-tags-on-android-textview) for which HTML tags are supported.~~
+If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), you should wrap the text in a *pre* element, like this:
+
+```
+
+ |\_/|
+ / @ @ \
+( > º < )
+ `>>x<<´
+ / O \
+
+```
@@ -2213,6 +2223,7 @@ Google manages all purchases, so as a developer I have little control over purch
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
+* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases
@@ -2220,6 +2231,7 @@ You can also try to clear the cache of the Play store app via the Android apps s
Note that:
+* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
@@ -2317,7 +2329,7 @@ Directly after the first step new messages will be notified. However, only until
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
-If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*.
+If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
@@ -2592,7 +2604,7 @@ There is **only support** on the latest Play store version, the latest GitHub re
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
-The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers have only allowed permission for official builds to use OAuth.
+The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.