mirror of https://github.com/M66B/FairEmail.git
Crowdin sync
This commit is contained in:
M66B
parent
d2db3f32e6
commit
0a1f43837a
|
|
@ -231,7 +231,6 @@
|
|||
<string name="title_advanced_suggest_sent">Предложи адреси, намерени в изпратените съобщения</string>
|
||||
<string name="title_advanced_suggest_received">Предложи адреси, намерени в получени съобщения</string>
|
||||
<string name="title_advanced_suggest_frequently">Сортиране на предложените адреси по използваемост</string>
|
||||
<string name="title_advanced_auto_list">Автоматично създаване на списъци</string>
|
||||
<string name="title_advanced_prefix_once">Префикс в темата само веднъж при отговор или препращане</string>
|
||||
<string name="title_advanced_extended_reply">Използвай разширено заглавие за отговор/препращане</string>
|
||||
<string name="title_advanced_quote_reply">Цитирай текста в отговора</string>
|
||||
|
|
|
|||
|
|
@ -233,7 +233,6 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_advanced_suggest_sent">Suggeriu adreces trobades als missatges enviats</string>
|
||||
<string name="title_advanced_suggest_received">Suggeriu adreces trobades als missatges rebuts</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordena les adreces suggerides en funció de la freqüència d’ús</string>
|
||||
<string name="title_advanced_auto_list">Crea llistes automàticament</string>
|
||||
<string name="title_advanced_prefix_once">El prefix de l\'assumpte només una vegada a la resposta o al reenviament</string>
|
||||
<string name="title_advanced_extended_reply">Utilitza resposta estesa/capçalera de reenviament</string>
|
||||
<string name="title_advanced_quote_reply">Text amb resposta a la cita</string>
|
||||
|
|
|
|||
|
|
@ -262,7 +262,6 @@
|
|||
<string name="title_advanced_suggest_received">Navrhovat adresy nalezené v přijatých zprávách</string>
|
||||
<string name="title_advanced_suggest_frequently">Řadit navrhované adresy dle četnosti použití</string>
|
||||
<string name="title_advanced_compose_font">Výchozí písmo</string>
|
||||
<string name="title_advanced_auto_list">Automaticky vytvářet seznamy</string>
|
||||
<string name="title_advanced_prefix_once">Při odpovídání nebo přeposílání přidat do předmětu pouze jednu předponu</string>
|
||||
<string name="title_advanced_extended_reply">Použít rozšířenou hlavičku odpovědi/přeposlání</string>
|
||||
<string name="title_advanced_quote_reply">Citovat text odpovědi</string>
|
||||
|
|
@ -815,9 +814,9 @@
|
|||
<string name="title_style_size_medium">Střední</string>
|
||||
<string name="title_style_size_large">Velký</string>
|
||||
<string name="title_style_color">Barva …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Seznam</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Odrážky</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Číslovaný</string>
|
||||
<string name="title_style_list">Seznam</string>
|
||||
<string name="title_style_list_bullets">Odrážky</string>
|
||||
<string name="title_style_list_numbered">Číslovaný</string>
|
||||
<string name="title_style_font">Písmo</string>
|
||||
<string name="title_style_font_default">Výchozí</string>
|
||||
<string name="title_style_clear">Vymazat formátování</string>
|
||||
|
|
|
|||
|
|
@ -246,7 +246,6 @@
|
|||
<string name="title_advanced_suggest_received">Foreslå adresser fra modtagne beskeder</string>
|
||||
<string name="title_advanced_suggest_frequently">Sortér foreslåede adresser efter brugsfrekvens</string>
|
||||
<string name="title_advanced_compose_font">Standardskrifttype</string>
|
||||
<string name="title_advanced_auto_list">Generér lister automatisk</string>
|
||||
<string name="title_advanced_prefix_once">Kun ét emnepræfiks ved svar eller videresendelse</string>
|
||||
<string name="title_advanced_extended_reply">Benyt udvidet svar-/videresendoverskrift</string>
|
||||
<string name="title_advanced_quote_reply">Citat af svartekst</string>
|
||||
|
|
@ -800,9 +799,9 @@
|
|||
<string name="title_style_size_medium">Mellem</string>
|
||||
<string name="title_style_size_large">Stor</string>
|
||||
<string name="title_style_color">Farve …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Liste</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Punktliste</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Nummereret</string>
|
||||
<string name="title_style_list">Liste</string>
|
||||
<string name="title_style_list_bullets">Punktliste</string>
|
||||
<string name="title_style_list_numbered">Nummereret</string>
|
||||
<string name="title_style_font">Skrifttype</string>
|
||||
<string name="title_style_font_default">Standard</string>
|
||||
<string name="title_style_clear">Ryd formatering</string>
|
||||
|
|
|
|||
|
|
@ -247,7 +247,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_advanced_suggest_received">Adressen aus empfangenen Nachrichten vorschlagen</string>
|
||||
<string name="title_advanced_suggest_frequently">Vorgeschlagene Adressen nach Nutzungshäufigkeit sortieren</string>
|
||||
<string name="title_advanced_compose_font">Standard-Schriftart</string>
|
||||
<string name="title_advanced_auto_list">Listen automatisch erstellen</string>
|
||||
<string name="title_advanced_prefix_once">Re: und Fwd: nur einmal beim Antworten oder Weiterleiten voranstellen</string>
|
||||
<string name="title_advanced_extended_reply">Erweiterte Antwort-/Weiterleitungs-Kopfzeile verwenden</string>
|
||||
<string name="title_advanced_quote_reply">Beantworteten Text zitieren</string>
|
||||
|
|
@ -765,6 +764,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_third_party">Sie verwenden eine Version eines Drittanbieters</string>
|
||||
<string name="title_expand_warning">Durch Erweitern dieser Nachricht wird %1$s heruntergeladen</string>
|
||||
<string name="title_download_message">wird heruntergeladen …</string>
|
||||
<string name="title_reformatted">Dies ist die neu formatierte Nachrichtenansicht. Sie können auf das ⛶ -Symbol tippen, um die ursprüngliche Nachricht zu sehen und diese Nachricht zu verstecken.</string>
|
||||
<string name="title_compose">Verfassen</string>
|
||||
<string name="title_submitter">Gesendet von:</string>
|
||||
<string name="title_delivered_to">Zugestellt an:</string>
|
||||
|
|
@ -800,9 +800,9 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_style_size_medium">Mittel</string>
|
||||
<string name="title_style_size_large">Groß</string>
|
||||
<string name="title_style_color">Farbe …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Liste</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Nummeriert</string>
|
||||
<string name="title_style_list">Liste</string>
|
||||
<string name="title_style_list_bullets">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered">Nummeriert</string>
|
||||
<string name="title_style_font">Schriftart</string>
|
||||
<string name="title_style_font_default">Standard</string>
|
||||
<string name="title_style_clear">Formatierung entfernen</string>
|
||||
|
|
|
|||
|
|
@ -247,7 +247,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_advanced_suggest_received">Adressen aus empfangenen Nachrichten vorschlagen</string>
|
||||
<string name="title_advanced_suggest_frequently">Vorgeschlagene Adressen nach Nutzungshäufigkeit sortieren</string>
|
||||
<string name="title_advanced_compose_font">Standard-Schriftart</string>
|
||||
<string name="title_advanced_auto_list">Listen automatisch erstellen</string>
|
||||
<string name="title_advanced_prefix_once">Re: und Fwd: nur einmal beim Antworten oder Weiterleiten voranstellen</string>
|
||||
<string name="title_advanced_extended_reply">Erweiterte Antwort-/Weiterleitungs-Kopfzeile verwenden</string>
|
||||
<string name="title_advanced_quote_reply">Beantworteten Text zitieren</string>
|
||||
|
|
@ -765,6 +764,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_third_party">Sie verwenden eine Version eines Drittanbieters</string>
|
||||
<string name="title_expand_warning">Durch Erweitern dieser Nachricht wird %1$s heruntergeladen</string>
|
||||
<string name="title_download_message">wird heruntergeladen …</string>
|
||||
<string name="title_reformatted">Dies ist die neu formatierte Nachrichtenansicht. Sie können auf das ⛶ -Symbol tippen, um die ursprüngliche Nachricht zu sehen und diese Nachricht zu verstecken.</string>
|
||||
<string name="title_compose">Verfassen</string>
|
||||
<string name="title_submitter">Gesendet von:</string>
|
||||
<string name="title_delivered_to">Zugestellt an:</string>
|
||||
|
|
@ -800,9 +800,9 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_style_size_medium">Mittel</string>
|
||||
<string name="title_style_size_large">Groß</string>
|
||||
<string name="title_style_color">Farbe …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Liste</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Nummeriert</string>
|
||||
<string name="title_style_list">Liste</string>
|
||||
<string name="title_style_list_bullets">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered">Nummeriert</string>
|
||||
<string name="title_style_font">Schriftart</string>
|
||||
<string name="title_style_font_default">Standard</string>
|
||||
<string name="title_style_clear">Formatierung entfernen</string>
|
||||
|
|
|
|||
|
|
@ -247,7 +247,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_advanced_suggest_received">Adressen aus empfangenen Nachrichten vorschlagen</string>
|
||||
<string name="title_advanced_suggest_frequently">Vorgeschlagene Adressen nach Nutzungshäufigkeit sortieren</string>
|
||||
<string name="title_advanced_compose_font">Standard-Schriftart</string>
|
||||
<string name="title_advanced_auto_list">Listen automatisch erstellen</string>
|
||||
<string name="title_advanced_prefix_once">Re: und Fwd: nur einmal beim Antworten oder Weiterleiten voranstellen</string>
|
||||
<string name="title_advanced_extended_reply">Erweiterte Antwort-/Weiterleitungs-Kopfzeile verwenden</string>
|
||||
<string name="title_advanced_quote_reply">Beantworteten Text zitieren</string>
|
||||
|
|
@ -765,6 +764,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_third_party">Sie verwenden eine Version eines Drittanbieters</string>
|
||||
<string name="title_expand_warning">Durch Erweitern dieser Nachricht wird %1$s heruntergeladen</string>
|
||||
<string name="title_download_message">wird heruntergeladen …</string>
|
||||
<string name="title_reformatted">Dies ist die neu formatierte Nachrichtenansicht. Sie können auf das ⛶ -Symbol tippen, um die ursprüngliche Nachricht zu sehen und diese Nachricht zu verstecken.</string>
|
||||
<string name="title_compose">Verfassen</string>
|
||||
<string name="title_submitter">Gesendet von:</string>
|
||||
<string name="title_delivered_to">Zugestellt an:</string>
|
||||
|
|
@ -800,9 +800,9 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_style_size_medium">Mittel</string>
|
||||
<string name="title_style_size_large">Groß</string>
|
||||
<string name="title_style_color">Farbe …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Liste</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Nummeriert</string>
|
||||
<string name="title_style_list">Liste</string>
|
||||
<string name="title_style_list_bullets">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered">Nummeriert</string>
|
||||
<string name="title_style_font">Schriftart</string>
|
||||
<string name="title_style_font_default">Standard</string>
|
||||
<string name="title_style_clear">Formatierung entfernen</string>
|
||||
|
|
|
|||
|
|
@ -247,7 +247,6 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_advanced_suggest_received">Adressen aus empfangenen Nachrichten vorschlagen</string>
|
||||
<string name="title_advanced_suggest_frequently">Vorgeschlagene Adressen nach Nutzungshäufigkeit sortieren</string>
|
||||
<string name="title_advanced_compose_font">Standard-Schriftart</string>
|
||||
<string name="title_advanced_auto_list">Listen automatisch erstellen</string>
|
||||
<string name="title_advanced_prefix_once">Re: und Fwd: nur einmal beim Antworten oder Weiterleiten voranstellen</string>
|
||||
<string name="title_advanced_extended_reply">Erweiterte Antwort-/Weiterleitungs-Kopfzeile verwenden</string>
|
||||
<string name="title_advanced_quote_reply">Beantworteten Text zitieren</string>
|
||||
|
|
@ -765,6 +764,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_third_party">Sie verwenden eine Version eines Drittanbieters</string>
|
||||
<string name="title_expand_warning">Durch Erweitern dieser Nachricht wird %1$s heruntergeladen</string>
|
||||
<string name="title_download_message">wird heruntergeladen …</string>
|
||||
<string name="title_reformatted">Dies ist die neu formatierte Nachrichtenansicht. Sie können auf das ⛶ -Symbol tippen, um die ursprüngliche Nachricht zu sehen und diese Nachricht zu verstecken.</string>
|
||||
<string name="title_compose">Verfassen</string>
|
||||
<string name="title_submitter">Gesendet von:</string>
|
||||
<string name="title_delivered_to">Zugestellt an:</string>
|
||||
|
|
@ -800,9 +800,9 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_style_size_medium">Mittel</string>
|
||||
<string name="title_style_size_large">Groß</string>
|
||||
<string name="title_style_color">Farbe …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Liste</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Nummeriert</string>
|
||||
<string name="title_style_list">Liste</string>
|
||||
<string name="title_style_list_bullets">Aufzählungspunkte</string>
|
||||
<string name="title_style_list_numbered">Nummeriert</string>
|
||||
<string name="title_style_font">Schriftart</string>
|
||||
<string name="title_style_font_default">Standard</string>
|
||||
<string name="title_style_clear">Formatierung entfernen</string>
|
||||
|
|
|
|||
|
|
@ -245,7 +245,6 @@
|
|||
<string name="title_advanced_suggest_received">Προτείνονται διευθύνσεις που βρέθηκαν σε μηνύματα που έχουν ληφθεί</string>
|
||||
<string name="title_advanced_suggest_frequently">Ταξινόμηση των προτεινόμενων διευθύνσεων με βάση τη συχνότητα που χρησιμοποιούνται</string>
|
||||
<string name="title_advanced_compose_font">Προεπιλεγμένη γραμματοσειρά</string>
|
||||
<string name="title_advanced_auto_list">Αυτόματη δημιουργία λιστών</string>
|
||||
<string name="title_advanced_prefix_once">Μόνο ένα πρόθεμα κατά την απάντηση ή προώθηση μηνύματος</string>
|
||||
<string name="title_advanced_extended_reply">Χρήση εκτεταμένων κεφαλίδων κατά την απάντηση/προώθηση</string>
|
||||
<string name="title_advanced_quote_reply">Παράθεση του προς απάντηση κειμένου</string>
|
||||
|
|
@ -760,6 +759,7 @@
|
|||
<string name="title_third_party">Χρησιμοποιείτε μια έκδοση ενός τρίτου παρόχου</string>
|
||||
<string name="title_expand_warning">Αν αναπτυχθεί αυτό το μήνυμα, θα κατέβει %1$s</string>
|
||||
<string name="title_download_message">Κατεβαίνει …</string>
|
||||
<string name="title_reformatted">Αυτή είναι η αναμορφοποιημένη προβολή μηνύματος. Μπορείτε να πατήσετε πάνω στο εικονίδιο ⛶ για να δείτε το αρχικό μήνυμα και να αποκρύψετε το παρόν μήνυμα.</string>
|
||||
<string name="title_compose">Σύνταξη</string>
|
||||
<string name="title_submitter">Στάλθηκε από:</string>
|
||||
<string name="title_delivered_to">Παραδόθηκε σε:</string>
|
||||
|
|
@ -795,9 +795,9 @@
|
|||
<string name="title_style_size_medium">Μεσαία</string>
|
||||
<string name="title_style_size_large">Μεγάλα</string>
|
||||
<string name="title_style_color">Χρώμα …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Λίστα</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Κουκκίδες</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Αρίθμηση</string>
|
||||
<string name="title_style_list">Λίστα</string>
|
||||
<string name="title_style_list_bullets">Κουκκίδες</string>
|
||||
<string name="title_style_list_numbered">Αρίθμηση</string>
|
||||
<string name="title_style_font">Γραμματοσειρά</string>
|
||||
<string name="title_style_font_default">Προεπιλογή</string>
|
||||
<string name="title_style_clear">Εκκαθάριση μορφοποίησης</string>
|
||||
|
|
|
|||
|
|
@ -247,7 +247,6 @@
|
|||
<string name="title_advanced_suggest_received">Sugerir direcciones encontradas en mensajes recibidos</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordenar direcciones sugeridas por frecuencia de uso</string>
|
||||
<string name="title_advanced_compose_font">Fuente por defecto</string>
|
||||
<string name="title_advanced_auto_list">Crear listas automáticamente</string>
|
||||
<string name="title_advanced_prefix_once">Prefijar el asunto solo una vez al responder o reenviar</string>
|
||||
<string name="title_advanced_extended_reply">Usar encabezado de respuesta/reenvío extendido</string>
|
||||
<string name="title_advanced_quote_reply">Citar texto a responder</string>
|
||||
|
|
@ -766,6 +765,7 @@
|
|||
<string name="title_third_party">Está usando una versión de un tercero</string>
|
||||
<string name="title_expand_warning">Expandir este mensaje descargará %1$s</string>
|
||||
<string name="title_download_message">Descargando …</string>
|
||||
<string name="title_reformatted">Esta es la vista de mensaje reformateada. Puede tocar el icono ⛶ para ver el mensaje original y ocultar este mensaje.</string>
|
||||
<string name="title_compose">Redactar</string>
|
||||
<string name="title_submitter">Enviado por:</string>
|
||||
<string name="title_delivered_to">Entregado a:</string>
|
||||
|
|
@ -801,6 +801,9 @@
|
|||
<string name="title_style_size_medium">Mediano</string>
|
||||
<string name="title_style_size_large">Grande</string>
|
||||
<string name="title_style_color">Color …</string>
|
||||
<string name="title_style_list">Lista</string>
|
||||
<string name="title_style_list_bullets">Viñetas</string>
|
||||
<string name="title_style_list_numbered">Numeradas</string>
|
||||
<string name="title_style_font">Fuente</string>
|
||||
<string name="title_style_font_default">Por defecto</string>
|
||||
<string name="title_style_clear">Quitar formato</string>
|
||||
|
|
|
|||
|
|
@ -227,7 +227,6 @@
|
|||
<string name="title_advanced_suggest_sent">Proposatu bidalitako mezuetan aurkitutako helbideak</string>
|
||||
<string name="title_advanced_suggest_received">Proposatu jasotako mezuetan aurkitutako helbideak</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordenatu iradokitako helbideak erabilera maiztasunaren arabera</string>
|
||||
<string name="title_advanced_auto_list">Sortu zerrendak automatikoki</string>
|
||||
<string name="title_advanced_prefix_once">Jarri aurrizkia mintzagaiari behin bakarrik erantzun edo birbidaltzean</string>
|
||||
<string name="title_advanced_extended_reply">Erabili erantzun/birbidali goiburu hedatua</string>
|
||||
<string name="title_advanced_quote_reply">Aipatu erantzundako testua</string>
|
||||
|
|
|
|||
|
|
@ -236,7 +236,6 @@
|
|||
<string name="title_advanced_suggest_received">پیشنهاد نشانیهای یافت شده در پیامهای دریافت شده</string>
|
||||
<string name="title_advanced_suggest_frequently">مرتبسازی نشانیهای پیشنهادی در دفعات استفاده</string>
|
||||
<string name="title_advanced_compose_font">قلم پیشفرض</string>
|
||||
<string name="title_advanced_auto_list">بهصورت خودکار فهرستها را ایجاد کن</string>
|
||||
<string name="title_advanced_quote_reply">متن پاسخ نقل قول شده</string>
|
||||
<string name="title_advanced_resize_reply">تغییر اندازه تصاویر در متن پاسخ داده شده</string>
|
||||
<string name="title_advanced_signature_location">موقعیت امضاء</string>
|
||||
|
|
|
|||
|
|
@ -238,7 +238,6 @@
|
|||
<string name="title_advanced_suggest_received">Ehdota saapuneista viesteistä löytyviä osoitteita</string>
|
||||
<string name="title_advanced_suggest_frequently">Järjestä ehdotetut osoitteet käytetyimmät ensin</string>
|
||||
<string name="title_advanced_compose_font">Oletuskirjasin</string>
|
||||
<string name="title_advanced_auto_list">Luo listoja automaattisesti</string>
|
||||
<string name="title_advanced_prefix_once">Lisää aiheeseen etuliite vain kerran vastatessa ja edelleenlähetettäessä</string>
|
||||
<string name="title_advanced_extended_reply">Käytä laajennettuja tunnistetietoja vastauksessa/edelleenlähetettäessä</string>
|
||||
<string name="title_advanced_quote_reply">Lainaa vastattu teksti</string>
|
||||
|
|
|
|||
|
|
@ -246,7 +246,6 @@
|
|||
<string name="title_advanced_suggest_received">Suggérer les adresses trouvées dans les messages reçus</string>
|
||||
<string name="title_advanced_suggest_frequently">Trier les adresses suggérées par fréquence d’utilisation</string>
|
||||
<string name="title_advanced_compose_font">Police par défaut</string>
|
||||
<string name="title_advanced_auto_list">Créer automatiquement des listes</string>
|
||||
<string name="title_advanced_prefix_once">Ne préfixer l’objet qu’une seule fois lors de la réponse ou du transfert</string>
|
||||
<string name="title_advanced_extended_reply">Utiliser l’en-tête de réponse/transfert étendu</string>
|
||||
<string name="title_advanced_quote_reply">Citer le texte répondu</string>
|
||||
|
|
@ -765,6 +764,7 @@
|
|||
<string name="title_third_party">Vous utilisez une version tierce</string>
|
||||
<string name="title_expand_warning">Développer ce message téléchargera %1$s</string>
|
||||
<string name="title_download_message">Téléchargement…</string>
|
||||
<string name="title_reformatted">Ceci est la vue de message reformatée. Vous pouvez appuyer sur l\'icône ⛶ pour afficher le message original et masquer ce message.</string>
|
||||
<string name="title_compose">Rédiger</string>
|
||||
<string name="title_submitter">Envoyé par :</string>
|
||||
<string name="title_delivered_to">Envoyé à :</string>
|
||||
|
|
@ -800,9 +800,9 @@
|
|||
<string name="title_style_size_medium">Moyen</string>
|
||||
<string name="title_style_size_large">Grand</string>
|
||||
<string name="title_style_color">Couleur…</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Liste</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Puces</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Numéros</string>
|
||||
<string name="title_style_list">Liste</string>
|
||||
<string name="title_style_list_bullets">Puces</string>
|
||||
<string name="title_style_list_numbered">Numérotée</string>
|
||||
<string name="title_style_font">Police de caractères</string>
|
||||
<string name="title_style_font_default">Par défaut</string>
|
||||
<string name="title_style_clear">Effacer la mise en forme</string>
|
||||
|
|
|
|||
|
|
@ -246,7 +246,6 @@
|
|||
<string name="title_advanced_suggest_received">Suggérer les adresses trouvées dans les messages reçus</string>
|
||||
<string name="title_advanced_suggest_frequently">Trier les adresses suggérées par fréquence d’utilisation</string>
|
||||
<string name="title_advanced_compose_font">Police de caractères par défaut</string>
|
||||
<string name="title_advanced_auto_list">Créer automatiquement des listes</string>
|
||||
<string name="title_advanced_prefix_once">Ne préfixer l\'objet qu\'une seule fois lors de la réponse ou du transfert</string>
|
||||
<string name="title_advanced_extended_reply">Utiliser l\'en-tête étendu de réponse/transfert</string>
|
||||
<string name="title_advanced_quote_reply">Citer le texte répondu</string>
|
||||
|
|
@ -765,6 +764,7 @@
|
|||
<string name="title_third_party">Vous utilisez une version tierce</string>
|
||||
<string name="title_expand_warning">Déplier ce message téléchargera %1$s</string>
|
||||
<string name="title_download_message">Téléchargement…</string>
|
||||
<string name="title_reformatted">Ceci est la vue de message reformaté. Vous pouvez appuyer sur l\'icône ⛶ pour afficher le message original et masquer ce message.</string>
|
||||
<string name="title_compose">Rédiger</string>
|
||||
<string name="title_submitter">Envoyé par :</string>
|
||||
<string name="title_delivered_to">Envoyé à :</string>
|
||||
|
|
@ -800,9 +800,9 @@
|
|||
<string name="title_style_size_medium">Moyen</string>
|
||||
<string name="title_style_size_large">Grand</string>
|
||||
<string name="title_style_color">Couleur…</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Liste</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Puces</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Numéros</string>
|
||||
<string name="title_style_list">Liste</string>
|
||||
<string name="title_style_list_bullets">Puces</string>
|
||||
<string name="title_style_list_numbered">Numéros</string>
|
||||
<string name="title_style_font">Police de caractères</string>
|
||||
<string name="title_style_font_default">Par défaut</string>
|
||||
<string name="title_style_clear">Effacer la mise en forme</string>
|
||||
|
|
|
|||
|
|
@ -240,7 +240,6 @@
|
|||
<string name="title_advanced_suggest_received">Suxerir enderezos atopados en mensaxes recibidas</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordenar enderezos suxeridos pola frecuencia de uso</string>
|
||||
<string name="title_advanced_compose_font">Fonte predefinida</string>
|
||||
<string name="title_advanced_auto_list">Crear listas automaticamente</string>
|
||||
<string name="title_advanced_prefix_once">Só poñer un único prefixo no asunto cando se responde ou reenvía</string>
|
||||
<string name="title_advanced_extended_reply">Usar cabeceira estendida de resposta/reenvío</string>
|
||||
<string name="title_advanced_quote_reply">Citar texto respondido</string>
|
||||
|
|
|
|||
|
|
@ -242,7 +242,6 @@ A szabályokkal kapcsolatos funkciók csak pro verzióban érhetők el.
|
|||
<string name="title_advanced_suggest_received">Fogadott üzenetekben szereplő címek felajánlása</string>
|
||||
<string name="title_advanced_suggest_frequently">A felajánlott címek rendezése gyakoriság alapján</string>
|
||||
<string name="title_advanced_compose_font">Alapértelmezett betűtípus</string>
|
||||
<string name="title_advanced_auto_list">Listák automatikus létrehozása</string>
|
||||
<string name="title_advanced_prefix_once">Válasz vagy továbbítás esetén tárgy előtaggal jelzése csak egyszer</string>
|
||||
<string name="title_advanced_extended_reply">Kiterjesztett válasz/továbbítás fejléc használata</string>
|
||||
<string name="title_advanced_quote_reply">Megválaszolt szöveg idézése</string>
|
||||
|
|
|
|||
|
|
@ -246,7 +246,6 @@
|
|||
<string name="title_advanced_suggest_received">Suggerisci indirizzi trovati nei messaggi ricevuti</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordina gli indirizzi suggeriti in base alla frequenza d\'uso</string>
|
||||
<string name="title_advanced_compose_font">Tipo di carattere predefinito</string>
|
||||
<string name="title_advanced_auto_list">Crea automaticamente liste</string>
|
||||
<string name="title_advanced_prefix_once">Prefissa l\'oggetto solo una volta per rispondere o inoltrare</string>
|
||||
<string name="title_advanced_extended_reply">Usa intestazione estesa di risposta/inoltro</string>
|
||||
<string name="title_advanced_quote_reply">Cita il testo nella risposta</string>
|
||||
|
|
@ -581,6 +580,7 @@
|
|||
<string name="title_oauth_support">OAuth non è supportato</string>
|
||||
<string name="title_review">Revisione</string>
|
||||
<string name="title_hint_alias">Premi a lungo per le opzioni, come copia per creare le identità alias</string>
|
||||
<string name="title_service_auth">Il server di posta elettronica ha detto: %1$s</string>
|
||||
<string name="title_service_vpn">Questo potrebbe essere causato dalla VPN in uso</string>
|
||||
<string name="title_service_port">Per favore ricontrolla il numero della porta</string>
|
||||
<string name="title_service_protocol">Si prega di controllare di nuovo il protocollo (SSL/TLS o STARTTLS)</string>
|
||||
|
|
@ -764,6 +764,7 @@
|
|||
<string name="title_third_party">Stai usando una versione di terze parti</string>
|
||||
<string name="title_expand_warning">Espandendo questo messaggio verrà scaricato %1$s</string>
|
||||
<string name="title_download_message">Download …</string>
|
||||
<string name="title_reformatted">Questa è la vista dei messaggi riformattati. Puoi toccare l\'icona ⛶ per visualizzare il messaggio originale e nascondere questo messaggio.</string>
|
||||
<string name="title_compose">Scrivi</string>
|
||||
<string name="title_submitter">Inviato da:</string>
|
||||
<string name="title_delivered_to">Consegnato a:</string>
|
||||
|
|
@ -799,6 +800,9 @@
|
|||
<string name="title_style_size_medium">Medio</string>
|
||||
<string name="title_style_size_large">Grande</string>
|
||||
<string name="title_style_color">Colore …</string>
|
||||
<string name="title_style_list">Lista</string>
|
||||
<string name="title_style_list_bullets">Punti</string>
|
||||
<string name="title_style_list_numbered">Numerata</string>
|
||||
<string name="title_style_font">Tipo di carattere</string>
|
||||
<string name="title_style_font_default">Predefinito</string>
|
||||
<string name="title_style_clear">Cancella formattazione</string>
|
||||
|
|
|
|||
|
|
@ -245,7 +245,6 @@
|
|||
<string name="title_advanced_suggest_received">Suggereer adressen gevonden in ontvangen berichten</string>
|
||||
<string name="title_advanced_suggest_frequently">Sorteer voorgestelde adressen op gebruiksfrequentie</string>
|
||||
<string name="title_advanced_compose_font">Standaard lettertype</string>
|
||||
<string name="title_advanced_auto_list">Automatisch lijsten aanmaken</string>
|
||||
<string name="title_advanced_prefix_once">Prefix onderwerp slechts één keer bij beantwoorden of doorsturen</string>
|
||||
<string name="title_advanced_extended_reply">Gebruik uitgebreide kop bij antwoorden/doorsturen</string>
|
||||
<string name="title_advanced_quote_reply">Haal beantwoorde tekst aan</string>
|
||||
|
|
@ -764,6 +763,7 @@
|
|||
<string name="title_third_party">U gebruikt een versie van een derde partij</string>
|
||||
<string name="title_expand_warning">Uitvouwen van dit bericht zal %1$s downloaden</string>
|
||||
<string name="title_download_message">Downloaden …</string>
|
||||
<string name="title_reformatted">Dit is de opnieuw opgemaakte berichtweergave. U kunt op het pictogram ⛶ klikken om het originele bericht te bekijken en dit bericht te verbergen.</string>
|
||||
<string name="title_compose">Opstellen</string>
|
||||
<string name="title_submitter">Verstuurd door:</string>
|
||||
<string name="title_delivered_to">Afgeleverd aan:</string>
|
||||
|
|
@ -799,9 +799,9 @@
|
|||
<string name="title_style_size_medium">Middelgroot</string>
|
||||
<string name="title_style_size_large">Groot</string>
|
||||
<string name="title_style_color">Kleur …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Lijst</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Opsommingstekens</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Nummers</string>
|
||||
<string name="title_style_list">Lijst</string>
|
||||
<string name="title_style_list_bullets">Opsommingstekens</string>
|
||||
<string name="title_style_list_numbered">Nummers</string>
|
||||
<string name="title_style_font">Lettertype</string>
|
||||
<string name="title_style_font_default">Standaard</string>
|
||||
<string name="title_style_clear">Opmaak wissen</string>
|
||||
|
|
|
|||
|
|
@ -267,7 +267,6 @@
|
|||
<string name="title_advanced_suggest_received">Proponuj adresy znalezione w otrzymanych wiadomościach</string>
|
||||
<string name="title_advanced_suggest_frequently">Sortuj sugerowane adresy według częstotliwości używania</string>
|
||||
<string name="title_advanced_compose_font">Domyślna czcionka</string>
|
||||
<string name="title_advanced_auto_list">Automatycznie twórz listy</string>
|
||||
<string name="title_advanced_prefix_once">Prefiksuj temat tylko raz przy odpowiedzi lub przesyłaniu dalej</string>
|
||||
<string name="title_advanced_extended_reply">Użyj rozszerzonego nagłówka odpowiedzi/przesyłania dalej</string>
|
||||
<string name="title_advanced_quote_reply">Cytuj treść w odpowiedzi</string>
|
||||
|
|
@ -821,9 +820,9 @@
|
|||
<string name="title_style_size_medium">Średni</string>
|
||||
<string name="title_style_size_large">Duży</string>
|
||||
<string name="title_style_color">Kolor …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Lista</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Wypunktowania</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Numerowane</string>
|
||||
<string name="title_style_list">Lista</string>
|
||||
<string name="title_style_list_bullets">Wypunktowania</string>
|
||||
<string name="title_style_list_numbered">Numerowane</string>
|
||||
<string name="title_style_font">Czcionka</string>
|
||||
<string name="title_style_font_default">Domyślny</string>
|
||||
<string name="title_style_clear">Wyczyść formatowanie</string>
|
||||
|
|
|
|||
|
|
@ -246,7 +246,6 @@
|
|||
<string name="title_advanced_suggest_received">Sugerir endereços encontrados em mensagens recebidas</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordenar endereços sugeridos de acordo com a frequência de uso</string>
|
||||
<string name="title_advanced_compose_font">Fonte padrão</string>
|
||||
<string name="title_advanced_auto_list">Criar listas automaticamente</string>
|
||||
<string name="title_advanced_prefix_once">Prefixo de assunto apenas uma vez na resposta ou encaminhamento</string>
|
||||
<string name="title_advanced_extended_reply">Usar cabeçalho de resposta/encaminhamento estendido</string>
|
||||
<string name="title_advanced_quote_reply">Citar texto respondido</string>
|
||||
|
|
|
|||
|
|
@ -233,7 +233,6 @@
|
|||
<string name="title_advanced_suggest_sent">Sugerir endereços encontrados nas mensagens enviadas</string>
|
||||
<string name="title_advanced_suggest_received">Sugerir endereços encontrados nas mensagens enviadas</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordenar endereços sugeridos por frequência de uso</string>
|
||||
<string name="title_advanced_auto_list">Criar listas automaticamente</string>
|
||||
<string name="title_advanced_prefix_once">Prefixo do assunto único ao responder ou encaminhar</string>
|
||||
<string name="title_advanced_extended_reply">Usar cabeçalho de resposta/encaminhamento extendido</string>
|
||||
<string name="title_advanced_quote_reply">Citar texto respondido</string>
|
||||
|
|
|
|||
|
|
@ -256,7 +256,6 @@
|
|||
<string name="title_advanced_suggest_received">Sugerează adrese găsite în mesajele primite</string>
|
||||
<string name="title_advanced_suggest_frequently">Sortați adresele sugerate în funcție de frecvența de utilizare</string>
|
||||
<string name="title_advanced_compose_font">Font prestabilit</string>
|
||||
<string name="title_advanced_auto_list">Creează automat liste</string>
|
||||
<string name="title_advanced_prefix_once">Adaugă prefix la subiect o singură dată pentru răspuns sau redirecționare</string>
|
||||
<string name="title_advanced_extended_reply">Folosește antetul extins pentru răspuns/redirecționare</string>
|
||||
<string name="title_advanced_quote_reply">Citează textul la care răspunzi</string>
|
||||
|
|
@ -810,9 +809,9 @@
|
|||
<string name="title_style_size_medium">Mediu</string>
|
||||
<string name="title_style_size_large">Mare</string>
|
||||
<string name="title_style_color">Culoare …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Listă</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Buline</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Numere</string>
|
||||
<string name="title_style_list">Listă</string>
|
||||
<string name="title_style_list_bullets">Buline</string>
|
||||
<string name="title_style_list_numbered">Numere</string>
|
||||
<string name="title_style_font">Font</string>
|
||||
<string name="title_style_font_default">Implicit</string>
|
||||
<string name="title_style_clear">Elimină toate formatările</string>
|
||||
|
|
|
|||
|
|
@ -268,7 +268,6 @@
|
|||
<string name="title_advanced_suggest_received">Предлагать адреса, найденные в полученных сообщениях</string>
|
||||
<string name="title_advanced_suggest_frequently">Сортировать предложенные адреса по частоте использования</string>
|
||||
<string name="title_advanced_compose_font">Шрифт по умолчанию</string>
|
||||
<string name="title_advanced_auto_list">Автоматическое создание списков</string>
|
||||
<string name="title_advanced_prefix_once">Добавлять только один префикс перед темой при ответе или пересылке</string>
|
||||
<string name="title_advanced_extended_reply">Использовать расширенный заголовок для ответа/пересылки</string>
|
||||
<string name="title_advanced_quote_reply">Цитировать текст при ответе</string>
|
||||
|
|
@ -787,6 +786,7 @@
|
|||
<string name="title_third_party">Вы используете стороннюю версию</string>
|
||||
<string name="title_expand_warning">При развёртывании этого сообщения будет загружено %1$s</string>
|
||||
<string name="title_download_message">Загрузка…</string>
|
||||
<string name="title_reformatted">Это переформатированное сообщение. Вы можете нажать на значок ⛶ для просмотра оригинального сообщения и скрытия этого сообщения.</string>
|
||||
<string name="title_compose">Создать</string>
|
||||
<string name="title_submitter">Отправлено:</string>
|
||||
<string name="title_delivered_to">Доставлено:</string>
|
||||
|
|
@ -822,9 +822,9 @@
|
|||
<string name="title_style_size_medium">Средний</string>
|
||||
<string name="title_style_size_large">Большой</string>
|
||||
<string name="title_style_color">Цвет…</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Список</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Маркированный список</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Нумерованный</string>
|
||||
<string name="title_style_list">Список</string>
|
||||
<string name="title_style_list_bullets">Маркированный</string>
|
||||
<string name="title_style_list_numbered">Нумерованный</string>
|
||||
<string name="title_style_font">Шрифт</string>
|
||||
<string name="title_style_font_default">По умолчанию</string>
|
||||
<string name="title_style_clear">Очистить форматирование</string>
|
||||
|
|
|
|||
|
|
@ -199,7 +199,6 @@
|
|||
<string name="title_advanced_suggest_sent">Navrhovať adresy nájdené v odoslaných správach</string>
|
||||
<string name="title_advanced_suggest_received">Navrhovať adresy nájdené v prijatých správach</string>
|
||||
<string name="title_advanced_suggest_frequently">Radiť navrhované správy podľa počtu použití</string>
|
||||
<string name="title_advanced_auto_list">Automaticky vytvárať zoznamy</string>
|
||||
<string name="title_advanced_prefix_once">Pri odpovedaní alebo preposielaní pridať do predmetu len jednu predponu</string>
|
||||
<string name="title_advanced_extended_reply">Používať rozšírenú hlavičku odpovede/preposlania</string>
|
||||
<string name="title_advanced_quote_reply">Citovať text odpovede</string>
|
||||
|
|
|
|||
|
|
@ -245,7 +245,6 @@
|
|||
<string name="title_advanced_suggest_received">Föreslå adresser som finns i mottagna meddelanden</string>
|
||||
<string name="title_advanced_suggest_frequently">Sortera föreslagna adresser vid användningsfrekvens</string>
|
||||
<string name="title_advanced_compose_font">Standardtypsnitt</string>
|
||||
<string name="title_advanced_auto_list">Skapa automatiskt listor</string>
|
||||
<string name="title_advanced_prefix_once">Prefix i ämnet endast när du svarar eller vidarebefordrar</string>
|
||||
<string name="title_advanced_extended_reply">Använd förlängd svars-/framåtriktad sidhuvud</string>
|
||||
<string name="title_advanced_quote_reply">Citera svarstext</string>
|
||||
|
|
@ -764,6 +763,7 @@
|
|||
<string name="title_third_party">Du använder en version av en tredje part</string>
|
||||
<string name="title_expand_warning">Utvidgningen av detta meddelande kommer att ladda ned %1$s</string>
|
||||
<string name="title_download_message">Hämtar …</string>
|
||||
<string name="title_reformatted">Detta är den formaterade meddelandevyn. Du kan trycka på ⛶ ikonen för att visa det ursprungliga meddelandet och för att dölja detta meddelande.</string>
|
||||
<string name="title_compose">Skriv</string>
|
||||
<string name="title_submitter">Skickad av:</string>
|
||||
<string name="title_delivered_to">Levererad till:</string>
|
||||
|
|
@ -799,9 +799,9 @@
|
|||
<string name="title_style_size_medium">Medel</string>
|
||||
<string name="title_style_size_large">Stor</string>
|
||||
<string name="title_style_color">Färg …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">Lista</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">Punkter</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">Numrerad</string>
|
||||
<string name="title_style_list">Lista</string>
|
||||
<string name="title_style_list_bullets">Punkter</string>
|
||||
<string name="title_style_list_numbered">Numrerad</string>
|
||||
<string name="title_style_font">Typsnitt</string>
|
||||
<string name="title_style_font_default">Standard</string>
|
||||
<string name="title_style_clear">Rensa formatering</string>
|
||||
|
|
|
|||
|
|
@ -234,7 +234,6 @@
|
|||
<string name="title_advanced_suggest_received">建议在已收到消息中找到的地址</string>
|
||||
<string name="title_advanced_suggest_frequently">按使用频率来排序建议地址</string>
|
||||
<string name="title_advanced_compose_font">默认字体</string>
|
||||
<string name="title_advanced_auto_list">自动创建列表</string>
|
||||
<string name="title_advanced_prefix_once">答复或抄送邮件时, 主题前的Re或CC只出现一次</string>
|
||||
<string name="title_advanced_extended_reply">使用扩展回复/转发头</string>
|
||||
<string name="title_advanced_quote_reply">引用回复文本</string>
|
||||
|
|
@ -753,6 +752,7 @@
|
|||
<string name="title_third_party">您使用的是第三方版本</string>
|
||||
<string name="title_expand_warning">展开此消息将下载 %1$s</string>
|
||||
<string name="title_download_message">… 下载中</string>
|
||||
<string name="title_reformatted">这是更改格式后的消息视图。你可以按⛶ 图标来查看原始消息并隐藏此消息。</string>
|
||||
<string name="title_compose">撰写</string>
|
||||
<string name="title_submitter">发送自：</string>
|
||||
<string name="title_delivered_to">发送给：</string>
|
||||
|
|
@ -788,9 +788,9 @@
|
|||
<string name="title_style_size_medium">中等</string>
|
||||
<string name="title_style_size_large">大</string>
|
||||
<string name="title_style_color">颜色 …</string>
|
||||
<string name="title_style_list" comment="title_style_list Create list in message composer ">列表</string>
|
||||
<string name="title_style_list_bullets" comment="title_style_list_bullets Create bulleted list in message composer ">项目符号</string>
|
||||
<string name="title_style_list_numbered" comment="title_style_list_numbered Create numbered list in message composer ">有编号的</string>
|
||||
<string name="title_style_list">列表</string>
|
||||
<string name="title_style_list_bullets">项目符号</string>
|
||||
<string name="title_style_list_numbered">有编号的</string>
|
||||
<string name="title_style_font">字体</string>
|
||||
<string name="title_style_font_default">默认</string>
|
||||
<string name="title_style_clear">清除格式</string>
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ Der er generelle såvel som specifikke fejl for Gmail-konti (se nedenfor).
|
|||
|
||||
**Generelle fejl**
|
||||
|
||||
Fejlen *... Godkendelse mislykkedes ...* eller *... GODKENDELSE mislykkedes ...* skyldes sandsynligvis forkert brugernavn/adgangskode. Viss udbydere forventer som brugernavn blot *brugernavn* og andre din fulde e-mail *brugernavn@eksempel.dk*. Benyttes kopiér/indsæt til angivelse af brugernavn/adgangskode kan der muligvis medtages usynlige tegn, hvilket også kan forårsage denne fejl. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
Fejlen *... Godkendelse mislykkedes ...* eller *... GODKENDELSE mislykkedes ...* skyldes sandsynligvis forkert brugernavn/adgangskode. Viss udbydere forventer som brugernavn blot *brugernavn* og andre din fulde e-mail *brugernavn@eksempel.dk*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -73,33 +73,33 @@
|
|||
* Ошибка в Nova Launcher на Android 5.x вызывает сбой FairEmail с *java.lang.StackOverflowError*, когда Nova Launcher имеет доступ к службе специальных возможностей.
|
||||
* ~~Выбор папки иногда не показывает папок по неизвестным причинам. Похоже, это исправлено.~~
|
||||
* ~~ [ошибка в AndroidX](https://issuetracker.google.com/issues/64729576) затрудняет захват быстрой прокрутки. Обходное решение было добавлено.~~
|
||||
* ~~~Шифрование с помощью YubiKey приводит к бесконечному циклу. Похоже, что это вызвано ошибкой [в OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
|
||||
* ~~Шифрование с помощью YubiKey приводит к бесконечному циклу. Похоже, что это вызвано ошибкой [в OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
|
||||
* Прокрутка к внутренне привязанному местоположению в оригинальных сообщениях не работает. Это не может быть исправлено, потому что исходный вид сообщения содержится в прокрутке.
|
||||
* Предпросмотр текста сообщения (всегда) не отображается на Samsung watch, потому что [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)), похоже, игнорируется. Известно, что текст предварительного просмотра сообщений правильно отображаются на экране Pebble 2, Fitbit Charge 3 и Mi band 3. См. также [этот FAQ](#user-content-faq126).
|
||||
|
||||
## Запланированные возможности
|
||||
|
||||
* ~~Синхронизировать по требованию (вручную)~~
|
||||
* ~~~Полуавтоматическое шифрование~~
|
||||
* ~~Полуавтоматическое шифрование~~
|
||||
* ~~Копировать сообщение~~
|
||||
* ~~~Цветные звезды~~
|
||||
* ~~~Настройки уведомлений для папок~~
|
||||
* ~~Цветные звезды~~
|
||||
* ~~Настройки уведомлений для папок~~
|
||||
* ~~Выбрать локальные изображения для подписей~~ (это не будет добавлено, потому что требуется управление файлами изображений и потому что изображения не отображаются по умолчанию в большинстве почтовых клиентов в любом случае)
|
||||
* ~~Показать сообщения, соответствующие правилу~~
|
||||
* ~~[ManageSieve](https://tools.ietf.org/html/rfc5804)~~ (нет поддерживаемых библиотек Java с соответствующей лицензией и без зависимостей, кроме того, у FairEmail есть свои собственные правила фильтрайии)
|
||||
* ~~~Поиск сообщений с / без вложений~~ (это нельзя добавить, потому что IMAP не поддерживает поиск вложений)
|
||||
* ~~~Поиск папки~~ (фильтрация списка иерархических папок проблематична)
|
||||
* ~~Поиск сообщений с/без вложений~~ (это нельзя добавить, потому что IMAP не поддерживает поиск вложений)
|
||||
* ~~Поиск папки~~ (фильтрация списка иерархических папок проблематична)
|
||||
* ~~Подсказки поиска~~
|
||||
* ~~[Настройка Автоматического Шифрования Сообщения](https://autocrypt.org/autocrypt-spec-1.0.0.pdf) (раздел 4.4)~~ (IMO нецелесообразно позволять почтовому клиенту обрабатывать такие чувствительные данные, как ключи шифрования, в то время как OpenKeychain тоже может экспортировать ключи)
|
||||
* ~~Унифицированные папки~~
|
||||
* ~~Новое уведомление для каждого аккаунта~~ (реализовано путем добавления условий времени в правила, чтобы сообщения могли быть отложены в выбранные периоды)
|
||||
* ~~Копировать учетные записи и идентификаторы~~
|
||||
* ~~Pinch zoom~~ (невозможно надежно использовать в прокручиваемом списке; вместо этого можно масштабировать всё сообщение)
|
||||
* ~~~Более компактный вид папок~~
|
||||
* ~~~Создавать списки и таблицы~~ (требуется rich text редактор, смотрите [этот FAQ](#user-content-faq99))
|
||||
* ~~Pinch zoom text size~~
|
||||
* ~~Display GIFs~~
|
||||
* ~~Themes~~ (a grey light and dark theme were added because this is what most people seems to want)
|
||||
* ~~Более компактный вид папок~~
|
||||
* ~~Создавать списки и таблицы~~ (требуется rich text редактор, смотрите [этот FAQ](#user-content-faq99))
|
||||
* ~~Масштабирование текста щипком~~
|
||||
* ~~Отображать GIFы-~~
|
||||
* ~~Темы~~ (светлая и темная серые темы добавлены, потому что, похоже, большинство людей этого хотят)
|
||||
* ~~Any day time condition~~ (any day doesn't really fit into the from/to date/time condition)
|
||||
* ~~Send as attachment~~
|
||||
* ~~Widget for selected account~~
|
||||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -812,7 +812,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When using copy/paste to enter a username or password, invisible characters might be copied, which could cause this problem as well. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to logging from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -1856,7 +1856,11 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
|
||||
|
||||
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue