<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Statusrapport</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Statusbericht</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Statusbericht</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Statusbericht</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Αναφορά κατάστασης</string>
<stringname="title_reply_template">Responder con plantilla</string>
<stringname="title_move_undo">Moviendo a %1$s (%2$d)</string>
<stringname="title_open_with">Abrir con</string>
@ -905,7 +905,7 @@
<stringname="title_key_missing">No hay clave para %1$s</string>
<stringname="title_send_reminder_remark">Los recordatorios pueden ser activados de nuevo en la configuración de envío</string>
<stringname="title_send_plain_text">Sólo en texto plano</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Informe de estado</string>
<stringname="title_send_dsn">Informe de estado</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Rapport d\'état</string>
<stringname="title_attachment_keywords">joint,jointe,joints,jointes,ci-joint,ci-jointe,ci-joints,ci-jointes,attaché,attachés,attachée,attachées,lettre de motivation,cv</string>
<stringname="title_attachment_reminder">Aviez-vous l’intention d’ajouter une pièce jointe?</string>
<stringname="title_plain_reminder">Tout le formatage sera supprimé</string>
<stringname="title_dsn_reminder">Les refus permanents nuisent à la réputation de l\'adresse courriel de l\'expéditeur initial !</string>
<stringname="title_size_reminder">Message (%1$s) plus grand que la limite du serveur (%2$s)</string>
<stringname="title_attachments_missing">Les pièces jointes ne sont pas toutes téléchargées</string>
<stringname="title_dialog_hint">Cette boîte de dialogue peut être réactivée via le menu à trois points de la barre d’action supérieure</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Rapport d\'état</string>
<stringname="title_attachment_keywords">joint,jointe,joints,jointes,ci-joint,ci-jointe,ci-joints,ci-jointes,attaché,attachés,attachée,attachées,lettre de motivation,cv</string>
<stringname="title_attachment_reminder">Aviez-vous l’intention d’ajouter une pièce jointe?</string>
<stringname="title_plain_reminder">Tout le formatage sera supprimé</string>
<stringname="title_dsn_reminder">Les refus permanents nuisent à la réputation de l\'adresse e-mail de l\'expéditeur initial !</string>
<stringname="title_size_reminder">Message (%1$s) plus grand que la limite du serveur (%2$s)</string>
<stringname="title_attachments_missing">Les pièces jointes n’ont pas toutes été téléchargées</string>
<stringname="title_dialog_hint">Cette boîte de dialogue peut être réactivée via le menu à trois points de la barre d’action supérieure</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Report di stato</string>
<stringname="title_send_dsn">Report di stato</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Statusrapport</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Raport o stanie</string>
<stringname="title_send_dsn">Raport o stanie</string>
<stringname="title_send_receipt">Poproś o potwierdzenie</string>
<stringname="title_send_receipt_remark">Większość dostawców i klientów e-mail ignoruje prośby o potwierdzenie</string>
<stringname="app_welcome">FairEmail este o aplicație pentru e-mail, cu sursă deschisă, ce se concentrează pe confidențialitate și securitate. Din acest motiv se poate ca unele caracteristici să funcționeze diferit de cum erați obișnuiți.</string>
<stringname="app_limitations">De exemplu, mesajele sunt reformatate în mod implicit pentru a elimina elemente nesigure și pentru a îmbunătăți lizibilitatea, iar deschiderea de adrese trebuie confirmată pentru siguranță. Ambele pot fi dezactivate dacă nu se doreşte asta.</string>
<stringname="app_crash">FairEmail nu suportă acest dispozitiv din cauza erorilor din Android ce duc la blocaje</string>
<stringname="app_exit">Apăsați din nou \'Înapoi\' pentru a ieși</string>
<stringname="app_cake">Spațiu de stocare insuficient rămas</string>
<stringname="title_ask_discard">Renunțați la ciornă?</string>
<stringname="title_ask_show_html">Vizualizarea mesajului original poate duce la divulgarea de informații confidențiale</string>
<stringname="title_ask_show_html_dark">Folosește tema întunecată</string>
<stringname="title_ask_show_html_remark">Afișarea mesajului original pe un fundal închis nu este posibilă pentru că imaginile și textul închise la culoare ar putea sa nu se vadă</string>
<stringname="title_ask_show_html_images">Arată mereu imaginile când se arată mesajele originale</string>
<stringname="title_ask_show_image">Vizualizarea imaginilor poate duce la divulgarea de informații confidențiale</string>
@ -913,6 +916,7 @@
<stringname="title_key_missing">Nici o cheie pentru %1$s</string>
<stringname="title_send_reminder_remark">Memento-urile pot fi activate din nou în setările de trimitere</string>
<stringname="title_send_plain_text">Doar text simplu</string>
<stringname="title_send_dsn">Raport de stare</string>
<stringname="title_reply_template">Ответить с шаблоном</string>
<stringname="title_move_undo">Перемещение в %1$s (%2$d)</string>
<stringname="title_open_with">Открыть с помощью</string>
@ -927,7 +927,7 @@
<stringname="title_key_missing">Нет ключа для %1$s</string>
<stringname="title_send_reminder_remark">Напоминания можно повторно включить в настройках отправки</string>
<stringname="title_send_plain_text">Только простой текст</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Отчёт о состоянии</string>
<stringname="title_send_dsn">Отчёт о состоянии</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">Звіти про стан</string>
<stringname="title_send_dsn">Звіти про стан</string>
<stringname="title_send_dsn"comment="title_send_dsn Title for delivery/disposition notifications (receipts and 'address unknown' messages)">状态报告</string>
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,9 +467,15 @@ Bruges Play Butik- eller GitHub-versionen af FairEmail, kan hurtigopsætningsgui
Vil du ikke benytte en Gmail-konto på enheden, kan du enten aktivere adgang for "mindre sikre apps" og benytte din kontoadgangskode (ikke anbefalet) eller aktivere tofaktorgodkendelse og benytte en app-specifik adgangskode. For brug af en adgangskode skal der opsættes en konto og identitet via den manuelle opsætning i stedet for hurtigopsætningsguiden.
Tjek [denne FAQ](#user-content-faq111) vedr., hvorfor kun konti på enheden kan benyttes.
**Vigtigt**: Google udsender af og til denne advarsel:
Bemærk, en app-specifik adgangskode kræves, når tofaktorgodkendelse er aktiveret.
*[ALERT] Log ind via din webbrowser: https://support.google.com/mail/accounts/answer/78754 (Fejlet)*
Dette sikkerhedstjek fra Google udløses oftere med *mindre sikre apps* aktiveret, mindre med en app-adgangskode og næsten aldrig ved brug af en konto på enheden (OAuth).
Tjek, hvorfor kun konti på enheden kan benyttes i [denne FAQ](#user-content-faq111).
Bemærk, at en app-specifik adgangskode kræves, når tofaktorgodkendelse er aktiveret.
<br/>
@ -481,49 +487,49 @@ Tjek [hér](https://support.google.com/accounts/answer/185833), hvordan en app-s
*Aktivér "Mindre sikre apps"*
**Vigtigt**: Brug af denne metode anbefales ikke grundet mindre pålidelighed.
**Vigtigt**: Brug af denne metode anbefales ikke, da den er mindre pålidelig.
**Vigtigt**: Brugernavn/adgangskode godkendte G Suite-konti vil [i nærmeste fremtid](https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html) ophøre med at fungere.
Tjek [hér](https://support.google.com/accounts/answer/6010255), hvordan "mindre sikre apps"aktiveres eller gå [direkte til indstillingerne](https://www.google.com/settings/security/lesssecureapps).
Tjek [hér](https://support.google.com/accounts/answer/6010255), hvordan "Mindre sikre apps" aktiveres eller gå [direkte til Indstillinger](https://www.google.com/settings/security/lesssecureapps).
Benyttes flere Gmail-konti, skal indstillingen "mindre sikre apps" ændres på alle relevante konti.
Benyttes flere Gmail-konti, så sørg for at ændre indstillingen "Mindre sikre apps" for enhver relevant konto.
Bemærk, at "mindre sikre apps"-indstillingsskærmen skal forlades vha. Tilbage-pilen, for at indstillingen effektueres.
Bemærk, at man for at effektuere indstillingen er nødt til at forlade "Mindre sikre apps"-indstillingsskærmen via Tilbage-pilen.
Benyttes denne metode, bør der anvendes en [stærk adgangskode](https://en.wikipedia.org/wiki/Password_strength) til Gmail-kontoen (i øvrigt altid er en god idé). Bemærk, at brug af [standard](https://tools.ietf.org/html/rfc3501) IMAP-protokollen ikke i sig selv er mindre sikker.
Benyttes denne metode, bør en [stærk adgangskode](https://en.wikipedia.org/wiki/Password_strength) anvendes til Gmail-kontoen (hvilket altid er en god idé). Bemærk, brug af [standard](https://tools.ietf.org/html/rfc3501) IMAP-protokollen er ikke i sig selv er mindre sikker.
Når "mindre sikre apps" ikke er aktiveret, ses fejlen *Godkendelse mislykkedes - ugyldige akkreditiver* for konti (IMAP) og *Brugernavn og adgangskode ikke accepteret* for identiteter (SMTP).
Når "Mindre sikre apps" ikke er aktiveret, ses fejlen *Godkendelse mislykkedes - ugyldige akkreditiver* for konti (IMAP) og *Brugernavn og adgangskode ikke accepteret* for identiteter (SMTP).
<br/>
*Generelt*
Advarslen "*Log ind via din webbrowser*" vises muligvis. Dette sker, når Google anser det netværk, hvormed der forbindes til Internet (hvilket kan være et VPN), som ikke-sikkert. Dette kan forhindres vha. Gmails hurtigopsætningsguide eller en app-specifik adgangskode.
Muligvis vises advarslen "*Log ind via din webbrowser*". Dette sker, når Google anser netværket, der forbinder til Internet (hvilket kan være et VPN), som ikke-sikkert. Dette kan forhindres vha. Gmails hurtigopsætningsguide eller en app-specifik adgangskode.
Tjek [hér](https://support.google.com/mail/answer/7126229) for Googles vejledning, og [hér](https://support.google.com/mail/accounts/answer/78754) for fejlfinding.
Tjek [hér](https://support.google.com/mail/answer/7126229) for Googles instruktioner, og [hér](https://support.google.com/mail/accounts/answer/78754) for fejlfinding.
<br/>
<aname="faq7"></a>
**(7) Hvorfor vises sendte beskeder ikke (direkte) i Sendt-mappen?**
Sendte beskeder flyttes normalt fra udbakken til Sendt-mappen, så snart disse af udbyderen er tilføjet Sendt-mappen. Dette kræver valg af en Sendt-mappe i kontoindstillingerne, samt at mappen er opsættes til synk.
Sendte beskeder flyttes normalt fra udbakken til Sendt-mappen, så snart udbyderen føjer sendte beskeder til Sendt-mappen. Dette kræver, at en Sendt-mappe vælges i kontoindstillingerne, og at Sendt-mappen ligeledes opsættes til synk.
Visse udbydere holder ikke styr på sendte beskeder, eller den anvendte SMTP-server er muligvis ikke relateret til udbyderen. I så tilfælde føjer FairEmail automatisk sendte beskeder til Sendt-mappen under synk af denne, hvilket vil ske, efter at en besked er afsendt. Bemærk, at dette vil forøge Internettrafikken.
~~Sker dette ikke, holder udbyderen muligvis ikke styr på sendte beskeder, eller den anvendte SMTP-server er muligvis ikke udbyderrelateret.~~ ~~I så tilfælde kan den avancerede identitetsindstilling *Gem sendte beskeder* aktiveres for at lade FairEmail føje sendte beskeder til Sendt-mappen umiddelbart efter afsendelsen.~~ ~~Bemærk, at aktivering af indstillingen kan resultere i dubletbeskeder, hvis udbyderen føjer sendte beskeder til Sendt-mappen.~~ ~~Bemærk også, at aktivering af indstillingen vil resultere i forøget dataforbrug især ved afsendelse af beskeder med store vedhæftninger.~~
~~Sker dette ikke, holder udbyderen muligvis ikke styr på sendte beskeder, eller der anvendes muligvis en ikke-udbyderrelateret SMTP-server.~~ ~~I så tilfælde kan man aktivere den avancerede identitetsindstilling *Gem sendte beskeder* for at lade FairEmail føje sendte beskeder til Sendt-mappen umiddelbart efter beskedafsendelsen.~~ ~~Bemærk, at aktivering af denne indstilling kan resultere i dubletbeskeder, hvis udbyderen også føjer sendte beskeder til Sendt-mappen.~~ ~~Bemærk også, at aktivering af indstillingen vil betyde forøget datatrafik, især når der sendes beskeder med store vedhæftninger.~~
~~Hvis afsendte beskeder i udbakken ikke findes i Sendt-mappen ved en fuld synk, flytes disse også fra udbakken til Sendt-mappen.~~ ~~En fuld synk sker, når der genforbindes til serveren, eller ved periodisk/manuel synk.~~ ~~ Det vil sandsynligvis være ønskeligt i stedet at aktivere den avancerede indstilling *Gem sendte beskeder* for hurtigere at flytte beskeder til Sendt-mappen.~~
~~Hvis afsendte beskeder i udbakken ikke findes i Sendt-mappen ved en fuld synk, flytes disse også fra udbakken til Sendt-mappen.~~ ~~En fuld synkning sker, når der genforbindes til serveren, eller ved periodisk eller manuel synkning.~~ ~~I stedet er ønsket sandsynligvis at aktivere den avancerede indstilling *Gem sendte beskeder* for hurtigere at flytte beskeder til Sendt-mappen.~~
<br/>
<aname="faq8"></a>
**(8) Kan en Microsoft Exchange-konto benyttes?**
En Microsoft Exchange-konto kan benyttes, såfremt den er tilgængelig via IMAP, hvilket plejer at være tilfældet. Tjek [hér](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for yderligere oplysninger.
En Microsoft Exchange-konto kan benyttes, såfremt den er tilgængelig via IMAP (er normalt tilfældet). Tjek [hér](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for yderligere information.
Tjek [hér](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for Microsoft-dokumentation vedr. opsætning af e-mailklient. Der er også et afsnit om almindelige forbindelsesfejl og løsninger.
Tjek [hér](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for Microsoft-dokumentation vedr. opsætning af e-mailklient. Der er også et afsnit om almindelige forbindelsesfejl og løsninger.
Visse ældre Exchange-serverversioner har en fejl, der forårsager tomme beskeder og ødelagte vedhæftninger. Tjek [denne FAQ](#user-content-faq110) for en løsning.
Identiteter repræsenterer e-mailadresser, der sendes *fra* via en e-mailserver (SMTP).
Visse udbydere tillader brug af flere aliaser. Disse kan opsættes ved at indstille e-mailadressefeltet fra en ekstra identitet til aliasadressen og indstille brugernavnefeltet til hoved e-mailadressen.
Visse udbydere tillader brug af flere aliaser. Disse kan opsættes ved at angive e-mailadressefeltet fra en ekstra identitet som aliasadressen og angive brugernavnefeltet til hoved e-mailadresse.
Bemærk, at en identitet kan kopieres vha. et langt tryk på den.
Alternativt kan *Tillad redigering af afsenderadresse* aktiveres under Avancerede indstillinger for en eksisterende identitet mhp. at redigere brugernavnet ved beskedoprettelsen, såfremt udbyderen tillader dette.
Såfremt udbyderen tillader dette, kan *Tillad redigering af afsenderadresse* alternativt aktiveres under Avancerede indstillinger for en eksisterende identitet for at redigere brugernavnet ved beskedoprettelsen.
FairEmail opdaterer automatisk adgangskoder til relaterede identiteter, når adgangskoden til den tilknyttede konto/relaterede identitet opdateres.
FairEmail opdaterer automatisk adgangskoder til relaterede identiteter, når adgangskoden til den tilknyttede konto/relateret identitet opdateres.
Tjek [denne FAQ](#user-content-faq33) om redigering af brugernavnet til e-mailadresser.
@ -553,20 +559,20 @@ Tjek [denne FAQ](#user-content-faq33) om redigering af brugernavnet til e-mailad
<aname="faq10"></a>
**~~(10) Hvad betyder 'UIDPLUS ikke understøttet'?~~**
~~Fejlmeddelelsen *UIDPLUS ikke understøttet* betyder, at e-mailudbyderen ikke tilbyder IMAP-udvidelsen [UIDPLUS](https://tools.ietf.org/html/rfc4315). Denne IMAP-udvidelse kræves for at implementere tovejs-synk, der ikke er en valgfri funktion. Medmindre udbyderen kan aktivere denne udvidelse, kan FairEmail ikke benyttes med udbyderen.~~
~~Fejlmeddelelsen *UIDPLUS ikke understøttet* betyder, at e-mailudbyderen ikke tilbyder IMAP-udvidelsen [UIDPLUS](https://tools.ietf.org/html/rfc4315). Denne IMAP-udvidelse kræves for at implementere tovejssynk, hvilket ikke er en valgfri funktion. Kan udbyderen ikke aktivere denne udvidelse, er FairEmail ikke kompatibel med udbyderen.~~
<br/>
<aname="faq11"></a>
**~~(11) Hvorfor er POP uunderstøttet?~~**
~~Udover at enhver anstændig e-mail-udbyder i dag understøtter [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol),~~ ~~vil brug af [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol) resultere i unødvendig ekstra strømforbrug samt forsinkede notifikationer om nye beskeder.~~ ~~Desuden er POP uegnet til tovejssynk, og oftere end ikke, læser og skriver folk beskeder på forskellige enheder i dag.~~
~~Udover at enhver anstændig e-mailudbyder i dag understøtter [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol),~~ ~~vil brug af [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol) resultere i unødvendig ekstra strømforbrug samt forsinkede notifikationer om nye beskeder.~~ ~~Desuden er POP uegnet til tovejssynk, og oftere end ikke, læses og skrives der i dag beskeder på forskellige enheder.~~
~~Grundlæggende understøtter POP kun download og sletning af beskeder fra indbakken.~~ ~~Dvs., at almindelige operationer, såsom indstilling af besekedattributter (læst, besvaret mv.), tilføjelse (sikkerhedskopiering) og flytning af beskeder ikke er mulige.~~
~~Grundlæggende understøtter POP kun download og sletning af beskeder fra indbakken.~~ ~~Dvs., at almindelige operationer, såsom indstilling af besekedattributter (læst, stjernemarkeret, besvaret mv.), tilføjelse (sikkerhedskopiering) og flytning af beskeder ikke er mulige.~~
~~Tjek også, [hvad Google skriverom det](https://support.google.com/mail/answer/7104828).~~
~~F.eks. kan [Gmail importere beskeder](https://support.google.com/mail/answer/21289) fra en anden POP-konto,~~ ~~hvilket kan anvendes som en løsning ifm. udbydere, som ikke understøtter IMAP.~~
~~F.eks. kan [Gmail importere beskeder](https://support.google.com/mail/answer/21289) fra en anden POP-konto,~~ ~~hvilket kan anvendes som en løsning, når en udbyder ikke understøtter IMAP.~~
~~tl;dr; overvej at skifte til IMAP.~~
@ -575,197 +581,197 @@ Tjek [denne FAQ](#user-content-faq33) om redigering af brugernavnet til e-mailad
<aname="faq12"></a>
**(12) Hvordan fungerer kryptering/dekryptering?**
Kommunikation med e-mailservere sker altid krypteret, medmindre dette eksplicit deaktiveres. Dette spørgsmål omhandler valgfri end-to-end kryptering med PGP eller S/MIME. Afsender og modtager bør først aftale dette og udveksle signerede beskeder for at overføre deres offentlige nøgler, før krypterede beskeder kan sendes.
E-mailserverkommunikation er altid krypteret, medmindre dette eksplicit er fravalgt. Dette spørgsmål angår valgfri end-to-end kryptering med PGP eller S/MIME. For at kommunikere vha. krypterede meddelelser, bør afsender og modtager først enes om dette og derefter udveksle signerede beskeder for at overføre deres respektive offentlige nøgler.
*Generelt*
[Tjek hér](https://en.wikipedia.org/wiki/Public-key_cryptography), hvordan kryptering vha. offentlige/private nøgler fungerer.
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
For at signere/kryptere en besked, vælg den passende metode i Send-dialogen. Er der tidliger valgt *Vis ikke igen* ifm. Send-dialogen, kan denne altid åbnes igen vha. trepunkts-overløbsmenuen.
To sign/encrypt a message, just select the appropriate method in the send dialog. You can always open the send dialog using the three-dots overflow menu in case you selected *Don't show again* before.
For at bekræfte en signatur eller dekryptere en modtaget besked, så åbn beskeden og tryk blot på gestussen eller på hængelåsikonet umiddelbart under beskedhandlingsbjælken.
To verify a signature or to decrypt a received message, open the message and just tap the gesture or padlock icon just below the message action bar.
Første gang en signeret/krypteret besked afsendes, anmodes der muligvis om en signaturnøgle. Mhp. efterfølgende brug gemmer FairEmail automatisk den valgte signeringsnøgle i den anvendte identitet. Er der behov for at nulstille signeringsnøglen, så gem blot identiteten eller brug et langt tryk på identiteten på identitetslisten og vælg *Nulstil signeringsnøgle*. Den valgte signeringsnøgle er synlig på identitetslisten. Skal en nøgle vælges fra gang til gang, kan flere identiteter oprettes til den samme konto med den samme e-mailadresse.
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
I fortrolighedsindstillingerne kan man vælge standardkrypteringsmetoden (PGP eller S/MIME), aktivere *Signér som standard*, *Kryptér som standard* og *Dekryptér automatisk beskeder*. Bemærk, at automatisk dekryptering ikke er mulig, hvis brugerinteraktion, f.eks.. valg af nøgle eller læsning af et sikkerhedstoken, kræves.
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
Beskedtekster/vedhæftninger, som skal krypteres, samt dekrypterede ditto, gemmes kun lokalt og tilføjes aldrig den eksterne server. Vil man fortryde dekryptering, kan menupunktet *gensynk* benyttes fra trepunktsmenuen på beskedhandlingsbjælken.
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
*PGP*
[OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) skal først installere og opsætte. FairEmail er aftestet med OpenKeychain version 5.4. Senere versioner sandsynligvis kompatible, men tidligere versioner er måske ikke.
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
**Vigtigt**: OpenKeychain-appen er kendt for at gå ned (upåagtet), når den kaldende app (FairEmail) endnu ikke er godkendt og får en eksisterende offentlig nøgle. Dette kan løses ved at prøve at sende en signeret/krypteret besked til en afsender med en ukendt offentlig nøgle.
**Important**: the OpenKeychain app is known to (silently) crash when the calling app (FairEmail) is not authorized yet and is getting an existing public key. You can workaround this by trying to send a signed/encrypted message to a sender with an unknown public key.
**Vigtigt**: Kan OpenKeychain-appen ikke (længere) finde en nøgle, skal en tidligere valgt nøgle muligvis nulstilles. Dette kan gøres via at langt tryk på en identitet i identitetslisten (Indstillinger, Manuel opsætning, flere valg, Identiteter).
**Important**: if the OpenKeychain app cannot find a key (anymore), you might need to reset a previously selected key. This can be done by long pressing an identity in the list of identities (Settings, tap Manual setup and more options, tap Identities).
**Vigtigt**: For at lade apps såsom FairEmail oprette forbindelse pålideligt til OpenKeychain-tjenesten for at kryptere/dekryptere beskeder, kan deaktivering af batterioptimering af OpenKeychain-appen være nødvendig.
**Important**: to let apps like FairEmail reliably connect to the OpenKeychain service to encrypt/decrypt messages, it might be necessary to disable battery optimizations for the OpenKeychain app.
**Vigtigt**: OpenKeychain-appen har angiveligt behov for kontakttilladelse for at fungere korrekt.
**Important**: the OpenKeychain app reportedly needs contacts permission to work correctly.
**Vigtigt**: På visse Android-versioner/-enheder er det nødvendigt at aktivere *Vis popups i baggrundstilstand * i de udvidede tilladelser til Android-app indstillingerne i OpenKeychain-appen. Uden denne tilladelse gemmes udkastet, men OpenKeychain-popup'en til bekræftelse/valg vises muligvis ikke.
**Important**: on some Android versions / devices it is necessary to enable *Show popups while running in background* in the additional permissions of the Android app settings of the OpenKeychain app. Without this permission the draft will be saved, but the OpenKeychain popup to confirm/select might not appear.
FairEmail vil sende [Autocrypt](https://autocrypt.org/)-headeren til brug for andre e-mailklienter, men kun for signerede og krypterede beskeder, da for mange e-mailservere har problemer med den ofte lange Autocrypt-header. Bemærk, at den mest sikre måde at starte en krypteret e-mailudveksling på, er ved først at sende signerede beskeder. Modtagne Autocrypt-headers sendes til og lagres af OpenKeychain-appen til brug for fremtidige signaturbekræftelser/beskeddekrypteringer.
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
Al nøglehåndtering uddelegeres af sikkerhedsårsager til OpenKeychain-appen. Dette betyder også, at FairEmail ikke gemmer PGP-nøgler.
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
Inline-krypteret PGP i modtagne beskeder understøttes, men ikke inline PGP-signaturer og inline PGP i udgående beskeder. Tjek [hér](https://josefsson.org/inline-openpgp-considered-harmful.html) for årsagen.
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
Kun signerede eller kun krypterede beskeder er ikke en god idé. Tjek her for årsagen:
Signed-only or encrypted-only messages are not a good idea, please see here about why not:
* [Overvejelser vedr. OpenPGP, del I](https://k9mail.github.io/2016/11/24/OpenPGP-Considerations-Part-I.html)
* [Overvejelser vedr. OpenPGP, del II](https://k9mail.github.io/2017/01/30/OpenPGP-Considerations-Part-II.html)
* [Overvejelser vedr. OpenPGP, del III, Autocrypt](https://k9mail.github.io/2018/02/26/OpenPGP-Considerations-Part-III-Autocrypt.html)
Kun-signerede beskeder understøttes, men ikke kun-krypterede beskeder.
Signed-only messages are supported, encrypted-only messages are not supported.
Almindelige fejl:
Common errors:
* *Ingen nøgle*: Ingen PGP-nøgle tilgængelig for en af de angivne e-mailadresser
* *Manglende krypteringsnøgle*: Der er sandsynligvis valgt en nøgle i FairEmail, der ikke længere forefindes i OpenKeychain-appen. Nulstilling af nøglen (se ovenfor) løser sandsynligvis dette problem.
*S/MIME*
Den/de offentlige modtagernøgle(r) kræves ved kryptering af en besked. Ens private nøgle kræves ved signering af en besked.
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
Private nøgler opbevares af Android og kan importeres via Androids avancerede sikkerhedsindstillinger. En genvej (knap) hertil findes under fortrolighedsindstillingerne. Android anmoder om opsætning af PIN-kode, mønster eller adgangskode, hvis dette ikke allerede er sket. Ved brug af en Nokia-enhed med Android 9, [tjek først dette](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
Bemærk, at certifikater kan indeholde flere nøgler til flere formål, f.eks. til godkendelse, kryptering og signering. Android importerer kun den første nøgle. For at importere alle nøgler, skal certifikatet først opdeles. Dette er en vigtig handling, så det anbefales at bede certifikatleverandøren om support.
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
Bemærk, at S/MIME-signering med andre algoritmer end RSA understøttes, dog understøtter muligvis ikke af af andre e-mailklienter. S/MIME-kryptering er kun mulig med symmetriske algoritmer, hvilket i praksis betyder brug af RSA.
Note that S/MIMEsigning with other algorithms than RSA is supported, but be aware that other email clients might not support this. S/MIME encryption is possible with symmetric algorithms only, which means in practice using RSA.
Standardkrypteringsmetoden er PGP, dog huskes den senest anvendte krypteringsmetode til næste gang for den valgte identitet. Det kan være nødvendigt igen at aktivere Send-mulighederne via trepriksmenuen for at kunne vælge krypteringsmetoden.
The default encryption method is PGP, but the last used encryption method will be remembered for the selected identity for the next time. You might need to enable the send options in the three dots menu again to be able to select the encryption method.
For at tillade forskellige private nøgler til den samme e-mailadresse, tillader FairEmail altid valg af en nøgle, når flere identiteter findes til den samme e-mailadresse for den samme konto.
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
Offentlige nøgler gemmes af FairEmail og kan importeres ifm. allerførste signaturbekræftelse eller via fortrolighedsindstillingerne (PEM- el. DER-format).
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
FairEmail foretager bekræftelse af både signaturen og den komplette certifikatkæde.
FairEmail verifies both the signature and the complete certificate chain.
Almindelige fejl:
Common errors:
* *Intet certifikat fundet, der matcher targetContraints*: Dette betyder sandsynligvis, at en gammel version af FairEmail benyttes
* *kunne ikke finde en gyldig certificeringssti til det anmodede mål*: Dette betyder grundlæggende, at der ikke blev fundet en eller flere mellem- eller rodcertifikater
* *Privat nøgle matcher ikke nogle krypteringsnøgler*: Den valgte nøgle kan ikke anvendes til beskeddekrypteringen, da den sandsynligvis ikke er den korrekte nøgle
* *Ingen privat nøgle*: Intet certifikat er valgt eller intet certifikat var tilgængeligt i Android-nøglelageret
Er certifikatkæden forkert, vil et tryk på den lille infoknap opliste alle eksisterende certifikater. Efter certifikatoplysningerne vises udstederen eller "selfSign". Et certifikat er selvsigneret, når både emne og udsteder er identiske. Certifikater fra en certifikatmyndighed (CA) er markeret med "[keyCertSign](https://tools.ietf.org/html/rfc5280#section-4.2.1.3)". Certifikater lokaliseret i Android-nøglelageret er markeret "Android".
In case the certificate chain is incorrect, you can tap on the little info button to show the all certificates. After the certificate details the issuer or "selfSign" is shown. A certificate is self signed when the subject and the issuer are the same. Certificates from a certificate authority (CA) are marked with "[keyCertSign](https://tools.ietf.org/html/rfc5280#section-4.2.1.3)". Certificates found in the Android key store are marked with "Android".
En gyldig kæde ser således ud:
A valid chain looks like this:
```
Dit certifikat > nul eller flere mellemliggende certifikater > CA (root) certifikat markeret med "Android"
```
Bemærk, at en certifikatkæde altid er ugyldig, hvis intet ankercertifikat findes i Android-nøglelageret, hvilket er fundamentalt for S/MIME-certifikatbekræftelse.
Note that a certificate chain will always be invalid when no anchor certificate can be found in the Android key store, which is fundamental to S/MIME certificate validation.
Tjek [hér](https://support.google.com/pixelphone/answer/2844832?hl=en), hvordan certifikater kan importeres til Android-nøglelageret.
Please see [here](https://support.google.com/pixelphone/answer/2844832?hl=en) how you can import certificates into the Android key store.
Brug af udløbne nøgler, inline-krypterede/-signerede beskeder samt hardwaresikkerhedstokens er uunderstøttet.
The use of expired keys, inline encrypted/signed messages and hardware security tokens is not supported.
Søger man et gratis (test) S/MIME-certifikat, så tjek [hér](http://kb.mozillazine.org/Getting_an_SMIME_certificate) for muligheder. Sørg for at [læse dette først](https://davidroessli.com/logs/2019/09/free-smime-certificates-in-2019/#update20191219) ved anmodning om et S/MIME Actalis-certifikat. Søger man et billigt S/MIME-certifikat, havde jeg en god oplevelse med [Certum](https://www.certum.eu/en/smime-certificates/).
If you are looking for a free (test) S/MIME certificate, see [here](http://kb.mozillazine.org/Getting_an_SMIME_certificate) for the options. Please be sure to [read this first](https://davidroessli.com/logs/2019/09/free-smime-certificates-in-2019/#update20191219) if you want to request an S/MIME Actalis certificate. If you are looking for a cheap S/MIME certificate, I had a good experience with [Certum](https://www.certum.eu/en/smime-certificates/).
Sådan udtrækkes en offentlig nøgle fra et S/MIME-certifikat:
How to extract a public key from a S/MIME certificate:
Afkodnig af S/MIME-signaturer mv. kan ske [hér](https://lapo.it/asn1js/).
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
S/MIME-signering/-kryptering er en Pro-funktion, alle øvrige PGP- og S/MIME-operationer er gratis i brug.
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br/>
<aname="faq13"></a>
**(13) Hvordan fungerer søgning på en enhed/server?**
**(13) How does search on device/server work?**
Beskedsøgning kan ske efter Afsender (fra), Modtager (til, kopi, bcc), Emne, nøgleord eller beskedtekst vha. forstørrelsesglasset i handlingslbjælken i en mappe. Søgning kan også ske fra enhver app ved at vælge *Søg e-mail * i popup-menuen kopiér/indsæt.
You can start searching for messages on sender (from), recipient (to, cc, bcc), subject, keywords or message text by using the magnify glass in the action bar of a folder. You can also search from any app by selecting *Search email* in the copy/paste popup menu.
Søgning i den fælles indbakke udføres i alle mapper på alle konti, søgning i mappelisten udføres kun for den tilknyttede konto og søgning i en mappe udføres kun i dén mappe.
Searching in the unified inbox will search in all folders of all accounts, searching in the folder list will search in the associated account only and searching in a folder will search in that folder only.
Beskedsøgning sker først på enheden. Der vil være en handlingsknap med et Søg igen-ikon i bunden for at fortsætte søgningen på serveren. Der kan vælges, i hvilken mappe, søgningen skal fortsætte.
Messages will be searched for on the device first. There will be an action button with a search again icon at the bottom to continue searching on the server. You can select in which folder to continue the search.
IMAP-protokollen understøtter ikke søgning i flere end én mappe ad gangen. Søgning på serveren er en ressourcekrævende operation, hvorfor valg af flere mapper ikke er muligt.
The IMAP protocol doesn't support searching in more than one folder at the same time. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
Søgning i lokale beskeder er versal/minuskel ufølsom på deltekst. Lokale beskedtekster gennemsøges kun, hvis selve beskedteksterne er blevet downloadet. Serversøning kan være både versal/minuskel følsom/ufølsom og kan, afhængigt af udbyderen, være på deltekst eller hele ord.
Searching local messages is case insensitive and on partial text. The message text of local messages will not be searched if the message text was not downloaded yet. Searching on the server might be case sensitive or case insensitive and might be on partial text or whole words, depending on the provider.
Visse servere kan ikke håndtere søgning i beskedtekst ifm. større beskedantal. I så tilfælde findes en mulighed for at deaktivere beskedtekstsøgning.
Some servers cannot handle searching in the message text when there are a large number of messages. For this case there is an option to disable searching in the message text.
Det er muligt at bruge Gmail-søgeoperatører vha. søgekommandopræfikset *raw:*. Er kun én Gmail-konto opsat, kan en raw søgning ske direkte på serveren ved at søge fra den fælles indbakke. Er flere Gmail-konti opsat, skal man først gå til mappelisten eller arkivmappen (alle beskeder) for den Gmail-konto, der skal gennemsøges. [Tjek hér](https://support.google.com/mail/answer/7190) ang. tilgængelige søgeoperatører. F.eks.:
It is possible to use Gmail search operators by prefixing a search command with *raw:*. If you configured just one Gmail account, you can start a raw search directly on the server by searching from the unified inbox. If you configured multiple Gmail accounts, you'll first need to navigate to the folder list or the archive (all messages) folder of the Gmail account you want to search in. Please [see here](https://support.google.com/mail/answer/7190) for the possible search operators. For example:
`
raw:larger:10M`
Gennemsøgning af et stort beskedantal på enheden sker ikke særligt hurtigt grundet to begrænsninger:
Searching through a large number of messages on the device is not very fast because of two limitations:
* [sqlite](https://www.sqlite.org/), Androids databasemotor har en poststørrelsesbegrænsning, der forhindrer, at beskedtekster gemmes i databasen
* Android-apps får kun begrænset hukommelse at arbejde med, selv hvis enheden har masser af hukommelse til rådighed
Det betyder, at søgning efter en beskedtekst kræver, at filer indeholdende beskedteksterne skal åbnes én efter én for at tjekke, om den søgte tekst optræder i filen, hvilket er en relativt ressourcekrævende proces.
This means that searching for a message text requires that files containing the message texts need to be opened one by one to check if the searched text is contained in the file, which is a relatively expensive process.
Under *Diverse indstillinger* kan *Byg søgeindeks* aktiveres for markant at øge søgehastigheden på enheden, hvilket dog samtidig øger både strøm- og lagerpladsforbrug. Søgeindekset er baseret på ord, så søgning efter deltekster er ikke muligt. Søgning vha. søgeindekset er som standard OG (AND), så søgning efter f.eks. *æble appelsin* vil søge efter både æble OG appelsin. Ord adskilt med komma resulterer i en ELLER (OR) søgning, så f.eks. *æble, appelsin* vil søge efter enten æble ELLER appelsin. Begge kan kombineres, så søgning efter f.eks. *æble, appelsin banan* vil søge efter æble ELLER (appelsin OG banan). Brug af søgeindekset er en Pro-funktion.
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
Fra version 1.1315 er det muligt at benytte søgeudtryk såsom:
From version 1.1315 it is possible to use search expressions like this:
```
æble +banan-kirsebær?nødder
```
Dette vil resultere i en søgning ala:
This will result in searching like this:
```
("æble" OG "banana" OG IKKE "kirsebær") ELLER "nødder"
```
Søgeudtryk kan benyttes til søgning på enheden via søgeindekset samt til søgning på e-mailserveren, men af ydelsesårsager ikke til søgning på enheden uden søgeindeks.
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
Søgning på enheden er en gratis funktion vha. søgeindekset, mens søgning på serveren er en Pro-funktion.
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
<br/>
<aname="faq14"></a>
**(14) Hvordan opsættes en Outlook-/Live-/Hotmail-konto?**
**(14) How can I set up an Outlook / Live / Hotmail account?**
En Outlook-/Live-/Hotmail-konto kan opsættes via hurtigopsætningsguiden ved at vælg *Outlook*.
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
Anvendelse af en Outlook-, Live- eller Hotmail-konto med tofaktorgodkendelse aktiveret kræver oprettelse af en app-adgangskode. Tjek informationen [hér](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-passwords-two-step-verification).
To use an Outlook, Live or Hotmail account with two factor authentication enabled, you need to create an app password. See [here](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-passwords-two-step-verification) for the details.
See [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for Microsoft's instructions.
For setting up an Office 365 account, please see [this FAQ](#user-content-faq156).
<br/>
<aname="faq15"></a>
**(15) Hvorfor genindlæses beskedteksten hele tiden?**
**(15) Why does the message text keep loading?**
Beskedhovede og -brødtekst hentes separat fra serveren. Brødteksten i større beskeder forudindlæses ikke på takserede forbindelser, men hentes efter behov, når en besked udfoldes. Beskedteksten vil fortsætte med at blive genindlæst ved manglende forbindelse til konto. Tjek også næste spørgsmål, eller hvorvidt andre operationer, såsom beskedsynk, afvikles.
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and will be fetched on demand on expanding a message. The message text will keep loading if there is no connection to the account, see also the next question, or if there other operations, like synchronizing messages, are being executed.
Man kan tjekke konto- og mappelisten for kontoen og mappetilstanden (se forklaringen til betydningen af ikonerne) og operationslisten tilgængelig via hovednavigeringsmenuen for afventende operationer (tjek [denne FAQ](#user-content-faq3) for betydningen af operationerne).
You can check the account and folder list for the account and folder state (see the legend for the meaning of the icons) and the operation list accessible via the main navigation menu for pending operations (see [this FAQ](#user-content-faq3) for the meaning of the operations).
Har FairEmail stoppet synk grundet forudgående konnektivitetsproblemer, så tjek [denne FAQ](#user-content-faq123). Synk kan også gennemtvinges via trepriksmenuen.
If FairEmail is holding off because of prior connectivity issues, please see [this FAQ](#user-content-faq123), you can force synchronization via the three dots menu.
Der kan i modtagelsesindstillingerne opsættes maksimalstørrelse for automatisk besked-downloads på takserede forbindelser.
In the receive settings you can set the maximum size for automatically downloading of messages on metered connections.
Mobilforbindelser er typisk altid takserede, og visse kommercielle Wi-Fi hotspots er det ligeledes.
Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are too.
<br/>
<aname="faq16"></a>
**(16) Hvorfor synkes beskeder ikke?**
**(16) Why are messages not being synchronized?**
Mulige årsager til fejl i beskedsynk (sendte eller modtagne):
Possible causes of messages not being synchronized (sent or received) are:
* Konto eller mappe(r) er ikke opsat til at synkronisere
* Der er indstillet for få synkroniseringsdage
@ -773,130 +779,130 @@ Mulige årsager til fejl i beskedsynk (sendte eller modtagne):
* E-mailserveren er midlertidigt utilgængelig
* Android har stoppet synkroniseringstjenesten
Tjek derfor konto- og mappeindstillinger, og tjek, at konti/mapper er forbundne (tjek forklaringen i navigeringsmenuen ang. ikonernes betydning).
So, check your account and folder settings and check if the accounts/folders are connected (see the legend in the navigation menu for the meaning of the icons).
Er der evt. fejlmeddelelser, så tjek [denne FAQ](#user-content-faq22).
If there are any error messages, please see [this FAQ](#user-content-faq22).
På enheder med en masse hukommelsehungrende apps, vil Android muligvis stoppe synk-tjenesten grundet ressourcemangel.
On some devices, where there are lots of applications competing for memory, Android may stop the synchronization service as a last resort.
Visse Android-versioner stopper apps og tjenester for aggressivt. Tjek [dette dedikerede websted](https://dontkillmyapp.com/) samt [dette Android-problem](https://issuetracker.google.com/issues/122098785) for mere info.
Some Android versions stop apps and services too aggressively. See [this dedicated website](https://dontkillmyapp.com/) and [this Android issue](https://issuetracker.google.com/issues/122098785) for more information.
Deaktivering af batterioptimering (opsætningstrin 3) mindsker risikoen for, at Android stopper synk-tjenesten.
Disabling battery optimizations (setup step 3) reduces the chance Android will stop the synchronization service.
Ved gentagne forbindelsesfejl pauser FairEmail synk i stadigt længere intervaller for ikke at dræne enhedens batteri. Dette beskrives i [denne FAQ](#user-content-faq123).
In case of successive connection errors, FairEmail will hold off increasingly longer to not drain the battery of your device. This is described in [this FAQ](#user-content-faq123).
<br/>
<aname="faq17"></a>
**~~(17) Hvorfor fungerer manuel synk ikke?~~**
**~~(17) Why does manual synchronize not work?~~**
~~Er menuen *Synkronisér nu* nedtonet, er der ingen forbindelse til kontoen.~~
~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
~~Tjek foregående spørgsmål for mere info.~~
~~See the previous question for more information.~~
<br/>
<aname="faq18"></a>
**(18) Hvorfor vises beskedforhåndsvisning ikke altid?**
**(18) Why is the message preview not always shown?**
Beskedforhåndsvisning kan ikke ske for beskedtekster, som endnu ikke er downloadet. Tjek også [denne FAQ](#user-content-faq15).
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
<br/>
<aname="faq19"></a>
**(19) Hvorfor er Pro-funktionerne så dyre?**
**(19) Why are the pro features so expensive?**
Det rette spørgsmål er, "*hvorfor er der så mange skatter og afgifter?*":
The right question is "*why are there so many taxes and fees?*":
* Moms: 25 % (afhængigt af land)
* Google-gebyr: 30 %
* Inkomstskat: 50 %
* <sub>Paypal-gebyr: 5-10 % afhængigt af land/beløb</sub>
Dét, der bliver tilbage til udvikleren, er blot en brøkdel af købsprisen.
So, what is left for the developer is just a fraction of what you pay.
Bemærk, det kun er nødvendigt at købe visse bekvemmeligheds og avancerede funktioner, dvs., at FairEmail grundlæggende kan bruges gratis.
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
Bemærk også, de fleste gratis apps ser ikke ud til at være bæredygtige i længden, hvorimod FairEmail vedligeholdes og supporteres korrekt, samt at gratis apps kan have faldgruber, f.eks. læk af fortrolige oplysninger.
Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
Der er arbejdet på FairEmail næsten dagligt i flere end to år, så prisen synes mere end rimelig. Af samme årsag vil der heller ikke være rabatter.
I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
<br/>
<aname="faq20"></a>
**(20) Gives der refusion?**
**(20) Can I get a refund?**
Fungerer en købt Pro-funktion ikke som tilsigtet, og dette ikke skyldes et problem i de gratis funktioner, og jeg ikke kan løse problemet rettidigt, så gives der refusion. I alle øvrigee tilfælde er refusion ikke mulig. Refusion er under ingen omstændigheder en mulighed for noget problem relateret til de gratis funktioner, da intet er betalt for disse, og da de kan evalueres uden begrænsninger. Jeg tager som sælger ansvar for at levere dét, der er blevet lovet, og jeg forventer, at du tager ansvar for at informere dig om, hvad det er, du køber.
If a purchased pro feature doesn't work as intended and this isn't caused by a problem in the free features and I cannot fix the problem in a timely manner, you can get a refund. In all other cases there is no refund possible. In no circumstances there is a refund possible for any problem related to the free features, since there wasn't paid anything for them and because they can be evaluated without any limitation. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
<aname="faq21"></a>
**(21) Hvordan aktiveres notifikationslyset?**
**(21) How do I enable the notification light?**
Før Android 8 Oreo: Der findes en avanceret indstilling i opsætningen til dette.
Before Android 8 Oreo: there is an advanced option in the notification settings of the app for this.
Android 8 Oreo og senere: Tjek [hér](https://developer.android.com/training/notify-user/channels), hvordan notifikationskanaler opsættes. Man kan bruge knappen *Standard kanal* i appens notifikationsindstillinger for at gå direkte til de relaterede Android-notifikationskanalindstillinger.
Android 8 Oreo and later: please see [here](https://developer.android.com/training/notify-user/channels) about how to configure notification channels. You can use the button *Default channel* in the notification settings of the app to directly go to the right Android notification channel settings.
Bemærk, at apps ikke længere kan ændre notifikationsindstillinger, herunder indstillinger for notifikationslys, på Android 8 Oreo og senere.
Note that apps cannot change notification settings, including the notification light setting, on Android 8 Oreo and later anymore.
Det er undertiden nødvendigt at deaktivere indstillingen *Vis beskedforhåndsvisning i notifikationer* eller at aktivere indstillingerne *Vis kun notifikationer med en forhåndsvisningstekst* for at omgå fejl i Android. Dette gælder muligvis også notifikationslyde og vibrationer.
Sometimes it is necessary to disable the setting *Show message preview in notifications* or to enable the settings *Show notifications with a preview text only* to workaround bugs in Android. This might apply to notification sounds and vibrations too.
Indstilling af lysfarven før Android 8 er uunderstøttes og er ikke muligt på Android 8 og senere.
Setting a light color before Android 8 is not supported and on Android 8 and later not possible.
<br/>
<aname="faq22"></a>
**(22) Hvad betyder konto-/mappefejl ...?**
**(22) What does account/folder error ... mean?**
For lettere at diagnosticere problemer, skjuler FairEmail ikke fejl (hvilket lignende apps ofte gør).
FairEmail does not hide errors like similar apps often do, so it is easier to diagnose problems.
FairEmail forsøger automatisk at genoprette forbindelse efter en forsinkelse. Denne forsinkelse fordobles efter hvert mislykket forsøg for at forhindre batteridræning samt at blive låst ude permanent.
FairEmail will automatically try to connect again after a delay. This delay will be doubled after each failed attempt to prevent draining the battery and to prevent from being locked out permanently.
Der er generelle såvel som specifikke fejl for Gmail-konti (tjek nedenfor).
There are general errors and errors specific to Gmail accounts (see below).
**Generelle fejl**
**General errors**
<aname="authfailed"></a>
Fejlen *... Godkendelse mislykkedes ...* eller *... GODKENDELSE mislykkedes ...* skyldes sandsynligvis forkert brugernavn/adgangskode. Visse udbydere forventer som brugernavn blot *brugernavn* og andre den fulde e-mail *brugernavn@eksempel.dk*. Benyttes kopiér/indsæt ved brugernavn/adgangskode angivelse, medtages muligvis usynlige tegn, hvilket også forårsager denne fejl. Visse adgangskodehåndteringer gøre også dette forkert. Brugernavn kan være minuskel/versal sensitivt, så prøv med kun minuskler. Adgangskoder er fortrinsvis minuskel/versal sensitive. Visse udbydere kræver brug af en app-adgangskode i stedet for kontoadgangskoden, så tjek din leverandørs dokumentation. Det nogle gange nødvendigt først at muliggøre ekstern adgang (IMAP/SMTP) på udbyderens websted. Øvrige mulige årsager er, at kontoen er blokeret, eller at indlogning på en eller anden måde er administrativt begrænset, f.eks. ved kun at tillade indlogning fra bestemte netværk/IP-adresser.
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
Fejlen *... For mange fejlede godkendelsesforsøg ... *betyder sandsynligvis, at der bruges en Yahoo-kontoadgangskode i stedet for en app ditto. Tjek [denne FAQ](#user-content-faq88) vedr. opsætning af en Yahoo-konto.
Fejlen *... 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 set up a Yahoo account.
Meddelelsen *... + OK ...* betyder sandsynligvis, at en POP3-port (normalt portnummer 995) anvendes til en IMAP-konto (normalt ellers portnummer 993).
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
Fejlene *... ugyldig hilsen ...*, *... kræver gyldig adresse ...* og *... Parameter til HELO overholder ikke RFC-syntaks ...* kan sandsynligvis løses ved at ændre den avancerede identitetsindstilling *Anvend lokal IP-adresse i stedet for værtsnavn*.
The errors *... invalid greeting ...*, *... requires valid address ...* and *... Parameter to HELO does not conform to RFC syntax ...* can likely be solved by changing the advanced identity setting *Use local IP address instead of host name*.
Fejlen *... Kunne ikke oprette forbindelse til vært...* betyder, at e-mailserveren ikke svarede inden for en rimelig tid (20 sekunder som standard). Dette indikerer i reglen Internetforbindelsesproblemer, muligvis forårsaget af et VPN eller firewall-app. I tilfælde af virkelige langsomme e-mailservere, kan man prøve at øge timeout for forbindelsen i FairEmails forbindelsesindstillinger.
Fejlen *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
Fejlen *... Forbindelse nægtet ...* betyder, at e-mailserveren eller noget mellem denne og appen, såsom en firewall, aktivt afviste forbindelsen.
Fejlen *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
Fejlen *... Netværk utilgængeligt ... * betyder, at e-mailserveren ikke kunne nås via den aktuelle netværksforbindelse, dvs. ingen tilgængelig Internetadgang.
The error *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
Fejlen *... Vært er uopløst ...*, "*... Kan ikke opløse vært...* eller *... Ingen adresse tilknyttet værtsnavn ...* betyder, at adressen på e-mailserveren ikke kunne opløses til en IP-adresse. Dette kan skyldes et VPN, adblocking eller en utilgængelig/ikke korrekt fungerende (lokal) [DNS-server](https://en.wikipedia.org/wiki/Domain_Name_System).
Fejlen *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
Fejlen *... Software forårsaget forbindelsesafbrydelse ...* betyder, at e-mailserveren, eller noget imellem denne og FairEmail, aktivt afsluttede en eksisterende forbindelse. Dette kan f.eks. ske, når konnektivitet pludselig mistes. Et typisk eksempel er aktivering af Flytilstand.
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
Fejlene *... BYE, logger ud ...*, *... Forbindelse nulstillet ...* betyder, at e-mailserveren eller noget mellem denne og appen, såsom en router eller firewall(-app), aktivt afsluttede forbindelsen.
The errors *... BYE Logging out ...*, *... Connection reset ...* mean that the email server or something between the email server and the app, for example a router or a firewall (app), actively terminated an existing connection.
Fejlen *... Forbindelse lukket af peer ...* kan forårsages af en ikke-opdateret Exchange-server, tjek [hér](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for mere info.
Fejlen *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
Fejlene *... Læsefejl ...*, *... Skrivefejl ...*, *... Læsning fik timeout ...*, *... Ødelagt pipe ...* betyder, at e-mailserveren ikke længere svarer, eller at Internetforbindelsen er ringe.
The errors *... Read error ...*, *... Write error ...*, *... Read timed out ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
<aname="connectiondropped"></a>
Fejlen *... Forbindelse droppet af server? ...* betyder, at e-mailserveren uventet afsluttede forbindelsen. Dette sker af og til ved for mange forbindelser på for kort tid, eller ved brug af forkert adgangskode for mange gange. Tjek i så tilfælde, at adgangskoden er korrekt, deaktivér modtagelse i modtagelsesindstillingerne i ca. 30 minutter og forsøg så igen. Om nødvendigt, tjek [denne FAQ](#user-content-faq23), vedr. reduktion af forbindelsesantallet.
The error *... Connection dropped by server? ...* means that the email server unexpectedly terminated the connection. This sometimes happen when there were too many connections in a too short time or when a wrong password was used for too many times. In this case, please make sure your password is correct and disable receiving in the receive settings for about 30 minutes and try again. If needed, see [this FAQ](#user-content-faq23) about how you can reduce the number of connections.
Fejlen *... Uventet afslutning af zlib-inputstrøm ...* betyder, at ikke alle data blev modtaget, muligvis grundet en dårlig/afbrudt forbindelse.
The error *... Unexpected end of zlib input stream ...* means that not all data was received, possibly due to a bad or interrupted connection.
Fejlen *... forbindelsesfejl ...* kan indikere [For mange samtidige forbindelser](#user-content-faq23).
The error *... connection failure ...* could indicate [Too many simultaneous connections](#user-content-faq23).
Advarslen *... Uunderstøttet kodning ...* betyder, at beskedens tegnsæt er ukendt eller uunderstøttet. FairEmail bruger generelt ISO-8859-1 (Latin1), hvilket som oftest resulterer i korrekt beskedvisning.
The warning *... Unsupported encoding ...* means that the character set of the message is unknown or not supported. FairEmail will assume ISO-8859-1 (Latin1), which will in most cases result in showing the message correctly.
[Tjek hér](#user-content-faq4) vedr. fejlene *... Ikke-betroet ... ikke i certifikat ...*, * ... Ugyldigt sikkerhedscertifikat (kan ikke bekræfte serveridentitet) ...* eller *... Betroet anker til certificeringssti ikke fundet ...*
Please [see here](#user-content-faq4) for the errors *... Untrusted ... not in certificate ...*, *... Invalid security certificate (Can't verify identity of server) ...* or *... Trust anchor for certification path not found ...*
Please [see here](#user-content-faq41) for the error *... Handshake failed ...*.
Tjek [hér](https://linux.die.net/man/3/connect) ang. betydningen af fejlkoder såsom EHOSTUNREACH og ETIMEDOUT.
See [here](https://linux.die.net/man/3/connect) for what error codes like EHOSTUNREACH and ETIMEDOUT mean.
Mulige årsager:
Possible causes are:
* Firewall eller router blokerer forbindelser til serveren
* Værtsnavnet eller portnummeret er ugyldigt
@ -906,13 +912,13 @@ Mulige årsager:
* E-mai-serveren nægter at acceptere en besked, fordi den f.eks. er for stor eller indeholder uacceptable links
* Der er for mange forbindelser til serveren, se også næste spørgsmål
Grundet spam, blokerer mange offentlige Wi-Fi netværk udgående e-mail. Dette kan somme tider omgås ved brug af en anden SMTP-port. Tjek leverandørdokumentationen ang. anvendelige portnumre.
Many public Wi-Fi networks block outgoing email to prevent spam. Sometimes you can workaround this by using another SMTP port. See the documentation of the provider for the usable port numbers.
Benyttes et [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), kan VPN-udbyderen muligvis blokere forbindelsen, hvis den for aggressivt forsøger at forhindre spam. Bemærk, at [Google Fi](https://fi.google.com/) også bruger et VPN.
If you are using a [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), the VPN provider might block the connection because it is too aggressively trying to prevent spam. Note that [Google Fi](https://fi.google.com/) is using a VPN too.
**Afsendelsesfejl**
**Send errors**
SMTP-servere kan [af forskellige årsager](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes) afvise beskeder. For store beskeder og udløsning af en e-mailservers spamfilter er de mest hyppige årsager.
SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes). Too large messages and triggering the spam filter of an email server are the most common reasons.
* Gmails størrelsesbegrænsning for vedhæftninger [udgør 25 MB](https://support.google.com/mail/answer/6584)
* Outlooks og Office 365' størrelsesbegrænsning for vedhæftninger [udgør 20 MB](https://support.microsoft.com/en-us/help/2813269/attachment-size-exceeds-the-allowable-limit-error-when-you-add-a-large)
@ -922,130 +928,130 @@ SMTP-servere kan [af forskellige årsager](https://en.wikipedia.org/wiki/List_of
* *503 5.5.0 Modtager allerede angivet* betyder typisk, at en adresse bruges som både TO- og CC-adresse
* *554 5.7.1 ... ikke tilladt at videresende* betyder, at e-mailserveren ikke genkender brugernavnet/e-mailadressen. Dobbelttjek værtsnavn og brugernavn/e-mailadresse i identitetsindstillingerne.
* *550 Spam besked afvist, da IP er listet af ...* betyder, at e-mailserveren har afvist at afsende en besked fra den aktuelle (offentlige) netværksadresse, fordi den tidligere har være misbrugt til spamafsendelse. Prøv at aktivere flytilstand i 10 minutter for at få tildelt en ny netværksadresse.
* *550 We're sorry, but we can't send your email. Either the subject matter, a link, or an attachment potentially contains spam, or phishing or malware.* means that the email provider considers an outgong message as harmful.
* *571 5.7.1 Message contains spam or virus or sender is blocked ...* means that the email server considered an outgoing message as spam. This probably means that the spam filters of the email server are too strict. You'll need to contact the email provider for support on this.
* *550 Beklager, din e-mail kan ikke afsendes. Enten emnet, et link, eller en vedhæftet fil indeholder potentielt spam, eller phishing eller malware.* betyder, at e-mailudbyderen anser en udgående besked for skadelig.
* *571 5.7.1 Besked indeholder spam eller virus eller afsender er blokeret ...* betyder, at e-mailserveren betragtede en udgående besked som spam. Dette betyder sandsynligvis, at e-mailserverens spamfiltre er for strikse. Kontakt e-mailudbyderen for support vedr. dette.
Ønskes Gmail SMTP-serveren brugt mhp. at omgå et for strikst, udgående spamfilter eller til at forbedre beskedlevering:
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
* Bekræft din e-mailadresse [hér](https://mail.google.com/mail/u/0/#settings/accounts) (en computerbrowser skal bruges til dette)
* Skift til f.eks. disse identitetsindstillinger (Indstillinger, Manuel opsætning, flere valg, Identiteter, identitet):
Godkendelsen af Gmail-kontiopsætningen vha. hurtigguiden skal periodisk opfriskes via [Androids Kontohåndtering](https://developer.android.com/reference/android/accounts/AccountManager). Dette kræver kontakt-/konto-tilladelser samt Internetforbindelse.
The authorization of Gmail accounts setup with the quick wizard needs to be periodically refreshed via the [Android account manager](https://developer.android.com/reference/android/accounts/AccountManager). This requires contact/account permissions and internet connectivity.
Fejlen *... Godkendelse mislykkedes... Konto ikke fundet ...* betyder, at en tidligere godkendt Gmail-konto er fjernet fra enheden.
Fejlen *... Godkendelse mislykkedes... Account not found ...* means that a previously authorized Gmail account was removed from the device.
Fejlene *... Godkendelse mislykkedes... Intet token ...* betyder, at Android-kontohåndteringen ikke kunne opfriske godkendelsen af en Gmail-konto.
The errors *... Authentication failed ... No token ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
Fejlen *... Ugyldige akkreditiverer ... netværksfejl ...* betyder, at Androids Kontohåndtering var ude af stand til at opfriske godkendelsen af en Gmail-konto grundet Internetforbindelsesproblemer
The error *... Authentication failed ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
Fejlen *... Godkendelse mislykkedes... Ugyldige akkreditiver ...* kan være forårsaget af et skift af kontoadgangskoden eller ophævelse af de krævede konto-/kontakttilladelser. Er kontoadgangskoden skiftet, så godkend igen Google-kontoen i Android-kontoindstillingerne. Er tilladelserne tilbagekaldt, kan hurtigopsætningsguiden til Gmail startes for at gentildele de nødvendige tilladelser (genopsætning af kontoen er ikke nødvendig).
The error *... Authentication failed ... Invalid credentials ...* could be caused by changing the account password or by having revoked the required account/contacts permissions. In case the account password was changed, you'll need to authenticate the Google account in the Android account settings again. In case the permissions were revoked, you can start the Gmail quick setup wizard to grant the required permissions again (you don't need to setup the account again).
Fejlen *... ServiceDisabled ...* kan skyldes indrullering i [Avanceret Beskyttelsesprogram](https://landing.google.com/advancedprotection/): "*For at læse e-mails, skal Gmail bruges. Google-kontoen kan ikke bruges med apps og tjenester, som kræver adgang til følsomme data såsom e-mails*". Tjek [hér](https://support.google.com/accounts/answer/7519408?hl=en&ref_topic=9264881) for mere info.
The eror *... ServiceDisabled ...* might be caused by enrolling in the [Advanced Protection Program](https://landing.google.com/advancedprotection/): "*To read your email, you can (must) use Gmail - You won’t be able to use your Google Account with some (all) apps & services that require access to sensitive data like your emails*", see [here](https://support.google.com/accounts/answer/7519408?hl=en&ref_topic=9264881).
Hvis i tvivl, kan der anmodes om [support](#user-content-support).
When in doubt, you can ask for [support](#user-content-support).
<br/>
<aname="faq23"></a>
**(23) Hvorfor ses advarslen ... ?**
**(23) Why do I get alert ... ?**
*Generelt*
*General*
Avarsler er advarselsmeddelelser sendt af e-mailservere.
Alerts are warning messages sent by email servers.
*For mange samtidige forbindelser* eller *Maksimalt antal forbindelser overskred*
*Too many simultaneous connections* or *Maximum number of connections exceeded*
Denne advarsel udsendes, når der er for mange samtidige mappeforbindelser til den samme e-mailkonto.
This alert will be sent when there are too many folder connections for the same email account at the same time.
Mulige årsager:
Possible causes are:
* Flere e-mailklienter er forbundet til den samme konto
* Samme e-mailklient er forbundet flere gange til den samme konto
* Tidligere forbindelser blev brat afsluttet, f.eks. ved en pludselig mistet Internetforbindelse
Prøv først at vente lidt for at se, om problemet løser sig selv, ellers:
First try to wait some time to see if the problem resolves itself, else:
* Skift enten til periodisk tjek for beskeder i modtagelsesindstillingerne, hvilket resulterer i, at mapper åbnes én ad gangen
* Eller indstil nogle mapper til polling i stedet for at synkronisation (langt tryk på mappen i mappelisten, redigér egenskaber)
En nem måde at opsætte periodisk tjek for beskeder for alle mapper undtagen indbakken er at bruge *Anvend for alle . .* i trepriksmenuen på mappelisten og at markere de to nederste afkrydsningsfelter.
An easy way to configure periodically checking for messages for all folders except the inbox is to use *Apply to all ...* in the three-dots menu of the folder list and to tick the bottom two advanced checkboxes.
Det maksimale antal samtidige mappeforbindelser til Gmail udgør 15, så der kan synkes maks. 15 mapper samtidigt på tværs af *alle* aktuelle enheder. Derfor er Gmail-*brugermapper* også som standard opsat til polling fremfor altid at synke. Dette kan, om nødvendigt eller ønsket, ændres vha. langt tryk på en mappe i mappelisten, vælg *Redigér egenskaber*. Tjek oplysningerne [hér](https://support.google.com/mail/answer/7126229).
The maximum number of simultaneous folder connections for Gmail is 15, so you can synchronize at most 15 folders simultaneously on *all* your devices at the same time. For this reason Gmail *user* folders are set to poll by default instead of synchronize always. When needed or desired, you can change this by long pressing a folder in the folder list and selecting *Edit properties*. See [here](https://support.google.com/mail/answer/7126229) for details.
Ved brug af en Dovecot-server, skal indstillingen [mail_max_userip_connections](https://doc.dovecot.org/settings/dovecot_core_settings/#mail-max-userip-connections) muligvis ændres.
When using a Dovecot server, you might want to change the setting [mail_max_userip_connections](https://doc.dovecot.org/settings/dovecot_core_settings/#mail-max-userip-connections).
Bemærk, at det vil tage e-mailserveren et stykke tid at opdage afbrudte/mistede forbindelser, hvilket betyder, at kun halvdelen af mappeforbindelserne reelt er tilgængelige. For Gmail vil det kun være 7 forbindelser.
Note that it will take the email server a while to discover broken connections, for example due to going out of range of a network, which means that effectively only half of the folder connections are available. For Gmail this would be just 7 connections.
<br/>
<aname="faq24"></a>
**(24) Hvad betyder gennemse beskeder på serveren?**
**(24) What is browse messages on the server?**
Gennemse beskeder på serveren henter beskeder fra e-mailserveren i realtid, når slutningen af listen over synkede beskeder nås, også hvis mappen er opsat til ikke at synke. Denne funktion kan deaktiveres under Avancerede kontoindstillinger.
Browse messages on the server will fetch messages from the email server in real time when you reach the end of the list of synchronized messages, even when the folder is set to not synchronize. You can disable this feature in the advanced account settings.
<br/>
<aname="faq25"></a>
**(25) Hvorfor kan der ikke vælges/åbnes/gemmes et billede, vedhæftning eller fil?**
**(25) Why can't I select/open/save an image, attachment or a file?**
Når et menupunkt til at vælge/åbne/gemme en fil er deaktiveret (nedtonet), eller når meddelelsen *Lageradgangs-framework ikke tilgængelig* vises, så er [lageradgangs-framework'en](https://developer.android.com/guide/topics/providers/document-provider), en standard Android-komponent, sandsynligvis ikke til stede. Dette kan skyldes, at den ikke er indeholdt i en tilpasset (og debloated) ROM.
When a menu item to select/open/save a file is disabled (dimmed) or when you get the message *Storage access framework not available*, the [storage access framework](https://developer.android.com/guide/topics/providers/document-provider), a standard Android component, is probably not present. This might be because your custom ROM does not include it or because it was actively removed (debloated).
FairEmail anmoder ikke om lagerpladstilladelser, så denne framework kræves for at kunne vælge filer og mapper. Ingen app, undtagen måske filhåndteringer målrettet Android 4.4 KitKat eller senere, bør anmode om lagerpladstilladelser, da dette giver adgang til *alle* filer.
FairEmail does not request storage permissions, so this framework is required to select files and folders. No app, except maybe file managers, targeting Android 4.4 KitKat or later should ask for storage permissions because it would allow access to *all* files.
Framework for lagerpladsadgang leveres af pakken *com.android.documentsui*, der er synlig som *Fil*-app i visse Android-versioner (særligt OxygenOS).
The storage access framework is provided by the package *com.android.documentsui*, which is visible as *Files* app on some Android versions (notable OxygenOS).
Framework'en for kan aktiveres for lagerpladsadgang (igen) med denne adb-kommando:
You can enable the storage access framework (again) with this adb command:
```
pm install -k --user 0 com.android.documentsui
```
Alternativt kan *Fil*-appen muligvis aktiveres igen vha. Androids app-indstillinger.
Alternatively, you might be able to enable the *Files* app again using the Android app settings.
<br/>
<aname="faq26"></a>
**(26) Kan man hjælpe med at oversætte FairEmail til ens sprog?**
**(26) Can I help to translate FairEmail in my own language?**
Ja, man kan oversætte FairEmail-teksterne til ens sprog [via Crowdin](https://crowdin.com/project/open-source-email). Tilmelding er gratis.
Yes, you can translate the texts of FairEmail in your own language [on Crowdin](https://crowdin.com/project/open-source-email). Registration is free.
Ønsker man sit navn/alias inkluderet på listen over bidragsydere i appens *Om*-afsnit, så [kontakt mig](https://contact.faircode.eu/?product=fairemailsupport) venligst.
If you would like your name or alias to be included in the list of contributors in *About* the app, please [contact me](https://contact.faircode.eu/?product=fairemailsupport).
<br/>
<aname="faq27"></a>
**(27) Hvordan skelnes mellem indlejrede eller eksterne billeder?**
**(27) How can I distinguish between embedded and external images?**
Bemærk, at download af eksterne billeder fra en fjernserver kan bruges til at registrere, at en besked er set, hvilket sandsynligvis ikke ønsket, såfremt beskeden er spam eller ondsindet.
Note that downloading external images from a remote server can be used to record you did see a message, which you likely don't want if the message is spam or malicious.
<br/>
<aname="faq28"></a>
**(28) Hvordan håndteres statusbjælkenotifikationer?**
**(28) How can I manage status bar notifications?**
I opsætningen findes knappen *Håndtér notifikationer* til at gå direkte til Android-notifikationsindstillingerne for FairEmail.
In the notification settings you'll find a button *Manage notifications* to directly navigate to the Android notifications settings for FairEmail.
I Android 8.0 Oreo og senere kan egenskaberne for de individuelle notifikationskanaler håndteres, f.eks. indstilling af en bestemt notifikationslyd eller notifikationsvisning på låseskærmen.
On Android 8.0 Oreo and later you can manage the properties of the individual notification channels, for example to set a specific notification sound or to show notifications on the lock screen.
FairEmail har flg. beskedkanaler:
FairEmail has the following notification channels:
* Tjeneste: Benytttes til notifikation om synkroniseringstjenesten, tjek også [denne FAQ](#user-content-faq2)
* Send: Benyttes til sendetjenestenotiifikation
@ -1053,39 +1059,39 @@ FairEmail har flg. beskedkanaler:
* Advarsel: Benyttes til advarselsnotifikationer
* Fejl: Benyttes til notifikationer om fejl
Tjek oplysningerne [hér](https://developer.android.com/guide/topics/ui/notifiers/notifications#ManageChannels) om notifikationskanaler. Kort sagt: Tryk på notifikationskanalens navn for at tilgå kanalindstillingerne.
See [here](https://developer.android.com/guide/topics/ui/notifiers/notifications#ManageChannels) for details on notification channels. In short: tap on the notification channel name to access the channel settings.
I Android før version 8 Oreo kan notifikationslyd opsættes via indstillingerne.
On Android before Android 8 Oreo you can set the notification sound in the settings.
Tjek [denne FAQ](#user-content-faq21), hvis enheden har et notifikationslys.
See [this FAQ](#user-content-faq21) if your device has a notification light.
<br/>
<aname="faq29"></a>
**(29) Hvordan vises notifikationer om nye beskeder for andre mapper?**
**(29) How can I get new message notifications for other folders?**
Langt tryk på en mappe, vælg *Redigér egenskaber*, og aktivér enten *Vis i den fælles indbakke* eller *Advisér om nye beskeder* (kun tilgængelig for Android 7 Nougat og senere) og tryk på *Gem*.
Just long press a folder, select *Edit properties*, and enable either *Show in unified inbox* or *Notify new messages* (available on Android 7 Nougat and later only) and tap *Save*.
<br/>
<aname="faq30"></a>
**(30) Hvordan kan de medfølgende hurtigindstillinger benyttes?**
**(30) How can I use the provided quick settings?**
Hurtigindstillinger (indstillingsfliser) er tilgængelige for:
There are quick settings (settings tiles) available to:
* globalt aktivere/deaktivere synkronisering
* vise antallet af nye beskeder og markere dem som set (ikke læst)
Hurtigindstillinger kræver Android 7.0 Nougat eller senere. Brug af indstillingsfliser forklares [hér](https://support.google.com/android/answer/9083864).
Quick settings require Android 7.0 Nougat or later. The usage of settings tiles is explained [here](https://support.google.com/android/answer/9083864).
<br/>
<aname="faq31"></a>
**(31) Hvordan bruges de foruddefinerede genveje?**
**(31) How can I use the provided shortcuts?**
Der findes genveje til oprettelse af en ny besked til en favoritkontakt.
There are shortcuts available to compose a new message to a favorite contact.
Genveje kræver Android 7.1 Nougat eller senere. Brug af genveje forklares [hér](https://support.google.com/android/answer/2781850).
Shortcuts require Android 7.1 Nougat or later. The usage of shortcuts is explained [here](https://support.google.com/android/answer/2781850).
It is also possible to create shortcuts to folders by long pressing a folder in the folder list of an account and selecting *Add shortcut*.
@ -1271,9 +1277,9 @@ If your provider doesn't support encrypted connections, you should ask to make t
See also [this FAQ](#user-content-faq4).
Fejlen '*Handshake mislykkedes ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either caused by a bug in the SSL protocol implementation or by a too short DH key on the email server and can unfortunately not be fixed by FairEmail.
The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either caused by a bug in the SSL protocol implementation or by a too short DH key on the email server and can unfortunately not be fixed by FairEmail.
Fejlen '*Handshake mislykkedes ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -243,7 +243,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [~~(122) Warum wird Empfängername/E-Mail-Adresse mit einer Warnfarbe angezeigt?~~](#user-content-faq122)
* [(123) Was geschieht, wenn FairEmail keine Verbindung zu einem E-Mail-Server herstellen kann?](#user-content-faq123)
* [(124) Warum erhalte ich den Hinweis »Nachricht zu groß oder zu komplex, um sie anzuzeigen«?](#user-content-faq124)
* [(125) Was sind die aktuellen experimentellen Eigenschaften?](#user-content-faq125)
* [(125) Was sind die aktuellen experimentellen Funktionen?](#user-content-faq125)
* [(126) Können Nachrichtenvorschauen an mein Wearable gesendet werden?](#user-content-faq126)
* [(127) Wie kann ich den Fehler »Syntaktisch ungültige HELO-Argumente« beheben?](#user-content-faq127)
* [(128) Wie kann ich die gestellten Fragen zurücksetzen, zum Beispiel um Bilder zu zeigen?](#user-content-faq128)
@ -443,7 +443,7 @@ In the display section of the settings you can enable or disable for example:
* *Conversation action bar*: to disable the bottom navigation bar
* *Hervorhebungsfarbe*: zum Auswählen einer Farbe für den Absender von ungelesenen Nachrichten
* *Show contact photos*: to hide contact photos
* *Show names and email addresses*: to show names or to show names and email addresses
* *Namen und E-Mail-Adressen anzeigen*: um Namen anzuzeigen oder um Namen und E-Mail-Adressen anzuzeigen
* *Show subject italic*: to show the message subject as normal text
* *Show stars*: to hide stars (favorites)
* *Show message preview*: to show 1-4 lines of the message text
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -873,7 +879,7 @@ The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *...
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
The errors *... BYE Logging out ...*, *... „Verbindung zurückgesetzt …”* bedeutet, dass der E-Mail-Server oder etwas zwischen dem E-Mail-Server und der App, zum Beispiel ein Router oder eine Firewall (App), eine bestehende Verbindung aktiv beendet hat.
The errors *... BYE Logging out ...*, *... Connection reset ...* mean that the email server or something between the email server and the app, for example a router or a firewall (app), actively terminated an existing connection.
The error *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -243,7 +243,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [~~(122) Warum wird Empfängername/E-Mail-Adresse mit einer Warnfarbe angezeigt?~~](#user-content-faq122)
* [(123) Was geschieht, wenn FairEmail keine Verbindung zu einem E-Mail-Server herstellen kann?](#user-content-faq123)
* [(124) Warum erhalte ich den Hinweis »Nachricht zu groß oder zu komplex, um sie anzuzeigen«?](#user-content-faq124)
* [(125) Was sind die aktuellen experimentellen Eigenschaften?](#user-content-faq125)
* [(125) Was sind die aktuellen experimentellen Funktionen?](#user-content-faq125)
* [(126) Können Nachrichtenvorschauen an mein Wearable gesendet werden?](#user-content-faq126)
* [(127) Wie kann ich den Fehler »Syntaktisch ungültige HELO-Argumente« beheben?](#user-content-faq127)
* [(128) Wie kann ich die gestellten Fragen zurücksetzen, zum Beispiel um Bilder zu zeigen?](#user-content-faq128)
@ -443,7 +443,7 @@ In the display section of the settings you can enable or disable for example:
* *Conversation action bar*: to disable the bottom navigation bar
* *Hervorhebungsfarbe*: zum Auswählen einer Farbe für den Absender von ungelesenen Nachrichten
* *Show contact photos*: to hide contact photos
* *Show names and email addresses*: to show names or to show names and email addresses
* *Namen und E-Mail-Adressen anzeigen*: um Namen anzuzeigen oder um Namen und E-Mail-Adressen anzuzeigen
* *Show subject italic*: to show the message subject as normal text
* *Show stars*: to hide stars (favorites)
* *Show message preview*: to show 1-4 lines of the message text
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -873,7 +879,7 @@ The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *...
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
The errors *... BYE Logging out ...*, *... „Verbindung zurückgesetzt …”* bedeutet, dass der E-Mail-Server oder etwas zwischen dem E-Mail-Server und der App, zum Beispiel ein Router oder eine Firewall (App), eine bestehende Verbindung aktiv beendet hat.
The errors *... BYE Logging out ...*, *... Connection reset ...* mean that the email server or something between the email server and the app, for example a router or a firewall (app), actively terminated an existing connection.
The error *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -243,7 +243,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
* [~~(122) Warum wird Empfängername/E-Mail-Adresse mit einer Warnfarbe angezeigt?~~](#user-content-faq122)
* [(123) Was geschieht, wenn FairEmail keine Verbindung zu einem E-Mail-Server herstellen kann?](#user-content-faq123)
* [(124) Warum erhalte ich den Hinweis »Nachricht zu groß oder zu komplex, um sie anzuzeigen«?](#user-content-faq124)
* [(125) Was sind die aktuellen experimentellen Eigenschaften?](#user-content-faq125)
* [(125) Was sind die aktuellen experimentellen Funktionen?](#user-content-faq125)
* [(126) Können Nachrichtenvorschauen an mein Wearable gesendet werden?](#user-content-faq126)
* [(127) Wie kann ich den Fehler »Syntaktisch ungültige HELO-Argumente« beheben?](#user-content-faq127)
* [(128) Wie kann ich die gestellten Fragen zurücksetzen, zum Beispiel um Bilder zu zeigen?](#user-content-faq128)
@ -443,7 +443,7 @@ In the display section of the settings you can enable or disable for example:
* *Conversation action bar*: to disable the bottom navigation bar
* *Hervorhebungsfarbe*: zum Auswählen einer Farbe für den Absender von ungelesenen Nachrichten
* *Show contact photos*: to hide contact photos
* *Show names and email addresses*: to show names or to show names and email addresses
* *Namen und E-Mail-Adressen anzeigen*: um Namen anzuzeigen oder um Namen und E-Mail-Adressen anzuzeigen
* *Show subject italic*: to show the message subject as normal text
* *Show stars*: to hide stars (favorites)
* *Show message preview*: to show 1-4 lines of the message text
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -873,7 +879,7 @@ The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *...
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
The errors *... BYE Logging out ...*, *... „Verbindung zurückgesetzt …”* bedeutet, dass der E-Mail-Server oder etwas zwischen dem E-Mail-Server und der App, zum Beispiel ein Router oder eine Firewall (App), eine bestehende Verbindung aktiv beendet hat.
The errors *... BYE Logging out ...*, *... Connection reset ...* mean that the email server or something between the email server and the app, for example a router or a firewall (app), actively terminated an existing connection.
The error *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,7 +467,13 @@ Si utiliza la versión Play Store o GitHub de FairEmail, puede utilizar el asist
Si no quiere usar una cuenta Gmail del dispositivo, puede habilitar el acceso para "aplicaciones menos seguras" y utilizar la contraseña de su cuenta (no recomendado) o habilitar la autenticación de dos factores y utilizar una contraseña específica de la aplicación. Para utilizar una contraseña necesitará configurar una cuenta e identidad a través de la configuración manual en lugar del asistente de configuración rápida.
Consulte [estas Preguntas Frecuentes](#user-content-faq111) sobre por qué sólo se pueden utilizar las cuentas en el dispositivo.
**Importante**: a veces Google emite esta alerta:
*[ALERT] Inicie sesión a través de su navegador web: https://support.google.com/mail/accounts/answer/78754 (Failure)*
Esta verificación de seguridad de Google se activa más a menudo con *aplicaciones menos seguras* activadas, menos a menudo con una contraseña de la aplicación, y casi nunca cuando se utiliza una cuenta en el dispositivo (OAuth).
Consulte [estas Preguntas Frecuentes](#user-content-faq111) sobre por qué sólo se pueden utilizar las cuentas del dispositivo.
Tenga en cuenta que se requiere una contraseña específica de la aplicación cuando la autenticación de dos factores está habilitada.
@ -475,254 +481,254 @@ Tenga en cuenta que se requiere una contraseña específica de la aplicación cu
*Contraseña específica de la aplicación*
Vea [aquí](https://support.google.com/accounts/answer/185833) sobre cómo generar una contraseña específica de la aplicación.
See [here](https://support.google.com/accounts/answer/185833) about how to generate an app specific password.
<br/>
*Habilitar "Aplicaciones menos seguras"*
**Importante**: no se recomienda usar este método porque es menos confiable.
**Important**: using this method is not recommended because it is less reliable.
**Importante**: Las cuentas de Gsuite autorizadas con un nombre de usuario/contraseña dejarán de funcionar [en un futuro próximo](https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html).
**Important**: Gsuite accounts authorized with a username/password will stop working [in the near future](https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html).
Vea [aquí](https://support.google.com/accounts/answer/6010255) acerca de cómo habilitar "aplicaciones menos seguras" o vaya [directamente a la configuración](https://www.google.com/settings/security/lesssecureapps).
See [here](https://support.google.com/accounts/answer/6010255) about how to enable "less secure apps" or go [directy to the setting](https://www.google.com/settings/security/lesssecureapps).
Si usa múltiples cuentas de Gmail, asegúrese de cambiar la configuración de "aplicaciones menos seguras" de la(s) cuenta(s) correcta(s).
If you use multiple Gmail accounts, make sure you change the "less secure apps" setting of the right account(s).
Tenga en cuenta que necesita salir de la pantalla de ajustes de "aplicaciones menos seguras" usando la flecha hacia atrás para aplicar la configuración.
Be aware that you need to leave the "less secure apps" settings screen by using the back arrow to apply the setting.
Si usa este método, debería usar una [contraseña fuerte](https://en.wikipedia.org/wiki/Password_strength) para su cuenta de Gmail, lo cual es una buena idea de todos modos. Tenga en cuenta que usar el protocolo IMAP [estándar](https://tools.ietf.org/html/rfc3501) en sí mismo no es menos seguro.
If you use this method, you should use a [strong password](https://en.wikipedia.org/wiki/Password_strength) for your Gmail account, which is a good idea anyway. Note that using the [standard](https://tools.ietf.org/html/rfc3501) IMAP protocol in itself is not less secure.
Cuando "aplicaciones menos seguras" no está activado, obtendrá el error *La autenticación falló - credenciales inválidas* para cuentas (IMAP) y *Nombre de usuario y contraseña no aceptados* para identidades (SMTP).
When "less secure apps" is not enabled, you'll get the error *Authentication failed - invalid credentials* for accounts (IMAP) and *Username and Password not accepted* for identities (SMTP).
<br/>
*General*
Puede obtener la alerta "*Inicie sesión a través de su navegador web*". Esto sucede cuando Google considera que la red que lo conecta a Internet (esto podría ser una VPN) es insegura. Esto se puede evitar usando el asistente de configuración rápida de Gmail o una contraseña específica de la aplicación.
You might get the alert "*Please log in via your web browser*". This happens when Google considers the network that connects you to the internet (this could be a VPN) to be unsafe. This can be prevented by using the Gmail quick setup wizard or an app specific password.
Mire [aquí](https://support.google.com/mail/answer/7126229) las instrucciones de Google y [aquí](https://support.google.com/mail/accounts/answer/78754) para solucionar problemas.
See [here](https://support.google.com/mail/answer/7126229) for Google's instructions and [here](https://support.google.com/mail/accounts/answer/78754) for troubleshooting.
<br/>
<aname="faq7"></a>
**(7) ¿Por qué los mensajes enviados no aparecen (directamente) en la carpeta enviados?**
**(7) Why are sent messages not appearing (directly) in the sent folder?**
Los mensajes enviados normalmente se mueven de la bandeja de salida a la carpeta enviados tan pronto como su proveedor agrega los mensajes enviados a la carpeta enviados. Esto requiere que se seleccione una carpeta enviados en la configuración de la cuenta y que la carpeta enviados se configure para sincronizar.
Sent messages are normally moved from the outbox to the sent folder as soon as your provider adds sent messages to the sent folder. This requires a sent folder to be selected in the account settings and the sent folder to be set to synchronizing.
Algunos proveedores no llevan un seguimiento de los mensajes enviados o el servidor SMTP utilizado podría no estar relacionado con el proveedor. En estos casos FairEmail automáticamente añadirá mensajes enviados a la carpeta enviados al sincronizar la carpeta enviados, lo que sucederá después de que se haya enviado un mensaje. Tenga en cuenta que esto resultará en tráfico extra de Internet.
Some providers do not keep track of sent messages or the used SMTP server might not be related to the provider. In these cases FairEmail, will automatically add sent messages to the sent folder on synchronizing the sent folder, which will happen after a message have been sent. Note that this will result in extra internet traffic.
~~Si esto no sucede, es posible que su proveedor no esté al tanto de los mensajes enviados o que esté utilizando un servidor SMTP no relacionado con el proveedor.~~ ~~En estos casos puede habilitar la configuración avanzada de identidad *Guardar mensajes enviados* para que FairEmail añada mensajes enviados a la carpeta enviados justo después de enviar un mensaje.~~~~Tenga en cuenta que habilitar este ajuste puede resultar en mensajes duplicados si su proveedor añade mensajes enviados a la carpeta enviados.~~ ~~Además tenga cuidado de que habilitar esta configuración dará como resultado un uso adicional de datos, especialmente cuando se envíen mensajes con grandes archivos adjuntos.~~
~~If this doesn't happen, your provider might not keep track of sent messages or you might be using an SMTP server not related to the provider.~~ ~~In these cases you can enable the advanced identity setting *Store sent messages* to let FairEmail add sent messages to the sent folder right after sending a message.~~~~Note that enabling this setting might result in duplicate messages if your provider adds sent messages to the sent folder too.~~ ~~Also beware that enabling this setting will result in extra data usage, especially when when sending messages with large attachments.~~
~~Si los mensajes enviados en la bandeja de salida no se encuentran en la carpeta enviados en una sincronización completa, también se moverán de la bandeja de salida a la carpeta enviados.~~ ~~Una sincronización completa ocurre al reconectar al servidor o al sincronizar periódicamente o manualmente.~~ ~~Probablemente querrá habilitar la configuración avanzada *Almacenar mensajes enviados* en su lugar para mover mensajes a la carpeta enviados más pronto.~~
~~If sent messages in the outbox are not found in the sent folder on a full synchronize, they will be moved from the outbox to the sent folder too.~~ ~~A full synchronize happens when reconnecting to the server or when synchronizing periodically or manually.~~ ~~You'll likely want to enable the advanced setting *Store sent messages* instead to move messages to the sent folder sooner.~~
<br/>
<aname="faq8"></a>
**(8) ¿Puedo usar una cuenta de Microsoft Exchange?**
**(8) Can I use a Microsoft Exchange account?**
Puede utilizar una cuenta de Microsoft Exchange si es accesible a través de IMAP, lo que es usualmente el caso. Vea [aquí](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) para más información.
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
Por favor consulte [aquí](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) la documentación de Microsoft acerca de la configuración de un cliente de correo electrónico. También hay una sección sobre errores de conexión comunes y soluciones.
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
Algunas versiones antiguas del servidor Exchange tienen un error que causa mensajes vacíos y adjuntos corruptos. Consulte [estas Preguntas Frecuentes](#user-content-faq110) para una solución provisional.
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
Consulte [estas Preguntas Frecuentes](#user-content-faq133) sobre el soporte de ActiveSync.
Please see [this FAQ](#user-content-faq133) about ActiveSync support.
Por favor vea [estas Preguntas Frecuentes](#user-content-faq111) sobre el soporte de OAuth.
Please see [this FAQ](#user-content-faq111) about OAuth support.
<br/>
<aname="faq9"></a>
**(9) ¿Qué son las identidades / cómo añadir un alias?**
**(9) What are identities / how do I add an alias?**
Las identidades representan las direcciones de correo electrónico *desde* las que está enviando a través de un servidor de correo electrónico (SMTP).
Identities represent email addresses you are sending *from* via an email (SMTP) server.
Algunos proveedores le permiten tener múltiples alias. Puede configurarlos estableciendo el campo de dirección de correo electrónico de una identidad adicional a la dirección de alias y configurando el campo nombre de usuario a su dirección de correo electrónico principal.
Some providers allow you to have multiple aliases. You can configure these by setting the email address field of an additional identity to the alias address and setting the user name field to your main email address.
Tenga en cuenta que puede copiar una identidad manteniéndola presionada.
Note that you can copy an identity by long pressing it.
Alternativamente, puede habilitar *Permitir editar la dirección del remitente* en la configuración avanzada de una identidad existente para editar el nombre de usuario cuando se compone un nuevo mensaje, si su proveedor lo permite.
Alternatively, you can enable *Allow editing sender address* in the advanced settings of an existing identity to edit the username when composing a new message, if your provider allows this.
FairEmail actualizará automáticamente las contraseñas de las identidades relacionadas cuando actualice la contraseña de la cuenta asociada o una identidad relacionada.
FairEmail will automatically update the passwords of related identities when you update the password of the associated account or a related identity.
Vea [estas Preguntas Frecuentes](#user-content-faq33) sobre la edición del nombre de usuario de las direcciones de correo electrónico.
See [this FAQ](#user-content-faq33) on editing the username of email addresses.
<br/>
<aname="faq10"></a>
**~~(10) ¿Qué significa 'UIDPLUS no soportado'?~~**
**~~(10) What does 'UIDPLUS not supported' mean?~~**
~~El mensaje de error *UIDPLUS no soportado* significa que su proveedor de correo no proporciona la extensión IMAP [UIDPLUS](https://tools.ietf.org/html/rfc4315). Esta extensión IMAP es necesaria para implementar la sincronización de dos vías, que no es una característica opcional. Así que, a menos que su proveedor pueda habilitar esta extensión, no puede usar FairEmail para este proveedor.~~
~~The error message *UIDPLUS not supported* means that your email provider does not provide the IMAP [UIDPLUS extension](https://tools.ietf.org/html/rfc4315). This IMAP extension is required to implement two way synchronization, which is not an optional feature. So, unless your provider can enable this extension, you cannot use FairEmail for this provider.~~
<br/>
<aname="faq11"></a>
**~~(11) ¿Por qué no se admite POP?~~**
**~~(11) Why is POP not supported?~~**
~~Además de que cualquier proveedor de correo electrónico decente soporta [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol) estos días,~~ ~~usar [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol) dará como resultado un uso adicional innecesario de la batería y un retraso en las notificaciones de nuevos mensajes.~~ ~~Además, POP es inadecuado para la sincronización de dos vías y la mayoría de las veces la gente lee y escribe mensajes en diferentes dispositivos hoy en día.~~
~~Besides that any decent email provider supports [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol) these days,~~ ~~using [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol) will result in unnecessary extra battery usage and delayed new message notifications.~~ ~~Moreover, POP is unsuitable for two way synchronization and more often than not people read and write messages on different devices these days.~~
~~Básicamente, POP sólo soporta descargar y borrar mensajes de la bandeja de entrada.~~ ~~Entonces, las operaciones comunes como configurar los atributos del mensaje (leer, marcar, responder, etc.), añadir (respaldar) y mover mensajes no es posible.~~
~~Basically, POP supports only downloading and deleting messages from the inbox.~~ ~~So, common operations like setting message attributes (read, starred, answered, etc), adding (backing up) and moving messages is not possible.~~
~~Ver también [lo que Google escribe sobre eso](https://support.google.com/mail/answer/7104828).~~
~~See also [what Google writes about it](https://support.google.com/mail/answer/7104828).~~
~~Por ejemplo [Gmail puede importar mensajes](https://support.google.com/mail/answer/21289) desde otra cuenta POP,~~ ~~que puede ser usado como solución temporal para cuando su proveedor no soporta IMAP.~~
~~For example [Gmail can import messages](https://support.google.com/mail/answer/21289) from another POP account,~~ ~~which can be used as a workaround for when your provider doesn't support IMAP.~~
~~en resumen, considere cambiar a IMAP.~~
~~tl;dr; consider to switch to IMAP.~~
<br/>
<aname="faq12"></a>
**(12) ¿Cómo funciona el cifrado/descifrado?**
**(12) How does encryption/decryption work?**
La comunicación con los servidores de correo electrónico siempre está cifrada, a menos que lo desactive explícitamente. Esta pregunta se refiere al cifrado opcional de extremo a extremo con PGP o S/MIME. El remitente y destinario primero deberían acordar esto e intercambiar mensajes firmados para transferir su clave pública para poder enviar mensajes cifrados.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
*General*
Por favor, [vea aquí](https://en.wikipedia.org/wiki/Public-key_cryptography) sobre cómo funciona el cifrado con clave pública/privada.
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
Cifrado en resumen:
Encryption in short:
* Los mensajes **salientes** se cifran con la **clave pública** del destinatario
* Los mensajes **entrantes** se descifran con la **clave privada** del destinatario
Firma en resumen:
Signing in short:
* Los mensajes **salientes** se firman con la **clave privada** del remitente
* Los mensajes **entrantes** se verifican con la **clave pública** del remitente
Para firmar/cifrar un mensaje, simplemente seleccione el método apropiado en el diálogo de enviar. También puede abrir el diálogo de enviar usando el menú de tres puntos en caso de que haya seleccionado *No volver a mostrar* anteriormente.
To sign/encrypt a message, just select the appropriate method in the send dialog. You can always open the send dialog using the three-dots overflow menu in case you selected *Don't show again* before.
Para verificar una firma o descifrar un mensaje recibido, abra el mensaje y pulse el icono de gesto o candado justo debajo de la barra de acción del mensaje.
To verify a signature or to decrypt a received message, open the message and just tap the gesture or padlock icon just below the message action bar.
La primera vez que envíe un mensaje firmado/cifrado puede que le pidan una clave de firma. FairEmail almacenará automáticamente la clave de firma seleccionada en la identidad utilizada para la próxima vez. Si necesita restablecer la clave de firma, simplemente guarde la identidad o mantenga pulsada la identidad en la lista de identidades y seleccione *Restablecer clave de firma*. La clave de firma seleccionada es visible en la lista de identidades. Si es necesario seleccionar una clave para cada caso puede crear múltiples identidades para la misma cuenta con la misma dirección de correo electrónico.
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
En la configuración de privacidad puede seleccionar el método de cifrado predeterminado (PGP o S/MIME), active *Firmar por defecto*, *Cifrar por defecto* y *Descifrar mensajes automáticamente*, pero tenga en cuenta que el descifrado automático no es posible si la interacción del usuario es requerida, como seleccionar una clave o leer un token de seguridad.
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
El texto/adjuntos a cifrar y el texto/adjunto descifrados se almacenan localmente sólo y nunca se añadirán al servidor remoto. Si quiere deshacer el descifrado, puedes usar el elemento de menú *Resincronizar* en el menú de tres puntos de la barra de acción del mensaje.
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
*PGP*
Necesitará instalar y configurar [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) primero. FairEmail ha sido probado con OpenKeychain versión 5.4. Es muy probable que las versiones posteriores sean compatibles, pero las versiones anteriores podrían no serlo.
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
**Importante**: la aplicación OpenKeychain es conocida por cerrarse (silenciosamente) cuando la aplicación que le llama (FairEmail) no está autorizada aún y está recibiendo una clave pública existente. Puede solucionar esto intentando enviar un mensaje firmado/cifrado a un remitente con una clave pública desconocida.
**Important**: the OpenKeychain app is known to (silently) crash when the calling app (FairEmail) is not authorized yet and is getting an existing public key. You can workaround this by trying to send a signed/encrypted message to a sender with an unknown public key.
**Importante**: si la aplicación OpenKeychain (ya) no puede encontrar una clave, puede que deba restablecer una clave previamente seleccionada. Esto se puede hacer manteniendo presionada una identidad en la lista de identidades (ajustes, configuración manual y más opciones, identidades).
**Important**: if the OpenKeychain app cannot find a key (anymore), you might need to reset a previously selected key. This can be done by long pressing an identity in the list of identities (Settings, tap Manual setup and more options, tap Identities).
**Importante**: para permitir que aplicaciones como FairEmail se conecten de forma confiable al servicio OpenKeychain para cifrar/descifrar mensajes, podría ser necesario desactivar las optimizaciones de batería para la aplicación OpenKeychain.
**Important**: to let apps like FairEmail reliably connect to the OpenKeychain service to encrypt/decrypt messages, it might be necessary to disable battery optimizations for the OpenKeychain app.
**Importante**: la aplicación OpenKeychain necesita el permiso de contactos para funcionar correctamente.
**Important**: the OpenKeychain app reportedly needs contacts permission to work correctly.
**Importante**: en algunas versiones / dispositivos Android es necesario habilitar *Mostrar ventanas emergentes mientras se ejecuta en segundo plano* en los permisos adicionales de la configuración de la aplicación Android de la aplicación OpenKeychain. Sin este permiso el borrador será guardado, pero la ventana emergente de OpenKeychain para confirmar/seleccionar podría no aparecer.
**Important**: on some Android versions / devices it is necessary to enable *Show popups while running in background* in the additional permissions of the Android app settings of the OpenKeychain app. Without this permission the draft will be saved, but the OpenKeychain popup to confirm/select might not appear.
FairEmail enviará el encabezado [Autocrypt](https://autocrypt.org/) para su uso por otros clientes de correo electrónico, pero sólo para mensajes firmados y cifrados porque demasiados servidores de correo tienen problemas con el a menudo largo encabezado Autocrypt. Tenga en cuenta que la forma más segura de iniciar un intercambio de correo electrónico cifrado es enviar primero los mensajes firmados. Los encabezados de Autocrypt recibidos serán enviados a la aplicación OpenKeychain para ser almacenados al verificar una firma o desencriptar un mensaje.
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
Todo el manejo de las llaves se delega a la aplicación de la cadena OpenKey por razones de seguridad. Esto también significa que FairEmail no almacena claves PGP.
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
Se admite cifrado PGP embebido en los mensajes recibidos, pero las firmas PGP embebidas y PGP embebido en los mensajes salientes no son soportados, mire [aquí](https://josefsson.org/inline-openpgp-considered-harmful.html) sobre por qué no.
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
Los mensajes sólo con firma o sólo encriptados no son una buena idea, por favor vea aquí por qué no:
Signed-only or encrypted-only messages are not a good idea, please see here about why not:
* [Consideraciones sobre OpenPGP Parte I](https://k9mail.github.io/2016/11/24/OpenPGP-Considerations-Part-I.html)
* [Consideraciones sobre OpenPGP Parte II](https://k9mail.github.io/2017/01/30/OpenPGP-Considerations-Part-II.html)
* [Consideraciones sobre OpenPGP Parte III Autocrypt](https://k9mail.github.io/2018/02/26/OpenPGP-Considerations-Part-III-Autocrypt.html)
Se admiten mensajes sólo firmados, los mensajes sólo cifrados no están soportados.
Signed-only messages are supported, encrypted-only messages are not supported.
Errores comunes:
Common errors:
* *Sin clave*: no hay ninguna clave PGP disponible para una de las direcciones de correo electrónico listadas
* *Falta la clave para el cifrado*: probablemente hay una clave seleccionada en FairEmail que ya no existe en la aplicación OpenKeychain. Restablecer la clave (ver arriba) probablemente solucione este problema.
*S/MIME*
Cifrar un mensaje requiere la(s) clave(s) pública(s) del destinatario(s). Firmar un mensaje requiere su clave privada.
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
Las claves privadas son almacenadas por Android y pueden ser importadas a través de la configuración de seguridad avanzada de Android. Hay un atajo (botón) para esto en la configuración de privacidad. Android le pedirá que establezca un PIN, patrón o contraseña si no lo ha hecho antes. Si tiene un dispositivo Nokia con Android 9, por favor [lea esto primero](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
Tenga en cuenta que los certificados pueden contener múltiples claves para múltiples propósitos, por ejemplo para la autenticación, el cifrado y la firma. Android sólo importa la primera clave, así que para importar todas las claves, el certificado primero debe ser dividido. Esto no es muy trivial y se le aconseja que pida ayuda al proveedor del certificado.
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
Nótese que la firma S/MIME con otros algoritmos que RSA es soportada, pero tenga en cuenta que otros clientes de correo electrónico tal vez no lo soporten. El cifrado S/MIME es posible únicamente con algoritmos simétricos, lo que significa que en la práctica se utiliza RSA.
Note that S/MIMEsigning with other algorithms than RSA is supported, but be aware that other email clients might not support this. S/MIME encryption is possible with symmetric algorithms only, which means in practice using RSA.
El método de cifrado por defecto es PGP, pero el último método de cifrado utilizado será recordado para la identidad seleccionada para la próxima vez. Puede que necesite activar las opciones de envío en el menú de tres puntos de nuevo para poder seleccionar el método de cifrado.
The default encryption method is PGP, but the last used encryption method will be remembered for the selected identity for the next time. You might need to enable the send options in the three dots menu again to be able to select the encryption method.
Para permitir diferentes claves privadas para la misma dirección de correo electrónico, FairEmail siempre le permitirá seleccionar una clave cuando haya múltiples identidades con la misma dirección de correo electrónico para la misma cuenta.
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
Las claves públicas son almacenadas por FairEmail y pueden ser importadas al verificar una firma por primera vez o a través de la configuración de privacidad (formatos PEM o DER).
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
FairEmail verifica tanto la firma como la cadena completa de certificados.
FairEmail verifies both the signature and the complete certificate chain.
Errores comunes:
Common errors:
* *No se ha encontrado ningún certificado que coincida con targetContraints*: esto seguramente significa que está usando una versión antigua de FairEmail
* *incapaz de encontrar una ruta de certificación válida para el objetivo solicitado*: básicamente esto significa que uno o más certificados intermedios o raíz no fueron encontrados
* *La clave privada no coincide con ninguna clave de cifrado*: la clave seleccionada no puede utilizarse para descifrar el mensaje, probablemente porque es la clave incorrecta
* *No hay clave privada*: no se ha seleccionado ningún certificado o no hay ningún certificado disponible en el almacén de claves Android
En caso de que la cadena de certificados sea incorrecta, puede pulsar el pequeño botón de información para mostrar todos los certificados. Después de los detalles del certificado se muestra el emisor o "auto-Firmado". Un certificado es auto-Firmado cuando el sujeto y el emisor son los mismos. Los certificados de una autoridad certificadora (CA) están marcados con "[keyCertSign](https://tools.ietf.org/html/rfc5280#section-4.2.1.3)". Los certificados encontrados en el almacén de claves Android están marcados con "Android".
In case the certificate chain is incorrect, you can tap on the little info button to show the all certificates. After the certificate details the issuer or "selfSign" is shown. A certificate is self signed when the subject and the issuer are the same. Certificates from a certificate authority (CA) are marked with "[keyCertSign](https://tools.ietf.org/html/rfc5280#section-4.2.1.3)". Certificates found in the Android key store are marked with "Android".
Una cadena válida se ve así:
A valid chain looks like this:
```
Su certificado > cero o más certificados intermedios > CA (raíz) certificado marcado con "Android"
```
Tenga en cuenta que una cadena de certificados siempre será inválida cuando no se pueda encontrar ningún certificado raíz en el almacén de claves Android, que es fundamental para la validación del certificado S/MIME.
Note that a certificate chain will always be invalid when no anchor certificate can be found in the Android key store, which is fundamental to S/MIME certificate validation.
Consulte [aquí](https://support.google.com/pixelphone/answer/2844832?hl=en) cómo puede importar certificados en la tienda de claves Android.
Please see [here](https://support.google.com/pixelphone/answer/2844832?hl=en) how you can import certificates into the Android key store.
El uso de claves caducadas, mensajes cifrados/firmados embebidos y tokens de seguridad de hardware no está soportado.
The use of expired keys, inline encrypted/signed messages and hardware security tokens is not supported.
Si está buscando un certificado S/MIME gratuito (de prueba), consulte [aquí](http://kb.mozillazine.org/Getting_an_SMIME_certificate) para ver las opciones. Por favor, asegúrese de [leer esto antes](https://davidroessli.com/logs/2019/09/free-smime-certificates-in-2019/#update20191219) si desea solicitar un certificado de S/MIME Actalis. Si está buscando un certificado S/MIME barato, he tenido buena experiencia con [Certum](https://www.certum.eu/en/smime-certificates/).
If you are looking for a free (test) S/MIME certificate, see [here](http://kb.mozillazine.org/Getting_an_SMIME_certificate) for the options. Please be sure to [read this first](https://davidroessli.com/logs/2019/09/free-smime-certificates-in-2019/#update20191219) if you want to request an S/MIME Actalis certificate. If you are looking for a cheap S/MIME certificate, I had a good experience with [Certum](https://www.certum.eu/en/smime-certificates/).
Cómo extraer una clave pública de un certificado S/MIME:
How to extract a public key from a S/MIME certificate:
Puede decodificar firmas S/MIME, etc, [aquí](https://lapo.it/asn1js/).
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
La firma/cifrado S/MIME es una característica pro, pero todas las demás operaciones PGP y S/MIME son gratis para usar.
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br/>
<aname="faq13"></a>
**(13) ¿Cómo funciona la búsqueda en dispositivo/servidor?**
**(13) How does search on device/server work?**
Puede empezar a buscar mensajes en el remitente (de), destinatario (a, cc, cco), asunto, palabras clave o texto de mensaje mediante el uso de la lupa en la barra de acción de una carpeta. También puede buscar desde cualquier aplicación seleccionando *Buscar en FairEmail* en el menú emergente.
You can start searching for messages on sender (from), recipient (to, cc, bcc), subject, keywords or message text by using the magnify glass in the action bar of a folder. You can also search from any app by selecting *Search email* in the copy/paste popup menu.
Buscar en la bandeja de entrada unificada buscará en todas las carpetas de todas las cuentas, buscar en la lista de carpetas sólo buscará en la cuenta asociada y buscar en una carpeta sólo buscará en esa carpeta.
Searching in the unified inbox will search in all folders of all accounts, searching in the folder list will search in the associated account only and searching in a folder will search in that folder only.
Los mensajes se buscarán primero en el dispositivo. Habrá un botón de acción con un icono de buscar de nuevo en la parte inferior para continuar la búsqueda en el servidor. Puede seleccionar en qué carpeta continuar la búsqueda.
Messages will be searched for on the device first. There will be an action button with a search again icon at the bottom to continue searching on the server. You can select in which folder to continue the search.
El protocolo IMAP no permite buscar en más de una carpeta al mismo tiempo. Buscar en el servidor es una operación costosa, por lo tanto no es posible seleccionar múltiples carpetas.
The IMAP protocol doesn't support searching in more than one folder at the same time. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
La búsqueda de mensajes locales no distingue mayúsulas/minúsculas y es sobre texto parcial. El texto del mensaje de los mensajes locales no se buscará si el texto del mensaje no se ha descargado todavía. Buscar en el servidor puede ser sensible a mayúsculas o minúsculas y puede estar en texto parcial o palabras enteras, dependiendo del proveedor.
Searching local messages is case insensitive and on partial text. The message text of local messages will not be searched if the message text was not downloaded yet. Searching on the server might be case sensitive or case insensitive and might be on partial text or whole words, depending on the provider.
Algunos servidores no pueden manejar la búsqueda en el texto del mensaje cuando hay un gran número de mensajes. Para este caso hay una opción para desactivar la búsqueda en el texto del mensaje.
Some servers cannot handle searching in the message text when there are a large number of messages. For this case there is an option to disable searching in the message text.
Es posible usar operadores de búsqueda de Gmail prefijando un comando de búsqueda con *raw:*. Si ha configurado sólo una cuenta de Gmail, puede iniciar una búsqueda directa directamente en el servidor buscando desde la bandeja de entrada unificada. Si configuró varias cuentas de Gmail, primero tendrá que navegar a la lista de carpetas o a la carpeta de archivo (todos los mensajes) de la cuenta de Gmail en la que quiere buscar. Por favor, [vea aquí](https://support.google.com/mail/answer/7190) para los posibles operadores de búsqueda. Por ejemplo:
It is possible to use Gmail search operators by prefixing a search command with *raw:*. If you configured just one Gmail account, you can start a raw search directly on the server by searching from the unified inbox. If you configured multiple Gmail accounts, you'll first need to navigate to the folder list or the archive (all messages) folder of the Gmail account you want to search in. Please [see here](https://support.google.com/mail/answer/7190) for the possible search operators. For example:
`
raw:larger:10M`
Buscar a través de un gran número de mensajes en el dispositivo no es muy rápido debido a dos limitaciones:
Searching through a large number of messages on the device is not very fast because of two limitations:
* [sqlite](https://www.sqlite.org/), el motor de base de datos de Android tiene un límite de tamaño de registro, evitando que los mensajes de texto se almacenen en la base de datos
* Las aplicaciones Android tienen memoria limitada para trabajar, incluso si el dispositivo tiene suficiente memoria disponible
Esto significa que la búsqueda de un texto de mensaje requiere que los archivos que contengan los textos del mensaje deban abrirse uno por uno para comprobar si el texto buscado está contenido en el archivo, que es un proceso relativamente costoso.
This means that searching for a message text requires that files containing the message texts need to be opened one by one to check if the searched text is contained in the file, which is a relatively expensive process.
En la *configuración miscelánea* puede habilitar *Construir índice de búsqueda* para aumentar significativamente la velocidad de búsqueda en el dispositivo, pero tenga en cuenta que esto aumentará el uso de la batería y el espacio de almacenamiento. El índice de búsqueda se basa en palabras, por lo que no es posible buscar texto parcial. La búsqueda usando el índice de búsqueda es por defecto Y, así que buscar *manzana naranja* buscará manzana Y naranja. Las palabras separadas por comas resultan en la búsqueda de O, así que por ejemplo *manzana, naranja* buscará manzana O naranja. Ambos se pueden combinar, así que buscar *manzana, naranja banana* buscará manzana O (naranja Y banana). Usar el índice de búsqueda es una característica pro.
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
Desde la versión 1.1315 es posible utilizar expresiones de búsqueda como esta:
From version 1.1315 it is possible to use search expressions like this:
```
manzana +banana -cereza ?nueces
```
Esto resultará en una búsqueda como esta:
This will result in searching like this:
```
("manzana" Y "banana" Y NO "cereza") O "nueces"
@ -737,7 +743,7 @@ Searching on the device is a free feature, using the search index and searching
<aname="faq14"></a>
**(14) How can I set up an Outlook / Live / Hotmail account?**
Se puede configurar una cuenta de Outlook / Live / Hotmail a través del asistente de configuración rápida y seleccionando*Outlook*.
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting*Outlook*.
To use an Outlook, Live or Hotmail account with two factor authentication enabled, you need to create an app password. See [here](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-passwords-two-step-verification) for the details.
@ -835,49 +841,49 @@ Before Android 8 Oreo: there is an advanced option in the notification settings
Android 8 Oreo and later: please see [here](https://developer.android.com/training/notify-user/channels) about how to configure notification channels. You can use the button *Default channel* in the notification settings of the app to directly go to the right Android notification channel settings.
Tenga en cuenta que las aplicaciones ya no pueden cambiar los ajustes de notificación, incluyendo la configuración de la luz de notificación, en Android 8 Oreo y posteriores.
Note that apps cannot change notification settings, including the notification light setting, on Android 8 Oreo and later anymore.
A veces es necesario desactivar la configuración *Mostrar vista previa del mensaje en las notificaciones* o habilitar *Mostrar notificaciones sólo con un texto de vista previa* para evitar un error en Android. Esto podría aplicarse también a los sonidos y vibración de notificaciones.
Sometimes it is necessary to disable the setting *Show message preview in notifications* or to enable the settings *Show notifications with a preview text only* to workaround bugs in Android. This might apply to notification sounds and vibrations too.
Establecer un color de luz antes de Android 8 no está soportado y no es posible en Android 8 y posteriores.
Setting a light color before Android 8 is not supported and on Android 8 and later not possible.
<br/>
<aname="faq22"></a>
**(22) ¿Qué significa el error de cuenta/carpeta?**
**(22) What does account/folder error ... mean?**
FairEmail no oculta errores como las aplicaciones similares a menudo lo hacen, por lo que es más fácil diagnosticar problemas.
FairEmail does not hide errors like similar apps often do, so it is easier to diagnose problems.
FairEmail intentará reconectarse automáticamente después de un retraso. Este retraso se duplicará tras cada intento fallido de evitar que se agote la batería y que se bloquee permanentemente el acceso.
FairEmail will automatically try to connect again after a delay. This delay will be doubled after each failed attempt to prevent draining the battery and to prevent from being locked out permanently.
Hay errores generales y errores específicos para las cuentas de Gmail (ver abajo).
There are general errors and errors specific to Gmail accounts (see below).
**Errores generales**
**General errors**
<aname="authfailed"></a>
El error *... La autenticación falló ...* o *... AUTHENTICATE falló...* probablemente significa que su nombre de usuario o contraseña era incorrecto. Algunos proveedores esperan como nombre de usuario sólo *nombre de usuario* y otros su dirección de correo electrónico completa *nombredeusuario@ejemplo.com*. Al copiar/pegar para introducir un nombre de usuario o contraseña, pueden copiarse caracteres invisibles, lo que también podría causar este problema. También se sabe que algunos administradores de contraseñas hacen esto incorrectamente. El nombre de usuario puede ser sensible a mayúsculas, así que intente sólo caracteres en minúsculas. La contraseña es casi siempre sensible a mayúsculas y minúsculas. Algunos proveedores requieren usar una contraseña de aplicación en lugar de la contraseña de la cuenta, así que por favor revise la documentación del proveedor. A veces es necesario habilitar primero el acceso externo (IMAP/SMTP) en el sitio web del proveedor. Otras posibles causas son que la cuenta está bloqueada o que el inicio de sesión ha sido restringido administrativamente de alguna manera, por ejemplo permitiendo iniciar sesión desde ciertas redes / direcciones IP solamente.
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
El error *... Demasiados intentos de autenticación incorrectos ...* probablemente significa que está utilizando una contraseña de cuenta Yahoo en lugar de una contraseña de la aplicación. Por favor, consulte [estas Preguntas Frecuentes](#user-content-faq88) sobre cómo configurar una cuenta Yahoo.
El 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 set up a Yahoo account.
El mensaje *... +OK ...* probablemente significa que un puerto POP3 (normalmente el número de puerto 995) está siendo usado para una cuenta IMAP (normalmente el puerto número 993).
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
Los errores *... saludo inválido ...*, *... requiere una dirección válida ...* y *... Parámetro HELO no se ajusta a la sintaxis RFC ...* puede resolverse cambiando la configuración de identidad avanzada *Utilice la dirección IP local en lugar del nombre de host*.
The errors *... invalid greeting ...*, *... requires valid address ...* and *... Parameter to HELO does not conform to RFC syntax ...* can likely be solved by changing the advanced identity setting *Use local IP address instead of host name*.
El error *... No se pudo conectar al host ...* significa que no hubo respuesta del servidor de correo en un tiempo razonable (20 segundos por defecto). Esto indica principalmente problemas de conectividad a internet, posiblemente causados por una VPN o por una aplicación de firewall. Puede intentar aumentar el tiempo de espera de conexión en la configuración de conexión de FairEmail, para cuando el servidor de correo es realmente lento.
El error *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
El error *... Conexión rechazada...* significa que el servidor de correo electrónico o algo entre el servidor de correo y la aplicación, como un cortafuegos, rechazó activamente la conexión.
El error *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
El error *... Red inaccesible ...* significa que el servidor de correo electrónico no fue accesible a través de la conexión a internet actual, por ejemplo, porque el tráfico de internet sólo está restringido al tráfico local.
The error *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
El error *... Host no resuelto ...*, *... No se puede resolver el host ...* o *... Ninguna dirección asociada con el nombre de host ...* significa que la dirección del servidor de correo electrónico no se pudo resolver en una dirección IP. Esto puede ser causado por un VPN, un bloqueador de anuncios o un servidor [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) que no esté funcionando apropiadamente (local).
El error *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
El error *... Software causó fin de conexión ...* significa que el servidor de correo o algo entre FairEmail y el servidor de correo terminó activamente una conexión existente. Esto puede suceder, por ejemplo, cuando la conectividad se perdió abruptamente. Un ejemplo típico es activar el modo avión.
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
Los errores *... BYE Cerrando sesión...*, *... Conexión restablecida...* significa que el servidor de correo o algo entre el servidor de correo y la aplicación, por ejemplo un router o un firewall (app), ha terminado activamente una conexión existente.
The errors *... BYE Logging out ...*, *... Connection reset ...* mean that the email server or something between the email server and the app, for example a router or a firewall (app), actively terminated an existing connection.
El error *... Conexión cerrada por el par ...* podría ser causada por un servidor de Exchange no actualizado, vea [aquí](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) para más información.
The error *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
Los errores *... Error de lectura ...*, *... Error de escritura ...*, *... Tiempo de lectura agotado ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
The errors *... Read error ...*, *... Write error ...*, *... Read timed out ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
<aname="connectiondropped"></a>
The error *... Connection dropped by server? ...* means that the email server unexpectedly terminated the connection. This sometimes happen when there were too many connections in a too short time or when a wrong password was used for too many times. In this case, please make sure your password is correct and disable receiving in the receive settings for about 30 minutes and try again. If needed, see [this FAQ](#user-content-faq23) about how you can reduce the number of connections.
@ -936,7 +942,7 @@ If you want to use the Gmail SMTP server to workaround a too strict outgoing spa
**Gmail errors**
La autorización de las cuentas de Gmail configuradas con el asistente de configuración rápida deben actualizarse periódicamente a través del [administrador de cuentas de Android](https://developer.android.com/reference/android/accounts/AccountManager). This requires contact/account permissions and internet connectivity.
The authorization of Gmail accounts setup with the quick wizard needs to be periodically refreshed via the [Android account manager](https://developer.android.com/reference/android/accounts/AccountManager). This requires contact/account permissions and internet connectivity.
The error *... Authentication failed ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
@ -944,7 +950,7 @@ The errors *... Authentication failed ... No token ...* means that the Android a
The error *... Authentication failed ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
The error *... Authentication failed ... Credenciales inválidas ...* podría ser causado al cambiar la contraseña de la cuenta o al haber revocado los permisos de cuenta/contactos requeridos. In case the account password was changed, you'll need to authenticate the Google account in the Android account settings again. En caso de que los permisos hayan sido revocados, puede iniciar el asistente de configuración rápida de Gmail para conceder los permisos necesarios de nuevo (no necesita configurar la cuenta de nuevo).
The error *... Authentication failed ... Invalid credentials ...* could be caused by changing the account password or by having revoked the required account/contacts permissions. In case the account password was changed, you'll need to authenticate the Google account in the Android account settings again. In case the permissions were revoked, you can start the Gmail quick setup wizard to grant the required permissions again (you don't need to setup the account again).
The eror *... ServiceDisabled ...* might be caused by enrolling in the [Advanced Protection Program](https://landing.google.com/advancedprotection/): "*To read your email, you can (must) use Gmail - You won’t be able to use your Google Account with some (all) apps & services that require access to sensitive data like your emails*", see [here](https://support.google.com/accounts/answer/7519408?hl=en&ref_topic=9264881).
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
* Ajouter un dossier au menu de navigation : appuyez longuement sur le dossier dans la liste des dossiers et cochez *Afficher dans le menu de navigation*
* Charger plus de messages : appuyez longuement sur un dossier dans la liste de dossiers, sélectionnez *Récupérer plus de messages*
* Supprimez un message, sautez la corbeille : dans le menu à 3 points juste au-dessus du texte du message *Supprimer* ou désélectionnez le dossier corbeille dans les paramètres du compte
* Delete an account/identity: Settings, tap Manual setup and more options, tap Accounts/Identities, three-dots menu, Delete
* Supprimer un compte: Paramètres > cliquer sur "gérer" dans Configurer les comptes > sélectionner le compte > menu à trois points > supprimer
* Supprimer un dossier : appuyez longuement sur le dossier dans la liste de dossiers > Modifier les propriétés > Menu à trois points > Supprimer
* Annuler l'envoi : Dans la boîte d'envoi, appuyez sur le message, appuyez sur l'icône d'annulation
* Stocker les messages envoyés dans la boîte de réception : veuillez [voir ceci dans FAQ](#user-content-faq142)
@ -282,7 +282,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
* [(161) Pouvez-vous ajouter un paramètre pour changer les couleurs primaire et d'accentuation ?](#user-content-faq161)
* [(162) L'IMAP NOTIFY est-il pris en charge ?](#user-content-faq162)
* [(163) Qu'est-ce que la classification des messages ?](#user-content-faq163)
* [(164) Can you add customizable themes?](#user-content-faq164)
* [(164) Pouvez-vous ajouter des thèmes personnalisables ?](#user-content-faq164)
[J’ai une autre question.](#user-content-support)
@ -390,15 +390,15 @@ Les opérations ne sont effectuées que lorsqu'il y a une connexion au serveur d
<br/>
*... Certificat de sécurité invalide (impossible de vérifier l'identité du serveur) ...*
This can be caused by using an incorrect host name, so first double check the host name in the advanced identity/account settings (tap Manual setup and more options). Please see the documentation of the email provider about the right host name.
Cela peut être dû à l'utilisation d'un nom de serveur incorrect, il faut donc d'abord vérifier le nom du serveur dans les paramètres avancés du compte/identité (Paramètres > "Gérer" dans configurer les comptes). Voir la documentation de votre fournisseur de messagerie concernant le nom du serveur.
You should try to fix this by contacting your provider or by getting a valid security certificate because invalid security certificates are insecure and allow [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). If money is an obstacle, you can get free security certificates from [Let’s Encrypt](https://letsencrypt.org).
Vous pouvez essayer de résoudre ce problème en contactant votre fournisseur de messagerie ou en obtenant un certificat de sécurité valide, car les certificats de sécurité non valides ne sont pas sécurisés et exposent aux attaques d'intermédiaires. Si l'argent est un problème, vous pouvez obtenir des certificats de sécurité gratuits auprès de [Let’s Encrypt](https://letsencrypt.org).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
Sinon, vous pouvez accepter l'empreinte digitale des certificats de serveur non valides comme ceci :
1. Assurez-vous que vous utilisez une connexion internet fiable (pas de réseaux Wi-Fi publics, etc)
1. Aller à l'écran de configuration rapide via le menu de navigation (Faites glisser depuis le côté gauche vers l'intérieur)
1. Tap Manual setup and more options, tap Accounts/Identities and tap the faulty account and identity
1. Paramètres/"Gérer" dans Configurer les comptes/sélectionner le compte défectueux
1. Contrôlez/enregistrez le compte et l'identité
1. Cochez la case en dessous du message d'erreur et enregistrez à nouveau
@ -453,7 +453,7 @@ In the display section of the settings you can enable or disable for example:
Note that messages can be previewed only when the message text was downloaded. Larger message texts are not downloaded by default on metered (generally mobile) networks. You can change this in the connection settings.
Some people ask:
Certaines personnes demandent :
* d'afficher l'objet en gras, mais l'affichage en gras est déjà utilisé pour mettre en évidence les messages non lus
* de déplacer l'étoile à gauche, mais il est beaucoup plus facile de manipuler l'étoile sur le côté droit
@ -461,12 +461,18 @@ Some people ask:
<br/>
<aname="faq6"></a>
**(6) How can I login to Gmail / G suite?**
**(6) Comment puis-je me connecter à Gmail / G suite ?**
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
Si vous utilisez la version Play Store ou GitHub de FairEmail, vous pouvez utiliser l'assistant de configuration rapide pour paramétrer facilement un compte Gmail et une identité. L'assistant de configuration rapide de Gmail n'est pas disponible pour les versions tierces, comme la version F-Droid, car Google n'a approuve l'utilisation d'OAuth que pour les versions officielles.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -1024,15 +1030,15 @@ If you would like your name or alias to be included in the list of contributors
Note that downloading external images from a remote server can be used to record you did see a message, which you likely don't want if the message is spam or malicious.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
* Ajouter un dossier au menu de navigation : appuyez longuement sur le dossier dans la liste des dossiers et cochez *Afficher dans le menu de navigation*
* Charger plus de messages : appuyez longuement sur un dossier dans la liste de dossiers, sélectionnez *Récupérer plus de messages*
* Supprimez un message, sautez la corbeille : dans le menu à 3 points juste au-dessus du texte du message *Supprimer* ou désélectionnez le dossier corbeille dans les paramètres du compte
* Delete an account/identity: Settings, tap Manual setup and more options, tap Accounts/Identities, three-dots menu, Delete
* Supprimer un compte: Paramètres > cliquer sur "gérer" dans Configurer les comptes > sélectionner le compte > menu à trois points > supprimer
* Supprimer un dossier : appuyez longuement sur le dossier dans la liste de dossiers > Modifier les propriétés > Menu à trois points > Supprimer
* Annuler l'envoi : Dans la boîte d'envoi, appuyez sur le message, appuyez sur l'icône d'annulation
* Stocker les messages envoyés dans la boîte de réception : veuillez [voir ceci dans FAQ](#user-content-faq142)
@ -282,7 +282,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
* [(161) Pouvez-vous ajouter un paramètre pour changer les couleurs primaire et d'accentuation ?](#user-content-faq161)
* [(162) L'IMAP NOTIFY est-il pris en charge ?](#user-content-faq162)
* [(163) Qu'est-ce que la classification des messages ?](#user-content-faq163)
* [(164) Can you add customizable themes?](#user-content-faq164)
* [(164) Pouvez-vous ajouter des thèmes personnalisables ?](#user-content-faq164)
[J’ai une autre question.](#user-content-support)
@ -390,15 +390,15 @@ Les opérations ne sont effectuées que lorsqu'il y a une connexion au serveur d
<br/>
*... Certificat de sécurité invalide (impossible de vérifier l'identité du serveur) ...*
This can be caused by using an incorrect host name, so first double check the host name in the advanced identity/account settings (tap Manual setup and more options). Please see the documentation of the email provider about the right host name.
Cela peut être dû à l'utilisation d'un nom de serveur incorrect, il faut donc d'abord vérifier le nom du serveur dans les paramètres avancés du compte/identité (Paramètres > "Gérer" dans configurer les comptes). Voir la documentation de votre fournisseur de messagerie concernant le nom du serveur.
You should try to fix this by contacting your provider or by getting a valid security certificate because invalid security certificates are insecure and allow [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). If money is an obstacle, you can get free security certificates from [Let’s Encrypt](https://letsencrypt.org).
Vous pouvez essayer de résoudre ce problème en contactant votre fournisseur de messagerie ou en obtenant un certificat de sécurité valide, car les certificats de sécurité non valides ne sont pas sécurisés et exposent aux attaques d'intermédiaires. Si l'argent est un problème, vous pouvez obtenir des certificats de sécurité gratuits auprès de [Let’s Encrypt](https://letsencrypt.org).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
Sinon, vous pouvez accepter l'empreinte digitale des certificats de serveur non valides comme ceci :
1. Assurez-vous que vous utilisez une connexion internet fiable (pas de réseaux Wi-Fi publics, etc)
1. Aller à l'écran de configuration rapide via le menu de navigation (Faites glisser depuis le côté gauche vers l'intérieur)
1. Tap Manual setup and more options, tap Accounts/Identities and tap the faulty account and identity
1. Paramètres/"Gérer" dans Configurer les comptes/sélectionner le compte défectueux
1. Contrôlez/enregistrez le compte et l'identité
1. Cochez la case en dessous du message d'erreur et enregistrez à nouveau
@ -453,7 +453,7 @@ In the display section of the settings you can enable or disable for example:
Note that messages can be previewed only when the message text was downloaded. Larger message texts are not downloaded by default on metered (generally mobile) networks. You can change this in the connection settings.
Some people ask:
Certaines personnes demandent :
* d'afficher l'objet en gras, mais l'affichage en gras est déjà utilisé pour mettre en évidence les messages non lus
* de déplacer l'étoile à gauche, mais il est beaucoup plus facile de manipuler l'étoile sur le côté droit
@ -461,12 +461,18 @@ Some people ask:
<br/>
<aname="faq6"></a>
**(6) How can I login to Gmail / G suite?**
**(6) Comment puis-je me connecter à Gmail / G suite ?**
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
Si vous utilisez la version Play Store ou GitHub de FairEmail, vous pouvez utiliser l'assistant de configuration rapide pour paramétrer facilement un compte Gmail et une identité. L'assistant de configuration rapide de Gmail n'est pas disponible pour les versions tierces, comme la version F-Droid, car Google n'a approuve l'utilisation d'OAuth que pour les versions officielles.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -1024,15 +1030,15 @@ If you would like your name or alias to be included in the list of contributors
Note that downloading external images from a remote server can be used to record you did see a message, which you likely don't want if the message is spam or malicious.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. Per usare una password dovrai configurar un profilo e un'identità tramite la configurazione manuale invece che tramite la procedura guidata rapida.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -607,7 +613,7 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
**Important**: the OpenKeychain app is known to (silently) crash when the calling app (FairEmail) is not authorized yet and is getting an existing public key. You can workaround this by trying to send a signed/encrypted message to a sender with an unknown public key.
**Important**: if the OpenKeychain app cannot find a key (anymore), you might need to reset a previously selected key. Questo può essere fatto premendo a lungo un'identità nell'elenco delle identità (Impostazioni, clicca Configurazione manuale ed altre opzioni, clicca Identità).
**Important**: if the OpenKeychain app cannot find a key (anymore), you might need to reset a previously selected key. This can be done by long pressing an identity in the list of identities (Settings, tap Manual setup and more options, tap Identities).
**Important**: to let apps like FairEmail reliably connect to the OpenKeychain service to encrypt/decrypt messages, it might be necessary to disable battery optimizations for the OpenKeychain app.
@ -781,7 +787,7 @@ On some devices, where there are lots of applications competing for memory, Andr
Some Android versions stop apps and services too aggressively. See [this dedicated website](https://dontkillmyapp.com/) and [this Android issue](https://issuetracker.google.com/issues/122098785) for more information.
Disabilitare le ottimizzazioni della batteria (passaggio 3 della configurazione) riduce la possibilità che Android interromperà il servizio di sincronizzazione.
Disabling battery optimizations (setup step 3) reduces the chance Android will stop the synchronization service.
In case of successive connection errors, FairEmail will hold off increasingly longer to not drain the battery of your device. This is described in [this FAQ](#user-content-faq123).
@ -855,9 +861,9 @@ There are general errors and errors specific to Gmail accounts (see below).
**General errors**
<aname="authfailed"></a>
L'errore*... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
The error*... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
The error*... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Sei pregato di vedere [questo FAQ](#user-content-faq88) su come configurare un profilo di Yahoo.
L'errore*... 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 set up a Yahoo account.
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
@ -865,11 +871,11 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
L'errore *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
L'errore*... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
The error*... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
L'errore*... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
The error*... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
L'errore*... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
The error*... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
@ -1041,7 +1047,7 @@ Note that downloading external images from a remote server can be used to record
<aname="faq28"></a>
**(28) How can I manage status bar notifications?**
Nella configurazione troverai il pulsante *Gestione notifiche* per navigare direttamente alle impostazioni di notifica di Android per FairEmail.
In the notification settings you'll find a button *Manage notifications* to directly navigate to the Android notifications settings for FairEmail.
On Android 8.0 Oreo and later you can manage the properties of the individual notification channels, for example to set a specific notification sound or to show notifications on the lock screen.
@ -1083,7 +1089,7 @@ Quick settings require Android 7.0 Nougat or later. The usage of settings tiles
<aname="faq31"></a>
**(31) How can I use the provided shortcuts?**
Ci sono scorciatoie disponibili per comporre un nuovo messaggio a un contatto preferito.
There are shortcuts available to compose a new message to a favorite contact.
Shortcuts require Android 7.1 Nougat or later. The usage of shortcuts is explained [here](https://support.google.com/android/answer/2781850).
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
@ -467,6 +467,12 @@ If you use the Play store or GitHub version of FairEmail, you can use the quick
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
This Google security check is triggered more often with *less secure apps* enabled, less with an app password, and hardly when using an on-device account (OAuth).
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Note that an app specific password is required when two factor authentication is enabled.
@ -2358,9 +2364,15 @@ Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
*Send user unknown (version 1.1477+)*
<br/>
*Send hard bounce (version 1.1477+)*
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) (=hard bounce) via the reply/answer menu.
Hard bounces will mostly be processed automatically because they affect the reputation of the email provider. The bounce address (=*Return-Path* header) is mostly very specific, so the email server can determine the sending account.
Send a [Delivery Status Notification](https://tools.ietf.org/html/rfc3464) *User unknown* via the answer menu.
For some background, see for [this Wikipedia article](https://en.wikipedia.org/wiki/Bounce_message).
M66B
3 years ago