From 2abb7d0ef9ca62ad6399af8867212327edbb7180 Mon Sep 17 00:00:00 2001 From: M66B Date: Thu, 24 Dec 2020 08:52:50 +0100 Subject: [PATCH] Crowdin sync --- app/src/main/res/values-bg-rBG/strings.xml | 2 - app/src/main/res/values-ca-rES/strings.xml | 2 - app/src/main/res/values-cs-rCZ/strings.xml | 4 +- app/src/main/res/values-da-rDK/strings.xml | 5 +- app/src/main/res/values-de-rAT/strings.xml | 4 +- app/src/main/res/values-de-rDE/strings.xml | 4 +- app/src/main/res/values-de-rLI/strings.xml | 4 +- app/src/main/res/values-el-rGR/strings.xml | 4 +- app/src/main/res/values-en-rGB/strings.xml | 1 - app/src/main/res/values-es-rES/strings.xml | 4 +- app/src/main/res/values-eu-rES/strings.xml | 2 - app/src/main/res/values-fa-rIR/strings.xml | 1 - app/src/main/res/values-fi-rFI/strings.xml | 3 +- app/src/main/res/values-fr-rCA/strings.xml | 4 +- app/src/main/res/values-fr-rFR/strings.xml | 4 +- app/src/main/res/values-fy-rNL/strings.xml | 2 - app/src/main/res/values-gl-rES/strings.xml | 2 - app/src/main/res/values-hr-rHR/strings.xml | 2 - app/src/main/res/values-hu-rHU/strings.xml | 2 - app/src/main/res/values-in-rID/strings.xml | 2 - app/src/main/res/values-it-rIT/strings.xml | 4 +- app/src/main/res/values-ja-rJP/strings.xml | 8 +- app/src/main/res/values-nl-rNL/strings.xml | 4 +- app/src/main/res/values-nn-rNO/strings.xml | 28 ++- app/src/main/res/values-no-rNO/strings.xml | 28 ++- app/src/main/res/values-pl-rPL/strings.xml | 4 +- app/src/main/res/values-pt-rBR/strings.xml | 2 - app/src/main/res/values-pt-rPT/strings.xml | 1 - app/src/main/res/values-ro-rRO/strings.xml | 2 - app/src/main/res/values-ru-rRU/strings.xml | 4 +- app/src/main/res/values-sk-rSK/strings.xml | 4 +- app/src/main/res/values-sl-rSI/strings.xml | 2 - app/src/main/res/values-sv-rSE/strings.xml | 4 +- app/src/main/res/values-tr-rTR/strings.xml | 2 - app/src/main/res/values-zh-rCN/strings.xml | 4 +- app/src/main/res/values-zh-rTW/strings.xml | 2 - docs/FAQ-af-rZA.md | 2 + docs/FAQ-ar-rBH.md | 2 + docs/FAQ-ar-rEG.md | 2 + docs/FAQ-ar-rYE.md | 2 + docs/FAQ-az-rAZ.md | 28 +-- docs/FAQ-bg-rBG.md | 2 + docs/FAQ-bn-rBD.md | 2 + docs/FAQ-bn-rIN.md | 2 + docs/FAQ-ca-rES.md | 2 + docs/FAQ-cs-rCZ.md | 2 + docs/FAQ-da-rDK.md | 194 +++++++++++---------- docs/FAQ-de-rAT.md | 2 + docs/FAQ-de-rDE.md | 2 + docs/FAQ-de-rLI.md | 2 + docs/FAQ-el-rGR.md | 2 + docs/FAQ-en-rGB.md | 2 + docs/FAQ-es-rES.md | 10 +- docs/FAQ-eu-rES.md | 2 + docs/FAQ-fa-rIR.md | 2 + docs/FAQ-fi-rFI.md | 4 +- docs/FAQ-fr-rCA.md | 2 + docs/FAQ-fr-rFR.md | 2 + docs/FAQ-fy-rNL.md | 2 + docs/FAQ-gl-rES.md | 2 + docs/FAQ-hi-rIN.md | 2 + docs/FAQ-hr-rHR.md | 2 + docs/FAQ-hu-rHU.md | 2 + docs/FAQ-in-rID.md | 2 + docs/FAQ-it-rIT.md | 2 + docs/FAQ-iw-rIL.md | 2 + docs/FAQ-ja-rJP.md | 2 + docs/FAQ-ka-rGE.md | 2 + docs/FAQ-kk-rKZ.md | 2 + docs/FAQ-ko-rKR.md | 2 + docs/FAQ-lt-rLT.md | 2 + docs/FAQ-nl-rNL.md | 2 + docs/FAQ-nn-rNO.md | 2 + docs/FAQ-no-rNO.md | 2 + docs/FAQ-pl-rPL.md | 2 + docs/FAQ-pt-rBR.md | 2 + docs/FAQ-pt-rPT.md | 2 + docs/FAQ-ro-rRO.md | 2 + docs/FAQ-ru-rRU.md | 2 + docs/FAQ-si-rLK.md | 2 + docs/FAQ-sk-rSK.md | 2 + docs/FAQ-sl-rSI.md | 2 + docs/FAQ-sr-rSP.md | 2 + docs/FAQ-sv-rSE.md | 2 + docs/FAQ-ta-rIN.md | 2 + docs/FAQ-tr-rTR.md | 2 + docs/FAQ-uk-rUA.md | 2 + docs/FAQ-vi-rVN.md | 2 + docs/FAQ-zh-rCN.md | 2 + docs/FAQ-zh-rTW.md | 2 + 90 files changed, 296 insertions(+), 201 deletions(-) diff --git a/app/src/main/res/values-bg-rBG/strings.xml b/app/src/main/res/values-bg-rBG/strings.xml index 2165b948cb..0b5e3cb758 100644 --- a/app/src/main/res/values-bg-rBG/strings.xml +++ b/app/src/main/res/values-bg-rBG/strings.xml @@ -217,7 +217,6 @@ Синхронизиране на споделени списъци с папки Управление на абонирани папки Проверка имейл адреса на изпращача при синхронизиране на съобщенията - Проверка имейл адреса на изпращача при синхронизиране на съобщенията Автоматично настройване на онлайн интервала Клавиатура по подразбиране Предложи локални контакти @@ -400,7 +399,6 @@ Деактивирането на това ще намали донякъде използването на данни и батерията, но ще деактивира и актуализирането на списъка с папки Проверка дали DNS MX записи съществуват Това ще забави синхронизирането на съобщенията - Това ще провери дали името на домейна на изпращача и адреса за отговор е едно и също В допълнение към контактите, осигурени от Android. Данните за контакт ще бъдат съхранявани за нови изпратени или получени съобщения, само когато са активирани. Вмъкнете \'-\' между текста и подписа Показва предупреждение когато текстът на съобщението или темата е празна или когато прикаченият файл липсва diff --git a/app/src/main/res/values-ca-rES/strings.xml b/app/src/main/res/values-ca-rES/strings.xml index b2b1da8625..52bf0dbb67 100644 --- a/app/src/main/res/values-ca-rES/strings.xml +++ b/app/src/main/res/values-ca-rES/strings.xml @@ -219,7 +219,6 @@ La creació i l\'ús de regles és una característica professional. Sincronitza la llista de carpetes Gestioneu les subscripcions de carpeta Comproveu les adreces de correu electrònic del remitent sobre la sincronització de missatges - Comproveu les adreces de correu electrònic del remitent a la sincronització de missatges Ajustar automàticament l’interval de mantenir viu Mostra el teclat per defecte Suggeriu contactes emmagatzemats localment @@ -407,7 +406,6 @@ La creació i l\'ús de regles és una característica professional. Si el desactiveu, reduireu una mica l’ús de les dades i la bateria, però també desactivareu l’actualització de la llista de carpetes Això comprovarà si existeixen registres MX al DNS Això alentirà la sincronització de missatges - Això comprovarà si el nom de domini de l’emissor i les adreces de resposta són els mateixos A més dels contactes proporcionats per Android. Les dades de contacte s’emmagatzemaran per als missatges recentment enviats o rebuts només quan estiguin habilitats. Inseriu \"--\" entre el text i la signatura Mostra un avís quan el text del missatge o el tema està buit o quan falta un fitxer adjunt diff --git a/app/src/main/res/values-cs-rCZ/strings.xml b/app/src/main/res/values-cs-rCZ/strings.xml index e80f00c8da..93786e4d1c 100644 --- a/app/src/main/res/values-cs-rCZ/strings.xml +++ b/app/src/main/res/values-cs-rCZ/strings.xml @@ -268,7 +268,6 @@ Spravovat odběry složek Automaticky synchronizovat odebírané složky Kontrolovat e-mailové adresy odesílatelů při synchronizaci zpráv - Kontrolovat e-mailové adresy pro odpověď při synchronizaci zpráv Automaticky vyladit interval udržení naživu Automaticky zobrazit klávesnici Zabránit zobrazení klávesnice na celou obrazovku @@ -487,7 +486,6 @@ Vypnutí o něco sníží množství přenesených dat a spotřebu baterie, zároveň však znemožní aktualizovat seznam složek Ověří existenci DNS MX záznamů Zpomalí synchronizaci zpráv - Ověří, zda jsou název domény odesílatele a adresy pro odpověď totožné Jako dodatek ke kontaktům poskytnutých Androidem. Je-li povoleno, kontaktní údaje budou ukládány pro nově odeslané či přijaté zprávy. Vložit \'-- \' mezi text a podpis Zobrazit upozornění, je-li text zprávy či předmět prázdný nebo může-li chybět příloha @@ -723,7 +721,7 @@ Pouze uživatelské složky Hlavní účet složky Složky sjednocené doručené pošty - Místní koncepty + Místní koncepty Žádné složky Žádné zprávy Jeden nebo více filtrů aktivních diff --git a/app/src/main/res/values-da-rDK/strings.xml b/app/src/main/res/values-da-rDK/strings.xml index b408d34b69..946a8551d0 100644 --- a/app/src/main/res/values-da-rDK/strings.xml +++ b/app/src/main/res/values-da-rDK/strings.xml @@ -246,7 +246,6 @@ Håndér mappeabonnementer Synkronisér automatisk mappeabonnementer Tjek afsenderadresser ved beskedsynkroniseringer - Tjek svar e-mailadresser ved beskedsynkroniseringer Justér automatisk hold i live intervallet Vis tastatur som standard Forhindr fuldskærmstastatur @@ -467,7 +466,6 @@ Deaktivering af dette reducerer data- og strømforbruget noget, men deaktiverer også mappelisteopdatering Dette tjekker, om der findes DNS MX-poster Dette vil forøge beskedsynkroniseringstiden - Dette tjekker, om domænenavnet for afsender- og svaradresser er ens Ud over kontakter fra Android. Kontaktdata gemmes kun for nyligt afsendte eller modtagne beskeder, når aktiveret. Indsæt \'-- \' mellem teksten og signaturen Vis en advarsel, når beskedtekst eller emne er tomt, eller en vedhæftet fil muligvis mangler @@ -703,7 +701,7 @@ Kun brugermapper Primærkontomapper Saml indbakkemapper - Lokale udkast + Lokale udkast Ingen mapper Ingen beskeder Ét eller flere filtre er aktive @@ -752,6 +750,7 @@ Spam Flyt Kopiér + Nøgleord Afmeld Opret regel Ikke spam diff --git a/app/src/main/res/values-de-rAT/strings.xml b/app/src/main/res/values-de-rAT/strings.xml index 6755c95cc0..e275cace22 100644 --- a/app/src/main/res/values-de-rAT/strings.xml +++ b/app/src/main/res/values-de-rAT/strings.xml @@ -247,7 +247,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Abonnierte Ordner verwalten Abonnierte Ordner automatisch synchronisieren Überprüft die Absender-E-Mail-Adressen beim Synchronisieren von Nachrichten per DNS MX - Überprüft die Antwort-An-E-Mail-Adressen beim Synchronisieren von Nachrichten Aktivitätsintervall automatisch anpassen Tastatur standardmäßig anzeigen Vollbild-Tastatur verhindern @@ -468,7 +467,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Die Deaktivierung dieser Funktion verringert den Daten- und Akkuverbrauch etwas, deaktiviert aber auch die Aktualisierung der Ordnerliste. Überprüft, ob DNS-MX-Einträge vorhanden sind Dies verzögert die Synchronisierung von Nachrichten - Überprüft, ob die Domain des Absenders und der Antwort-An-Adresse gleich sind Zusätzlich zu den von Android bereitgestellten Kontakten werden weitere Kontaktdaten für neue gesendete oder erhaltene Nachrichten nur dann gespeichert, wenn dies aktiviert ist. Signaturtrenner »-- « zwischen Text und Signatur einfügen Eine Warnung anzeigen, wenn der Nachrichtentext oder der Betreff leer ist oder wenn ein Anhang zu fehlen scheint @@ -703,7 +701,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Nur Benutzerordner Hauptkontoordner Sammeleingangsordner - Lokale Entwürfe + Lokale Entwürfe Keine Ordner Keine Nachrichten Ein oder mehrere Filter aktiv diff --git a/app/src/main/res/values-de-rDE/strings.xml b/app/src/main/res/values-de-rDE/strings.xml index 6755c95cc0..e275cace22 100644 --- a/app/src/main/res/values-de-rDE/strings.xml +++ b/app/src/main/res/values-de-rDE/strings.xml @@ -247,7 +247,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Abonnierte Ordner verwalten Abonnierte Ordner automatisch synchronisieren Überprüft die Absender-E-Mail-Adressen beim Synchronisieren von Nachrichten per DNS MX - Überprüft die Antwort-An-E-Mail-Adressen beim Synchronisieren von Nachrichten Aktivitätsintervall automatisch anpassen Tastatur standardmäßig anzeigen Vollbild-Tastatur verhindern @@ -468,7 +467,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Die Deaktivierung dieser Funktion verringert den Daten- und Akkuverbrauch etwas, deaktiviert aber auch die Aktualisierung der Ordnerliste. Überprüft, ob DNS-MX-Einträge vorhanden sind Dies verzögert die Synchronisierung von Nachrichten - Überprüft, ob die Domain des Absenders und der Antwort-An-Adresse gleich sind Zusätzlich zu den von Android bereitgestellten Kontakten werden weitere Kontaktdaten für neue gesendete oder erhaltene Nachrichten nur dann gespeichert, wenn dies aktiviert ist. Signaturtrenner »-- « zwischen Text und Signatur einfügen Eine Warnung anzeigen, wenn der Nachrichtentext oder der Betreff leer ist oder wenn ein Anhang zu fehlen scheint @@ -703,7 +701,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Nur Benutzerordner Hauptkontoordner Sammeleingangsordner - Lokale Entwürfe + Lokale Entwürfe Keine Ordner Keine Nachrichten Ein oder mehrere Filter aktiv diff --git a/app/src/main/res/values-de-rLI/strings.xml b/app/src/main/res/values-de-rLI/strings.xml index 6755c95cc0..e275cace22 100644 --- a/app/src/main/res/values-de-rLI/strings.xml +++ b/app/src/main/res/values-de-rLI/strings.xml @@ -247,7 +247,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Abonnierte Ordner verwalten Abonnierte Ordner automatisch synchronisieren Überprüft die Absender-E-Mail-Adressen beim Synchronisieren von Nachrichten per DNS MX - Überprüft die Antwort-An-E-Mail-Adressen beim Synchronisieren von Nachrichten Aktivitätsintervall automatisch anpassen Tastatur standardmäßig anzeigen Vollbild-Tastatur verhindern @@ -468,7 +467,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Die Deaktivierung dieser Funktion verringert den Daten- und Akkuverbrauch etwas, deaktiviert aber auch die Aktualisierung der Ordnerliste. Überprüft, ob DNS-MX-Einträge vorhanden sind Dies verzögert die Synchronisierung von Nachrichten - Überprüft, ob die Domain des Absenders und der Antwort-An-Adresse gleich sind Zusätzlich zu den von Android bereitgestellten Kontakten werden weitere Kontaktdaten für neue gesendete oder erhaltene Nachrichten nur dann gespeichert, wenn dies aktiviert ist. Signaturtrenner »-- « zwischen Text und Signatur einfügen Eine Warnung anzeigen, wenn der Nachrichtentext oder der Betreff leer ist oder wenn ein Anhang zu fehlen scheint @@ -703,7 +701,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se Nur Benutzerordner Hauptkontoordner Sammeleingangsordner - Lokale Entwürfe + Lokale Entwürfe Keine Ordner Keine Nachrichten Ein oder mehrere Filter aktiv diff --git a/app/src/main/res/values-el-rGR/strings.xml b/app/src/main/res/values-el-rGR/strings.xml index 879c4c6850..119f7c3837 100644 --- a/app/src/main/res/values-el-rGR/strings.xml +++ b/app/src/main/res/values-el-rGR/strings.xml @@ -246,7 +246,6 @@ Διαχείριση συνδρομών σε φακέλους Αυτόματος συγχρονισμός των φακέλων με συνδρομή Έλεγχος διευθύνσεων των αποστολέων κατά τον συγχρονισμό μηνυμάτων - Έλεγχος διευθύνσεων των απαντήσεων κατά τον συγχρονισμό μηνυμάτων Αυτόματη ρύθμιση του χρονικού διαστήματος για διατήρηση ενεργής σύνδεσης Εμφάνιση του πληκτρολογίου από προεπιλογή Να μην προβάλλεται το πληκτρολόγιο σε πλήρη οθόνη @@ -465,7 +464,6 @@ Αν απενεργοποιηθεί, θα μειωθεί κάπως η χρήση δεδομένων και μπαταρίας, αλλά θα απενεργοποιηθεί και ο συγχρονισμός της λίστας των φακέλων επίσης Ελέγχει αν υπάρχουν καταγραφές DNS MX Η επιλογή αυτή θα επιβραδύνει τον συγχρονισμό των μηνυμάτων - Ελέγχει αν το το όνομα τομέα του αποστολέα και οι διευθύνσεις απάντησης είναι ίδια Επιπρόσθετα στις παρεχόμενες από το Android επαφές, θα αποθηκεύονται πληροφορίες επαφών για πρόσφατα απεσταλμένα ή ειλημμένα μηνύματα, μόνον εφόσον οι σχετικές δυνατότητες έχουν ενεργοποιηθεί. Να παρεμβάλλεται ένα \'-- \' ανάμεσα στο κείμενο και την υπογραφή Να προβάλλεται μια προειδοποίηση όταν το κείμενο του μηνύματος ή το θέμα είναι κενό ή όταν φαίνεται πως ένα συνημμένο λείπει @@ -701,7 +699,7 @@ Φάκελοι χρήστη μόνον Φάκελοι κύριου λογαριασμού Φάκελοι ενοποιημένων εισερχομένων - Τοπικά πρόχειρα + Τοπικά πρόχειρα Κανείς φάκελος Κανένα μήνυμα Ένα ή περισσότερα φίλτρα ενεργά diff --git a/app/src/main/res/values-en-rGB/strings.xml b/app/src/main/res/values-en-rGB/strings.xml index 2985dd5b6b..3db10d66ac 100644 --- a/app/src/main/res/values-en-rGB/strings.xml +++ b/app/src/main/res/values-en-rGB/strings.xml @@ -8,7 +8,6 @@ Reverse colours Synchronise folder list Check sender email addresses on synchronising messages - Check reply email addresses on synchronising messages Use two rows in portrait mode Show colour stripe Threshold letter colour diff --git a/app/src/main/res/values-es-rES/strings.xml b/app/src/main/res/values-es-rES/strings.xml index 3c060d250b..9ab789acb8 100644 --- a/app/src/main/res/values-es-rES/strings.xml +++ b/app/src/main/res/values-es-rES/strings.xml @@ -247,7 +247,6 @@ Administrar suscripciones de carpeta Sincronizar automáticamente las carpetas suscritas Compruebe las direcciones de correo electrónico de remitentes al sincronizar mensajes - Comprobar direcciones de correo de respuesta al sincronizar mensajes Ajustar automáticamente el intervalo de keep-alive Mostrar teclado por defecto Evitar teclado de pantalla completa @@ -468,7 +467,6 @@ Desactivar esto reducirá el uso de datos y batería, pero también desactivará la actualización de la lista de carpetas Esto comprobará si existen registros DNS MX Esto ralentizará la sincronización de mensajes - Esto comprobará si el nombre de dominio del remitente y las direcciones de respuesta son las mismas Además de los contactos proporcionados por Android, los datos de contactos se almacenarán para nuevos mensajes enviados o recibidos sólo cuando esté activado. Insertar \'-- \' entre el texto y la firma Mostrar una advertencia cuando el texto del mensaje o el asunto estén vacíos o cuando un archivo adjunto pueda estar ausente @@ -704,7 +702,7 @@ Sólo carpetas de usuario Cuenta primaria de carpetas Carpetas de bandeja de entrada unificada - Borradores locales + Borradores locales No hay carpetas Sin mensajes Uno o más filtros activos diff --git a/app/src/main/res/values-eu-rES/strings.xml b/app/src/main/res/values-eu-rES/strings.xml index 2f3bfec81a..cc69b1a0b4 100644 --- a/app/src/main/res/values-eu-rES/strings.xml +++ b/app/src/main/res/values-eu-rES/strings.xml @@ -219,7 +219,6 @@ Sinkronizatu partekatutako karpeten zerrenda Kudeatu karpeten harpidetzak Egiaztatu bidaltzailearen helbide elektronikoak mezuak sinkronizatzean - Egiaztatu erantzuteko helbide elektronikoak mezuak sinkronizatzean Doitu automatikoki biziri-mantendu tartea Erakutsi teklatua lehenetsita Proposatu lokalean gordetako kontaktuak @@ -399,7 +398,6 @@ Hori ezgaitzeak datuak eta bateriaren erabilera zertxobait murriztuko ditu, baina karpeten zerrenda eguneratzea ere ezgaituko du Honek DNS MX erregistroak dauden ala ez egiaztatuko du Honek mezuen sinkronizazioa motelduko du - Honek egiaztatuko du bidaltzailearen domeinuaren izena eta erantzutekoa berdinak ote diren Android-en kontaktuez gain. Kontaktuen datuak gordeko dira mezuak bidali edo jasotzean soilik baimenduta badago. Txertatu \'-- \' testua eta sinaduraren artean Erakutsi abisua mezuaren edo gairen testua hutsik dagoenean edo eranskina falta denean diff --git a/app/src/main/res/values-fa-rIR/strings.xml b/app/src/main/res/values-fa-rIR/strings.xml index 3e99b52f4f..82740d90ac 100644 --- a/app/src/main/res/values-fa-rIR/strings.xml +++ b/app/src/main/res/values-fa-rIR/strings.xml @@ -221,7 +221,6 @@ فهرست‌های پوشه‌های همرسانی شده را همگام‌سازی کن مدیریت اشتراکات پوشه نشانی‌های ایمیل فرستنده را هنگام همگام‌سازی پیام‌ها بررسی کن - نشانی‌های ایمیل پاسخ را هنگام همگام‌سازی پیام‌ها بررسی کن وقفه زنده-نگه‌داشتن را خودکار کوک کن نمایش صفحه کلید به‌صورت پیش‌فرض پیشنهاد مخاطبین ذخیره‌شده محلی diff --git a/app/src/main/res/values-fi-rFI/strings.xml b/app/src/main/res/values-fi-rFI/strings.xml index 7b6a177f71..2f0fe94ae4 100644 --- a/app/src/main/res/values-fi-rFI/strings.xml +++ b/app/src/main/res/values-fi-rFI/strings.xml @@ -244,7 +244,6 @@ Hallinnoi tilattuja kansioita Synkronoi tilatut kansiot automaattisesti Tarkista lähettäjien sähköpostiosoitteet viestejä synkronoitaessa - Tarkista vastaussähköpostiosoitteet viestejä synkronoitaessa Säädä ylläpitokyselyn aikaväli automaattisesti Näytä näppäimistö oletuksena Estä koko näytön näppäimistö @@ -464,7 +463,6 @@ Tämän kytkeminen pois vähentää datan ja akun käyttöä, mutta kytkee pois myös kansiolistan päivittymisen Tämä tarkistaa löytyykö DNS MX-tietoja Tämä hidastaa viestien synkronointia - Tämä tarkistaa, ovatko lähetys- ja vastaussähköpostiosoitteiden verkkotunnukset samat Androidin yhteystietojen lisäksi. Yhteystietoja tallennetaan uusista lähetetyistä ja vastaanotetuista viesteistä vain, jos asetus on päällä. Lisää \'--\' tekstin ja allekirjoituksen väliin Näytä varoitus, kun viestin teksti tai aihe on tyhjä tai kun liite puuttuu @@ -700,6 +698,7 @@ Vain käyttäjän kansiot Kansion ensisijainen tili Yhdistetyn saapuneet-kansion kansiot + Paikalliset luonnokset Ei kansioita Ei viestejä Yksi tai useampi suodatin aktiivinen diff --git a/app/src/main/res/values-fr-rCA/strings.xml b/app/src/main/res/values-fr-rCA/strings.xml index 7e0fcfd74f..1753cf3bb6 100644 --- a/app/src/main/res/values-fr-rCA/strings.xml +++ b/app/src/main/res/values-fr-rCA/strings.xml @@ -246,7 +246,6 @@ Gérer les abonnements aux dossiers Synchroniser automatiquement les dossiers abonnés Vérifier l’adresse courriel de l’expéditeur lors de la synchronisation des messages - Vérifier les adresses courriel de réponse lors de la synchronisation des messages Ajuster automatiquement l\'intervalle de connexion Afficher le clavier par défaut Ne pas afficher le clavier en plein écran @@ -467,7 +466,6 @@ Désactiver ceci réduira quelque peu l’utilisation des données et de la pile mais désactivera également la mise à jour de la liste des dossiers Ceci vérifiera si des enregistrements MX DNS existent Ceci ralentira la synchronisation des messages - Ceci vérifiera si le nom de domaine de l’expéditeur et des adresses de réponse sont identiques En plus des contacts fournis par Android. Les données de contact seront stockées pour les messages récemment envoyés ou reçus uniquement lorsque ceci est activé. Insérer -- entre le texte et la signature Afficher un avertissement quand le texte du message ou l’objet sont vides ou quand une pièce jointe semble avoir été oubliée @@ -703,7 +701,7 @@ Dossiers utilisateur seulement Dossiers du compte principal Dossiers de la boîte de réception unifiée - Brouillons locaux + Brouillons locaux Aucun dossier Aucun message Un ou plusieurs filtres actifs diff --git a/app/src/main/res/values-fr-rFR/strings.xml b/app/src/main/res/values-fr-rFR/strings.xml index 659ad94c06..284a7e3019 100644 --- a/app/src/main/res/values-fr-rFR/strings.xml +++ b/app/src/main/res/values-fr-rFR/strings.xml @@ -246,7 +246,6 @@ Gérer les abonnements aux dossiers Synchroniser automatiquement les dossiers abonnés Vérifier l\'adresse e-mail de l\'expéditeur lors de la synchronisation des messages - Vérifier les adresses e-mail de réponse lors de la synchronisation des messages Ajuster automatiquement l\'intervalle de connexion Afficher le clavier par défaut Ne pas afficher le clavier en plein écran @@ -467,7 +466,6 @@ Désactiver ceci réduira quelque peu l\'utilisation des données et de la batterie mais désactivera également la mise à jour de la liste des dossiers Ceci vérifiera l’existence d’enregistrements DNS mail exchanger (MX) Ceci ralentira la synchronisation des messages - Ceci vérifiera si le nom de domaine de l’expéditeur et des adresses de réponse sont identiques En plus des contacts fournis par Android. Les informations des contacts seront stockées pour les messages récemment envoyés ou reçus seulement si ceci est activé. Insérer \'-- \' entre le texte et la signature Afficher un avertissement quand le texte du message ou l’objet sont vides ou quand une pièce jointe semble avoir été oubliée @@ -703,7 +701,7 @@ Dossiers utilisateur seulement Dossiers du compte principal Dossiers de la boîte de réception unifiée - Brouillons locaux + Brouillons locaux Aucun dossier Aucun message Un ou plusieurs filtres actifs diff --git a/app/src/main/res/values-fy-rNL/strings.xml b/app/src/main/res/values-fy-rNL/strings.xml index 06bfd85105..13559e2aec 100644 --- a/app/src/main/res/values-fy-rNL/strings.xml +++ b/app/src/main/res/values-fy-rNL/strings.xml @@ -246,7 +246,6 @@ Mapabonneminten beheare Syngroniseare mappen automatysk syngronisearje Kontrolearje e-postadressen fan stjoerder op syngronisearjen fan berjochten - Kontrolearje e-postadressen foar antwurd op berjochten syngronisearje Tune it ynterval foar libbenhâlden automatysk Sjoch toetseboerd mei standert Foarkom toetseboerd op folslein skerm @@ -465,7 +464,6 @@ As jo dit útskeakelje, sille gegevens en batterijgebrûk wat ferminderje, mar sil it bywurkjen fan de list mei mappen ek útskeakelje Kontrolearje periodyk lykas FairEmail noch aktyf is Dit sil syngronisearjende berjochten fertrage - Dit sil kontrolearje as domeinnamme fan \'e stjoerder en antwurdadressen itselde binne Neist kontakten levere troch Android. Kontaktgegevens wurde allinich opslein foar nij ferstjoerde of ûntfange berjochten as dizze ynskeakele is. Foegje \'-\' yn tusken de tekst en de hantekening Toan in warskôging as de tekst fan it berjocht as it ûnderwerp leech is of as in bylage miskien mist diff --git a/app/src/main/res/values-gl-rES/strings.xml b/app/src/main/res/values-gl-rES/strings.xml index 802892b22f..7ed280428f 100644 --- a/app/src/main/res/values-gl-rES/strings.xml +++ b/app/src/main/res/values-gl-rES/strings.xml @@ -239,7 +239,6 @@ Sincronizar lista de cartafoles compartidos Xestionar subscricións a cartafoles Verificar o enderezo de email dos remitentes ao sincronizar as mensaxes - Verificar o enderezo de email das réplicas ao sincronizar as mensaxes Axustar automaticamente o intervalo de comprobación de conexión Mostrar teclado por defecto Suxerir contactos almacenados localmente @@ -451,7 +450,6 @@ Ao desactivar isto, reducirase algo o consumo de datos e de batería, pero tamén se desactivará a actualización dos cartafoles Isto comproba se as entradas DNS MX existen Isto retardará a sincronización das mensaxes - Isto comproba se o dominio do remitente e o enderezo de resposta coinciden Ademais dos contactos de Android. A información dos contactos almacenarase para as novas mensaxes enviadas ou recibidas soamente cando estea activado. Inserir \'-- \' entre o texto e a sinatura Mostrar unha advertencia cando o texto ou o asunto da mensaxe está baleiro ou cando podería ser que faltara un anexo diff --git a/app/src/main/res/values-hr-rHR/strings.xml b/app/src/main/res/values-hr-rHR/strings.xml index 4ddf3269d3..11ad55c966 100644 --- a/app/src/main/res/values-hr-rHR/strings.xml +++ b/app/src/main/res/values-hr-rHR/strings.xml @@ -220,7 +220,6 @@ Sinkroniziraj popis mapa Upravljanje pretplatama za mape Provjerite adrese pošiljatelja pri sinkronizaciji poruka - Provjerite adrese e-pošte s odgovorima na usklađivanje poruka Standardno pokaži tastaturu Predložiti lokalno pohranjene kontakte Predložiti adrese pronađene u poslanim porukama @@ -361,7 +360,6 @@ Onemogućavanjem će se nešto smanjiti korištenje podataka i baterija, ali će se onemogućiti i ažuriranje popisa mapa Ovo će provjeriti dali postoju DNS MX zapisi Ovo će usporiti sinkronizaciju poruka - Ovim će se provjeriti jesu li ime domene pošiljatelja i adrese odgovora isti Pored kontakata koje pruža Android. Podaci za kontakte bit će pohranjeni za novoprimljene ili primljene poruke samo ako su omogućene. Umetni \'--\' između teksta i potpisa Pokaži upozorenje kada je tekst poruke ili predmet prazan ili kada prilog možda nedostaje diff --git a/app/src/main/res/values-hu-rHU/strings.xml b/app/src/main/res/values-hu-rHU/strings.xml index 4f2e36afd9..6292ae2d02 100644 --- a/app/src/main/res/values-hu-rHU/strings.xml +++ b/app/src/main/res/values-hu-rHU/strings.xml @@ -244,7 +244,6 @@ Szinkronizált mappák listája Mappa feliratkozások kezelése Küldő email címek ellenőrzése az üzenetek szinkronizálásakor - Válasz email címek ellenőrzése az üzenetek szinkronizálásakor Az ébrentartás időtartamának automatikus hangolása Billentyűzet alapértelmezett megjelenítése Teljes képernyős billentyűzet letiltása @@ -455,7 +454,6 @@ Kikapcsolása valamelyest csökkentheti az adatforgalom- és akkumulátorhasználatot, de egyúttal a mappák listájának frissítését is megakadályozza Ez a DNS MX bejegyzés ellenőrzésével jár Ez lelassítja az üzenetek szinkronizálását - Ez ellenőrzi hogy a feladott domain neve és a válasz címe megegyezik Az Android által biztosított névjegyek mellett. A kapcsolattartási adatokat az újonnan elküldött vagy fogadott üzenetek csak akkor fogják tárolni, ha ez engedélyezve van. Elválasztó \'--\' beillesztése a szövegtörzs és az aláírás közé Figyelmeztetés megjelenítése, ha az üzenet szövege vagy a tárgy üres, illetve ha a melléklet feltehetőleg hiányzik diff --git a/app/src/main/res/values-in-rID/strings.xml b/app/src/main/res/values-in-rID/strings.xml index f75fcfa029..1d5ff46bee 100644 --- a/app/src/main/res/values-in-rID/strings.xml +++ b/app/src/main/res/values-in-rID/strings.xml @@ -227,7 +227,6 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot Kelola folder langganan Sinkronisasi folder langganan secara otomatis Periksa alamat email pengirim di sinkronisasi pesan - Periksa alamat email balasan pada sinkronisasi pesan Secara otomatis mengatur interval tetap-hidup Tampilkan keyboard secara bawaan Nonaktifkan keyboard layar penuh @@ -443,7 +442,6 @@ Akun dan identitas (alias) juga dapat diatur secara manual jika diperlukan. Prot Menonaktifkan ini akan mengurangi penggunaan data dan sedikit baterai, tetapi juga akan menonaktifkan pembaruan daftar folder Ini akan memeriksa apakah catatan DNS MX ada Ini akan memperlambat sinkronisasi pesan - Ini akan memeriksa apakah nama domain dari alamat pengirim dan balasannya sama Selain kontak yang disediakan oleh Android. Data kontak akan disimpan untuk pesan yang baru dikirim atau diterima hanya ketika diaktifkan. Sisipkan \'-- \' antara teks dan tanda tangan Menampilkan peringatan ketika teks pesan atau subjek kosong atau mungkin ketika lampiran pesan hilang diff --git a/app/src/main/res/values-it-rIT/strings.xml b/app/src/main/res/values-it-rIT/strings.xml index 0659bdc280..d7e0fd0a29 100644 --- a/app/src/main/res/values-it-rIT/strings.xml +++ b/app/src/main/res/values-it-rIT/strings.xml @@ -246,7 +246,6 @@ Gestisci abbonamenti cartelle Sincronizza automaticamente le cartelle sottoscritte Controlla gli indirizzi e-mail mittente alla sincronizzazione dei messaggi - Controlla gli indirizzi e-mail di risposta alla sincronizzazione dei messaggi Regola automaticamente l\'intervallo keepalive Mostra tastiera in modo predefinito Impedisci la tastiera a schermo intero @@ -467,7 +466,6 @@ Disabilitando questa opzione si ridurranno in qualche modo i dati e l\'utilizzo della batteria, ma disattiverà anche l\'aggiornamento della lista delle cartelle Questo controllerà se esistono record DNS MX Questo rallenterà la sincronizzazione dei messaggi - Questo controlla se il nome di dominio del mittente e gli indirizzi di risposta sono uguali Oltre ai contatti forniti da Android. I dati di contatto verranno archiviati per i messaggi appena inviati o ricevuti solo quando abilitato. Inserisci \'-- \' tra il testo e la firma Mostra un avviso quando il testo del messaggio o l\'oggetto è vuoto o quando un allegato potrebbe mancare @@ -703,7 +701,7 @@ Solo cartelle utente Cartelle account principale Cartella posta in arrivo unificata - Bozze locali + Bozze locali Nessuna cartella Nessun messaggio Uno o più filtri attivi diff --git a/app/src/main/res/values-ja-rJP/strings.xml b/app/src/main/res/values-ja-rJP/strings.xml index 7a8dc4199e..77c0abafbd 100644 --- a/app/src/main/res/values-ja-rJP/strings.xml +++ b/app/src/main/res/values-ja-rJP/strings.xml @@ -108,13 +108,13 @@ Microsoft Exchange WebサービスやMicrosoft ActiveSyncなどの非標準プロトコルはサポートされていません。 アプリの説明もご覧ください クイックセットアップ - 殆どのプロバイダーでアカウントとIDを素早く設定します + ほとんどのプロバイダーでアカウントとIDを素早く設定できます 一部のプロバイダはアカウントを追加しにくくしています。FairEmailを非難せずに、代わりにサポートを依頼してください。 クイックセットアップはautoconfig.thunderbird.netから構成情報を取得します メッセージを受信する為のIMAPサーバ メッセージを送信する為のSMTPサーバ ウィザード - インストールウィザードを複数回使用し複数アカウントをセットアップ出来ます + インストールウィザードを繰り返し使用すると、複数のアカウントを設定できます 新しいメールアドレスを取得したい場合 「戻る」で受信トレイに戻ります メールプロバイダーは、公式のアプリに対してのみOAuthを承認しています @@ -233,7 +233,6 @@ Microsoft Exchange WebサービスやMicrosoft ActiveSyncなどの非標準プ 購読したフォルダーの管理 購読したフォルダを自動的に同期する メッセージの同期時に送信者のメールアドレスを確認 - メッセージ同期に関する返信メールアドレスを確認 キープアライブ間隔を自動的に調整します デフォルトでキーボードを表示 全画面キーボードを無効にする @@ -452,7 +451,6 @@ Microsoft Exchange WebサービスやMicrosoft ActiveSyncなどの非標準プ これを無効にするとデータと電池の使用量が多少減りますが、フォルダーのリストの更新も無効になります DNS MXレコードが存在するかどうか確認 メッセージの同期が遅くなります - 送信者のドメイン名と返信アドレスが同じかどうかを確認 Android内の連絡先に加えます。連絡先データは有効にした場合のみ新しく送信又は受信メッセージへ保存されます テキストと署名の間に「-」を挿入 メッセージテキスト又は件名が空の場合や添付ファイルが無い場合に警告を表示 @@ -688,7 +686,7 @@ Microsoft Exchange WebサービスやMicrosoft ActiveSyncなどの非標準プ ユーザーフォルダーのみ 基本アカウントのフォルダー 統合受信トレイフォルダー - 下書き（ローカル） + 下書き（ローカル） フォルダーが有りません メッセージが有りません 1つ以上のフィルターがアクティブです diff --git a/app/src/main/res/values-nl-rNL/strings.xml b/app/src/main/res/values-nl-rNL/strings.xml index 910f061f0d..3ab93a733c 100644 --- a/app/src/main/res/values-nl-rNL/strings.xml +++ b/app/src/main/res/values-nl-rNL/strings.xml @@ -245,7 +245,6 @@ Beheer map abonnementen Geabonneerde mappen automatisch synchroniseren Controleer e-mailadressen van de afzenders bij het synchroniseren van berichten - Controleer antwoordadressen bij het synchroniseren van berichten De keep-alive interval automatisch aanpassen Toon standaard het toetsenbord Toetsenbord in volledige scherm voorkomen @@ -466,7 +465,6 @@ Dit uitschakelen zal het gebruik van gegevens en batterij enigszins verminderen, maar zal ook het bijwerken van de lijst met mappen uitschakelen Dit zal controleren of DNS MX records bestaan Dit zal de synchronisatie van berichten vertragen - Dit controleert of de domeinnaam van de afzender en antwoordadressen hetzelfde zijn Naast contacten die door Android worden geleverd. Contactgegevens worden alleen opgeslagen voor nieuw verzonden of ontvangen berichten wanneer ingeschakeld. Voeg \'-- \' in tussen de tekst en de handtekening Toon een waarschuwing wanneer de berichttekst of het onderwerp leeg is of wanneer een bijlage zou kunnen ontbreken @@ -702,7 +700,7 @@ Alleen gebruikersmappen Mappen primaire account Gecombineerde postvak in mappen - Lokale concepten + Lokale concepten Geen mappen Geen berichten Eén of meer filters actief diff --git a/app/src/main/res/values-nn-rNO/strings.xml b/app/src/main/res/values-nn-rNO/strings.xml index 63f9160a8e..9afb22cf78 100644 --- a/app/src/main/res/values-nn-rNO/strings.xml +++ b/app/src/main/res/values-nn-rNO/strings.xml @@ -129,6 +129,7 @@ Installasjonsveiviseren kan brukes flere ganger for å sette opp flere kontoer Jeg trenger en ny e-postadresse Gå \'tilbake\' for å gå til innboksen + E-postleverandøren har bare godkjent OAuth for offisielle versjoner av appen Annen leverandør Å autorisere Google kontoer fungerer bare i offisielle versjoner fordi Android sjekker appens signatur Gi tillatelser til å velge en konto og lese navnet ditt @@ -138,6 +139,7 @@ Microsoft gir ikke denne typen autorisasjon for kontoer som Outlook, Live, Hotmail osv. Feilen \'AUTHENTICATE failed\' kan skyldes at IMAP/SMTP er deaktivert av systemadministratoren Autoriser tilgang til din %1$s konto + Autoriser eksisterende konto på nytt Konto autorisasjon ble oppdatert Godkjenne Velg konto @@ -244,7 +246,6 @@ Administrere mappeabonnementer Synkroniser abonnerte mapper automatisk Sjekk avsenderens e-postadresser når meldinger synkroniseres - Sjekk avsenderens e-postadresser når meldinger synkroniseres Juster automatisk hold i live intervallet Vis tastatur som standard Forhindre fullskjermtastatur @@ -258,6 +259,7 @@ Bruk utvidet svar/videresendt overskrift Skriv under avsenderens tekst Sitat svarte tekst + Begrens antall nestede sitater Endre størrelse på bilder i tekstsvaret Signaturposisjon Bruk signatur når du svarer @@ -289,6 +291,7 @@ Vis navigasjonsmenyen i liggende modus som standard Vis på startskjermen Bruk kortstil i stedet for tabellstil + Bruk beige bakgrunn når du bruker kortstil Gruppere etter dato Konversasjonstråder Vis antall uleste meldinger i samtaler @@ -314,6 +317,7 @@ Vis emne over avsender Vis emnet i kursivt Forkorte emnet ved behov + Uthev farge Vis nøkkelord i meldingshode Vis Gmail-etiketter i meldingshodet Vis stjerner @@ -328,17 +332,22 @@ Zoom originale meldinger slik at de passer til skjermen Bruk høy kontrast for meldingstekst Bruk monospaced skrift for meldingstekst som standard + Bruk monospaced skrift (skrifttype med lik bredde) for formatert tekst Bruk tekstfarger Bruk tekststørrelser Bruk skrifttyper Bruk tekstjustering Bruk skillelinje Kollapse sitert tekst + Vis plassholdere for bilde Vis automatisk innebygde bilder Vis relativ samtaleposisjon med en prikk Vis samtale handlingslinje + Bruke kontofarge som bakgrunnsfarge for samtalelinjen Fargelegg Android-navigasjonslinjen + Analyser stilark Vis en advarsel når mottakeren ikke kunne godkjenne meldingen + Synkroniser ved start Dobbel \'tilbake\' for å avslutte Dra ned for å oppdatere Rull til toppen når du mottar nye meldinger @@ -369,8 +378,10 @@ Motta kanal Vis de nyeste varslene først Bruk bakgrunnstjeneste for å synkronisere meldinger + En bakgrunnstjeneste kan stanses av Android når som helst, men krever ikke en statuslinje varsel Vis epost ikonet med antall nye meldinger La antallet nye meldinger samsvare med antall varsler + Vis varsler kun i bakgrunnen Vis kun varsler fra kontakter Vis bare sammendragsvarsel Vis forhåndsvisning av melding i varsler @@ -389,6 +400,7 @@ Fjern varsel om ny melding når du trykker på varslingen Fjern nye meldingsvarsler i visning av meldingsliste Send bare varsler med forhåndsvisning av meldingen til bærbare enheter + Bruk Android \'meldingsstil\' varslingsformat Vis varselinnhold når du bruker biometrisk godkjenning Bruk meldingslys Velg varslingslyd @@ -407,6 +419,7 @@ Signer som standard Krypter som standard Dekrypter meldinger automatisk + Angre dekryptering på avsluttende samtale OpenPGP-leverandør Bruk autokrypt Autokrypt gjensidig modus @@ -423,6 +436,7 @@ Vis ofte brukte kontakter i Android-menyen Foreslå handlinger Foreslå svartekster + Oppdag meldings tekstspråk Bygg søkeindeks %1$d / %2$d meldinger indeksert (%3$s) Språk @@ -441,20 +455,24 @@ Innstillinger Flere valg Hvis synkronisering er deaktivert, kan du fremdeles oppdatere listen ved å sveipe ned fra toppen + Synkronisering med jevne mellomrom vil sammenligne lokale og eksterne meldinger hver gang, noe som er en dyr operasjon som muligens resulterer i ekstra batteribruk, spesielt når det er mange meldinger som skal synkroniseres. Alltid synkronisering vil unngå dette ved kontinuerlig sjekking for endringer. + Dette kan endre synkroniseringsfrekvensen for å spare batteribruk avhengig av egenskaper og oppførsel til e-postserverne Trykk på en tid for å angi en tid + Noen leverandører lagrer meldinger med ukjent, ugyldig eller senere dato som meldinger uten dato Noen leverandører støtter ikke dette ordentlig, noe som kan føre til synkronisering av ingen eller alle meldinger Når den er deaktivert, lagres uleste meldinger på enheten for alltid Dette vil overføre ekstra data og bruke ekstra batteristrøm, spesielt hvis det er lagret mange meldinger på enheten + Dette gjelder bare for nylig mottatte meldinger og kan ødelegge eksisterende grupper Deaktivering av dette vil redusere data og batteribruk noe, men deaktiverer også oppdateringen av listen over mapper Dette vil sjekke om DNS MX-poster eksisterer Dette vil redusere synkroniseringen av meldinger - Dette vil sjekke om domenenavnet til avsenderen og svaradressene er det samme I tillegg til kontakter levert av Android. Vil kontaktdata blir lagret for nylig sendte eller mottatte meldinger når de er aktivert. Sett inn \'-- \' mellom teksten og signaturen Vis en advarsel når meldingsteksten eller emnet er tomt eller når et vedlegg mangler Målte tilkoblinger er vanligvis mobile tilkoblinger eller betalte Wi-Fi-hotspots Deaktivering av dette alternativet deaktiverer mottak og sending av meldinger på mobile internettforbindelser Forutsatt ingen roaming i EU + Aktivering av dette kan forårsake tilkoblingsproblemer på noen enheter Tidsavbrudd for lese/skriving blir satt til den doble av tilkoblings avbruddstiden. Høyere verdier vil føre til mer batteribruk. Aktivering av dette vil deaktivere svake SSL-protokoller og chiffer, noe som kan føre til tilkoblingsproblemer Meldingsoverskrifter vil alltid bli hentet når du roamer. Du kan bruke enhetens roaming-innstilling for å deaktivere Internett mens du roamer. @@ -465,6 +483,7 @@ Meldinger grupperes bare etter dato hvis de er sortert etter tid Om dette fungerer avhenger av Android-versjonen og varianten Gruppemeldinger knyttet til hverandre + Farge på temaet vil bli brukt for å framheve Det kan være en personvernrisiko Når deaktivert, vil bare navn bli vist når det er tilgjengelig Kun tilgjengelig når meldingstekst ble lastet ned @@ -472,6 +491,8 @@ Dette kan resultere i veldig liten skrift Dette gjelder kun reformaterte meldinger Innebygde bilder er bilder som er inkludert i meldingen + Dette vil mer nøyaktig vise meldinger, men muligens med en forsinkelse + Støtte for oppdagelse av språk avhenger av produsenten av enheten Åpne automatisk melding når det bare er én melding eller bare en ulest melding i en samtale Automatisk merking av meldinger som lest ved utvidelse, kan deaktiveres i de enkelte kontoinnstillingene Lukk samtaler automatisk når alle meldinger arkiveres, sendes eller kastet @@ -485,12 +506,15 @@ Varsler om nye meldinger vil alltid bli fjernet når de blir sveipet og når merking av meldinger er lest Trykk på kanalnavnet for å angi kanalegenskapene Slik angir du standardlyden, osv + For å deaktivere \'overvåking\' varsling For wearables som kan vise fulltekst (opptil 5000 tegn) + Dette forsinker visning av varsler til meldingsteksten er lastet ned Varsler sendes bare til bærbare enheter etter at meldingsteksten er lastet ned Påkrevd for Android Auto support Målmappen kan konfigureres i kontoinnstillingene Denne Android versjonen støtter ikke varslingsgruppering Denne Android versjonen støtter ikke varslingskanaler + Aktivering av dette vil redusere ytelsen, men aktivering er nødvendig på noen enheter Aktivering av dette vil øke søke ytelsen, men også øke batteri bruken og bruke mer lagringsplass Dette vil starte appen på nytt Liste over aktuelle eksperimentelle funksjoner diff --git a/app/src/main/res/values-no-rNO/strings.xml b/app/src/main/res/values-no-rNO/strings.xml index d0b95fadf1..0a5c1dec56 100644 --- a/app/src/main/res/values-no-rNO/strings.xml +++ b/app/src/main/res/values-no-rNO/strings.xml @@ -129,6 +129,7 @@ Installasjonsveiviseren kan brukes flere ganger for å sette opp flere kontoer Jeg trenger en ny e-postadresse Gå \'tilbake\' for å gå til innboksen + E-postleverandøren har bare godkjent OAuth for offisielle versjoner av appen Annen leverandør Å autorisere Google kontoer fungerer bare i offisielle versjoner fordi Android sjekker appens signatur Gi tillatelser til å velge en konto og lese navnet ditt @@ -138,6 +139,7 @@ Microsoft gir ikke denne typen autorisasjon for kontoer som Outlook, Live, Hotmail osv. Feilen \'AUTHENTICATE failed\' kan skyldes at IMAP/SMTP er deaktivert av systemadministratoren Autoriser tilgang til din %1$s konto + Autoriser eksisterende konto på nytt Konto autorisasjon ble oppdatert Godkjenne Velg konto @@ -244,7 +246,6 @@ Administrere mappeabonnementer Synkroniser abonnerte mapper automatisk Sjekk avsenderens e-postadresser når meldinger synkroniseres - Sjekk avsenderens e-postadresser når meldinger synkroniseres Juster automatisk hold i live intervallet Vis tastatur som standard Forhindre fullskjermtastatur @@ -258,6 +259,7 @@ Bruk utvidet svar/videresendt overskrift Skriv under avsenderens tekst Sitat svarte tekst + Begrens antall nestede sitater Endre størrelse på bilder i tekstsvaret Signaturposisjon Bruk signatur når du svarer @@ -289,6 +291,7 @@ Vis navigasjonsmenyen i liggende modus som standard Vis på startskjermen Bruk kortstil i stedet for tabellstil + Bruk beige bakgrunn når du bruker kortstil Gruppere etter dato Konversasjonstråder Vis antall uleste meldinger i samtaler @@ -314,6 +317,7 @@ Vis emne over avsender Vis emnet i kursivt Forkorte emnet ved behov + Uthev farge Vis nøkkelord i meldingshode Vis Gmail-etiketter i meldingshodet Vis stjerner @@ -328,17 +332,22 @@ Zoom originale meldinger slik at de passer til skjermen Bruk høy kontrast for meldingstekst Bruk monospaced skrift for meldingstekst som standard + Bruk monospaced skrift (skrifttype med lik bredde) for formatert tekst Bruk tekstfarger Bruk tekststørrelser Bruk skrifttyper Bruk tekstjustering Bruk skillelinje Kollapse sitert tekst + Vis plassholdere for bilde Vis automatisk innebygde bilder Vis relativ samtaleposisjon med en prikk Vis samtale handlingslinje + Bruke kontofarge som bakgrunnsfarge for samtalelinjen Fargelegg Android-navigasjonslinjen + Analyser stilark Vis en advarsel når mottakeren ikke kunne godkjenne meldingen + Synkroniser ved start Dobbel \'tilbake\' for å avslutte Dra ned for å oppdatere Rull til toppen når du mottar nye meldinger @@ -369,8 +378,10 @@ Motta kanal Vis de nyeste varslene først Bruk bakgrunnstjeneste for å synkronisere meldinger + En bakgrunnstjeneste kan stanses av Android når som helst, men krever ikke en statuslinje varsel Vis epost ikonet med antall nye meldinger La antallet nye meldinger samsvare med antall varsler + Vis varsler kun i bakgrunnen Vis kun varsler fra kontakter Vis bare sammendragsvarsel Vis forhåndsvisning av melding i varsler @@ -389,6 +400,7 @@ Fjern varsel om ny melding når du trykker på varslingen Fjern nye meldingsvarsler i visning av meldingsliste Send bare varsler med forhåndsvisning av meldingen til bærbare enheter + Bruk Android \'meldingsstil\' varslingsformat Vis varselinnhold når du bruker biometrisk godkjenning Bruk meldingslys Velg varslingslyd @@ -407,6 +419,7 @@ Signer som standard Krypter som standard Dekrypter meldinger automatisk + Angre dekryptering på avsluttende samtale OpenPGP-leverandør Bruk autokrypt Autokrypt gjensidig modus @@ -423,6 +436,7 @@ Vis ofte brukte kontakter i Android-menyen Foreslå handlinger Foreslå svartekster + Oppdag meldings tekstspråk Bygg søkeindeks %1$d / %2$d meldinger indeksert (%3$s) Språk @@ -441,20 +455,24 @@ Innstillinger Flere valg Hvis synkronisering er deaktivert, kan du fremdeles oppdatere listen ved å sveipe ned fra toppen + Synkronisering med jevne mellomrom vil sammenligne lokale og eksterne meldinger hver gang, noe som er en dyr operasjon som muligens resulterer i ekstra batteribruk, spesielt når det er mange meldinger som skal synkroniseres. Alltid synkronisering vil unngå dette ved kontinuerlig sjekking for endringer. + Dette kan endre synkroniseringsfrekvensen for å spare batteribruk avhengig av egenskaper og oppførsel til e-postserverne Trykk på en tid for å angi en tid + Noen leverandører lagrer meldinger med ukjent, ugyldig eller senere dato som meldinger uten dato Noen leverandører støtter ikke dette ordentlig, noe som kan føre til synkronisering av ingen eller alle meldinger Når den er deaktivert, lagres uleste meldinger på enheten for alltid Dette vil overføre ekstra data og bruke ekstra batteristrøm, spesielt hvis det er lagret mange meldinger på enheten + Dette gjelder bare for nylig mottatte meldinger og kan ødelegge eksisterende grupper Deaktivering av dette vil redusere data og batteribruk noe, men deaktiverer også oppdateringen av listen over mapper Dette vil sjekke om DNS MX-poster eksisterer Dette vil redusere synkroniseringen av meldinger - Dette vil sjekke om domenenavnet til avsenderen og svaradressene er det samme I tillegg til kontakter levert av Android. Vil kontaktdata blir lagret for nylig sendte eller mottatte meldinger når de er aktivert. Sett inn \'-- \' mellom teksten og signaturen Vis en advarsel når meldingsteksten eller emnet er tomt eller når et vedlegg mangler Målte tilkoblinger er vanligvis mobile tilkoblinger eller betalte Wi-Fi-hotspots Deaktivering av dette alternativet deaktiverer mottak og sending av meldinger på mobile internettforbindelser Forutsatt ingen roaming i EU + Aktivering av dette kan forårsake tilkoblingsproblemer på noen enheter Tidsavbrudd for lese/skriving blir satt til den doble av tilkoblings avbruddstiden. Høyere verdier vil føre til mer batteribruk. Aktivering av dette vil deaktivere svake SSL-protokoller og chiffer, noe som kan føre til tilkoblingsproblemer Meldingsoverskrifter vil alltid bli hentet når du roamer. Du kan bruke enhetens roaming-innstilling for å deaktivere Internett mens du roamer. @@ -465,6 +483,7 @@ Meldinger grupperes bare etter dato hvis de er sortert etter tid Om dette fungerer avhenger av Android-versjonen og varianten Gruppemeldinger knyttet til hverandre + Farge på temaet vil bli brukt for å framheve Det kan være en personvernrisiko Når deaktivert, vil bare navn bli vist når det er tilgjengelig Kun tilgjengelig når meldingstekst ble lastet ned @@ -472,6 +491,8 @@ Dette kan resultere i veldig liten skrift Dette gjelder kun reformaterte meldinger Innebygde bilder er bilder som er inkludert i meldingen + Dette vil mer nøyaktig vise meldinger, men muligens med en forsinkelse + Støtte for oppdagelse av språk avhenger av produsenten av enheten Åpne automatisk melding når det bare er én melding eller bare en ulest melding i en samtale Automatisk merking av meldinger som lest ved utvidelse, kan deaktiveres i de enkelte kontoinnstillingene Lukk samtaler automatisk når alle meldinger arkiveres, sendes eller kastet @@ -485,12 +506,15 @@ Varsler om nye meldinger vil alltid bli fjernet når de blir sveipet og når merking av meldinger er lest Trykk på kanalnavnet for å angi kanalegenskapene Slik angir du standardlyden, osv + For å deaktivere \'overvåking\' varsling For wearables som kan vise fulltekst (opptil 5000 tegn) + Dette forsinker visning av varsler til meldingsteksten er lastet ned Varsler sendes bare til bærbare enheter etter at meldingsteksten er lastet ned Påkrevd for Android Auto support Målmappen kan konfigureres i kontoinnstillingene Denne Android versjonen støtter ikke varslingsgruppering Denne Android versjonen støtter ikke varslingskanaler + Aktivering av dette vil redusere ytelsen, men aktivering er nødvendig på noen enheter Aktivering av dette vil øke søke ytelsen, men også øke batteri bruken og bruke mer lagringsplass Dette vil starte appen på nytt Liste over aktuelle eksperimentelle funksjoner diff --git a/app/src/main/res/values-pl-rPL/strings.xml b/app/src/main/res/values-pl-rPL/strings.xml index 95c3011114..6859fb66f6 100644 --- a/app/src/main/res/values-pl-rPL/strings.xml +++ b/app/src/main/res/values-pl-rPL/strings.xml @@ -267,7 +267,6 @@ Zarządzaj subskrypcjami folderów Automatycznie synchronizuj subskrybowane foldery Sprawdź adresy e-mail nadawcy przy synchronizowaniu wiadomości - Sprawdź adresy e-mail odpowiedzi podczas synchronizacji wiadomości Automatycznie dostosuj interwał zachowania aktywności Domyślnie pokaż klawiaturę Blokuj klawiaturę pełnoekranową @@ -488,7 +487,6 @@ Wyłączenie tej opcji nieco zmniejszy zużycie danych i baterii, ale wyłączy także aktualizację listy folderów To sprawdzi, czy istnieją rekordy MX DNS Wydłuży to synchronizację wiadomości - Spowoduje to sprawdzenie, czy nazwa domeny nadawcy i adresy odpowiedzi są takie same Oprócz kontaktów dostarczanych przez Androida. Dane kontaktowe będą przechowywane dla nowo wysłanych lub odebranych wiadomości tylko kiedy włączone. Wstaw \'-- \' między tekstem a podpisem Pokaż ostrzeżenie, gdy tekst wiadomości lub temat jest pusty lub gdy może brakować załącznika @@ -724,7 +722,7 @@ Tylko foldery użytkownika Podstawowe konto folderów Wspólne foldery - Szkice lokalne + Szkice lokalne Brak folderów Brak wiadomości Jeden lub więcej filtrów jest aktywnych diff --git a/app/src/main/res/values-pt-rBR/strings.xml b/app/src/main/res/values-pt-rBR/strings.xml index f46d52a18f..e2c3f7b099 100644 --- a/app/src/main/res/values-pt-rBR/strings.xml +++ b/app/src/main/res/values-pt-rBR/strings.xml @@ -240,7 +240,6 @@ Sincronizar listas de pastas compartilhadas Gerenciar assinaturas de pastas Verificar endereços de e-mail do remetente na sincronização de mensagens - Verificar endereços de e-mail de resposta ao sincronizar mensagens Sintonizar automaticamente o intervalo de manutenção de vida Mostrar teclado por padrão Sugerir contatos armazenados localmente @@ -444,7 +443,6 @@ Desativar isto irá reduzir um pouco o uso de dados e bateria, mas irá também desativar a atualização da lista de pastas Isto irá verificar se existem registros DNS MX Isto atrasará a sincronização de mensagens - Isto irá verificar se o nome do domínio do remetente e os endereços de resposta são os mesmos Além dos contatos fornecidos pelo Android. Os dados de contato serão armazenados para novas mensagens enviadas ou recebidas somente quando ativados. Inserir \'-- \' entre o texto e a assinatura Mostrar um aviso quando o texto da mensagem ou o assunto estiver vazio ou quando um anexo puder estar ausente diff --git a/app/src/main/res/values-pt-rPT/strings.xml b/app/src/main/res/values-pt-rPT/strings.xml index 09e72bfc89..0a11e598a7 100644 --- a/app/src/main/res/values-pt-rPT/strings.xml +++ b/app/src/main/res/values-pt-rPT/strings.xml @@ -233,7 +233,6 @@ Gerir subscrições de pastas Sincronizar automaticamente as pastas subscritas Verificar endereços de e-mail do remetente ao sincronizar mensagens - Verificar endereços de e-mail de resposta ao sincronizar mensagens Ajustar automaticamente o intervalo de manutenção de connexão Mostrar teclado por padrão Sugerir contatos armazenados localmente diff --git a/app/src/main/res/values-ro-rRO/strings.xml b/app/src/main/res/values-ro-rRO/strings.xml index 650a19fff9..bf79f084d6 100644 --- a/app/src/main/res/values-ro-rRO/strings.xml +++ b/app/src/main/res/values-ro-rRO/strings.xml @@ -256,7 +256,6 @@ Gestionați abonările la dosare Sincronizează automat dosarele abonate Verifică adresa expeditorului la sincronizarea mesajelor - Verifică adresa destinatarului la sincronizarea mesajelor Reglaţi automat intervalul de păstrare al conexiunii Afișare implicită a tastaturii Dezactivare tastatură pe tot ecranul @@ -477,7 +476,6 @@ Dezactivând aceasta se va reduce utilizarea datelor și a bateriei, dar se va dezactiva și actualizarea listei de dosare Se verifică dacă există înregistrări DNS MX Această opțiune va încetini viteza de sincronizare a mesajelor - Se va verifica dacă numele de domeniu al expeditorului și adresa de răspuns coincid Pe lângă contactele furnizate de Android. Datele contactelor vor fi memorate pentru mesajele nou trimise sau primite doar când este activată. Inserează \'-- \' între text și semnătură Arată o avertizare atunci când textul mesajului sau subiectul e gol sau când atașamentul s-ar putea să lipsească diff --git a/app/src/main/res/values-ru-rRU/strings.xml b/app/src/main/res/values-ru-rRU/strings.xml index 3d600b7696..70413e4be2 100644 --- a/app/src/main/res/values-ru-rRU/strings.xml +++ b/app/src/main/res/values-ru-rRU/strings.xml @@ -268,7 +268,6 @@ Управление подпиской на папки Автоматически синхронизировать подписанные папки Проверять адреса электронной почты отправителя при синхронизации сообщений - Проверять адреса электронной почты для ответа при синхронизации сообщений Автоматически настраивать интервал keep-alive Показывать клавиатуру по умолчанию Не показывать клавиатуру в полноэкранном режиме @@ -489,7 +488,6 @@ Отключение этой функции уменьшит потребление трафика и заряда батареи, но также отключит обновление списка папок Проверка наличия записей DNS MX Это замедлит синхронизацию сообщений - Проверяет, совпадает ли доменное имя отправителя и адреса для ответа В дополнение к контактам, предоставляемым Android. Контактные данные будут сохранены только для вновь отправленных или полученных сообщений при включении этой функции. Вставлять \'-- \' между текстом и подписью Показывать предупреждение, если отсутствует текст сообщения, тема или, возможно, отсутствует вложение @@ -725,7 +723,7 @@ Только папки пользователя Папки основной учётной записи Папки единого почтового ящика - Локальные черновики + Локальные черновики Нет папок Нет сообщений Один или несколько фильтров активны diff --git a/app/src/main/res/values-sk-rSK/strings.xml b/app/src/main/res/values-sk-rSK/strings.xml index 5abe601a6a..313a1c0ae3 100644 --- a/app/src/main/res/values-sk-rSK/strings.xml +++ b/app/src/main/res/values-sk-rSK/strings.xml @@ -265,7 +265,6 @@ Spravovať odoberanie priečinkov Automaticky synchronizovať odoberané priečinky Kontrolovať e-mailové adresy odosielateľov pri synchronizácii správ - Kontrolovať odpovede e-mailových adries pri synchronizácii správ Automaticky upravovať interval udržania spojenia Predvolene zobrazovať klávesnicu Zabrániť zobrazeniu klávesnice na celú obrazovku @@ -367,6 +366,7 @@ Zafarbiť navigačný panel Androidu Spracovať štýly CSS Zobraziť varovanie, ak server príjemcu nemohol overiť správu + Synchronizovať pri spustení Ukončiť dvojitým stlačením tlačidla \'Späť\' Obnoviť stiahnutím Po prijatí nových správ posunúť zoznam na začiatok @@ -485,7 +485,6 @@ Nastavenie vždy toto kompenzuje neustálym sledovaním zmien. Vypnutím čiastočne ušetríte prenos údajov aj využívanie batérie, ale zároveň zastavíte obnovovanie zoznamu priečinkov Skontroluje, či existujú MX záznamy v systéme DNS Spomalí synchronizáciu správ - Skontroluje, či sa názov domény odosielateľa zhoduje s doménou adresy pre odpoveď Okrem kontaktov poskytnutých systémom. Zaznamenané budú kontaktné údaje z prijatých a odoslaných správ, len ak je to povolené. Oddeliť podpis od textu správy znakmi \'-- \' Zobraziť varovanie, ak je text správy alebo predmet prázdny alebo môže chýbať príloha @@ -719,6 +718,7 @@ Nastavenie vždy toto kompenzuje neustálym sledovaním zmien. Len používateľské priečinky Priečinky primárneho účtu Priečinky spoločnej doručenej pošty + Lokálne koncepty Žiadne priečinky Žiadne správy Jeden alebo viac filtrov aktívnych diff --git a/app/src/main/res/values-sl-rSI/strings.xml b/app/src/main/res/values-sl-rSI/strings.xml index 9fc053d3dd..849861d207 100644 --- a/app/src/main/res/values-sl-rSI/strings.xml +++ b/app/src/main/res/values-sl-rSI/strings.xml @@ -229,7 +229,6 @@ Sinhroniziraj seznam map Upravljaj z naročninami na mape Preveri pošiljateljeve e-poštne naslove ob sinhronizaciji sporočil - Preveri e-poštne naslove za odgovor ob sinhronizaciji sporočil Privzeto prikaži tipkovnico Predlagaj krajevno shranjene stike Predlagaj naslove, najdene v poslanih sporočilih @@ -386,7 +385,6 @@ Onemogočanje tega bo nekoliko zmanjšalo porabo podatkov in energije, vendar bo obenem tudi onemogočilo posodabljanje seznama map. To bo preverilo, ali obstajajo zapisi DNS MX. To bo upočasnilo sinhronizacijo sporočil. - To bo preverilo, ali so ime domene pošiljatelja in naslovi za odgovor enaki. Poleg stikov iz Androida. Podatki o stikih bodo shranjeni za na novo poslana ali prejeta sporočila samo, ko je omogočeno. Vstavi \'-- \' med besedilo in podpis. Prikaži opozorilo, kadar je besedilo ali zadeva sporočila prazna, ali ko morda manjka priloga. diff --git a/app/src/main/res/values-sv-rSE/strings.xml b/app/src/main/res/values-sv-rSE/strings.xml index fa6c4e2003..f11f82ef23 100644 --- a/app/src/main/res/values-sv-rSE/strings.xml +++ b/app/src/main/res/values-sv-rSE/strings.xml @@ -245,7 +245,6 @@ Hantera mapprenumerationer Synkronisera automatiskt prenumererade mappar Kontrollera avsändarens e-postadresser vid synkronisering av meddelanden - Kontrollera svarsadresser vid synkronisering av meddelanden Justera automatiskt keep-alive intervallet Visa tangentbord som standard Förhindra helskärmstangentbord @@ -466,7 +465,6 @@ Inaktivering av detta kommer att minska data och batterianvändning något, men kommer att inaktivera uppdatering av listan över mappar också Detta kommer att kontrollera om DNS MX-poster finns Detta kommer att sakta ner synkronisering av meddelanden - Detta kommer att kontrollera om domännamnet för avsändaren och svarsadresser är samma Förutom kontakter som tillhandahålls av Android. Kontaktdata lagras endast för nyligen skickade eller mottagna meddelanden när det aktiverat. Infoga \'-- \' mellan texten och signaturen Visa en varning när meddelandetexten eller ämnet är tomt eller när en bilaga kanske saknas @@ -702,7 +700,7 @@ Endast användarmappar Mappar primärt konto Samlad inkorg mappar - Lokala utkast + Lokala utkast Inga mappar Inga meddelanden Ett eller flera filter är aktiva diff --git a/app/src/main/res/values-tr-rTR/strings.xml b/app/src/main/res/values-tr-rTR/strings.xml index 3fa56688a9..e2524124d0 100644 --- a/app/src/main/res/values-tr-rTR/strings.xml +++ b/app/src/main/res/values-tr-rTR/strings.xml @@ -246,7 +246,6 @@ Dizin aboneliklerini yönet Abone olunan klasörleri otomatik olarak senkronize edin İletilerin eşzamanlanmasında gönderen e-posta adreslerini kontrol et - Mesajları senkronize ederken yanıtlama e-posta adreslerini kontrol et Canlı tutma aralığını otomatik olarak ayarlayın Öntanımlı olarak klavyeyi göster Tam ekran klavyeyi önleyin, gizleyin @@ -463,7 +462,6 @@ Bunu devre dışı bırakmak veri ve pil kullanımını bir miktar azaltır, ancak klasör listesinin güncellenmesini de devre dışı bırakır Bu, DNS MX kayıtlarının olup olmadığını kontrol eder Bu, iletilerin eşzamanlamasını yavaşlatır - Bu, gönderenin alan adının ve yanıtlama adreslerinin aynı olup olmadığını kontrol edecektir Android tarafından sağlanan kişilere ek olarak. Kişi verileri yeni gönderilen veya alınan mesajlar için yalnızca etkin olduğunda saklanacaktır. Metin ve imza arasına \'-- \' ekle Mesaj metni veya konu boş olduğunda veya bir ek eksik olduğunda bir uyarı göster diff --git a/app/src/main/res/values-zh-rCN/strings.xml b/app/src/main/res/values-zh-rCN/strings.xml index 91f221e22a..e76dbece69 100644 --- a/app/src/main/res/values-zh-rCN/strings.xml +++ b/app/src/main/res/values-zh-rCN/strings.xml @@ -234,7 +234,6 @@ 管理文件夹订阅 自动同步订阅的文件夹 同步消息时检查发送者电子邮件地址 - 同步消息时检查回复邮件地址 自动调整保持活动时间间隔 默认显示键盘 防止全屏键盘 @@ -455,7 +454,6 @@ 禁用此功能某种程度上会减少数据和电量使用，但也会禁用更新文件夹列表 这将检查 DNS MX 记录是否存在 这将减缓同步消息的速度 - 这将检查发件人和回复对象的地址是否相同 除了Android提供的联系人，只有在设置中允许，应用才会储存新接收或发送消息的联系人数据。 在文本和签名之间插入 \'-- \' 当消息文本或主题为空或缺失某个附件时显示警告 @@ -691,7 +689,7 @@ 仅用户文件夹 文件夹主账户 聚合收件箱文件夹 - 本地草稿文件夹 + 本地草稿文件夹 无文件夹 没有邮件 一个或多个过滤器已启用 diff --git a/app/src/main/res/values-zh-rTW/strings.xml b/app/src/main/res/values-zh-rTW/strings.xml index 63d37527a9..db980ad9df 100644 --- a/app/src/main/res/values-zh-rTW/strings.xml +++ b/app/src/main/res/values-zh-rTW/strings.xml @@ -233,7 +233,6 @@ 管理資料夾訂閱 自動同步訂閱的資料夾 在同步訊息時檢查發送者的email地址。 - 在同步訊息時檢查回覆 email 的地址。 自動調整保持活躍的間隔 預設顯示鍵盤 避免全螢幕鍵盤 @@ -448,7 +447,6 @@ 停用此功能將在某種程度上減少資料和電池的使用，但是也會停用更新文件夾列表 這將檢查 DNS MX 記錄是否存在 這將會減緩同步訊息的速度 - 這將檢查寄件人的域名和回覆地址是否相同 除了 Android 提供的聯絡人。 僅在啟用後，聯絡人資料將被儲存以用於新寄送或接收的郵件。 在文字和簽名之間插入 “--” 當郵件內文或主旨為空或可能缺少附件時顯示警告 diff --git a/docs/FAQ-af-rZA.md b/docs/FAQ-af-rZA.md index 87aecbce14..230a8ba5e6 100644 --- a/docs/FAQ-af-rZA.md +++ b/docs/FAQ-af-rZA.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-ar-rBH.md b/docs/FAQ-ar-rBH.md index 13947460b1..367f6feae7 100644 --- a/docs/FAQ-ar-rBH.md +++ b/docs/FAQ-ar-rBH.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-ar-rEG.md b/docs/FAQ-ar-rEG.md index 775def692e..cc08b2748c 100644 --- a/docs/FAQ-ar-rEG.md +++ b/docs/FAQ-ar-rEG.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-ar-rYE.md b/docs/FAQ-ar-rYE.md index 775def692e..cc08b2748c 100644 --- a/docs/FAQ-ar-rYE.md +++ b/docs/FAQ-ar-rYE.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-az-rAZ.md b/docs/FAQ-az-rAZ.md index d2ba0c6a78..bedf2a564e 100644 --- a/docs/FAQ-az-rAZ.md +++ b/docs/FAQ-az-rAZ.md @@ -1,22 +1,22 @@ -# FairEmail support +# FairEmail texniki dəstək -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. +Sualınız varsa, əvvəlcə aşağıdakı tez-tez soruşulan sualları yoxlayın. Aşağıda, düzgün sorğu göndərmə xüsusiyyətlərini öyrənə və texniki səhvlər barədə sorğu göndərə bilərsiniz. -## Index +## İndeksi -* [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) -* [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) -* [Get support](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support) +* [Hesabların avtorizasiyası](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-authorizing-accounts) +* [Necə ...?](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-howto) +* [Mə`lum problemlər](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-known-problems) +* [Planlaşdırılan yeniliklər](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-planned-features) +* [Tez-tez sorğu edilən funksiyalar](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-frequently-requested-features) +* [Tez-tez verilən suallar](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-frequently-asked-questions) +* [Dəstək almaq](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support) -## Authorizing accounts +## Hesabların avtorizasiyası -In most cases, the quick setup will be able to automatically identify the correct configuration. +Əksər hallarda, sürətli quraşdırma avtomatik olaraq düzgün konfiqurasiyanı müəyyən edə bilər. -If the quick setup fails, you'll need to manually set up an account (to receive email) and an identity (to send email). For this you'll need the IMAP and SMTP server addresses and port numbers, whether SSL/TLS or STARTTLS should be used and your username (mostly, but not always, your email address) and your password. +Əgər sürətli quraşdırma müvəffəqiyyətsiz olarsa, hesabınızı (e-poçt almaq üçün) və şəxsiyyət vəsiqənizi (e-poçt göndərmək üçün) özünüz konfiqurasiya etməlisiniz. For this you'll need the IMAP and SMTP server addresses and port numbers, whether SSL/TLS or STARTTLS should be used and your username (mostly, but not always, your email address) and your password. Searching for *IMAP* and the name of the provider is mostly sufficient to find the right documentation. @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-bg-rBG.md b/docs/FAQ-bg-rBG.md index 87aecbce14..230a8ba5e6 100644 --- a/docs/FAQ-bg-rBG.md +++ b/docs/FAQ-bg-rBG.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-bn-rBD.md b/docs/FAQ-bn-rBD.md index 87aecbce14..230a8ba5e6 100644 --- a/docs/FAQ-bn-rBD.md +++ b/docs/FAQ-bn-rBD.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-bn-rIN.md b/docs/FAQ-bn-rIN.md index 87aecbce14..230a8ba5e6 100644 --- a/docs/FAQ-bn-rIN.md +++ b/docs/FAQ-bn-rIN.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-ca-rES.md b/docs/FAQ-ca-rES.md index 87aecbce14..230a8ba5e6 100644 --- a/docs/FAQ-ca-rES.md +++ b/docs/FAQ-ca-rES.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-cs-rCZ.md b/docs/FAQ-cs-rCZ.md index 6416d2f97f..ab19b289f2 100644 --- a/docs/FAQ-cs-rCZ.md +++ b/docs/FAQ-cs-rCZ.md @@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to. +Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076). + Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder. Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are. diff --git a/docs/FAQ-da-rDK.md b/docs/FAQ-da-rDK.md index 7b24432caa..47bfb07f4f 100644 --- a/docs/FAQ-da-rDK.md +++ b/docs/FAQ-da-rDK.md @@ -1393,53 +1393,53 @@ Benyt et langt tryk på *Indstillinger* i navigeringsmenuen for straks at genopr
-**(53) Can you stick the message action bar to the top/bottom?** +**(53) Kan man fastgøre beskedhandlingsbjælken øverst/nederst?** -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. +Brevhandlingshandlingsbjælken virker på en enkelt besked, og den nederste handlingsbjælke virker på alle beskeder i en konversation. Da der ofte er flere end én besked i en samtale, så er dette ikke muligt. Desuden findes en del beskedspecifikke handlinger, f.eks. videresendelse. -Moving the message action bar to the bottom of the message is visually not appealing because there is already a conversation action bar at the bottom of the screen. +Flytning af beskedhandlingbjælken til bunden af beskeden er visuelt ikke tiltalende, dai der allerede er en konversationshandlingsbjælke nederst på skærmen. -Note that there are not many, if any, email apps that display a conversation as a list of expandable messages. This has a lot of advantages, but the also causes the need for message specific actions. +Bemærk, at der ikke er mange (om nogen) e-mail apps, som viser en konversation som en liste over udvidelige beskeder. Det har mange fordele, men det er også årsagen til behovet for beskedspecifikke handlinger.
-**~~(54) How do I use a namespace prefix?~~** +**~~~(54) Hvordan benyttes et navneområdepræfiks? ~~** -~~A namespace prefix is used to automatically remove the prefix providers sometimes add to folder names.~~ +~~Et navneområdepræfix benyttes til automatisk at fjerne det præfiks, udbydere undertiden tilføjer mappenavne.~~ -~~For example the Gmail spam folder is called:~~ +~~F.eks. betegnes Gmail Spam-mappen:~~ ``` [Gmail]/Spam ``` -~~By setting the namespace prefix to *[Gmail]* FairEmail will automatically remove *[Gmail]/* from all folder names.~~ +~~Ved at sætte mavneområdepræfikset til *[Gmail]*, vil FairEmail automatisk fjerne *[Gmail]/* fra alle mappenavne.~~
-**(55) How can I mark all messages as read / move or delete all messages?** +**(55) Hvordan kan man markere alle beskeder som læst/flyttet eller slette dem alle?** -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. +Man kan bruge flere valg til dette. Tryk og hold fingeren på den første besked og træk ned til den sidste besked. Brug derefter treprikshandlingsknappen til at udføre den ønskede handling.
-**(56) Can you add support for JMAP?** +**(56) Kan der blive tilføjet understøttelse af 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. +Der er næsten ingen udbydere, som tilbyder [JMAP](https://jmap.io/)-protokollen, så det er ikke umagen værd at tilføje understøttelse for denne i FairEmail.
-**(57) Can I use HTML in signatures?** +**(57) Kan HTML benyttes i signaturer?** -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. +Ja, [HTML](https://en.wikipedia.org/wiki/HTML) kan benyttes. I signaturredigeringsværktøjet kan man via trepriksmenuen skifte til HTML-tilstand. -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. +Bemærk, at skiftes tilbage til teksredigeringsværktøjet, gengives måske ikke alt HTML korrekt, da Android-teksredigeringsværktøjet ikke kan gengive alt HTML. Omvendt, benyttes tekstredigerinsværktøjet, kan HTML blive ændret på uventede måder. -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: +Ønsker man at bruge præformateret tekst, såsom [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), bør teksten ombryde i et *præelement* således: ``` 
@@ -1454,184 +1454,184 @@ If you want to use preformatted text, like [ASCII art](https://en.wikipedia.org/
 

 
 
-**(58) What does an open/closed email icon mean?**
+**(58) Hvad er et åbn/luk e-mailikon?**
 
-The email icon in the folder list can be open (outlined) or closed (solid):
+E-mailikonet i mappelisten kan åbnes (omrids) eller lukkes (udfyldt):
 
-![External image](https://github.com/M66B/FairEmail/blob/master/images/baseline_mail_outline_black_48dp.png)
+![Eksternt billede](https://github.com/M66B/FairEmail/blob/master/images/baseline_mail_outline_black_48dp.png)
 
-Message bodies and attachments are not downloaded by default.
+Beskedbrødtekster og vedhæftninger downloades ikke som standard.
 
-![External image](https://github.com/M66B/FairEmail/blob/master/images/baseline_email_black_48dp.png)
+![Eksternt billede](https://github.com/M66B/FairEmail/blob/master/images/baseline_email_black_48dp.png)
 
-Message bodies and attachments are downloaded by default.
+Beskedbrødtekster og vedhæftninger downloades som standard.
 
 

 
 
-**(59) Can original messages be opened in the browser?**
+**(59) Kan originale beskeder åbnes i browseren?**
 
-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.
+Af sikkerhedsårsager er filerne med de originale beskedtekster ikke tilgængelige for andre apps, så dette er ikke muligt. I teorien kunne [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider) bruges til at dele disse filer, men selv Googles Chrome kan ikke håndtere dette.
 
 

 
 
-**(60) Did you know ... ?**
-
-* 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?
-* Did you know there is an advanced option to mark messages read when they are moved? (archiving and trashing is also moving)
-* Did you know that you can select text (or an email address) in any app on recent Android versions and let FairEmail search for it?
-* Did you know that FairEmail has a tablet mode? Rotate your device in landscape mode and conversation threads will be opened in a second column if there is enough screen space.
-* Did you know that you can long press a reply template to create a draft message from the template?
-* Did you know that you can long press, hold and swipe to select a range of messages?
-* Did you know that you can retry sending messages by using pull-down-to-refresh in the outbox?
-* Did you know that you can swipe a conversation left or right to go to the next or previous conversation?
-* Did you know that you can tap on an image to see where it will be downloaded from?
-* Did you know that you can long press the folder icon in the action bar to select an account?
-* Did you know that you can long press the star icon in a conversation thread to set a colored star?
-* Did you know that you can open the navigation drawer by swiping from the left, even when viewing a conversation?
-* Did you know that you can long press the people's icon to show/hide the CC/BCC fields and remember the visibility state for the next time?
-* Did you know that you can insert the email addresses of an Android contact group via the three dots overflow menu?
-* Did you know that if you select text and hit reply, only the selected text will be quoted?
-* Did you know that you can long press the trash icons (both in the message and the bottom action bar) to permanently delete a message or conversation? (version 1.1368+)
-* Did you know that you can long press the send action to show the send dialog, even if it was disabled?
-* Did you know that you can long press the full screen icon to show the original message text only?
+**(60) Vidste du ... ?**
+
+* Vidste du, at stjernemarkerede beskeder kan synkroniseres/beholdes for altid? (dette kan aktiveres i modtagelsesindstillingerne)
+* Vidste du, at du et langt tryk på ikonet 'Skriv besked' tager dig til Udkast-mappen?
+* Vidste du, at der er en avanceret mulighed for at markere beskeder som læst, når de flyttes? (arkivering og kassering er også i flytning)
+* Vidste du, at du kan vælge tekst (eller en e-mailadresse) i en app i de seneste Android-versioner og lade FairEmail søge efter den?
+* Vidste du, at FairEmail har en tablettilstand? Rotér din enhed til liggende tilstand og konversationstråde åbnes i en 2. kolonne, hvis der er tilstrækkelig skærmplads.
+* Vidste du, at et langt tryk kan bruges på en svarskabelon for at oprette en udkastbesked fra denne?
+* Vidste du, at man kan trykke og holde, og dernæst stryge for at vælge en række beskeder?
+* Vidste du, at man kan prøve at gensende en besked ved at bruge træk-ned-for-at-opfriske i Udbakken?
+* Vidste du, at man kan stryge en konversation til venstre/højre for at gå til den næste/forrige?
+* Vidste du, at man kan trykke på et billede for at se, hvorfra det downloades?
+* Vidste du, at et langt tryk på mappeikonet i handlingsbjælken muliggør valg af konto?
+* Vidste du, at et langt tryk på stjerneikonet i en konversationstråd muliggør valg af stjernefarve?
+* Vidste du, at navigeringsskuffen kan åbnes med et stryge fra venstre, selv når man kigger på en konversation?
+* Vidste du, at et langt tryk på personers ikon viser/skjuler CC-/BCC-felter samt huske synlighedstilstanden til næste gang?
+* Vidste du, at man kan indsætte en Android-kontaktgruppes e-mailadresser via trepriksoverløbsmenuen?
+* Vidste du, at vælger man tekst og trykker på svar, så vil kun den valgte tekst blive citeret?
+* Vidste du, at med et langt tryk på papirkurvsikoner (både i beskeden og den nederste handlingsbjæle) kan man permanent slette en besked/konversation? (version 1.1368+)
+* Vidste du, at et langt tryk på send-handlingen vil vise Send-dialogen, selv hvis den er deaktiveret?
+* Vidste du, at man med et lang tryk på fuldskærmsikonet kan få vist originalbeskedteksten?
 
 

 
 
-**(61) Why are some messages shown dimmed?**
+**(61) Hvorfor vises nogle beskeder nedtonet?**
 
-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.
+Nedtonede (grå) beskeder er lokalt flyttede beskeder, hvis flytning endnu ikke er bekræftet af serveren. Dette kan ske ved manglende forbindelse til serveren eller kontoen. Disse beskeder synkroniseres, når der er etableret server- og kontoforbindelse eller, hvis dette aldrig sker, slettes, hvis de er for gamle til at blive synkroniseret.
 
-You might need to manually synchronize the folder, for example by pulling down.
+Du skal muligvis synkronisere mappen manuelt, f.eks. ved at trække ned.
 
-You can view these messages, but you cannot move these messages again until the previous move has been confirmed.
+Du kan se disse beskeder, men du kan ikke flytte dem igen, før den foregående flytning er blevet bekræftet.
 
-Pending [operations](#user-content-faq3) are shown in the operations view accessible from the main navigation menu.
+Afventende [operationer](#user-content-faq3) vises i operationsvisningen tilgængelig via hovednavigeringsmenuen.
 
 

 
 
-**(62) Which authentication methods are supported?**
+**(62) Hvilke godkendelsesmetoder understøttes?**
 
-The following authentication methods are supported and used in this order:
+Flg. godkendelsesmetoder understøttes og anvendes i denne rækkefølge:
 
 * LOGIN
 * PLAIN
 * CRAM-MD5
 * XOAUTH2 ([Gmail](https://developers.google.com/gmail/imap/xoauth2-protocol), [Yandex](https://tech.yandex.com/oauth/))
-* NTLM (untested)
+* NTLM (ikke-testet)
 
-SASL authentication methods, besides CRAM-MD5, are not supported because [JavaMail for Android](https://javaee.github.io/javamail/Android) does not support SASL authentication.
+Da [JavaMail til Android](https://javaee.github.io/javamail/Android) ikke understøtter SASL-godkendelsesmetoder, er disse, udover CRAM-MD4, uunderstøttede.
 
-If your provider requires an unsupported authentication method, you'll likely get the error message *authentication failed*.
+Kræver udbyderen en uunderstøttet godkendelsesmetode, vil fejlmeddelelsen *godkendelse mislykkedes* sandsynligvis ses.
 
-[Server Name Indication](https://en.wikipedia.org/wiki/Server_Name_Indication) is supported by [all supported Android versions](https://developer.android.com/training/articles/security-ssl).
+[Server Name Indication](https://en.wikipedia.org/wiki/Server_Name_Indication) understøttes af [alle understøttede Android-versioner](https://developer.android.com/training/articles/security-ssl).
 
 

 
 
-**(63) How are images resized for displaying on screens?**
+**(63) Hvordan skaleres billeder til skærmvisning?**
 
-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.
+Store indlejrede eller vedhæftede [PNG-](https://en.wikipedia.org/wiki/Portable_Network_Graphics) og [JPEG-](https://en.wikipedia.org/wiki/JPEG)billeder skaleres automatisk mhp. skærmvisning. Dette skyldes, at e-mails er begrænset i størrelse til, afhængigt af udbyderen, fortrinsvis mellem 10 og 50 MB. Billeder skaleres som standard til en maksimal bredde og højde på ca. 1440 pixels og gemmes med et komprimeringsforhold på 90%. Billeder nedskaleres vha. heltalsfaktorer for at reducere hukommelsesforbruget og bevare billedkvalitet. Automatisk ændring af størrelse af indlejrede og/eller vedhæftede billeder og den maksimale målbilledstørrelse kan opsættes i Send-indstillinger.
 
-If you want to resize images on a case-by-case basis, you can use [Send Reduced](https://f-droid.org/en/packages/mobi.omegacentauri.SendReduced/) or a similar app.
+Ønsker man at ændre størrelsen på billeder fra gang til gang, kan [Send Reduced](https://f-droid.org/en/packages/mobi.omegacentauri.SendReduced/), eller en lignende app, benyttes.
 
 

 
 
-**~~(64) Can you add custom actions for swipe left/right?~~**
+**~~~(64) Kan der blive tilføjet tilpassede handlinger for venstre/højre stryg?~~**
 
-~~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.~~
+~~Den mest logiske konsekvens ifm. at stryge en listepost til venstre/højre er at fjerne denne fra listen.~~ ~~Den mest logiske handling ifm. en e-mail-app er at flytte beskeden til en anden mappe.~~ ~~Du kan vælge mappen, der skal flyttes til, via kontoindstillingerne.~~
 
-~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. See also [this question](#user-content-faq55).~~
+~~Andre handlinger, såsom markering af beskeder som læste og slumre beskeder, er tilgængelige via multivalg.~~ ~~~Lang tryk på en besked giver adgang til multivalg. Tjek også [dette spørgsmål](#user-content-faq55).~~
 
-~~Swiping left or right to mark a message read or unread is unnatural because the message first goes away and later comes back in a different shape.~~ ~~Note that there is an advanced option to mark messages automatically read on moving,~~ ~~which is in most cases a perfect replacement for the sequence mark read and move to some folder.~~ ~~You can also mark messages read from new message notifications.~~
+~~Strygning til venstre/højre for at markere en besked som læst/ulæst er ulogisk, da beskeden først tildeles én status for senere at få en anden. ~ ~~Bemærk, at der er en avanceret mulighed for automatisk at markere beskeder læste ved flytning,~~ ~~ som for det meste er en perfekt erstatning for sekvensen markér som læst og flyt til anden mappe.~~ ~~Man kan også markere beskeder læst via Nye beskeder-notifikationen.~~
 
-~~If you want to read a message later, you can hide it until a specific time by using the *snooze* menu.~~
+~~Vil man læse en besked senere, kan denne skjules indtil en bestemt tidspunkt ved brug af menuen *slumre*.~~
 
 

 
 
-**(65) Why are some attachments shown dimmed?**
+**(65) Hvorfor vises nogle beskeder nedtonet?**
 
-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.
+Indlejrede (billede) og vedhæftede filer vises nedtonet. [Indlejrede, vedhæftede filer](https://tools.ietf.org/html/rfc2183) er begrenet på automatisk download og visning. men da FairEmail ikke altid downloader vedhæftede filer automatisk (tjek også [denne FAQ](#user-content-faq40)), vil alle vedhæftningstyper blive vist. For at differentiere indlejringer og regulære vedhæftninger, vises indlejrede filer nedtonet.
 
 

 
 
-**(66) Is FairEmail available in the Google Play Family Library?**
+**(66) Er FairEmail tilgængelig i Google Play Familie-biblioteket?**
 
-The price of the few pro features is too low, lower than the price of most similar apps, and there are [too many fees and taxes](#user-content-faq19), 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.
+Prisen på de få Pro-funktioner er for lav, lavere end prisen på de fleste lignende apps, og der er [for mange gebyrer og skatter](#user-content-faq19), til at begrunde en tilgængeliggørelse af FairEmail i [Google Play Familie-biblioteket](https://support.google.com/googleone/answer/7007852). Bemærk, at Google promoverer Familie-biblioteket, men samtidig lader udviklere betale for det.
 
 

 
 
-**(67) How can I snooze conversations?**
+**(67) Hvordan slumres konversationer?**
 
-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.
+Vælg via multivalg én af flere konversationer (langt tryk for at tilgå multivalg), tryk på trepriksknappen og vælg *Slumre ...*. Alternativt kan *Slumre...* benyttes via den udvidede beskedvisning i trepriksmenuenpunktet 'mere' eller tidsforskydningshandlingen i den nederste handlingsbjælke. Vælg konversationsslumretid(er) og bekræft med et tryk på OK. Konversationerne skjules i det valgte tidsrum og vises derefter igen. En Ny besked-notifikation som påmindelse.
 
-It is also possible to snooze messages with [a rule](#user-content-faq71).
+Det er også muligt at slumre beskeder vha, [en regel](#user-content-faq71).
 
-You can show snoozed messages by unchecking *Filter out* > *Hidden* in the three dot overflow menu.
+Slumrede beskeder kan vises ved at afmarkerere *Bortfiltrér* > *Skjult* i trepriksoverløbsmenuen.
 
-You can tap on the small snooze icon to see until when a conversation is snoozed.
+Man kan trykke på det lille slumreikon for at se, hvor længe en konversation slumrer.
 
-By selecting a zero snooze duration you can cancel snoozing.
+Ved at angive nul som slumrevarighed, annulleres slumringen.
 
 

 
 
-**~~(68) Why can Adobe Acrobat reader not open PDF attachments / Microsoft apps not open attached documents?~~**
+**~~(68) Hvorfor kan Adobe Acrobat Reader/Microsoft-apps ikke åbne PDF-vedhæftninger/dokumentvedhæftninger?~~**
 
-~~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.~~
+~~Adobe Acrobat Reader og Microsoft apps forventer stadig fuld adgang til alle lagrede filer,~~ ~~selvom apps skal bruge [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider) siden Android KitKat (2013)~~ ~~~for at tilgå aktivt delte filer. Dette er af fortroligheds- og sikkerhedsårsager.~~
 
-~~You can workaround this by saving the attachment and opening it from the Adobe Acrobat reader / Microsoft app,~~ ~~but you are advised to install an up-to-date and preferably open source PDF reader / document viewer,~~ ~~for example one listed [here](https://github.com/offa/android-foss#-document--pdf-viewer).~~
+~~Dette kan løse ved at gemme vedhæftningen og åbne den fra Adobe Acrobat Reader/Microsoft-appen,~~ ~~, men det anbefales at installere en opdateret og helst open-source PDF-læser/dokumentfremviser,~~ ~~f.eks. en af de [hér](https://github.com/offa/android-foss#-document--pdf-viewer) anførte.~~
 
 

 
 
-**(69) Can you add auto scroll up on new message?**
+**(69) Kan der blive tilføjet auto-rul op ved ny besked?**
 
-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.
+Beskedlisten ruller automatisk op, når der navigeres fra en ny beskednotifikation eller efter manuel opfriskning. Altid automatisk rul op ved modtagelse af nye beskeder ville interferere ens egen rulning, men om ønsket, kan dette aktivere i indstillingerne.
 
 

 
 
-**(70) When will messages be auto expanded?**
+**(70) Hvornår auto-ekspanderes beskeder?**
 
-When navigation to a conversation one message will be expanded if:
+Ved navigering til en konversation, auto-ekspanderes én besked, hvis:
 
-* There is just one message in the conversation
-* There is exactly one unread message in the conversation
+* Der er kun én besked i konversationen
+* Der kun er én ulæst besked i konversationen
 
-There is one exception: the message was not downloaded yet and the message is too large to download automatically on a metered (mobile) connection. You can set or disable the maximum message size on the 'connection' settings tab.
+Der er én undtagelse: Beskeden er endnu ikke downloadet, og beskeden er for stor til at auto-downloade på en takseret (mobildata-) forbindelse. Maks. beskedstørrelse kan opsættes/deaktiveres på fanen 'Forbindelsesindstillinger'.
 
-Duplicate (archived) messages, trashed messages and draft messages are not counted.
+Dublet (arkiveret), kasserede og udkastbeskeder indregnes ikke.
 
-Messages will automatically be marked read on expanding, unless this was disabled in the individual account settings.
+Ved ekspandering auto-markeres beskeder som læste, medmindre dette er deaktiveret i de individuelle kontoindstillinger.
 
 

 
 
-**(71) How do I use filter rules?**
+**(71) Hvordan benyttes filterregler?**
 
-You can edit filter rules by long pressing a folder in the folder list of an account (tap the account name in the navigation/side menu).
+Man kan redigere filterregler via et langt tryk på en mappe i kontomappelisten (tryk på kontonavnet i navigering/sidemenuen).
 
-New rules will be applied to new messages received in the folder, not to existing messages. You can check the rule and apply the rule to existing messages or, alternatively, long press the rule in the rule list and select *Execute now*.
+Nye regler effektueres for nye, modtagne beskeder i mappen, ikke for eksisterende beskeder. Man kan tjekke reglen og anvende den på eksisterende beskeder eller, alternativt, via et langt tryk på regellisten vælge *Eksekvér nu*.
 
-You'll need to give a rule a name and you'll need to define the order in which a rule should be executed relative to other rules.
+En regel skal gives et navn, og rækkefølgen skal defineres, for hvilken en regel skal eksekveres relativt til andre regler.
 
-You can disable a rule and you can stop processing other rules after a rule has been executed.
+En regel kan deaktiveres og udførsel af andre regler kan stoppes efter en regel er blevet eksekveret.
 
-The following rule conditions are available:
+Flg. regelbetingelser er tilgængelige:
 
-* Sender contains
-* Recipient contains
-* Subject contains
-* Has attachments
+* Afsender indeholder
+* Modtager indeholder
+* Emne indeholder
+* Har vedhæftninger
 * Header contains
 * Day/time between
 
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-de-rAT.md b/docs/FAQ-de-rAT.md
index 68c4e6bb26..7bef9e3966 100644
--- a/docs/FAQ-de-rAT.md
+++ b/docs/FAQ-de-rAT.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-de-rDE.md b/docs/FAQ-de-rDE.md
index 68c4e6bb26..7bef9e3966 100644
--- a/docs/FAQ-de-rDE.md
+++ b/docs/FAQ-de-rDE.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-de-rLI.md b/docs/FAQ-de-rLI.md
index 68c4e6bb26..7bef9e3966 100644
--- a/docs/FAQ-de-rLI.md
+++ b/docs/FAQ-de-rLI.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-el-rGR.md b/docs/FAQ-el-rGR.md
index 93ef507188..fc85719dec 100644
--- a/docs/FAQ-el-rGR.md
+++ b/docs/FAQ-el-rGR.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-en-rGB.md b/docs/FAQ-en-rGB.md
index d0821f8dc2..5062dc362c 100644
--- a/docs/FAQ-en-rGB.md
+++ b/docs/FAQ-en-rGB.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-es-rES.md b/docs/FAQ-es-rES.md
index 5e73ec70b3..23016d68ca 100644
--- a/docs/FAQ-es-rES.md
+++ b/docs/FAQ-es-rES.md
@@ -858,13 +858,13 @@ El mensaje *... +OK ...* probablemente significa que un puerto POP3 (normalmente
 
 Los errores *... saludo inválido ...*, *... requiere una dirección válida ...* y *... Parámetro HELO no se ajusta a la sintaxis RFC ...* puede resolverse cambiando la configuración de identidad avanzada *Utilice la dirección IP local en lugar del nombre de host*.
 
-El error *... No se pudo conectar al host ...* significa que no hubo respuesta del servidor de correo en un tiempo razonable (20 segundos por defecto). Esto indica principalmente problemas de conectividad a internet, posiblemente causados por una VPN o por una aplicación de firewall. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
+El error *... No se pudo conectar al host ...* significa que no hubo respuesta del servidor de correo en un tiempo razonable (20 segundos por defecto). Esto indica principalmente problemas de conectividad a internet, posiblemente causados por una VPN o por una aplicación de firewall. Puede intentar aumentar el tiempo de espera de conexión en la configuración de conexión de FairEmail, para cuando el servidor de correo es realmente lento.
 
-El error *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
+El error *... Conexión rechazada...* significa que el servidor de correo electrónico o algo entre el servidor de correo y la aplicación, como un cortafuegos, rechazó activamente la conexión.
 
-El 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.
+El error *... Red inaccesible ...* significa que el servidor de correo electrónico no fue accesible a través de la conexión a internet actual, por ejemplo, porque el tráfico de internet sólo está restringido al tráfico local.
 
-The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
+El error *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
 
 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.
 
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-eu-rES.md b/docs/FAQ-eu-rES.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-eu-rES.md
+++ b/docs/FAQ-eu-rES.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-fa-rIR.md b/docs/FAQ-fa-rIR.md
index d9b0340ddf..509dd3e26d 100644
--- a/docs/FAQ-fa-rIR.md
+++ b/docs/FAQ-fa-rIR.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-fi-rFI.md b/docs/FAQ-fi-rFI.md
index dab78cbd9d..9d10fd1976 100644
--- a/docs/FAQ-fi-rFI.md
+++ b/docs/FAQ-fi-rFI.md
@@ -16,7 +16,7 @@ Jos sinulla on kysymyksiä, ole hyvä ja tarkista ensin alla olevat usein kysyty
 
 Useimmissa tapauksissa pika-asennus pystyy automaattisesti tunnistamaan oikeat asetukset.
 
-Jos nopea asennus epäonnistuu, sinun on määritettävä tili manuaalisesti (sähköpostin vastaanottamiseksi) ja identiteetti (sähköpostin lähettämiseksi). Tätä varten tarvitset IMAP- ja SMTP-palvelimien osoitteet ja porttinumerot, tiedon käytetäänkö SSL/TLS- tai STARTTLS-salausta ja käyttäjätunnuksesi (useimmiten sähköpostiosoitteesi, mutta ei aina) ja salasanasi.
+Jos pika-asennus epäonnistuu, sinun on määritettävä tili manuaalisesti (sähköpostin vastaanottamiseksi) ja identiteetti (sähköpostin lähettämiseksi). Tätä varten tarvitset IMAP- ja SMTP-palvelimien osoitteet ja porttinumerot, tiedon käytetäänkö SSL/TLS- tai STARTTLS-salausta ja käyttäjätunnuksesi (useimmiten sähköpostiosoitteesi, mutta ei aina) ja salasanasi.
 
 Hakemalla *IMAP* ja palveluntarjoajan nimi riittää useimmiten oikean dokumentaation löytämiseen.
 
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-fr-rCA.md b/docs/FAQ-fr-rCA.md
index 51bfc0a0d1..449f850520 100644
--- a/docs/FAQ-fr-rCA.md
+++ b/docs/FAQ-fr-rCA.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-fr-rFR.md b/docs/FAQ-fr-rFR.md
index 681381ca08..31df508461 100644
--- a/docs/FAQ-fr-rFR.md
+++ b/docs/FAQ-fr-rFR.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-fy-rNL.md b/docs/FAQ-fy-rNL.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-fy-rNL.md
+++ b/docs/FAQ-fy-rNL.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-gl-rES.md b/docs/FAQ-gl-rES.md
index 9d746dce8e..904776cc29 100644
--- a/docs/FAQ-gl-rES.md
+++ b/docs/FAQ-gl-rES.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-hi-rIN.md b/docs/FAQ-hi-rIN.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-hi-rIN.md
+++ b/docs/FAQ-hi-rIN.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-hr-rHR.md b/docs/FAQ-hr-rHR.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-hr-rHR.md
+++ b/docs/FAQ-hr-rHR.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-hu-rHU.md b/docs/FAQ-hu-rHU.md
index 10c94ce3a4..ba0286e468 100644
--- a/docs/FAQ-hu-rHU.md
+++ b/docs/FAQ-hu-rHU.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-in-rID.md b/docs/FAQ-in-rID.md
index 26e3ef1ef1..507882fb96 100644
--- a/docs/FAQ-in-rID.md
+++ b/docs/FAQ-in-rID.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-it-rIT.md b/docs/FAQ-it-rIT.md
index 97311fae50..a5f67ab797 100644
--- a/docs/FAQ-it-rIT.md
+++ b/docs/FAQ-it-rIT.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-iw-rIL.md b/docs/FAQ-iw-rIL.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-iw-rIL.md
+++ b/docs/FAQ-iw-rIL.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-ja-rJP.md b/docs/FAQ-ja-rJP.md
index 8eb2b00e86..d714c8709c 100644
--- a/docs/FAQ-ja-rJP.md
+++ b/docs/FAQ-ja-rJP.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-ka-rGE.md b/docs/FAQ-ka-rGE.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-ka-rGE.md
+++ b/docs/FAQ-ka-rGE.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-kk-rKZ.md b/docs/FAQ-kk-rKZ.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-kk-rKZ.md
+++ b/docs/FAQ-kk-rKZ.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-ko-rKR.md b/docs/FAQ-ko-rKR.md
index f96cf78a2b..cf15ffa9e4 100644
--- a/docs/FAQ-ko-rKR.md
+++ b/docs/FAQ-ko-rKR.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-lt-rLT.md b/docs/FAQ-lt-rLT.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-lt-rLT.md
+++ b/docs/FAQ-lt-rLT.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-nl-rNL.md b/docs/FAQ-nl-rNL.md
index 4bbefcd4f2..999230560d 100644
--- a/docs/FAQ-nl-rNL.md
+++ b/docs/FAQ-nl-rNL.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-nn-rNO.md b/docs/FAQ-nn-rNO.md
index d09ae7aed9..d6a5308d9e 100644
--- a/docs/FAQ-nn-rNO.md
+++ b/docs/FAQ-nn-rNO.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-no-rNO.md b/docs/FAQ-no-rNO.md
index d09ae7aed9..d6a5308d9e 100644
--- a/docs/FAQ-no-rNO.md
+++ b/docs/FAQ-no-rNO.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-pl-rPL.md b/docs/FAQ-pl-rPL.md
index ea588d4650..4468dcbfa4 100644
--- a/docs/FAQ-pl-rPL.md
+++ b/docs/FAQ-pl-rPL.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-pt-rBR.md b/docs/FAQ-pt-rBR.md
index b448bf778b..754100892a 100644
--- a/docs/FAQ-pt-rBR.md
+++ b/docs/FAQ-pt-rBR.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-pt-rPT.md b/docs/FAQ-pt-rPT.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-pt-rPT.md
+++ b/docs/FAQ-pt-rPT.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-ro-rRO.md b/docs/FAQ-ro-rRO.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-ro-rRO.md
+++ b/docs/FAQ-ro-rRO.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-ru-rRU.md b/docs/FAQ-ru-rRU.md
index 5e1ef59e3e..f32cf982c8 100644
--- a/docs/FAQ-ru-rRU.md
+++ b/docs/FAQ-ru-rRU.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-si-rLK.md b/docs/FAQ-si-rLK.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-si-rLK.md
+++ b/docs/FAQ-si-rLK.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-sk-rSK.md b/docs/FAQ-sk-rSK.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-sk-rSK.md
+++ b/docs/FAQ-sk-rSK.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-sl-rSI.md b/docs/FAQ-sl-rSI.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-sl-rSI.md
+++ b/docs/FAQ-sl-rSI.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-sr-rSP.md b/docs/FAQ-sr-rSP.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-sr-rSP.md
+++ b/docs/FAQ-sr-rSP.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-sv-rSE.md b/docs/FAQ-sv-rSE.md
index 2ac61bd065..f48e1ae4c4 100644
--- a/docs/FAQ-sv-rSE.md
+++ b/docs/FAQ-sv-rSE.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-ta-rIN.md b/docs/FAQ-ta-rIN.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-ta-rIN.md
+++ b/docs/FAQ-ta-rIN.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-tr-rTR.md b/docs/FAQ-tr-rTR.md
index b0be77e3d1..e84ed371b7 100644
--- a/docs/FAQ-tr-rTR.md
+++ b/docs/FAQ-tr-rTR.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-uk-rUA.md b/docs/FAQ-uk-rUA.md
index 167f4be5b2..b8be36900f 100644
--- a/docs/FAQ-uk-rUA.md
+++ b/docs/FAQ-uk-rUA.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-vi-rVN.md b/docs/FAQ-vi-rVN.md
index 87aecbce14..230a8ba5e6 100644
--- a/docs/FAQ-vi-rVN.md
+++ b/docs/FAQ-vi-rVN.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-zh-rCN.md b/docs/FAQ-zh-rCN.md
index a7925dbc56..a2db140dbb 100644
--- a/docs/FAQ-zh-rCN.md
+++ b/docs/FAQ-zh-rCN.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
diff --git a/docs/FAQ-zh-rTW.md b/docs/FAQ-zh-rTW.md
index 92b84a3d99..d3c2682956 100644
--- a/docs/FAQ-zh-rTW.md
+++ b/docs/FAQ-zh-rTW.md
@@ -1955,6 +1955,8 @@ Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but link
 
 Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
 
+Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
+
 Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
 
 Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.