mirror
/
FairEmail
mirror of https://github.com/M66B/FairEmail.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Crowdin sync

This commit is contained in:
M66B 2021-03-09 13:25:36 +01:00
parent 306f27ba54
commit 6173d300dc
60 changed files with 387 additions and 438 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
app/src/main/assets/SETUP-vi-rVN.md
View File

@ -8,19 +8,19 @@ Yêu cầu kết nối internet để thiết lập các tài khoản và danh t
## Thiết lập nhanh
Just select the appropriate provider or *Other provider* and enter your name, email address and password and tap *Check*.
Chỉ cần chọn nhà cung cấp phù hợp hoặc *Nhà cung cấp khác* và nhập tên, địa chỉ email và mật khẩu của bạn và nhấn *Kiểm tra*.
This will work for most email providers.
Việc này sẽ được đối với đa số nhà cung cấp email.
If the quick setup doesn't work, you'll need to set up an account and an identity manually, see below for instructions.
Nếu thiết lập nhanh không được, bạn sẽ cần thiết lập một tài khoản và một danh tính thủ công, hãy xem hướng dẫn ở dưới.
## Set up account - to receive email
## Thiết lập tài khoản - để nhận email
To add an account, tap *Manual setup and more options*, tap *Accounts* and tap the 'plus' button at the bottom and select IMAP (or POP3). Select a provider from the list, enter the username, which is mostly your email address and enter your password. Tap *Check* to let FairEmail connect to the email server and fetch a list of system folders. After reviewing the system folder selection you can add the account by tapping *Save*.
If your provider is not in the list of providers, there are thousands of providers, select *Custom*. Enter the domain name, for example *gmail.com* and tap *Get settings*. If your provider supports [auto-discovery](https://tools.ietf.org/html/rfc6186), FairEmail will fill in the host name and port number, else check the setup instructions of your provider for the right IMAP host name, port number and encryption protocol (SSL/TLS or STARTTLS). For more about this, please see [here](https://github.com/M66B/FairEmail/blob/master/FAQ.md#authorizing-accounts).
Nếu nhà cung cấp của bạn không ở trong danh sách các nhà cung cấp, có hàng nghìn nhà cung cấp, chọn *Tùy chỉnh*. Nhập tên miền, ví dụ *gmail.com* và nhấn *Lấy cài đặt*. If your provider supports [auto-discovery](https://tools.ietf.org/html/rfc6186), FairEmail will fill in the host name and port number, else check the setup instructions of your provider for the right IMAP host name, port number and encryption protocol (SSL/TLS or STARTTLS). For more about this, please see [here](https://github.com/M66B/FairEmail/blob/master/FAQ.md#authorizing-accounts).
## Set up identity - to send email
## Thiết lập danh tính - để gửi email
Similarly, to add an identity, tap *Manual setup and more options*, tap *Identities* and tap the 'plus' button at the bottom. Enter the name you want to appear in the from address of the emails you send and select a linked account. Tap *Save* to add the identity.
@ -28,11 +28,11 @@ If the account was configured manually, you likely need to configure the identit
See [this FAQ](https://github.com/M66B/FairEmail/blob/master/FAQ.md#FAQ9) about using aliases.
## Grant permissions - to access contact information
## Cấp quyền - để truy cập thông tin liện hệ
If you want to lookup email addresses, have contact photos shown, etc, you'll need to grant permission to read contact information to FairEmail. Just tap *Grant* and select *Allow*.
## Setup battery optimizations - to continuously receive emails
## Thiết lập tối ưu hoá pin - để nhận email liên tục
On recent Android versions, Android will put apps to sleep when the screen is off for some time to reduce battery usage. If you want to receive new emails without delays, you should disable battery optimizations for FairEmail. Tap *Manage* and follow the instructions.

6
app/src/main/res/values-fr-rCA/strings.xml
View File

@ -1407,9 +1407,9 @@
<item>512 Ko</item>
<item>1 Mo</item>
<item>2 Mo</item>
<item>4 MB</item>
<item>8 MB</item>
<item>16 MB</item>
<item>4 Mo</item>
<item>8 Mo</item>
<item>16 Mo</item>
<item comment="downloadNames&#10;∞ = infinite (size)">∞</item>
</string-array>
<string-array name="onCloseNames">

6
app/src/main/res/values-fr-rFR/strings.xml
View File

@ -1407,9 +1407,9 @@
<item>512 Ko</item>
<item>1 Mo</item>
<item>2 Mo</item>
<item>4 MB</item>
<item>8 MB</item>
<item>16 MB</item>
<item>4 Mo</item>
<item>8 Mo</item>
<item>16 Mo</item>
<item comment="downloadNames&#10;∞ = infinite (size)">∞</item>
</string-array>
<string-array name="onCloseNames">

8
app/src/main/res/values-ro-rRO/strings.xml
View File

@ -136,6 +136,7 @@
<string name="title_setup_wizard">Asistent</string>
<string name="title_setup_wizard_multiple">Asistentul poate fi folosit de mai multe ori pentru a configura conturi multiple</string>
<string name="title_setup_wizard_new">Am nevoie de o nouă adresă de e-mail</string>
<string name="title_setup_manual">Setări manuale și opțiuni cont</string>
<string name="title_setup_account_remark">Primire e-mail</string>
<string name="title_setup_identity_remark">Trimitere e-mail</string>
<string name="title_setup_account_identity_hint">Puteți configura numele, culoarea și acțiunile de glisare în setările contului și puteți configura o semnătură în setările de identitate</string>
@ -230,6 +231,7 @@
<string name="title_advanced_hint_message"> Navigați la opțiunile mai avansate.
Toate opțiunile au utilizat în mod obișnuit valori standard, pe care nu trebuie să o schimbați decât dacă aveți o preferință diferită.
</string>
<string name="title_advanced_section_main">Principal</string>
<string name="title_advanced_section_synchronize">Primire</string>
<string name="title_advanced_section_send">Trimitere</string>
<string name="title_advanced_section_connection">Conexiune</string>
@ -1417,9 +1419,9 @@
<item>512 Ko</item>
<item>1 Mo</item>
<item>2 Mo</item>
<item>4 MB</item>
<item>8 MB</item>
<item>16 MB</item>
<item>4 Mo</item>
<item>8 Mo</item>
<item>16 Mo</item>
<item comment="downloadNames&#10;∞ = infinite (size)">∞</item>
</string-array>
<string-array name="onCloseNames">

6
app/src/main/res/values-ru-rRU/strings.xml
View File

@ -1431,9 +1431,9 @@
<item>512 КБ</item>
<item>1 МБ</item>
<item>2 МБ</item>
<item>4 MB</item>
<item>8 MB</item>
<item>16 MB</item>
<item>4 МБ</item>
<item>8 МБ</item>
<item>16 МБ</item>
<item comment="downloadNames&#10;∞ = infinite (size)">∞</item>
</string-array>
<string-array name="onCloseNames">

1
app/src/main/res/values-vi-rVN/strings.xml
View File

@ -430,6 +430,7 @@
<string name="title_advanced_no_date_hint">Một số nhà cung cấp lưu trữ các thư có ngày không xác định, không hợp lệ hoặc trong tương lai là thư không có ngày</string>
<string name="title_advanced_unseen_hint">Một số nhà cung cấp không hỗ trợ điều này đúng cách, điều đó có thể gây ra không đồng bộ hoá thư nào hoặc đồng bộ tất cả thư</string>
<string name="title_advanced_deleted_unseen">Khi được tắt, các thư chưa đọc được giữ trên thiết bị vĩnh viễn</string>
<string name="title_advanced_gmail_thread_hint">Cái này chỉ áp dụng cho các thư mới nhận và có thể làm hỏng các nhóm đang tồn tại</string>
<string name="title_advanced_sync_folders_hint">Việc tắt cái này sẽ làm giảm phần nào sử dụng dữ liệu và pin, nhưng cũng sẽ tắt việc cập nhật các thư mục</string>
<string name="title_advanced_check_reply_hint">Cái này sẽ kiểm tra xem tên miền của người gửi và địa chỉ trả lời có như nhau không</string>
<string name="title_advanced_lookup_mx_hint">Cái này sẽ kiểm tra xem các bản ghi DNS MX có tồn tại không</string>

7
docs/FAQ-af-rZA.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ar-rBH.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ar-rEG.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ar-rYE.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-az-rAZ.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-bg-rBG.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-bn-rBD.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-bn-rIN.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

9
docs/FAQ-ca-rES.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2184,7 +2187,7 @@ Depending on what you want, the notification settings *Let the number of new mes
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Algunos lanzadores muestran un punto o un '1' para el monitoreo de la notificación a pesar de que FairEmail pida explícitamente que no se muestre insignia para esta notificación. This could be caused by a bug in the launcher app or in your Android version. Por favor comprueba si el punto de notificación (insignia) está deshabilitado para el canal de notificación (servicio). You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Some launchers display a dot or a '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a *badge* for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot (badge) is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
FairEmail does send a new message count intent as well:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

9
docs/FAQ-cs-rCZ.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -539,7 +541,7 @@ Note that the desciption of FairEmail starts with the remark that non-standard p
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.
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Pro provizorní řešení se prosím podívejte na [tento nejčastější dotaz](#user-content-faq110).
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
Please see [this FAQ](#user-content-faq133) about ActiveSync support.
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

25
docs/FAQ-da-rDK.md
View File

@ -398,6 +398,8 @@ Dette kan skyldes brug af et forkert værtsnavn, så dobbelttjek først værtsna
Dette bør forsøges løst ved at kontakte udbyderen eller ved at få et gyldigt sikkerhedscertifikat, da ugyldige sikkerhedscertifikater er usikre og tillader [mand-i-midten-angreb](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Er penge en hindring, kan et gratis sikkerhedscertifikater erhverves fra [Let's Encrypt](https://letsencrypt.org).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Sørg for at benytt en betroet Internetforbindelse (ingen offentlige Wi-Fi netværk mv.)
@ -406,19 +408,19 @@ Alternatively, you can accept the fingerprint of invalid server certificates lik
1. Tjek/gem kontoen og identiteten
1. Markér afkrydsningsfeltet under fejlmeddelelsen og gem igen
Dette vil "fiksere" servercertifikatet for at forhindre mand-i-midten angreb.
This will "pin" the server certificate to prevent man-in-the-middle attacks.
Bemærk, at ældre Android-versioner muligvis ikke genkender nyere certificeringsmyndigheder såsom Let’s Encrypt, og forbindelser derfor kan blive betragtet som usikre. Tjek også [hér](https://developer.android.com/training/articles/security-ssl).
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
*Tillidsanker til certificeringssti ikke fundet*
*Trust anchor for certification path not found*
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found...* betyder, at Androids standard tillidshåndtering ikke kunne bekræfte servercertifikatkæden.
*... java.security.cert.CertPathValidatorException: Trust anchor for certification path not found ...* means that the default Android trust manager was not able to verify the server certificate chain.
Enten bør serveropsætningen rettes eller fingeraftrykket vist neden for fejlmeddelelsen accepteres.
You should either fix the server configuration or accept the fingerprint shown below the error message.
Bemærk, at dette problem kan skyldes af, at serveren ikke sender alle mellemliggende certifikater.
Note that this problem can be caused by the server not sending all intermediate certificates too.
*Kryptere adgangskode*
*Empty password*
Your username is likely easily guessed, so this is insecure.
@ -469,7 +471,7 @@ Some people ask:
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.
Vil/kan der ikke bruges en enhedsbaseret Gmail-konto på f.eks. nyere Huawei-enheder, aktivér da enten adgang for "mindre sikre apps" med brug af kontoadgangskode (ikke anbefalet), eller tofaktorgodkendelse med brug af en app-specifik adgangskode. 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.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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:
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *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 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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2184,7 +2187,7 @@ Depending on what you want, the notification settings *Let the number of new mes
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Visse launchers viser en prik eller '1'' for [moniteringsnotifikationen](#user-content-faq2) trods FairEmails eksplicitte anmodning om íkke om at vise et *badge* til denne notifikation. This could be caused by a bug in the launcher app or in your Android version. Dobbelttjek, at notifikationsprikken (badge) er deaktiveret for notifikationsmodtagelseskanalen (tjenesten). You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Some launchers display a dot or a '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a *badge* for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot (badge) is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
FairEmail does send a new message count intent as well:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

15
docs/FAQ-de-rAT.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Stellen Sie sicher, dass Sie eine vertrauenswürdige Internetverbindung verwenden (keine öffentlichen WLAN-Netzwerke, etc)
@ -469,7 +471,7 @@ Some people ask:
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.
Wenn Sie kein Gmail-Konto auf dem Gerät verwenden möchten oder können, z. B. auf neueren Huawei-Geräten, können Sie entweder den Zugriff für „weniger sichere Apps” aktivieren und Ihr Kontenpasswort verwenden (nicht empfohlen) oder die Zwei-Faktor-Authentifizierung aktivieren und ein appspezifisches Passwort verwenden. 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.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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:
@ -906,7 +908,7 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
Der Fehler *… 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.
Der Fehler *… 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.
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.
@ -929,7 +931,7 @@ The error *... connection failure ...* could indicate [Too many simultaneous con
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.
Der Fehler * … Anmelderaten-Beschränkung überschritten …* bedeutet, dass es zu viele Anmeldeversuche mit einem falschen Passwort gab. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
The error *... Login Rate Limit Hit ...* means that there were too many login attempts with an incorrect password. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
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 ...*
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2184,7 +2187,7 @@ Depending on what you want, the notification settings *Let the number of new mes
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Einige Launcher zeigen einen Punkt oder eine '1' für [die Überwachungsbenachrichtigung](#user-content-faq2) an, obwohl FairEmail ausdrücklich fordert, für diese Benachrichtigung kein *Benachrichtigung* anzuzeigen. This could be caused by a bug in the launcher app or in your Android version. Bitte überprüfen Sie, ob der Benachrichtigungspunkt (Badge) für den Empfangs-Benachrichtigungskanal (Dienst) deaktiviert ist. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Some launchers display a dot or a '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a *badge* for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot (badge) is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
FairEmail does send a new message count intent as well:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

15
docs/FAQ-de-rDE.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Stellen Sie sicher, dass Sie eine vertrauenswürdige Internetverbindung verwenden (keine öffentlichen WLAN-Netzwerke, etc)
@ -469,7 +471,7 @@ Some people ask:
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.
Wenn Sie kein Gmail-Konto auf dem Gerät verwenden möchten oder können, z. B. auf neueren Huawei-Geräten, können Sie entweder den Zugriff für „weniger sichere Apps” aktivieren und Ihr Kontenpasswort verwenden (nicht empfohlen) oder die Zwei-Faktor-Authentifizierung aktivieren und ein appspezifisches Passwort verwenden. 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.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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:
@ -906,7 +908,7 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
Der Fehler *… 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.
Der Fehler *… 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.
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.
@ -929,7 +931,7 @@ The error *... connection failure ...* could indicate [Too many simultaneous con
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.
Der Fehler * … Anmelderaten-Beschränkung überschritten …* bedeutet, dass es zu viele Anmeldeversuche mit einem falschen Passwort gab. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
The error *... Login Rate Limit Hit ...* means that there were too many login attempts with an incorrect password. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
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 ...*
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2184,7 +2187,7 @@ Depending on what you want, the notification settings *Let the number of new mes
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Einige Launcher zeigen einen Punkt oder eine '1' für [die Überwachungsbenachrichtigung](#user-content-faq2) an, obwohl FairEmail ausdrücklich fordert, für diese Benachrichtigung kein *Benachrichtigung* anzuzeigen. This could be caused by a bug in the launcher app or in your Android version. Bitte überprüfen Sie, ob der Benachrichtigungspunkt (Badge) für den Empfangs-Benachrichtigungskanal (Dienst) deaktiviert ist. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Some launchers display a dot or a '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a *badge* for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot (badge) is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
FairEmail does send a new message count intent as well:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

15
docs/FAQ-de-rLI.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Stellen Sie sicher, dass Sie eine vertrauenswürdige Internetverbindung verwenden (keine öffentlichen WLAN-Netzwerke, etc)
@ -469,7 +471,7 @@ Some people ask:
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.
Wenn Sie kein Gmail-Konto auf dem Gerät verwenden möchten oder können, z. B. auf neueren Huawei-Geräten, können Sie entweder den Zugriff für „weniger sichere Apps” aktivieren und Ihr Kontenpasswort verwenden (nicht empfohlen) oder die Zwei-Faktor-Authentifizierung aktivieren und ein appspezifisches Passwort verwenden. 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.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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:
@ -906,7 +908,7 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
Der Fehler *… 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.
Der Fehler *… 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.
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.
@ -929,7 +931,7 @@ The error *... connection failure ...* could indicate [Too many simultaneous con
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.
Der Fehler * … Anmelderaten-Beschränkung überschritten …* bedeutet, dass es zu viele Anmeldeversuche mit einem falschen Passwort gab. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
The error *... Login Rate Limit Hit ...* means that there were too many login attempts with an incorrect password. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
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 ...*
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2184,7 +2187,7 @@ Depending on what you want, the notification settings *Let the number of new mes
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Einige Launcher zeigen einen Punkt oder eine '1' für [die Überwachungsbenachrichtigung](#user-content-faq2) an, obwohl FairEmail ausdrücklich fordert, für diese Benachrichtigung kein *Benachrichtigung* anzuzeigen. This could be caused by a bug in the launcher app or in your Android version. Bitte überprüfen Sie, ob der Benachrichtigungspunkt (Badge) für den Empfangs-Benachrichtigungskanal (Dienst) deaktiviert ist. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Some launchers display a dot or a '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a *badge* for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot (badge) is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
FairEmail does send a new message count intent as well:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-el-rGR.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-en-rGB.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-es-rES.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Asegúrese de estar usando una conexión a internet de confianza (no redes Wi-Fi publicas, etc.)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-eu-rES.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-fa-rIR.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

9
docs/FAQ-fi-rFI.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -418,7 +420,7 @@ You should either fix the server configuration or accept the fingerprint shown b
Note that this problem can be caused by the server not sending all intermediate certificates too.
*Tyhjä salasana*
*Empty password*
Your username is likely easily guessed, so this is insecure.
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

171
docs/FAQ-fr-rCA.md
View File

@ -398,6 +398,8 @@ Ceci peut être dû à l'utilisation d'un nom de serveur incorrect, donc vérifi
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Assurez-vous que vous utilisez une connexion internet fiable (pas de réseaux Wi-Fi publics, etc)
@ -406,7 +408,7 @@ Alternatively, you can accept the fingerprint of invalid server certificates lik
1. Contrôlez/enregistrez le compte et l'identité
1. Cochez la case en dessous du message d'erreur et enregistrez à nouveau
Ceci va « épingler » le certificat du serveur pour éviter les attaques de l'homme du milieu.
This will "pin" the server certificate to prevent man-in-the-middle attacks.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@ -418,11 +420,11 @@ You should either fix the server configuration or accept the fingerprint shown b
Note that this problem can be caused by the server not sending all intermediate certificates too.
*Mot de passe vide*
*Empty password*
Votre nom d'utilisateur est probablement facilement deviné, donc ce n'est pas sûr.
Your username is likely easily guessed, so this is insecure.
*Connexion en texte brut*
*Plain text connection*
Your username and password and all messages will be sent and received unencrypted, which is **very insecure** because a [man-in-the-middle attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) is very simple on an unencrypted connection.
@ -431,14 +433,14 @@ If you still want to use an invalid security certificate, an empty password or a
<br />
<a name="faq5"></a>
Comment personnaliser l'affichage des messages
**(5) How can I customize the message view?**
Dans le menu à trois points, vous pouvez activer ou désactiver ou sélectionner :
In the three dot overflow menu you can enable or disable or select:
* *taille de texte* : pour trois tailles de police différentes
* *Vue compacte* : pour des éléments de message plus condensés et une police de texte de message plus petite
Dans la section "Affichage" vous pouvez activer ou désactiver par exemple :
In the display section of the settings you can enable or disable for example:
* *Boîte de réception unifiée* : pour désactiver la boîte de réception unifiée et pour lister les dossiers sélectionnés pour la boîte de réception unifiée
* *Style tabulaire*: afficher une liste linéaire au lieu de cartes
@ -455,9 +457,9 @@ Dans la section "Affichage" vous pouvez activer ou désactiver par exemple :
* *Afficher automatiquement le message original pour les contacts connus*: pour automatiquement afficher les messages originaux pour les contacts de votre appareil, merci de lire [cette FAQ](#user-content-faq35)
* *Afficher automatiquement les images pour les contacts connus*: pour automatiquement afficher les images pour les contacts de votre appareil, merci de lire[cette FAQ](#user-content-faq35)
Attention, les messages ne peuvent être prévisualisés que lorsque le texte du message a été téléchargé. Par défaut, les messages textes les plus volumineux ne sont pas téléchargés sur les réseaux limités (généralement mobiles). Ceci peut être changé dans la section "Connexion" des paramètres.
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.
Certaines personnes demandent :
Some people ask:
* 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
@ -465,62 +467,62 @@ Certaines personnes demandent :
<br />
<a name="faq6"></a>
**(6) Comment puis-je me connecter à Gmail / G suite ?**
**(6) How can I login to Gmail / G suite?**
Si vous utilisez la version Play Store ou GitHub de FairEmail, vous pouvez utiliser l'assistant de configuration rapide pour configurer 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, parce que Google n'a approuve l'utilisation d'OAuth que pour les versions officielles.
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 ne voulez pas ou ne pouvez pas utiliser un compte Google sur votre appareil, par exemple sur les appareils Huawei récents, vous pouvez soit activer l'accès pour les « applications moins sécurisées » et utiliser le mot de passe de votre compte (non conseillé), soit activer l'authentification en deux étapes et utiliser un mot de passe spécifique à l'application. Pour utiliser un mot de passe, vous devrez configurer manuellement un compte et une identité au lieu de l’assistant de configuration rapide.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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**: parfois Google publie cette alerte :
**Important**: sometimes Google issues this alert:
*[ALERT] Veuillez vous connecter via votre navigateur web : https://support.google.com/mail/accounts/answer/78754 (Echec)*
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
Cette vérification de sécurité de Google est plus souvent déclenchée lorsque l'option *applications moins sécurisées* est activée. Elle l'est moins avec un mot de passe d'application et elle est presque jamais déclenchée lorsque vous utilisez un compte sur l'appareil (OAuth).
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).
Veuillez consulter [cette FAQ](#user-content-faq111) pour savoir pourquoi seuls les comptes sur l'appareil peuvent être utilisés.
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Notez qu'un mot de passe spécifique à l'application est nécessaire lorsque l'authentification à deux facteurs est activée.
Note that an app specific password is required when two factor authentication is enabled.
<br />
*Mot de passe spécifique à l'application*
*App specific password*
Voir [ici](https://support.google.com/accounts/answer/185833) sur la façon de générer un mot de passe spécifique à l'application.
See [here](https://support.google.com/accounts/answer/185833) about how to generate an app specific password.
<br />
*Autoriser les "Applications moins sécurisées"*
*Enable "Less secure apps"*
**Important **: l'utilisation de cette méthode n'est pas recommandée car elle est moins fiable.
**Important**: using this method is not recommended because it is less reliable.
**Important **: Les comptes Gsuite autorisés avec un nom d'utilisateur/mot de passe cesseront de fonctionner [dans un avenir proche](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).
Voir [ici](https://support.google.com/accounts/answer/6010255) comment autoriser les "applications moins sécurisées" ou aller [directement au paramètre en question](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 vous utilisez plusieurs comptes Gmail, assurez-vous de modifier le paramètre "Autoriser les applications moins sécurisées" du ou des comptes concernés.
If you use multiple Gmail accounts, make sure you change the "less secure apps" setting of the right account(s).
Sachez que vous devez quitter l'écran de paramétrage des "applications moins sécurisées" en utilisant la flèche de retour arrière pour que le paramètre soit appliqué.
Be aware that you need to leave the "less secure apps" settings screen by using the back arrow to apply the setting.
Si vous utilisez cette méthode, vous devriez utiliser un [mot de passe robuste](https://en.wikipedia.org/wiki/Password_strength) pour votre compte Gmail, ce qui est de toute façon une bonne idée. Notez que l'utilisation du protocole [standard](https://tools.ietf.org/html/rfc3501) IMAP n'est en soi pas moins sécurisée.
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.
Lorsque les "applications moins sécurisées" ne sont pas activées, vous obtiendrez l'erreur *L'authentification a échoué - identifiants non valides* pour les comptes (IMAP) et *nom d'utilisateur et mot de passe non acceptés* pour les identités (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 />
*Général*
*General*
Il se peut que vous obteniez l'alerte "*S'il vous plaît connectez-vous via votre navigateur web*". This happens when Google considers the network that connects you to the internet (this could be a VPN) to be unsafe. Ceci peut être évité en utilisant l'assistant de configuration rapide de Gmail ou un mot de passe spécifique d'application.
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.
Voir [ici](https://support.google.com/mail/answer/7126229) pour les instructions de Google et [ici](https://support.google.com/mail/accounts/answer/78754) pour le dépannage.
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 />
<a name="faq7"></a>
**(7) Pourquoi les messages envoyés n'apparaissent-ils pas (directement) dans le dossier « Envoyés » ? **
**(7) Why are sent messages not appearing (directly) in the sent folder?**
Les messages envoyés sont normalement déplacés de la boîte d'envoi vers le dossier Envoyés dès que votre fournisseur ajoute les messages envoyés au dossier Envoyés. Ceci nécessite qu'un dossier Envoyés soit sélectionné dans les paramètres du compte et que le dossier Envoyés soit configuré pour être synchronisé.
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.
Certains fournisseurs ne gardent pas de trace des messages envoyés ou le serveur SMTP utilisé peut ne pas être lié au fournisseur. Dans ce cas, FairEmail ajoutera automatiquement les messages envoyés au dossier Envoyés lors de la synchronisation du dossier Envoyés qui se produira après l'envoi d'un message. Notez que cela entraînera un trafic Internet supplémentaire.
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.
~~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.~~
@ -548,7 +550,7 @@ Please see [this FAQ](#user-content-faq111) about OAuth support.
<br />
<a name="faq9"></a>
**(9) Qu'est-ce que les identités / Comment ajouter un alias ?**
**(9) What are identities / how do I add an alias?**
Identities represent email addresses you are sending *from* via an email (SMTP) server.
@ -565,14 +567,14 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
<br />
<a name="faq10"></a>
**~~(10) Que signifie "UIDPLUS n'est pas pris en charge" ?~~**
**~~(10) What does 'UIDPLUS not supported' mean?~~**
~~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 />
<a name="faq11"></a>
**~~(11) Pourquoi POP n'est pas pris en charge ?~~**
**~~(11) Why is POP not supported?~~**
~~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.~~
@ -587,57 +589,57 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
<br />
<a name="faq12"></a>
**(12) Comment fonctionne le chiffrement/déchiffrement ?**
**(12) How does encryption/decryption work?**
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.
<br />
*Général*
*General*
Veuillez [voir ici](https://en.wikipedia.org/wiki/Public-key_cryptography) le fonctionnement du chiffrement par des clé publique/privée.
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
Chiffrement en bref :
Encryption in short:
* Les messages **sortants** sont chiffrés avec la **clé publique** du destinataire
* Les messages **entrants** sont déchiffrés avec la **clé privée** du destinataire
Signature en bref :
Signing in short:
* Les messages **sortants** sont signés avec la **clé privée** de l'expéditeur
* Les messages **entrants** sont vérifiés avec la **clé publique** de l'expéditeur
Pour signer/chiffrer un message, il suffit de sélectionner la méthode appropriée dans la boîte de dialogue d'envoi. Vous pouvez toujours ouvrir la boîte de dialogue d'envoi en utilisant le menu déroulant symbolisé par trois points dans le cas où vous aviez sélectionné *Ne plus afficher* avant.
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.
Pour vérifier une signature ou déchiffrer un message reçu, ouvrez le message et appuyez sur l'icône du geste ou du cadenas juste en dessous de la barre d'action du message.
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 première fois que vous envoyez un message signé/chiffré, il se peut que l'on vous demande une clé de signature. FairEmail stockera automatiquement la clé de signature sélectionnée dans l'identité utilisée pour la prochaine fois. Si vous avez besoin de réinitialiser la clé de signature, enregistrez simplement l'identité ou appuyez longuement sur l'identité dans la liste des identités et sélectionnez *réinitialiser la clé de signature*. La clé de signature sélectionnée est visible dans la liste des identités. Si vous avez besoin de sélectionner une clé cas par cas, vous pouvez créer plusieurs identités pour le même compte avec la même adresse e-mail.
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.
Dans les paramètres de chiffrement, vous pouvez sélectionner la méthode de cryptage par défaut (PGP ou S/MIME), activer *Signer par défaut*, *Chiffrer par défaut* et *Déchiffrer automatiquement les messages*, mais sachez que le décryptage automatique n'est pas possible si l'interaction de l'utilisateur est requise, comme la sélection d'une clé ou la lecture d'un jeton de sécurité.
In the encryption 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.
Les textes/pièces jointes de message à chiffrer et les textes/pièces jointes du message déchiffré sont stockés localement seulement et ne seront jamais ajoutés au serveur distant. Si vous voulez annuler le déchiffrement, vous pouvez utiliser l'option *resynchroniser* dans le menu à trois points de la barre d'action des messages.
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.
<br />
*PGP*
Vous devez d'abord installer et configurer [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/). FairEmail a été testé avec OpenKeychain version 5.4. Les versions ultérieures seront probablement compatibles, mais les versions antérieures pourraient ne pas l'être.
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.
**Important**: l'application OpenKeychain est connue pour planter (silencieusement) lorsque l'application qui l'appel (FairEmail) n'est pas encore autorisée et obtient une clé publique existante. Vous pouvez contourner cela en essayant d'envoyer un message signé/chiffré à un expéditeur avec une clé publique inconnue.
**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**: si l'application OpenKeychain ne peut plus trouver de clé, vous devrez peut-être réinitialiser une clé précédemment sélectionnée. Cela peut être fait en appuyant longuement sur une identité dans la liste des identités (Paramètres, appuyez sur Configuration manuelle et plus d'options, appuyez sur Identités).
**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**: pour permettre aux applications comme FairEmail de se connecter de manière fiable au service OpenKeychain pour chiffrer/déchiffrer les messages, il peut être nécessaire de désactiver les optimisations de batterie pour l'application 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.
**Important**: il est dit que l'application OpenKeychain aurait besoin d'une autorisation d'acces aux contacts pour fonctionner correctement.
**Important**: the OpenKeychain app reportedly needs contacts permission to work correctly.
**Important**: sur certaines versions d'Android / appareils, il est nécessaire d'activer *Afficher les fenêtres pop-up lors de l'exécution en arrière-plan* dans les autorisations supplémentaires des paramètres de l'application Android de l'application OpenKeychain. Sans cette autorisation, le brouillon sera enregistré, mais la popup OpenKeychain pour confirmer/sélectionner pourrait ne pas apparaître.
**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 enverra l'en-tête [Autocrypt](https://autocrypt.org/) pour être utilisé par d'autres clients de messagerie, mais uniquement pour les messages signés et chiffrés parce que trop de serveurs de messagerie ont des problèmes avec l'en-tête Autocrypt qui est souvent longue. Notez que le moyen le plus sûr de démarrer un échange de messages chiffrés est d'envoyer d'abord des messages signés. Les en-têtes Autocrypt reçues seront envoyées à l'application OpenKeychain pour être stockées lors de la vérification d'une signature ou du déchiffrement d'un message.
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.
Bien que cela ne devrait pas être nécessaire pour la plupart des clients de messagerie, vous pouvez joindre votre clé publique à un message et si vous utilisez *.key* comme extension, le type mime sera correctement *application/pgp-keys*.
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
Toute la gestion des clés est déléguée à l'application porte-clés OpenKey pour des raisons de sécurité. Cela signifie également que FairEmail ne stocke pas les clés PGP.
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
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.
@ -710,26 +712,26 @@ You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
*pretty Easy privacy*
Il n'y a pour le moment [aucune norme approuvée](https://tools.ietf.org/id/draft-birk-pep-00.html) pour Pretty Easy Privacy (p≡p) et peu de gens l'utilisent.
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and not many people are using it.
Cependant, FairEmail peut envoyer et recevoir des messages chiffrés par PGP, qui sont compatibles avec p≡p. De plus, FairEmail comprend les messages entrants de p≡p depuis la version 1. 519, ainsi le sujet chiffré sera affiché et le texte du message intégré sera mieux affiché.
However, FairEmail can send and receive PGP encrypted messages, which are compatible with p≡p. Also, FairEmail understands incoming p≡p messages since version 1.1519, so the encrypted subject will be shown and the embedded message text will be shown more nicely.
<br />
S/MIME sign/encrypt est une fonctionnalité de la version pro, mais toutes les autres opérations PGP et S/MIME sont libres accessibles.
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br />
<a name="faq13"></a>
**(13) Comment fonctionne la recherche sur l'appareil / le serveur ?**
**(13) How does search on device/server work?**
Vous pouvez commencer par rechercher des messages sur l'expéditeur (de), le destinataire (à, cc, cci), le sujet, mots clés ou le texte du message en utilisant la loupe dans la barre d'action d'un dossier. Vous pouvez également rechercher depuis n'importe quelle application en sélectionnant *Chercher un courrier électronique* dans le menu contextuel copier/coller.
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.
La recherche dans la boîte de réception unifiée recherche dans tous les dossiers de tous les comptes, la recherche dans la liste de dossiers va chercher dans le compte associé seulement et la recherche dans un dossier ne sera effectuée que dans ce dossier.
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.
Les messages seront d'abord recherchés sur l'appareil. Il y aura un bouton en bas avec une icône "rechercher à nouveau" pour continuer la recherche sur le serveur. Vous pouvez choisir le dossier dans lequel vous souhaitez continuer la recherche.
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.
Le protocole IMAP ne supporte pas la recherche dans plusieurs dossiers en même temps. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
The IMAP protocol doesn't support searching in more than one folder at the same time. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
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.
@ -929,17 +931,17 @@ The error *... connection failure ...* could indicate [Too many simultaneous con
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.
L'erreur *... Limite de connexion atteinte ...* signifie qu'il y a eu trop de tentatives de connexion avec un mot de passe incorrect. Veuillez revérifier votre mot de passe ou authentifier le compte à nouveau avec l'assistant d'installation rapide (OAuth seulement).
The error *... Login Rate Limit Hit ...* means that there were too many login attempts with an incorrect password. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
Veuillez [voir ici](#user-content-faq4) pour les erreurs *... Non fiable ... pas dans le certificat ...*, *... Certificat de sécurité invalide (impossible de vérifier l'identité du serveur) ...* ou *... Ancre de confiance pour le chemin de certification introuvable...*
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 ...*
Veuillez [voir ici](#user-content-faq127) pour les erreurs *... Syntaxe de(s) argument(s) HELO invalide...*.
Please [see here](#user-content-faq127) for the error *... Syntactically invalid HELO argument(s) ...*.
Veuillez [voir ici](#user-content-faq41) pour les erreurs *... Echec de l'établissement d'une liaison...*.
Please [see here](#user-content-faq41) for the error *... Handshake failed ...*.
Voir [ici](https://linux.die.net/man/3/connect) pour les explications des codes d'erreur comme EHOSTUNREACH et ETIMEDOUT.
See [here](https://linux.die.net/man/3/connect) for what error codes like EHOSTUNREACH and ETIMEDOUT mean.
Les causes possibles sont:
Possible causes are:
* A firewall or router is blocking connections to the server
* The host name or port number is invalid
@ -949,13 +951,13 @@ Les causes possibles sont:
* Le serveur de messagerie refuse d'accepter un message, par exemple parce qu'il est trop grand ou qu'il contient des liens inacceptables
* Il y a trop de connexions au serveur, voir aussi la question suivante
De nombreux réseaux Wi-Fi publics bloquent les courriels sortants pour empêcher les spams. Parfois, vous pouvez contourner cela en utilisant un autre port SMTP. Voir la documentation du fournisseur d'accès pour les numéros de port utilisables.
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.
Si vous utilisez un [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), le fournisseur de VPN peut bloquer la connexion car il essaye de prévenir le spam de manière trop agressive. Notez que [Google Fi](https://fi.google.com/) utilise également un 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.
**Erreur d'envoi**
**Send errors**
Les serveurs SMTP peuvent rejeter les messages pour [une variété de raisons](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes). Les messages trop volumineux et le déclenchement du filtre de spam d'un serveur de messagerie sont les raisons les plus courantes.
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.
* The attachment size limit for Gmail [is 25 MB](https://support.google.com/mail/answer/6584)
* The attachment size limit for Outlook and Office 365 [is 20 MB](https://support.microsoft.com/en-us/help/2813269/attachment-size-exceeds-the-allowable-limit-error-when-you-add-a-large)
@ -967,27 +969,28 @@ Les serveurs SMTP peuvent rejeter les messages pour [une variété de raisons](h
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
Si vous voulez utiliser le serveur SMTP Gmail pour contourner un filtre de spam sortant trop strict ou pour améliorer la livraison des messages :
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
* Verify your email address [here](https://mail.google.com/mail/u/0/#settings/accounts) (you'll need to use a desktop browser for this)
* Change the identity settings like this (Settings, tap Manual setup and more options, tap Identities, tap identity):
&emsp;&emsp;Nom d'utilisateur : *votre adresse Gmail*<br /> &emsp;&emsp;Mot de passe : *[un mot de passe de l'application](#user-content-faq6)*<br /> &emsp;&emsp;Hôte : *smtp.gmail.com*<br /> &emsp;&emsp;Port : *465*<br /> &emsp;&emsp;Chiffrement : *SSL/TLS*<br /> &emsp;&emsp;Répondre à l'adresse : *votre adresse e-mail* (paramètres d'identité avancés)<br />
&emsp;&emsp;Username: *your Gmail address*<br /> &emsp;&emsp;Password: *[an app password](#user-content-faq6)*<br /> &emsp;&emsp;Host: *smtp.gmail.com*<br /> &emsp;&emsp;Port: *465*<br /> &emsp;&emsp;Encryption: *SSL/TLS*<br /> &emsp;&emsp;Reply to address: *your email address* (advanced identity settings)<br />
<br />
**Erreurs Gmail**
**Gmail errors**
L'autorisation de la configuration des comptes Gmail avec l'assistant rapide doit être périodiquement actualisée via le [gestionnaire de comptes Android](https://developer.android.com/reference/android/accounts/AccountManager). Cela nécessite des autorisations de contact/compte et une connexion internet.
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.
En cas d'erreur, il est possible d'autoriser/restaurer un compte Gmail à nouveau via l'assistant de configuration rapide de Gmail.
In case of errors it is possible to authorize/restore a Gmail account again via the Gmail quick setup wizard.
L'erreur *... Authentication failed ... Compte introuvable ...* signifie qu'un compte Gmail précédemment autorisé a été supprimé de l'appareil.
The error *... Échec de l'authentification ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
Les erreurs *... Échec de l'authentification ... Aucun jeton ...* signifie que le gestionnaire de comptes Android n'a pas réussi à actualiser l'autorisation d'un compte Gmail.
The errors *... Authentication failed ... No token ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
The error *... Échec de l'authentification... erreur de réseau...* signifie que le gestionnaire de compte Android n'a pas pu actualiser l'autorisation d'un compte Gmail en raison de problèmes de connexion internet
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 ... 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).
@ -2184,7 +2187,7 @@ Depending on what you want, the notification settings *Let the number of new mes
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Certains lanceurs affichent un point ou un « 1 » pour [la notification de surveillance](#user-content-faq2) malgré la demande explicite de FairEmail de ne pas afficher de *badge* pour cette notification. This could be caused by a bug in the launcher app or in your Android version. Veuillez vérifier si le "point" de notification (badge) est désactivé pour le canal de notification de réception (service). You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Some launchers display a dot or a '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a *badge* for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot (badge) is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
FairEmail does send a new message count intent as well:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

171
docs/FAQ-fr-rFR.md
View File

@ -398,6 +398,8 @@ Ceci peut être dû à l'utilisation d'un nom de serveur incorrect, donc vérifi
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Assurez-vous que vous utilisez une connexion internet fiable (pas de réseaux Wi-Fi publics, etc)
@ -406,7 +408,7 @@ Alternatively, you can accept the fingerprint of invalid server certificates lik
1. Contrôlez/enregistrez le compte et l'identité
1. Cochez la case en dessous du message d'erreur et enregistrez à nouveau
Ceci va « épingler » le certificat du serveur pour éviter les attaques de l'homme du milieu.
This will "pin" the server certificate to prevent man-in-the-middle attacks.
Note that older Android versions might not recognize newer certification authorities like Let’s Encrypt causing connections to be considered insecure, see also [here](https://developer.android.com/training/articles/security-ssl).
@ -418,11 +420,11 @@ You should either fix the server configuration or accept the fingerprint shown b
Note that this problem can be caused by the server not sending all intermediate certificates too.
*Mot de passe vide*
*Empty password*
Votre nom d'utilisateur est probablement facilement deviné, donc ce n'est pas sûr.
Your username is likely easily guessed, so this is insecure.
*Connexion en texte brut*
*Plain text connection*
Your username and password and all messages will be sent and received unencrypted, which is **very insecure** because a [man-in-the-middle attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) is very simple on an unencrypted connection.
@ -431,14 +433,14 @@ If you still want to use an invalid security certificate, an empty password or a
<br />
<a name="faq5"></a>
Comment personnaliser l'affichage des messages
**(5) How can I customize the message view?**
Dans le menu à trois points, vous pouvez activer ou désactiver ou sélectionner :
In the three dot overflow menu you can enable or disable or select:
* *taille de texte* : pour trois tailles de police différentes
* *Vue compacte* : pour des éléments de message plus condensés et une police de texte de message plus petite
Dans la section "Affichage" vous pouvez activer ou désactiver par exemple :
In the display section of the settings you can enable or disable for example:
* *Boîte de réception unifiée* : pour désactiver la boîte de réception unifiée et pour lister les dossiers sélectionnés pour la boîte de réception unifiée
* *Style tabulaire*: afficher une liste linéaire au lieu de cartes
@ -455,9 +457,9 @@ Dans la section "Affichage" vous pouvez activer ou désactiver par exemple :
* *Afficher automatiquement le message original pour les contacts connus*: pour automatiquement afficher les messages originaux pour les contacts de votre appareil, merci de lire [cette FAQ](#user-content-faq35)
* *Afficher automatiquement les images pour les contacts connus*: pour automatiquement afficher les images pour les contacts de votre appareil, merci de lire[cette FAQ](#user-content-faq35)
Attention, les messages ne peuvent être prévisualisés que lorsque le texte du message a été téléchargé. Par défaut, les messages textes les plus volumineux ne sont pas téléchargés sur les réseaux limités (généralement mobiles). Ceci peut être changé dans la section "Connexion" des paramètres.
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.
Certaines personnes demandent :
Some people ask:
* 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
@ -465,62 +467,62 @@ Certaines personnes demandent :
<br />
<a name="faq6"></a>
**(6) Comment puis-je me connecter à Gmail / G suite ?**
**(6) How can I login to Gmail / G suite?**
Si vous utilisez la version Play Store ou GitHub de FairEmail, vous pouvez utiliser l'assistant de configuration rapide pour configurer 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, parce que Google n'a approuve l'utilisation d'OAuth que pour les versions officielles.
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 ne voulez pas ou ne pouvez pas utiliser un compte Google sur votre appareil, par exemple sur les appareils Huawei récents, vous pouvez soit activer l'accès pour les « applications moins sécurisées » et utiliser le mot de passe de votre compte (non conseillé), soit activer l'authentification en deux étapes et utiliser un mot de passe spécifique à l'application. Pour utiliser un mot de passe, vous devrez configurer manuellement un compte et une identité au lieu de l’assistant de configuration rapide.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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**: parfois Google publie cette alerte :
**Important**: sometimes Google issues this alert:
*[ALERT] Veuillez vous connecter via votre navigateur web : https://support.google.com/mail/accounts/answer/78754 (Echec)*
*[ALERT] Please log in via your web browser: https://support.google.com/mail/accounts/answer/78754 (Failure)*
Cette vérification de sécurité de Google est plus souvent déclenchée lorsque l'option *applications moins sécurisées* est activée. Elle l'est moins avec un mot de passe d'application et elle est presque jamais déclenchée lorsque vous utilisez un compte sur l'appareil (OAuth).
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).
Veuillez consulter [cette FAQ](#user-content-faq111) pour savoir pourquoi seuls les comptes sur l'appareil peuvent être utilisés.
Please see [this FAQ](#user-content-faq111) on why only on-device accounts can be used.
Notez qu'un mot de passe spécifique à l'application est nécessaire lorsque l'authentification à deux facteurs est activée.
Note that an app specific password is required when two factor authentication is enabled.
<br />
*Mot de passe spécifique à l'application*
*App specific password*
Voir [ici](https://support.google.com/accounts/answer/185833) sur la façon de générer un mot de passe spécifique à l'application.
See [here](https://support.google.com/accounts/answer/185833) about how to generate an app specific password.
<br />
*Autoriser les "Applications moins sécurisées"*
*Enable "Less secure apps"*
**Important **: l'utilisation de cette méthode n'est pas recommandée car elle est moins fiable.
**Important**: using this method is not recommended because it is less reliable.
**Important **: Les comptes Gsuite autorisés avec un nom d'utilisateur/mot de passe cesseront de fonctionner [dans un avenir proche](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).
Voir [ici](https://support.google.com/accounts/answer/6010255) comment autoriser les "applications moins sécurisées" ou aller [directement au paramètre en question](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 vous utilisez plusieurs comptes Gmail, assurez-vous de modifier le paramètre "Autoriser les applications moins sécurisées" du ou des comptes concernés.
If you use multiple Gmail accounts, make sure you change the "less secure apps" setting of the right account(s).
Sachez que vous devez quitter l'écran de paramétrage des "applications moins sécurisées" en utilisant la flèche de retour arrière pour que le paramètre soit appliqué.
Be aware that you need to leave the "less secure apps" settings screen by using the back arrow to apply the setting.
Si vous utilisez cette méthode, vous devriez utiliser un [mot de passe robuste](https://en.wikipedia.org/wiki/Password_strength) pour votre compte Gmail, ce qui est de toute façon une bonne idée. Notez que l'utilisation du protocole [standard](https://tools.ietf.org/html/rfc3501) IMAP n'est en soi pas moins sécurisée.
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.
Lorsque les "applications moins sécurisées" ne sont pas activées, vous obtiendrez l'erreur *L'authentification a échoué - identifiants non valides* pour les comptes (IMAP) et *nom d'utilisateur et mot de passe non acceptés* pour les identités (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 />
*Général*
*General*
Il se peut que vous obteniez l'alerte "*S'il vous plaît connectez-vous via votre navigateur web*". This happens when Google considers the network that connects you to the internet (this could be a VPN) to be unsafe. Ceci peut être évité en utilisant l'assistant de configuration rapide de Gmail ou un mot de passe spécifique d'application.
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.
Voir [ici](https://support.google.com/mail/answer/7126229) pour les instructions de Google et [ici](https://support.google.com/mail/accounts/answer/78754) pour le dépannage.
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 />
<a name="faq7"></a>
**(7) Pourquoi les messages envoyés n'apparaissent-ils pas (directement) dans le dossier « Envoyés » ? **
**(7) Why are sent messages not appearing (directly) in the sent folder?**
Les messages envoyés sont normalement déplacés de la boîte d'envoi vers le dossier Envoyés dès que votre fournisseur ajoute les messages envoyés au dossier Envoyés. Ceci nécessite qu'un dossier Envoyés soit sélectionné dans les paramètres du compte et que le dossier Envoyés soit configuré pour être synchronisé.
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.
Certains fournisseurs ne gardent pas de trace des messages envoyés ou le serveur SMTP utilisé peut ne pas être lié au fournisseur. Dans ce cas, FairEmail ajoutera automatiquement les messages envoyés au dossier Envoyés lors de la synchronisation du dossier Envoyés qui se produira après l'envoi d'un message. Notez que cela entraînera un trafic Internet supplémentaire.
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.
~~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.~~
@ -548,7 +550,7 @@ Please see [this FAQ](#user-content-faq111) about OAuth support.
<br />
<a name="faq9"></a>
**(9) Qu'est-ce que les identités / Comment ajouter un alias ?**
**(9) What are identities / how do I add an alias?**
Identities represent email addresses you are sending *from* via an email (SMTP) server.
@ -565,14 +567,14 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
<br />
<a name="faq10"></a>
**~~(10) Que signifie "UIDPLUS n'est pas pris en charge" ?~~**
**~~(10) What does 'UIDPLUS not supported' mean?~~**
~~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 />
<a name="faq11"></a>
**~~(11) Pourquoi POP n'est pas pris en charge ?~~**
**~~(11) Why is POP not supported?~~**
~~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.~~
@ -587,57 +589,57 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
<br />
<a name="faq12"></a>
**(12) Comment fonctionne le chiffrement/déchiffrement ?**
**(12) How does encryption/decryption work?**
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.
<br />
*Général*
*General*
Veuillez [voir ici](https://en.wikipedia.org/wiki/Public-key_cryptography) le fonctionnement du chiffrement par des clé publique/privée.
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
Chiffrement en bref :
Encryption in short:
* Les messages **sortants** sont chiffrés avec la **clé publique** du destinataire
* Les messages **entrants** sont déchiffrés avec la **clé privée** du destinataire
Signature en bref :
Signing in short:
* Les messages **sortants** sont signés avec la **clé privée** de l'expéditeur
* Les messages **entrants** sont vérifiés avec la **clé publique** de l'expéditeur
Pour signer/chiffrer un message, il suffit de sélectionner la méthode appropriée dans la boîte de dialogue d'envoi. Vous pouvez toujours ouvrir la boîte de dialogue d'envoi en utilisant le menu déroulant symbolisé par trois points dans le cas où vous aviez sélectionné *Ne plus afficher* avant.
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.
Pour vérifier une signature ou déchiffrer un message reçu, ouvrez le message et appuyez sur l'icône du geste ou du cadenas juste en dessous de la barre d'action du message.
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 première fois que vous envoyez un message signé/chiffré, il se peut que l'on vous demande une clé de signature. FairEmail stockera automatiquement la clé de signature sélectionnée dans l'identité utilisée pour la prochaine fois. Si vous avez besoin de réinitialiser la clé de signature, enregistrez simplement l'identité ou appuyez longuement sur l'identité dans la liste des identités et sélectionnez *réinitialiser la clé de signature*. La clé de signature sélectionnée est visible dans la liste des identités. Si vous avez besoin de sélectionner une clé cas par cas, vous pouvez créer plusieurs identités pour le même compte avec la même adresse e-mail.
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.
Dans les paramètres de chiffrement, vous pouvez sélectionner la méthode de cryptage par défaut (PGP ou S/MIME), activer *Signer par défaut*, *Chiffrer par défaut* et *Déchiffrer automatiquement les messages*, mais sachez que le décryptage automatique n'est pas possible si l'interaction de l'utilisateur est requise, comme la sélection d'une clé ou la lecture d'un jeton de sécurité.
In the encryption 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.
Les textes/pièces jointes de message à chiffrer et les textes/pièces jointes du message déchiffré sont stockés localement seulement et ne seront jamais ajoutés au serveur distant. Si vous voulez annuler le déchiffrement, vous pouvez utiliser l'option *resynchroniser* dans le menu à trois points de la barre d'action des messages.
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.
<br />
*PGP*
Vous devez d'abord installer et configurer [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/). FairEmail a été testé avec OpenKeychain version 5.4. Les versions ultérieures seront probablement compatibles, mais les versions antérieures pourraient ne pas l'être.
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.
**Important**: l'application OpenKeychain est connue pour planter (silencieusement) lorsque l'application qui l'appel (FairEmail) n'est pas encore autorisée et obtient une clé publique existante. Vous pouvez contourner cela en essayant d'envoyer un message signé/chiffré à un expéditeur avec une clé publique inconnue.
**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**: si l'application OpenKeychain ne peut plus trouver de clé, vous devrez peut-être réinitialiser une clé précédemment sélectionnée. Cela peut être fait en appuyant longuement sur une identité dans la liste des identités (Paramètres, appuyez sur Configuration manuelle et plus d'options, appuyez sur Identités).
**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**: pour permettre aux applications comme FairEmail de se connecter de manière fiable au service OpenKeychain pour chiffrer/déchiffrer les messages, il peut être nécessaire de désactiver les optimisations de batterie pour l'application 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.
**Important**: il est dit que l'application OpenKeychain aurait besoin d'une autorisation d'acces aux contacts pour fonctionner correctement.
**Important**: the OpenKeychain app reportedly needs contacts permission to work correctly.
**Important**: sur certaines versions d'Android / appareils, il est nécessaire d'activer *Afficher les fenêtres pop-up lors de l'exécution en arrière-plan* dans les autorisations supplémentaires des paramètres de l'application Android de l'application OpenKeychain. Sans cette autorisation, le brouillon sera enregistré, mais la popup OpenKeychain pour confirmer/sélectionner pourrait ne pas apparaître.
**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 enverra l'en-tête [Autocrypt](https://autocrypt.org/) pour être utilisé par d'autres clients de messagerie, mais uniquement pour les messages signés et chiffrés parce que trop de serveurs de messagerie ont des problèmes avec l'en-tête Autocrypt qui est souvent longue. Notez que le moyen le plus sûr de démarrer un échange de messages chiffrés est d'envoyer d'abord des messages signés. Les en-têtes Autocrypt reçues seront envoyées à l'application OpenKeychain pour être stockées lors de la vérification d'une signature ou du déchiffrement d'un message.
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.
Bien que cela ne devrait pas être nécessaire pour la plupart des clients de messagerie, vous pouvez joindre votre clé publique à un message et si vous utilisez *.key* comme extension, le type mime sera correctement *application/pgp-keys*.
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
Toute la gestion des clés est déléguée à l'application porte-clés OpenKey pour des raisons de sécurité. Cela signifie également que FairEmail ne stocke pas les clés PGP.
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
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.
@ -710,26 +712,26 @@ You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
*pretty Easy privacy*
Il n'y a pour le moment [aucune norme approuvée](https://tools.ietf.org/id/draft-birk-pep-00.html) pour Pretty Easy Privacy (p≡p) et peu de gens l'utilisent.
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and not many people are using it.
Cependant, FairEmail peut envoyer et recevoir des messages chiffrés par PGP, qui sont compatibles avec p≡p. De plus, FairEmail comprend les messages entrants de p≡p depuis la version 1. 519, ainsi le sujet chiffré sera affiché et le texte du message intégré sera mieux affiché.
However, FairEmail can send and receive PGP encrypted messages, which are compatible with p≡p. Also, FairEmail understands incoming p≡p messages since version 1.1519, so the encrypted subject will be shown and the embedded message text will be shown more nicely.
<br />
S/MIME sign/encrypt est une fonctionnalité de la version pro, mais toutes les autres opérations PGP et S/MIME sont libres accessibles.
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br />
<a name="faq13"></a>
**(13) Comment fonctionne la recherche sur l'appareil / le serveur ?**
**(13) How does search on device/server work?**
Vous pouvez commencer par rechercher des messages sur l'expéditeur (de), le destinataire (à, cc, cci), le sujet, mots clés ou le texte du message en utilisant la loupe dans la barre d'action d'un dossier. Vous pouvez également rechercher depuis n'importe quelle application en sélectionnant *Chercher un courrier électronique* dans le menu contextuel copier/coller.
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.
La recherche dans la boîte de réception unifiée recherche dans tous les dossiers de tous les comptes, la recherche dans la liste de dossiers va chercher dans le compte associé seulement et la recherche dans un dossier ne sera effectuée que dans ce dossier.
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.
Les messages seront d'abord recherchés sur l'appareil. Il y aura un bouton en bas avec une icône "rechercher à nouveau" pour continuer la recherche sur le serveur. Vous pouvez choisir le dossier dans lequel vous souhaitez continuer la recherche.
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.
Le protocole IMAP ne supporte pas la recherche dans plusieurs dossiers en même temps. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
The IMAP protocol doesn't support searching in more than one folder at the same time. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
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.
@ -929,17 +931,17 @@ The error *... connection failure ...* could indicate [Too many simultaneous con
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.
L'erreur *... Limite de connexion atteinte ...* signifie qu'il y a eu trop de tentatives de connexion avec un mot de passe incorrect. Veuillez revérifier votre mot de passe ou authentifier le compte à nouveau avec l'assistant d'installation rapide (OAuth seulement).
The error *... Login Rate Limit Hit ...* means that there were too many login attempts with an incorrect password. Please double check your password or authenticate the account again with the quick setup wizard (OAuth only).
Veuillez [voir ici](#user-content-faq4) pour les erreurs *... Non fiable ... pas dans le certificat ...*, *... Certificat de sécurité invalide (impossible de vérifier l'identité du serveur) ...* ou *... Ancre de confiance pour le chemin de certification introuvable...*
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 ...*
Veuillez [voir ici](#user-content-faq127) pour les erreurs *... Syntaxe de(s) argument(s) HELO invalide...*.
Please [see here](#user-content-faq127) for the error *... Syntactically invalid HELO argument(s) ...*.
Veuillez [voir ici](#user-content-faq41) pour les erreurs *... Echec de l'établissement d'une liaison...*.
Please [see here](#user-content-faq41) for the error *... Handshake failed ...*.
Voir [ici](https://linux.die.net/man/3/connect) pour les explications des codes d'erreur comme EHOSTUNREACH et ETIMEDOUT.
See [here](https://linux.die.net/man/3/connect) for what error codes like EHOSTUNREACH and ETIMEDOUT mean.
Les causes possibles sont:
Possible causes are:
* A firewall or router is blocking connections to the server
* The host name or port number is invalid
@ -949,13 +951,13 @@ Les causes possibles sont:
* Le serveur de messagerie refuse d'accepter un message, par exemple parce qu'il est trop grand ou qu'il contient des liens inacceptables
* Il y a trop de connexions au serveur, voir aussi la question suivante
De nombreux réseaux Wi-Fi publics bloquent les courriels sortants pour empêcher les spams. Parfois, vous pouvez contourner cela en utilisant un autre port SMTP. Voir la documentation du fournisseur d'accès pour les numéros de port utilisables.
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.
Si vous utilisez un [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), le fournisseur de VPN peut bloquer la connexion car il essaye de prévenir le spam de manière trop agressive. Notez que [Google Fi](https://fi.google.com/) utilise également un 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.
**Erreur d'envoi**
**Send errors**
Les serveurs SMTP peuvent rejeter les messages pour [une variété de raisons](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes). Les messages trop volumineux et le déclenchement du filtre de spam d'un serveur de messagerie sont les raisons les plus courantes.
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.
* The attachment size limit for Gmail [is 25 MB](https://support.google.com/mail/answer/6584)
* The attachment size limit for Outlook and Office 365 [is 20 MB](https://support.microsoft.com/en-us/help/2813269/attachment-size-exceeds-the-allowable-limit-error-when-you-add-a-large)
@ -967,27 +969,28 @@ Les serveurs SMTP peuvent rejeter les messages pour [une variété de raisons](h
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
Si vous voulez utiliser le serveur SMTP Gmail pour contourner un filtre de spam sortant trop strict ou pour améliorer la livraison des messages :
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
* Verify your email address [here](https://mail.google.com/mail/u/0/#settings/accounts) (you'll need to use a desktop browser for this)
* Change the identity settings like this (Settings, tap Manual setup and more options, tap Identities, tap identity):
&emsp;&emsp;Nom d'utilisateur : *votre adresse Gmail*<br /> &emsp;&emsp;Mot de passe : *[un mot de passe de l'application](#user-content-faq6)*<br /> &emsp;&emsp;Hôte : *smtp.gmail.com*<br /> &emsp;&emsp;Port : *465*<br /> &emsp;&emsp;Chiffrement : *SSL/TLS*<br /> &emsp;&emsp;Répondre à l'adresse : *votre adresse e-mail* (paramètres d'identité avancés)<br />
&emsp;&emsp;Username: *your Gmail address*<br /> &emsp;&emsp;Password: *[an app password](#user-content-faq6)*<br /> &emsp;&emsp;Host: *smtp.gmail.com*<br /> &emsp;&emsp;Port: *465*<br /> &emsp;&emsp;Encryption: *SSL/TLS*<br /> &emsp;&emsp;Reply to address: *your email address* (advanced identity settings)<br />
<br />
**Erreurs Gmail**
**Gmail errors**
L'autorisation de la configuration des comptes Gmail avec l'assistant rapide doit être périodiquement actualisée via le [gestionnaire de comptes Android](https://developer.android.com/reference/android/accounts/AccountManager). Cela nécessite des autorisations de contact/compte et une connexion internet.
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.
En cas d'erreur, il est possible d'autoriser/restaurer un compte Gmail à nouveau via l'assistant de configuration rapide de Gmail.
In case of errors it is possible to authorize/restore a Gmail account again via the Gmail quick setup wizard.
L'erreur *... Authentication failed ... Compte introuvable ...* signifie qu'un compte Gmail précédemment autorisé a été supprimé de l'appareil.
The error *... Échec de l'authentification ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
Les erreurs *... Échec de l'authentification ... Aucun jeton ...* signifie que le gestionnaire de comptes Android n'a pas réussi à actualiser l'autorisation d'un compte Gmail.
The errors *... Authentication failed ... No token ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
The error *... Échec de l'authentification... erreur de réseau...* signifie que le gestionnaire de compte Android n'a pas pu actualiser l'autorisation d'un compte Gmail en raison de problèmes de connexion internet
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 ... 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).
@ -2184,7 +2187,7 @@ Depending on what you want, the notification settings *Let the number of new mes
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Certains lanceurs affichent un point ou un « 1 » pour [la notification de surveillance](#user-content-faq2) malgré la demande explicite de FairEmail de ne pas afficher de *badge* pour cette notification. This could be caused by a bug in the launcher app or in your Android version. Veuillez vérifier si le "point" de notification (badge) est désactivé pour le canal de notification de réception (service). You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Some launchers display a dot or a '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a *badge* for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot (badge) is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
FairEmail does send a new message count intent as well:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-fy-rNL.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-gl-rES.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-hi-rIN.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-hr-rHR.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-hu-rHU.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-in-rID.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Pastikan Anda menggunakan koneksi internet tepercaya (tidak di jaringan Wi-Fi publik, dll)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

9
docs/FAQ-it-rIT.md
View File

@ -398,6 +398,8 @@ Questo può essere causato dall'uso di un nome host errato, per cui controllare
È possibile risolvere questo problema contattando il proprio provider oppure ottenendo un certificato di sicurezza valido poiché i certificati di sicurezza non validi sono insicuri e consentono [attacchi man-in-the-middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Se il prezzo di questi rappresenta un ostacolo, è possibile ottenere certificati di sicurezza gratuiti da [Let's Encrypt](https://letsencrypt.org).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Assicurati di star usando una connessione internet affidabile (nessuna rete Wi-Fi pubblica, etc)
@ -469,7 +471,7 @@ Some people ask:
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.
Se non desideri utilizzare o non puoi utilizzare un account Google sul dispositivo, ad esempio sui dispositivi Huawei recenti, puoi abilitare l'accesso per "app meno sicure" ed usare la password del tuo account (non consigliato), oppure abilitare due fattori di autenticazione ed usare una password specifica per l'app. 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.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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:
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Messaggio di spam rifiutato perché l'IP è elencato per ...* significa che il server dell'email ha rifiutato di inviare un messaggio dall'indirizzo di rete attuale (pubblico) perché usato erroneamente per inviare spam da qualcun altro (si spera) in precedenza. Sei pregato di provare ad abilitare la modalità aereo per 10 minuti per acquisire un nuovo indirizzo di rete.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-iw-rIL.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ja-rJP.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ka-rGE.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-kk-rKZ.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ko-rKR.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-lt-rLT.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-nl-rNL.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-nn-rNO.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-no-rNO.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-pl-rPL.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-pt-rBR.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-pt-rPT.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ro-rRO.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ru-rRU.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-si-rLK.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-sk-rSK.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-sl-rSI.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-sr-rSP.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-sv-rSE.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-ta-rIN.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-tr-rTR.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-uk-rUA.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *550 Нам дуже шкода, але ми не можемо відправити Вашу пошту. Для потенційного визначення на спам мають значення тема, посилання або прикріплення, або фішинг або шкідливі програми.* означає, що провайдер електронної пошти вважає вихідне повідомлення шкідливим.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

19
docs/FAQ-vi-rVN.md
View File

@ -80,15 +80,15 @@ Câu hỏi liên quan:
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, Mi band 3, and Xiaomi Amazfit BIP wearables. See also [this FAQ](#user-content-faq126).
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
* Language detection [is not working anymore](https://issuetracker.google.com/issues/173337263) on Pixel devices with (upgraded to?) Android 11
* Dò tìm ngôn ngữ [không hoạt động nữa](https://issuetracker.google.com/issues/173337263) trên các thiết bị Pixel với (được nâng cấp lên?) Android 11
## Các tính năng được lên kế hoạch
* ~~Synchronize on demand (manual)~~
* ~~Semi-automatic encryption~~
* ~~Copy message~~
* ~~Colored stars~~
* ~~Notification settings per folder~~
* ~~Đồng bộ hoá theo yêu cầu (thủ công)~~
* ~~Mã hoá bán tự động~~
* ~~Sao chép thư~~
* ~~Sao có màu~~
* ~~Cài đặt thông báo cho từng thư mục~~
* ~~Select local images for signatures~~ (this will not be added because it requires image file management and because images are not shown by default in most email clients anyway)
* ~~Show messages matched by a rule~~
* ~~[ManageSieve](https://tools.ietf.org/html/rfc5804)~~ (there are no maintained Java libraries with a suitable license and without dependencies and besides that, FairEmail has its own filter rules)
@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

7
docs/FAQ-zh-rCN.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**

21
docs/FAQ-zh-rTW.md
View File

@ -398,6 +398,8 @@ This can be caused by using an incorrect host name, so first double check the ho
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).
The quick, but unsafe solution (not advised), is to enable *Insecure connections* in the advanced identity settings (navigation menu, tap *Settings*, tap *Manual setup and more options*, tap *Identities*, tap the identity, tap *Advanced*).
Alternatively, you can accept the fingerprint of invalid server certificates like this:
1. Make sure you are using a trusted internet connection (no public Wi-Fi networks, etc)
@ -418,9 +420,9 @@ You should either fix the server configuration or accept the fingerprint shown b
Note that this problem can be caused by the server not sending all intermediate certificates too.
*未輸入密碼*
*Empty password*
使用者名稱太容易猜到了，這樣很不安全喔。
Your username is likely easily guessed, so this is insecure.
*Plain text connection*
@ -457,7 +459,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:
* to show the subject bold, but bold is already being used to highlight unread messages
* to move the star to the left, but it is much easier to operate the star on the right side
@ -465,9 +467,9 @@ Note that messages can be previewed only when the message text was downloaded. L
<br />
<a name="faq6"></a>
**(6) 我要怎麼登入Gmail / G suite?**
**(6) How can I login to Gmail / G suite?**
如果你用 Play 商店或 GitHub 版本的 FairEmail, 那麼快速設定精靈可以幫你設定 Gmail 帳號跟身分。 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.
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.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, 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.
@ -483,9 +485,9 @@ Note that an app specific password is required when two factor authentication is
<br />
*App專用密碼*
*App specific password*
[這裡](https://support.google.com/accounts/answer/185833) 告訴你如何產生app專用密碼。
See [here](https://support.google.com/accounts/answer/185833) about how to generate an app specific password.
<br />
@ -967,6 +969,7 @@ SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia
* *550 Spam message rejected because IP is listed by ...* means that the email server rejected to send a message from the current (public) network address because it was misused to send spam by (hopefully) somebody else before. Please try to enable flight mode for 10 minutes to acquire a new network address.
* *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.
* *451 4.7.0 Temporary server error. Please try again later. PRX4 ...*: please [see here](https://judeperera.wordpress.com/2019/10/11/fixing-451-4-7-0-temporary-server-error-please-try-again-later-prx4/).
If you want to use the Gmail SMTP server to workaround a too strict outgoing spam filter or to improve delivery of messages:
@ -2422,10 +2425,6 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
<br />
*Background for unread messages*
<br />
<a name="faq126"></a>
**(126) Can message previews be sent to my wearable?**