mirror of https://github.com/M66B/FairEmail.git
Crowdin sync
This commit is contained in:
M66B
parent
7be9ad2582
commit
fc0ca0749e
|
|
@ -15,6 +15,9 @@
|
|||
<string name="channel_error">Erros</string>
|
||||
<string name="channel_alert">Alertas do servidor</string>
|
||||
<string name="channel_group_contacts">Contactos</string>
|
||||
<string name="channel_service_description">Sincronizando e monitorizando as contas</string>
|
||||
<string name="channel_send_description">Envío de mensaxes</string>
|
||||
<string name="channel_notification_description">Notificación de novas mensaxes</string>
|
||||
<plurals name="page_conversation">
|
||||
<item quantity="one">Conversa</item>
|
||||
<item quantity="other">Conversas</item>
|
||||
|
|
@ -1004,6 +1007,7 @@
|
|||
<string name="title_rule_answer_remark">Enviarase só unha resposta para cada conversa, co fin de evitar bucles de respostas</string>
|
||||
<string name="title_rule_name_missing">Falta o nome da regra</string>
|
||||
<string name="title_rule_condition_missing">Falta a condición</string>
|
||||
<string name="title_rule_automation_hint">Esto enviará o intento \'%1$s\' cos extras \'%2$s\'</string>
|
||||
<string name="title_rule_execute">Executar agora</string>
|
||||
<string name="title_rule_applied">Mensaxes afectadas: %1$d</string>
|
||||
<string name="title_rule_check">Comprobar</string>
|
||||
|
|
@ -1162,6 +1166,7 @@
|
|||
<string name="title_enabled">Activado</string>
|
||||
<string name="title_executing">Executando</string>
|
||||
<string name="title_completed">Finalizado</string>
|
||||
<string name="title_default_changed">Cambiados axustes por omisión</string>
|
||||
<string name="title_clipboard_copy">Copiar o portapapeis</string>
|
||||
<string name="title_clipboard_copied">Copiado ao portapapeis</string>
|
||||
<string name="title_ask_what">Preguntar que facer</string>
|
||||
|
|
@ -1211,7 +1216,15 @@
|
|||
<string name="title_boundary_retry">Tentar de novo</string>
|
||||
<string name="title_unexpected_error">Erro imprevisto</string>
|
||||
<string name="title_log">Rexistro</string>
|
||||
<string name="title_auto_scroll">Desprazamento automático</string>
|
||||
<string name="title_log_clear">Limpar</string>
|
||||
<string name="title_rules_search_hint">Buscar nome ou condición</string>
|
||||
<string name="title_rules_export">Exportar regras</string>
|
||||
<string name="title_rules_import">Importar regras</string>
|
||||
<string name="title_rules_delete_all">Eliminar todas as regras</string>
|
||||
<string name="title_rules_delete_junk">Eliminar regras de spam</string>
|
||||
<string name="title_rules_delete_all_confirm">Eliminar todas?</string>
|
||||
<string name="title_rules_delete_junk_confirm">Eliminar todas as regras movendo as mensaxes ó cartafol spam?</string>
|
||||
<string name="title_debug_info">Información de depuración</string>
|
||||
<string name="title_debug_info_remark">Por favor, describa o problema e indique o tempo do problema:</string>
|
||||
<string name="title_crash_info_remark">Por favor, describa que estaba a facer cando a aplicación se detivo:</string>
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -708,7 +722,7 @@ To use an Outlook, Live or Hotmail account with two factor authentication enable
|
|||
|
||||
See [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for Microsoft's instructions.
|
||||
|
||||
Pro nastavení účtu Office 365 se prosím podívejte na [tento nejčastější dotaz](#user-content-faq156).
|
||||
For setting up an Office 365 account, please see [this FAQ](#user-content-faq156).
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -760,7 +774,7 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<a name="faq18"></a>
|
||||
**(18) Why is the message preview not always shown?**
|
||||
|
||||
The preview of the message text cannot be shown if the message body has not been downloaded yet. Viz také [tento nejčastější dotaz](#user-content-faq15).
|
||||
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -790,7 +804,7 @@ I have been working on FairEmail almost every day for more than two years, so I
|
|||
If a purchased pro feature doesn't work as intended and this isn't caused by a problem in the free features and I cannot fix the problem in a timely manner, you can get a refund. In all other cases there is no refund possible. In no circumstances there is a refund possible for any problem related to the free features, since there wasn't paid anything for them and because they can be evaluated without any limitation. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
|
||||
<a name="faq21"></a>
|
||||
**(21) Jak povolím oznamovací LED?**
|
||||
**(21) How do I enable the notification light?**
|
||||
|
||||
Before Android 8 Oreo: there is an advanced option in the setup for this.
|
||||
|
||||
|
|
@ -811,9 +825,9 @@ FairEmail will automatically try to connect again after a delay. This delay will
|
|||
|
||||
There are general errors and errors specific to Gmail accounts (see below).
|
||||
|
||||
**Obecné chyby**
|
||||
**General errors**
|
||||
|
||||
Chyba *... Ověření selhalo ...* či *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -891,7 +905,7 @@ When in doubt, you can ask for [support](#user-content-support).
|
|||
<a name="faq23"></a>
|
||||
**(23) Why do I get alert ... ?**
|
||||
|
||||
*Obecné*
|
||||
*General*
|
||||
|
||||
Alerts are warning messages sent by email servers.
|
||||
|
||||
|
|
@ -924,7 +938,7 @@ Browse messages on the server will fetch messages from the email server in real
|
|||
<br />
|
||||
|
||||
<a name="faq25"></a>
|
||||
**(25) Proč nemohu vybrat/otevřít/uložit obrázek, přílohu nebo soubor?**
|
||||
**(25) Why can't I select/open/save an image, attachment or a file?**
|
||||
|
||||
When a menu item to select/open/save a file is disabled (dimmed) or when you get the message *Storage access framework not available*, the [storage access framework](https://developer.android.com/guide/topics/providers/document-provider), a standard Android component, is probably not present. This might be because your custom ROM does not include it or because it was actively removed (debloated).
|
||||
|
||||
|
|
@ -952,19 +966,19 @@ If you would like your name or alias to be included in the list of contributors
|
|||
<br />
|
||||
|
||||
<a name="faq27"></a>
|
||||
**(27) Jak odliším vložené obrázky od externích?**
|
||||
**(27) How can I distinguish between embedded and external images?**
|
||||
|
||||
Externí obrázek:
|
||||
External image:
|
||||
|
||||
|
||||
|
||||
|
||||
Vložený obrázek:
|
||||
Embedded image:
|
||||
|
||||
|
||||
|
||||
|
||||
Poškozený obrázek:
|
||||
Broken image:
|
||||
|
||||
|
||||
|
||||
|
||||
Note that downloading external images from a remote server can be used to record you did see a message, which you likely don't want if the message is spam or malicious.
|
||||
|
||||
|
|
@ -989,7 +1003,7 @@ See [here](https://developer.android.com/guide/topics/ui/notifiers/notifications
|
|||
|
||||
On Android before Android 8 Oreo you can set the notification sound in the settings.
|
||||
|
||||
Má-li vaše zařízení oznamovací LED, podívejte se na [tento nejčastější dotaz](#user-content-faq21).
|
||||
See [this FAQ](#user-content-faq21) if your device has a notification light.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -1075,7 +1089,7 @@ Matched identities can be used to color code messages. The identity color takes
|
|||
<br />
|
||||
|
||||
<a name="faq35"></a>
|
||||
**(35) Proč bych měl být opatrný při prohlížení obrázků, příloh a původních zpráv?**
|
||||
**(35) Why should I be careful with viewing images, attachments, and the original message?**
|
||||
|
||||
Viewing remotely stored images (see also [this FAQ](#user-content-faq27)) might not only tell the sender that you have seen the message, but will also leak your IP address.
|
||||
|
||||
|
|
@ -1185,7 +1199,7 @@ Most providers provide encrypted connections using different ports, typically po
|
|||
|
||||
If your provider doesn't support encrypted connections, you should ask to make this possible. If this isn't an option, you could enable *Allow insecure connections* both in the advanced settings AND the account/identity settings.
|
||||
|
||||
Viz také [tento nejčastější dotaz](#user-content-faq4).
|
||||
See also [this FAQ](#user-content-faq4).
|
||||
|
||||
The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either caused by a bug in the SSL protocol implementation or by a too short DH key on the email server and can unfortunately not be fixed by FairEmail.
|
||||
|
||||
|
|
@ -1202,9 +1216,9 @@ You can use [this website](https://ssl-tools.net/mailservers) or [this website](
|
|||
<a name="faq42"></a>
|
||||
**(42) Can you add a new provider to the list of providers?**
|
||||
|
||||
Používá-li poskytovatele více než pár lidí, ano, s radostí.
|
||||
If the provider is used by more than a few people, yes, with pleasure.
|
||||
|
||||
Potřebné jsou následující údaje:
|
||||
The following information is needed:
|
||||
|
||||
```
|
||||
<provider
|
||||
|
|
@ -1228,7 +1242,7 @@ So, pure SSL connections are safer than using [STARTTLS](https://en.wikipedia.or
|
|||
|
||||
Please make sure receiving and sending messages works properly before contacting me to add a provider.
|
||||
|
||||
Podívejte se níže pro informace jak mě kontaktovat.
|
||||
See below about how to contact me.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -1269,7 +1283,7 @@ You'll get the error message *No primary account or no drafts folder* when tryin
|
|||
|
||||
This can also happen when you try to reply to a message or to forward a message from an account with no drafts folder while there is no primary account or when the primary account does not have a drafts folder.
|
||||
|
||||
Pro více informací si prosím přečtěte [tento nejčastější dotaz](#user-content-faq141).
|
||||
Please see [this FAQ](#user-content-faq141) for some more information.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -1372,11 +1386,11 @@ There are almost no providers offering the [JMAP](https://jmap.io/) protocol, so
|
|||
|
||||
The email icon in the folder list can be open (outlined) or closed (solid):
|
||||
|
||||
|
||||
|
||||
|
||||
Message bodies and attachments are not downloaded by default.
|
||||
|
||||
|
||||
|
||||
|
||||
Message bodies and attachments are downloaded by default.
|
||||
|
||||
|
|
@ -1456,7 +1470,7 @@ If you want to resize images on a case-by-case basis, you can use [Send Reduced]
|
|||
|
||||
~~The most natural thing to do when swiping a list entry left or right is to remove the entry from the list.~~ ~~The most natural action in the context of an email app is moving the message out of the folder to another folder.~~ ~~You can select the folder to move to in the account settings.~~
|
||||
|
||||
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. Viz také [tento dotaz](#user-content-faq55).~~
|
||||
~~Other actions, like marking messages read and snoozing messages are available via multiple selection.~~ ~~You can long press a message to start multiple selection. See also [this question](#user-content-faq55).~~
|
||||
|
||||
~~Swiping left or right to mark a message read or unread is unnatural because the message first goes away and later comes back in a different shape.~~ ~~Note that there is an advanced option to mark messages automatically read on moving,~~ ~~which is in most cases a perfect replacement for the sequence mark read and move to some folder.~~ ~~You can also mark messages read from new message notifications.~~
|
||||
|
||||
|
|
@ -1494,11 +1508,11 @@ By selecting a zero snooze duration you can cancel snoozing.
|
|||
<br />
|
||||
|
||||
<a name="faq68"></a>
|
||||
**~~(68) Proč Adobe Acrobat Reader nemůže otevírat PDF přílohy / Microsoft aplikace nemohou otevírat přiložené dokumenty?~~**
|
||||
**~~(68) Why can Adobe Acrobat reader not open PDF attachments / Microsoft apps not open attached documents?~~**
|
||||
|
||||
~~Adobe Acrobat Reader a aplikace Microsoftu stále očekávají plný a neomezený přístup ke všem uloženým souborům,~~ ~~byť by aplikace už od Androidu KitKat (2013) měly používat [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider),~~ ~~pro přístup pouze k záměrně sdíleným souborům. Je to z důvodů bezpečnosti a ochrany soukromí.~~
|
||||
~~Adobe Acrobat reader and Microsoft apps still expects full access to all stored files,~~ ~~while apps should use the [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider) since Android KitKat (2013)~~ ~~to have access to actively shared files only. This is for privacy and security reasons.~~
|
||||
|
||||
~~Lze to obejít uložením přílohy a jejím otevřením z Adobe Acrobat Reader / Microsoft aplikace,~~ ~~ale raději doporučujeme nainstalovat aktualizovanou PDF čtečku / prohlížeč dokumentů, pokud možno s otevřeným kódem,~~ ~~například ten uvedený [zde](https://github.com/offa/android-foss#-document--pdf-viewer).~~
|
||||
~~You can workaround this by saving the attachment and opening it from the Adobe Acrobat reader / Microsoft app,~~ ~~but you are advised to install an up-to-date and preferably open source PDF reader / document viewer,~~ ~~for example one listed [here](https://github.com/offa/android-foss#-document--pdf-viewer).~~
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -1751,7 +1765,7 @@ Please see [here](https://en.wikipedia.org/wiki/Web_beacon) about what a trackin
|
|||
|
||||
FairEmail will in most cases automatically recognize tracking images and replace them by this icon:
|
||||
|
||||
|
||||
|
||||
|
||||
Automatic recognition of tracking images can be disabled in the privacy settings.
|
||||
|
||||
|
|
@ -1815,7 +1829,7 @@ To authorize a Yahoo, AOL, or Sky account you will need to create an app passwor
|
|||
* [for AOL](https://help.aol.com/articles/Create-and-manage-app-password)
|
||||
* [for Sky](https://www.sky.com/help/articles/getting-started-with-sky-yahoo-mail) (under *Other email apps*)
|
||||
|
||||
Podívejte se prosím na [tento nejčastější dotaz](#user-content-faq111) o podpoře OAuth.
|
||||
Please see [this FAQ](#user-content-faq111) about OAuth support.
|
||||
|
||||
Note that Yahoo, AOL, and Sky do not support standard push messages. The Yahoo email app uses a proprietary, undocumented protocol for push messages.
|
||||
|
||||
|
|
@ -1850,12 +1864,12 @@ Links for less usual protocols like telnet and ftp will not automatically be lin
|
|||
|
||||
~~Synchronizing messages is an expensive proces because the local and remote messages need to be compared,~~ ~~so periodically synchronizing messages will not result in saving battery power, more likely the contrary.~~
|
||||
|
||||
~~~Podívejte se na [tento nejčastější dotaz](#user-content-faq39) o optimalizaci využití baterie.~~
|
||||
~~See [this FAQ](#user-content-faq39) about optimizing battery usage.~~
|
||||
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq92" mark="crwd-mark"></a>
|
||||
<a name="faq92"></a>
|
||||
**(92) Can you add spam filtering, verification of the DKIM signature and SPF authorization?**
|
||||
|
||||
Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
|
||||
|
|
@ -1874,10 +1888,10 @@ If legitimate messages are failing authentication, you should notify the sender
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq93" mark="crwd-mark"></a>
|
||||
<a name="faq93"></a>
|
||||
**(93) Can you allow installation/data storage on external storage media (sdcard)?**
|
||||
|
||||
FairEmail uses services and alarms, provides widgets and listens for the boot completed event to be started on device start, so it is not possible to store the app on external storage media, like an sdcard. Viz také [zde](https://developer.android.com/guide/topics/data/install-location).
|
||||
FairEmail uses services and alarms, provides widgets and listens for the boot completed event to be started on device start, so it is not possible to store the app on external storage media, like an sdcard. See also [here](https://developer.android.com/guide/topics/data/install-location).
|
||||
|
||||
Messages, attachments, etc stored on external storage media, like an sdcard, can be accessed by other apps and is therefore not safe. See [here](https://developer.android.com/training/data-storage) for the details.
|
||||
|
||||
|
|
@ -1887,14 +1901,14 @@ If you need to save on storage space, you can limit the number of days messages
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq94" mark="crwd-mark"></a>
|
||||
<a name="faq94"></a>
|
||||
**(94) What does the red/orange stripe at the end of the header mean?**
|
||||
|
||||
The red/orange stripe at the left side of the header means that the DKIM, SPF or DMARC authentication failed. Viz také [tento nejčastější dotaz](#user-content-faq92).
|
||||
The red/orange stripe at the left side of the header means that the DKIM, SPF or DMARC authentication failed. See also [this FAQ](#user-content-faq92).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq95" mark="crwd-mark"></a>
|
||||
<a name="faq95"></a>
|
||||
**(95) Why are not all apps shown when selecting an attachment or image?**
|
||||
|
||||
For privacy and security reasons FairEmail does not have permissions to directly access files, instead the Storage Access Framework, available and recommended since Android 4.4 KitKat (released in 2013), is used to select files.
|
||||
|
|
@ -1905,14 +1919,14 @@ Android Q will make it harder and maybe even impossible to directly access files
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq96" mark="crwd-mark"></a>
|
||||
<a name="faq96"></a>
|
||||
**(96) Where can I find the IMAP and SMTP settings?**
|
||||
|
||||
The IMAP settings are part of the (custom) account settings and the SMTP settings are part of the identity settings.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq97" mark="crwd-mark"></a>
|
||||
<a name="faq97"></a>
|
||||
**(97) What is 'cleanup' ?**
|
||||
|
||||
About each four hours FairEmail runs a cleanup job that:
|
||||
|
|
@ -1927,14 +1941,14 @@ Note that the cleanup job will only run when the synchronize service is active.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq98" mark="crwd-mark"></a>
|
||||
<a name="faq98"></a>
|
||||
**(98) Why can I still pick contacts after revoking contacts permissions?**
|
||||
|
||||
After revoking contacts permissions Android does not allow FairEmail access to your contacts anymore. However, picking contacts is delegated to and done by Android and not by FairEmail, so this will still be possible without contacts permissions.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq99" mark="crwd-mark"></a>
|
||||
<a name="faq99"></a>
|
||||
**(99) Can you add a rich text or markdown editor?**
|
||||
|
||||
FairEmail provides common text formatting (bold, italic, underline, text size and color) via a toolbar that appears after selecting some text.
|
||||
|
|
@ -1943,7 +1957,7 @@ A [Rich text](https://en.wikipedia.org/wiki/Formatted_text) or [Markdown](https:
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq100" mark="crwd-mark"></a>
|
||||
<a name="faq100"></a>
|
||||
**(100) How can I synchronize Gmail categories?**
|
||||
|
||||
You can synchronize Gmail categories by creating filters to label categorized messages:
|
||||
|
|
@ -1967,7 +1981,7 @@ You can use *Force sync* in the three-dots menu of the unified inbox to let Fair
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq101" mark="crwd-mark"></a>
|
||||
<a name="faq101"></a>
|
||||
**(101) What does the blue/orange dot at the bottom of the conversations mean?**
|
||||
|
||||
The dot shows the relative position of the conversation in the message list. The dot will be show orange when the conversation is the first or last in the message list, else it will be blue. The dot is meant as an aid when swiping left/right to go to the previous/next conversation.
|
||||
|
|
@ -1976,7 +1990,7 @@ The dot is disabled by default and can be enabled with the display settings *Sho
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq102" mark="crwd-mark"></a>
|
||||
<a name="faq102"></a>
|
||||
**(102) How can I enable auto rotation of images?**
|
||||
|
||||
Images will automatically be rotated when automatic resizing of images is enabled in the settings (enabled by default). However, automatic rotating depends on the [Exif](https://en.wikipedia.org/wiki/Exif) information to be present and to be correct, which is not always the case. Particularly not when taking a photo with a camara app from FairEmail.
|
||||
|
|
@ -1985,7 +1999,7 @@ Note that only [JPEG](https://en.wikipedia.org/wiki/JPEG) and [PNG](https://en.w
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq103" mark="crwd-mark"></a>
|
||||
<a name="faq103"></a>
|
||||
**(103) How can I record audio?**
|
||||
|
||||
You can record audio if you have a recording app installed which supports the [RECORD_SOUND_ACTION](https://developer.android.com/reference/android/provider/MediaStore.Audio.Media#RECORD_SOUND_ACTION) intent. If no supported app is installed, FairEmail will not show a record audio action/icon.
|
||||
|
|
@ -1994,7 +2008,7 @@ Unfortunately and surprisingly, most recording apps do not seem to support this
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq104" mark="crwd-mark"></a>
|
||||
<a name="faq104"></a>
|
||||
**(104) What do I need to know about error reporting?**
|
||||
|
||||
* Error reports will help improve FairEmail
|
||||
|
|
@ -2008,7 +2022,7 @@ Unfortunately and surprisingly, most recording apps do not seem to support this
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq105" mark="crwd-mark"></a>
|
||||
<a name="faq105"></a>
|
||||
**(105) How does the roam-like-at-home option work?**
|
||||
|
||||
FairEmail will check if the country code of the SIM card and the country code of the network are in the [EU roam-like-at-home countries](https://en.wikipedia.org/wiki/European_Union_roaming_regulations#Territorial_extent) and assumes no roaming if the country codes are equal and the advanced roam-like-at-home option is enabled.
|
||||
|
|
@ -2017,7 +2031,7 @@ So, you don't have to disable this option if you don't have an EU SIM or are not
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq106" mark="crwd-mark"></a>
|
||||
<a name="faq106"></a>
|
||||
**(106) Which launchers can show a badge count with the number of unread messages?**
|
||||
|
||||
Please [see here](https://github.com/leolin310148/ShortcutBadger#supported-launchers) for a list of launchers which can show the number of unread messages.
|
||||
|
|
@ -2044,7 +2058,7 @@ The number of new, unread messages will be in an integer "*count*" parameter.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq107" mark="crwd-mark"></a>
|
||||
<a name="faq107"></a>
|
||||
**(107) How do I use colored stars?**
|
||||
|
||||
You can set a colored star via the *more* message menu, via multiple selection (started by long pressing a message), by long pressing a star in a conversation or automatically by using [rules](#user-content-faq71).
|
||||
|
|
@ -2055,14 +2069,14 @@ Some email clients use IMAP keywords for colors. However, not all servers suppor
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq108" mark="crwd-mark"></a>
|
||||
<a name="faq108"></a>
|
||||
**~~(108) Can you add permanently delete messages from any folder?~~**
|
||||
|
||||
~~When you delete messages from a folder the messages will be moved to the trash folder, so you have a chance to restore the messages.~~ ~~You can permanently delete messages from the trash folder.~~ ~~Permanently delete messages from other folders would defeat the purpose of the trash folder, so this will not be added.~~
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq109" mark="crwd-mark"></a>
|
||||
<a name="faq109"></a>
|
||||
**~~(109) Why is 'select account' available in official versions only?~~**
|
||||
|
||||
~~Using *select account* to select and authorize Google accounts require special permission from Google for security and privacy reasons.~~ ~~This special permission can only be acquired for apps a developer manages and is responsible for.~~ ~~Third party builds, like the F-Droid builds, are managed by third parties and are the responsibility of these third parties.~~ ~~So, only these third parties can acquire the required permission from Google.~~ ~~Since these third parties do not actually support FairEmail, they are most likely not going to request the required permission.~~
|
||||
|
|
@ -2076,7 +2090,7 @@ Some email clients use IMAP keywords for colors. However, not all servers suppor
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq110" mark="crwd-mark"></a>
|
||||
<a name="faq110"></a>
|
||||
**(110) Why are (some) messages empty and/or attachments corrupt?**
|
||||
|
||||
Empty messages and/or corrupt attachments are probably being caused by a bug in the server software. Older Microsoft Exchange software is known to cause this problem. Mostly you can workaround this by disabling *Partial fetch* in the advanced account settings:
|
||||
|
|
@ -2089,7 +2103,7 @@ Disabling *Partial fetch* will result in more memory usage.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq111" mark="crwd-mark"></a>
|
||||
<a name="faq111"></a>
|
||||
**(111) Is OAuth supported?**
|
||||
|
||||
OAuth for Gmail is supported via the quick setup wizard. The Android account manager will be used to fetch and refresh OAuth tokens for selected on-device accounts. OAuth for non on-device accounts is not supported because Google requires a [yearly security audit](https://support.google.com/cloud/answer/9110914) ($15,000 to $75,000) for this.
|
||||
|
|
@ -2102,20 +2116,20 @@ OAuth access for Yahoo was requested, but Yahoo never responded to the request.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq112" mark="crwd-mark"></a>
|
||||
<a name="faq112"></a>
|
||||
**(112) Which email provider do you recommend?**
|
||||
|
||||
FairEmail is an email client only, so you need to bring your own email address.
|
||||
|
||||
There are plenty of email providers to choose from. Which email provider is best for you depends on your wishes/requirements. Please see the websites of [Restore privacy](https://restoreprivacy.com/secure-email/) or [Privacy Tools](https://www.privacytools.io/providers/email/) for a list of privacy oriented email providers with advantages and disadvantages.
|
||||
|
||||
Some providers, like ProtonMail, Tutanota, use proprietary email protocols, which make it impossible to use third party email apps. Pro více informací si prosím přečtěte [tento nejčastější dotaz](#user-content-faq129).
|
||||
Some providers, like ProtonMail, Tutanota, use proprietary email protocols, which make it impossible to use third party email apps. Please see [this FAQ](#user-content-faq129) for more information.
|
||||
|
||||
Using your own (custom) domain name, which is supported by most email providers, will make it easier to switch to another email provider.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq113" mark="crwd-mark"></a>
|
||||
<a name="faq113"></a>
|
||||
**(113) How does biometric authentication work?**
|
||||
|
||||
If your device has a biometric sensor, for example a fingerprint sensor, you can enable/disable biometric authentication in the navigation (hamburger) menu of the setup screen. When enabled FairEmail will require biometric authentication after a period of inactivity or after the screen has been turned off while FairEmail was running. Activity is navigation within FairEmail, for example opening a conversation thread. The inactivity period duration can be configured in the miscellaneous settings. When biometric authentication is enabled new message notifications will not show any content and FairEmail won't be visible on the Android recents screen.
|
||||
|
|
@ -2126,14 +2140,14 @@ Biometric authentication is a pro feature.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq114" mark="crwd-mark"></a>
|
||||
<a name="faq114"></a>
|
||||
**(114) Can you add an import for the settings of other email apps?**
|
||||
|
||||
The format of the settings files of most other email apps is not documented, so this is difficult. Sometimes it is possible to reverse engineer the format, but as soon as the settings format changes things will break. Also, settings are often incompatible. For example, FairEmail has unlike most other email apps settings for the number of days to synchronize messages for and for the number of days to keep messages for, mainly to save on battery usage. Moreover, setting up an account/identity with the quick setup is simple, so it is not really worth the effort.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq115" mark="crwd-mark"></a>
|
||||
<a name="faq115"></a>
|
||||
**(115) Can you add email address chips?**
|
||||
|
||||
Email address [chips](https://material.io/design/components/chips.html) look nice, but cannot be edited, which is quite inconvenient when you made a typo in an email address.
|
||||
|
|
@ -2146,7 +2160,7 @@ Reverted [commit](https://github.com/M66B/FairEmail/commit/2c80c25b8aa75af2287f4
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq116" mark="crwd-mark"></a>
|
||||
<a name="faq116"></a>
|
||||
**~~(116) How can I show images in messages from trusted senders by default?~~**
|
||||
|
||||
~~You can show images in messages from trusted senders by default by enabled the display setting *Automatically show images for known contacts*.~~
|
||||
|
|
@ -2155,8 +2169,8 @@ Reverted [commit](https://github.com/M66B/FairEmail/commit/2c80c25b8aa75af2287f4
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq38" mark="crwd-mark"></a>
|
||||
<a name="faq117" mark="crwd-mark"></a>
|
||||
<a name="faq38"></a>
|
||||
<a name="faq117"></a>
|
||||
**(117) Can you help me restore my purchase?**
|
||||
|
||||
Google manages all purchases, so as a developer I have little control over purchases. So, basically the only thing I can do, is give some advice:
|
||||
|
|
@ -2182,14 +2196,14 @@ If you cannot solve the problem with the purchase, you will have to contact Goog
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq118" mark="crwd-mark"></a>
|
||||
<a name="faq118"></a>
|
||||
**(118) What does 'Remove tracking parameters' exactly?**
|
||||
|
||||
Checking *Remove tracking parameters* will remove all [UTM parameters](https://en.wikipedia.org/wiki/UTM_parameters) from a link.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq119" mark="crwd-mark"></a>
|
||||
<a name="faq119"></a>
|
||||
**~~(119) Can you add colors to the unified inbox widget?~~**
|
||||
|
||||
~~The widget is designed to look good on most home/launcher screens by making it monochrome and by using a half transparent background.~~ ~~This way the widget will nicely blend in, while still being properly readable.~~
|
||||
|
|
@ -2200,7 +2214,7 @@ Due to Android limitations it is not possible to dynamically set the opacity of
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq120" mark="crwd-mark"></a>
|
||||
<a name="faq120"></a>
|
||||
**(120) Why are new message notifications not removed on opening the app?**
|
||||
|
||||
New message notifications will be removed on swiping notifications away or on marking the associated messages read. Opening the app will not remove new message notifications. This gives you a choice to leave new message notifications as a reminder that there are still unread messages.
|
||||
|
|
@ -2209,7 +2223,7 @@ On Android 7 Nougat and later new message notifications will be [grouped](https:
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq121" mark="crwd-mark"></a>
|
||||
<a name="faq121"></a>
|
||||
**(121) How are messages grouped into a conversation?**
|
||||
|
||||
By default FairEmail groups messages in conversations. This can be turned of in the display settings.
|
||||
|
|
@ -2218,14 +2232,14 @@ FairEmail groups messages based on the standard *Message-ID*, *In-Reply-To* and
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq122" mark="crwd-mark"></a>
|
||||
<a name="faq122"></a>
|
||||
**~~(122) Why is the recipient name/email address show with a warning color?~~**
|
||||
|
||||
~~The recipient name and/or email address in the addresses section will be shown in a warning color~~ ~~when the sender domain name and the domain name of the *to* address do not match.~~ ~~Mostly this indicates that the message was received *via* an account with another email address.~~
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq123" mark="crwd-mark"></a>
|
||||
<a name="faq123"></a>
|
||||
**(123) What will happen when FairEmail cannot connect to an email server?**
|
||||
|
||||
When FairEmail cannot connect to an email server to receive messages, for example when the internet connection is bad or a firewall or a VPN is blocking the connection, FairEmail will wait 8, 16 and 32 seconds while keeping the device awake (=use battery power) and try again to connect. If this fails, FairEmail will schedule an alarm to retry after 15, 30 and 60 minutes and let the device sleep (=no battery usage).
|
||||
|
|
@ -2242,21 +2256,21 @@ Note that sending will not be retried in case of authentication problems and whe
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq124" mark="crwd-mark"></a>
|
||||
<a name="faq124"></a>
|
||||
**(124) Why do I get 'Message too large or too complex to display'?**
|
||||
|
||||
The message *Message too large or too complex to display* will be shown if there are more than 100,000 characters or more than 500 links in a message. Reformatting and displaying such messages will take too long. You can try to use the original message view, powered by the browser, instead.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq125" mark="crwd-mark"></a>
|
||||
<a name="faq125"></a>
|
||||
**(125) What are the current experimental features?**
|
||||
|
||||
* ...
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126" mark="crwd-mark"></a>
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
FairEmail fetches a message in two steps:
|
||||
|
|
@ -2276,21 +2290,21 @@ If you use a Samsung wearable with the Galaxy Wearable (Samsung Gear) app, you m
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq127" mark="crwd-mark"></a>
|
||||
<a name="faq127"></a>
|
||||
**(127) How can I fix 'Syntactically invalid HELO argument(s)'?**
|
||||
|
||||
The error *... Syntactically invalid HELO argument(s) ...* means that the SMTP server rejected the local IP address or host name. You can likely fix this error by enabling or disabling the advanced indentity option *Use local IP address instead of host name*.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq128" mark="crwd-mark"></a>
|
||||
<a name="faq128"></a>
|
||||
**(128) How can I reset asked questions, for example to show images?**
|
||||
|
||||
You can reset asked questions via the three dots overflow menu in the miscellaneous settings.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq129" mark="crwd-mark"></a>
|
||||
<a name="faq129"></a>
|
||||
**(129) Are ProtonMail, Tutanota supported?**
|
||||
|
||||
ProtonMail uses a proprietary email protocol and [does not directly support IMAP](https://protonmail.com/support/knowledge-base/imap-smtp-and-pop3-setup/), so you cannot use FairEmail to access ProtonMail.
|
||||
|
|
@ -2299,7 +2313,7 @@ Tutanota uses a proprietary email protocol and [does not support IMAP](https://t
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq130" mark="crwd-mark"></a>
|
||||
<a name="faq130"></a>
|
||||
**(130) What does message error ... mean?**
|
||||
|
||||
A series of lines with orangish or red texts with technical information means that debug mode was enabled in the miscellaneous settings.
|
||||
|
|
@ -2316,7 +2330,7 @@ Please see [here](#user-content-faq22) for other error messages in the outbox.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq131" mark="crwd-mark"></a>
|
||||
<a name="faq131"></a>
|
||||
**(131) Can you change the direction for swiping to previous/next message?**
|
||||
|
||||
If you read from left to right, swiping to the left will show the next message. Similarly, if you read from right to left, swiping to the right will show the next message.
|
||||
|
|
@ -2327,7 +2341,7 @@ Anyway, there is a behavior setting to reverse the swipe direction.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq132" mark="crwd-mark"></a>
|
||||
<a name="faq132"></a>
|
||||
**(132) Why are new message notifications silent?**
|
||||
|
||||
Notifications are silent by default on some MIUI versions. Please see [here](http://en.miui.com/thread-3930694-1-1.html) how you can fix this.
|
||||
|
|
@ -2338,7 +2352,7 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq133" mark="crwd-mark"></a>
|
||||
<a name="faq133"></a>
|
||||
**(133) Why is ActiveSync not supported?**
|
||||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
|
@ -2349,7 +2363,7 @@ Note that the desciption of FairEmail starts with the remark that non-standard p
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq134" mark="crwd-mark"></a>
|
||||
<a name="faq134"></a>
|
||||
**(134) Can you add deleting local messages?**
|
||||
|
||||
*POP3*
|
||||
|
|
@ -2366,7 +2380,7 @@ It is also possible to set the swipe left or right action to hide a message.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq135" mark="crwd-mark"></a>
|
||||
<a name="faq135"></a>
|
||||
**(135) Why are trashed messages and drafts shown in conversations?**
|
||||
|
||||
Individual messages will rarely be trashed and mostly this happens by accident. Showing trashed messages in conversations makes it easier to find them back.
|
||||
|
|
@ -2377,7 +2391,7 @@ Similarly, drafts are shown in conversations to find them back in the context wh
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq136" mark="crwd-mark"></a>
|
||||
<a name="faq136"></a>
|
||||
**(136) How can I delete an account/identity/folder?**
|
||||
|
||||
Deleting an account/identity/folder is a little bit hidden to prevent accidents.
|
||||
|
|
@ -2390,14 +2404,14 @@ In the three-dots overflow menu at the top right there is an item to delete the
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq137" mark="crwd-mark"></a>
|
||||
<a name="faq137"></a>
|
||||
**(137) How can I reset 'Don't ask again'?**
|
||||
|
||||
You can reset all questions set to be not asked again in the miscellaneous settings.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq138" mark="crwd-mark"></a>
|
||||
<a name="faq138"></a>
|
||||
**(138) Can you add calendar/contact management/synchronizing?**
|
||||
|
||||
Calendar and contact management can better be done by a separate, specialized app. Note that FairEmail is a specialized email app, not an office suite.
|
||||
|
|
@ -2412,8 +2426,8 @@ Note that FairEmail does support replying to calendar invites (a pro feature) an
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq83" mark="crwd-mark"></a>
|
||||
<a name="faq139" mark="crwd-mark"></a>
|
||||
<a name="faq83"></a>
|
||||
<a name="faq139"></a>
|
||||
**(139) How do I fix 'User is authenticated but not connected'?**
|
||||
|
||||
In fact this Microsoft Exchange specific error is an incorrect error message caused by a bug in older Exchange server software.
|
||||
|
|
@ -2435,14 +2449,14 @@ Note that it should be a backslash and not a forward slash.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq140" mark="crwd-mark"></a>
|
||||
<a name="faq140"></a>
|
||||
**(140) Why does the message text contain strange characters?**
|
||||
|
||||
Displaying strange characters is almost always caused by specifying no or an invalid character encoding by the sending software. FairEmail will assume [ISO 8859-1](https://en.wikipedia.org/wiki/ISO/IEC_8859-1) when no character set or when [US-ASCII](https://en.wikipedia.org/wiki/ASCII) was specified. Other than that there is no way to reliably determine the correct character encoding automatically, so this cannot be fixed by FairEmail. The right action is to complain to the sender.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq141" mark="crwd-mark"></a>
|
||||
<a name="faq141"></a>
|
||||
**(141) How can I fix 'A drafts folder is required to send messages'?**
|
||||
|
||||
To store draft messages a drafts folder is required. In most cases FairEmail will automatically select the drafts folders on adding an account based on [the attributes](https://www.iana.org/assignments/imap-mailbox-name-attributes/imap-mailbox-name-attributes.xhtml) the email server sends. However, some email servers are not configured properly and do not send these attributes. In this case FairEmail tries to identify the drafts folder by name, but this might fail if the drafts folder has an unusual name or is not present at all.
|
||||
|
|
@ -2455,7 +2469,7 @@ Quick link for Gmail: [https://mail.google.com/mail/u/0/#settings/labels](https:
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq142" mark="crwd-mark"></a>
|
||||
<a name="faq142"></a>
|
||||
**(142) How can I store sent messages in the inbox?**
|
||||
|
||||
Generally, it is not a good idea to store sent messages in the inbox because this is hard to undo and could be incompatible with other email clients.
|
||||
|
|
@ -2468,7 +2482,7 @@ If this is not an option, you can [create a rule](#user-content-faq71) to automa
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq143" mark="crwd-mark"></a>
|
||||
<a name="faq143"></a>
|
||||
**~~(143) Can you add a trash folder for POP3 accounts?~~**
|
||||
|
||||
[POP3](https://en.wikipedia.org/wiki/Post_Office_Protocol) is a very limited protocol. Basically only messages can be downloaded and deleted from the inbox. It is not even possible to mark a message read.
|
||||
|
|
@ -2481,12 +2495,12 @@ Version 1.1082 added a local trash folder. Note that trashing a message will per
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq144" mark="crwd-mark"></a>
|
||||
<a name="faq144"></a>
|
||||
**(144) How can I record voice notes?**
|
||||
|
||||
To record voice notes you can press this icon in the bottom action bar of the message composer:
|
||||
|
||||
|
||||
|
||||
|
||||
This requires a compatible audio recorder app to be installed. In particular [this common intent](https://developer.android.com/reference/android/provider/MediaStore.Audio.Media.html#RECORD_SOUND_ACTION) needs to be supported.
|
||||
|
||||
|
|
@ -2496,7 +2510,7 @@ Voice notes will automatically be attached.
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq145" mark="crwd-mark"></a>
|
||||
<a name="faq145"></a>
|
||||
**(145) How can I set a notification sound for an account, folder or sender?**
|
||||
|
||||
Account:
|
||||
|
|
@ -2521,7 +2535,7 @@ Setting a notification sound for an account, folder or sender requires Android 8
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq146" mark="crwd-mark"></a>
|
||||
<a name="faq146"></a>
|
||||
**(146) How can I fix incorrect message times?**
|
||||
|
||||
Since the sent date/time is optional and can be manipulated by the sender, FairEmail uses the server received date/time by default.
|
||||
|
|
@ -2534,7 +2548,7 @@ This will not change the time of already synchronized messages. To solve this, l
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq147" mark="crwd-mark"></a>
|
||||
<a name="faq147"></a>
|
||||
**(147) What should I know about third party versions?**
|
||||
|
||||
You likely came here because you are using a third party build of FairEmail.
|
||||
|
|
@ -2555,7 +2569,7 @@ If you have a problem with the F-Droid build, please check if there is a newer G
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq148" mark="crwd-mark"></a>
|
||||
<a name="faq148"></a>
|
||||
**(148) How can I use an Apple iCloud account?**
|
||||
|
||||
There is a built-in profile for Apple iCloud, but if needed you can find the right settings [here](https://support.apple.com/en-us/HT202304).
|
||||
|
|
@ -2564,7 +2578,7 @@ When using two-factor authentication you might need to use an [app-specific pass
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq149" mark="crwd-mark"></a>
|
||||
<a name="faq149"></a>
|
||||
**(149) How does the unread message count widget work?**
|
||||
|
||||
The unread message count widget shows the number of unread messages either for all accounts or for a selected account, but only for the folders for which new message notifications are enabled.
|
||||
|
|
@ -2577,7 +2591,7 @@ Tapping on the notification will synchronize all folders for which synchronizati
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq150" mark="crwd-mark"></a>
|
||||
<a name="faq150"></a>
|
||||
**(150) Can you add cancelling calendar invites?**
|
||||
|
||||
Cancelling calendar invites (removing calendar events) requires write calendar permission, which will result in effectively granting permission to read and write *all* calendar events of *all* calendars.
|
||||
|
|
@ -2588,7 +2602,7 @@ Inserting new calendar events can be done without permissions with special [inte
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq151" mark="crwd-mark"></a>
|
||||
<a name="faq151"></a>
|
||||
**(151) Can you add backup/restore of messages?**
|
||||
|
||||
An email client is meant to read and write messages, not to backup and restore messages. Note that breaking or losing your device, means losing your messages!
|
||||
|
|
@ -2601,7 +2615,7 @@ If you want to import an mbox file to an existing email account, you can use Thu
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq152" mark="crwd-mark"></a>
|
||||
<a name="faq152"></a>
|
||||
**(152) How can I insert a contact group?**
|
||||
|
||||
You can insert the email addresses of all contacts in a contact group via the three dots menu of the message composer.
|
||||
|
|
@ -2610,7 +2624,7 @@ You can define contact groups with the Android contacts app, please see [here](h
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq153" mark="crwd-mark"></a>
|
||||
<a name="faq153"></a>
|
||||
**(153) Why does permanently deleting Gmail message not work?**
|
||||
|
||||
You might need to change [the Gmail IMAP settings](https://mail.google.com/mail/u/0/#settings/fwdandpop) on a desktop browser to make it work:
|
||||
|
|
@ -2624,14 +2638,14 @@ Some background: Gmail seems to have an additional message view for IMAP, which
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq154" mark="crwd-mark"></a>
|
||||
<a name="faq154"></a>
|
||||
**~~(154) Can you add favicons as contact photos?~~**
|
||||
|
||||
~~Besides that a [favicon](https://en.wikipedia.org/wiki/Favicon) might be shared by many email addresses with the same domain name~~ ~~and therefore is not directly related to an email address, favicons can be used to track you.~~
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq155" mark="crwd-mark"></a>
|
||||
<a name="faq155"></a>
|
||||
**(155) What is a winmail.dat file?**
|
||||
|
||||
A *winmail.dat* file is sent by an incorrectly configured Outlook client. It is a Microsoft specific file format ([TNEF](https://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format)) containing a message and possibly attachments.
|
||||
|
|
@ -2642,7 +2656,7 @@ You can view it with for example the Android app [Letter Opener](https://play.go
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq156" mark="crwd-mark"></a>
|
||||
<a name="faq156"></a>
|
||||
**(156) How can I set up an Office 365 account?**
|
||||
|
||||
An Office 365 account can be set up via the quick setup wizard and selecting *Office 365 (OAuth)*.
|
||||
|
|
@ -2651,7 +2665,7 @@ If the wizard ends with *AUTHENTICATE failed*, IMAP and/or SMTP might be disable
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq157" mark="crwd-mark"></a>
|
||||
<a name="faq157"></a>
|
||||
**(157) How can I set up an Free.fr account?**
|
||||
|
||||
Veuillez [voir ici](https://free.fr/assistance/597.html) pour les instructions.
|
||||
|
|
@ -2662,7 +2676,7 @@ Veuillez [voir ici](http://jc.etiemble.free.fr/abc/index.php/trucs-astuces/confi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq158" mark="crwd-mark"></a>
|
||||
<a name="faq158"></a>
|
||||
**(158) Which camera / audio recorder do you recommend?**
|
||||
|
||||
To take photos and to record audio a camera and an audio recorder app are needed. The following apps are open source cameras and audio recorders:
|
||||
|
|
@ -2674,7 +2688,7 @@ To record voice notes, etc, the audio recorder needs to support [MediaStore.Audi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq159" mark="crwd-mark"></a>
|
||||
<a name="faq159"></a>
|
||||
**(159) What are Disconnect's tracker protection lists?**
|
||||
|
||||
Please see [here](https://disconnect.me/trackerprotection) for more information about Disconnect's tracker protection lists.
|
||||
|
|
@ -2700,19 +2714,19 @@ Updating once a week will probably be sufficient, please see [here](https://gith
|
|||
|
||||
## Podpora
|
||||
|
||||
Podporovány jsou pouze nejnovější verze z Obchodu Play a nejnovější vydání z GitHubu. Znamená to také, že ponížení na starší verze aplikace není podporováno.
|
||||
Only the latest Play store version and latest GitHub release are supported. This also means that downgrading is not supported.
|
||||
|
||||
Požadované funkce by měly:
|
||||
Requested features should:
|
||||
|
||||
* být užitečné pro většinu lidí
|
||||
* nekomplikovat používání FairEmailu
|
||||
* být v souladu s filozofií FairEmailu (zaměření na soukromí s ohledem na bezpečnost)
|
||||
* neporušovat společné standardy (IMAP, SMTP, apod.)
|
||||
|
||||
Funkce, které tyto požadavky nesplňují, budou pravděpodobně odmítnuty. Důvodem je i dlouhodobé zachování udržovatelnosti a podpory.
|
||||
Features not fulfilling these requirements will likely be rejected. This is also to keep maintenance and support in the long run feasible.
|
||||
|
||||
Máte-li dotaz, chcete požádat o funkci, nebo nahlásit chybu, použijte prosím [tento formulář](https://contact.faircode.eu/?product=fairemailsupport).
|
||||
If you have a question, want to request a feature or report a bug, please use [this form](https://contact.faircode.eu/?product=fairemailsupport).
|
||||
|
||||
GitHub issues jsou kvůli častému zneužívání zakázány.
|
||||
GitHub issues are disabled due to frequent misusage.
|
||||
|
||||
Copyright © 2018-2020 Marcel Bokhorst.
|
||||
|
|
|
|||
|
|
@ -695,16 +695,30 @@ Dette betyder, at søgning efter en beskedtekst kræver, at filer indeholdende b
|
|||
|
||||
Under *diverse indstillinger* kan du aktivere *Byg søgeindeks* for markant at øge søgehastigheden på enheden, men dette øger dog samtidig både strøm- og lagerpladsforbruget. Søgeindekset er ordbaseret, så søgning efter deltekster er ikke muligt. Søgning vha. søgeindekset er som standard OG (AND), så søgning efter *æble appelsin* vil søge efter både æble OG appelsin. Ord adskilt med komma resulterer i en ELLER (OR) søgning, så f.eks. *æble, appelsin* vil søge efter enten æble ELLER appelsin. Begge kan kombineres, så søgning efter *æble, appelsin banan* vil søge efter æble ELLER (appelsin OG banan). Brug af søgeindekset er en Pro-funktion.
|
||||
|
||||
Beskedsøgning på enheden er en gratis funktion, beskedsøgning på serveren er en Pro-funktion.
|
||||
Fra version 1.1315 er det muligt at benytte søgeudtryk som dette:
|
||||
|
||||
```
|
||||
æble +banan-kirsebær?nødder
|
||||
```
|
||||
|
||||
Dette vil resultere i en søgning som denne:
|
||||
|
||||
```
|
||||
("æble" OG "banana" OG IKKE "kirsebær") ELLER "nødder"
|
||||
```
|
||||
|
||||
Søgeudtryk kan benyttes søgning på enheden via søgeindekset samt til søgning på e-mailserveren, men af ydelsesårsager ikke til søgning på enheden uden søgeindeks.
|
||||
|
||||
Søgning på enheden er en gratis funktion vha. søgeindekset, mens søgning på serveren er en Pro-funktion.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq14"></a>
|
||||
**(14) Hvordan opsættes en Outlook-/Live-/Hotmail-konto?**
|
||||
|
||||
En Outlook-/Live-/Hotmail-konto kan opsættes via hurtig opsætningsguiden ved at vælg *Outlook*.
|
||||
En Outlook-/Live-/Hotmail-konto kan opsættes via guiden hurtig opsætning ved valg af *Outlook*.
|
||||
|
||||
Anvendelse af en Outlook-, Live- eller Hotmail-konto med tofaktorgodkendelse aktiveret kræver oprettelse af en app-adgangskode. Tjek oplysningerne [hér](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-passwords-two-step-verification).
|
||||
Brug af en Outlook-, Live- eller Hotmail-konto vha. tofaktorgodkendelse forudsætter oprettelse af en app-adgangskode. Tjek informationen [hér](https://support.microsoft.com/en-us/help/12409/microsoft-account-app-passwords-two-step-verification).
|
||||
|
||||
Tjek Microsoft-instruktionerne [hér](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040).
|
||||
|
||||
|
|
@ -715,20 +729,20 @@ Tjek [denne FAQ](#user-content-faq156) for opsætnig af en Office365-konto.
|
|||
<a name="faq15"></a>
|
||||
**(15) Hvorfor genindlæses beskedteksten hele tiden?**
|
||||
|
||||
Beskedhovede og -brødtekst hentes separat fra serveren. Større beskeders beskedtekst forudindlæses ikke på takserede forbindelser, og den skal derfor hentes, når beskeden åbnes. Beskedteksten genindlæses kontinuerligt, hvis der ingen forbindelse er til kontoen, se også næste spørgsmål.
|
||||
Beskedhovede og -brødtekst hentes separat fra serveren. Beskedteksten i større beskeder forudindlæses ikke på takserede forbindelser, og den skal derfor hentes, når beskeden åbnes. Beskedteksten genindlæses kontinuerligt ved manglende forbindelse til kontoen. Se også næste spørgsmål.
|
||||
|
||||
Du kan tjekke konto- og mappelisten for kontoen og mappetilstanden (se forklaringen til betydningen af ikonerne) og operationslisten tilgængelig via hovednavigeringsmenuen til afventende operationer (se [denne FAQ](#user-content-faq3) for betydningen af operationerne).
|
||||
Du kan tjekke konto- og mappelisten for kontoen og mappetilstanden (se forklaringen til betydningen af ikonerne) samt operationslisten tilgængelig via hovednavigeringsmenuen til afventende operationer (se [denne FAQ](#user-content-faq3) for betydningen af operationerne).
|
||||
|
||||
I modtagelsesindstillingerne kan man indstille den maksimale størrelse for automatisk download af beskeder på takserede forbindelser.
|
||||
I modtagelsesindstillingerne kan den maksimale størrelse for automatisk download af beskeder på takserede forbindelser indstilles.
|
||||
|
||||
Mobilforbindelser er næsten altid takserede, og visse Wi-Fi hotspots (betalte) er det ligeledes.
|
||||
Mobilforbindelser er næsten altid takserede, og visse Wi-Fi hotspots er det ligeledes.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Hvorfor synkroniseres beskeder ikke?**
|
||||
|
||||
Mulige årsager til fejl i beskedsynkronisering (sendte eller modtagne) er:
|
||||
Mulige årsager til fejl i beskedsynkronisering (sendte eller modtagne):
|
||||
|
||||
* Konto eller mappe(r) er ikke opsat til at synkronisere
|
||||
* Der er indstillet for få synkroniseringsdage
|
||||
|
|
@ -736,11 +750,11 @@ Mulige årsager til fejl i beskedsynkronisering (sendte eller modtagne) er:
|
|||
* E-mailserveren er midlertidigt utilgængelig
|
||||
* Android har stoppet synkroniseringstjenesten
|
||||
|
||||
Tjek derfor dine konto- og mappeindstillinger, og tjek, at konti/mapper er forbundet (se forklaringen i navigeringsmenuen om ikonernes betydning).
|
||||
Tjek derfor dine konto- og mappeindstillinger, og tjek, at konti/mapper er forbundet (se forklaringen i navigeringsmenuen ang. ikonernes betydning).
|
||||
|
||||
Er der nogle fejlmeddelelser, så tjek [denne FAQ](#user-content-faq22).
|
||||
Er der evt. fejlmeddelelser, så tjek [denne FAQ](#user-content-faq22).
|
||||
|
||||
På enheder, hvor en masse apps som slås om hukommelsen, kan Android muligvis som en sidste udvej stoppe synkroniseringstjenesten.
|
||||
På enheder, hvor en masse apps som slås om hukommelsen, kan Android muligvis stoppe synkroniseringstjenesten som en sidste udvej.
|
||||
|
||||
Visse Android-versioner stopper apps og tjenester for aggressivt. Se [dette dedikerede websted](https://dontkillmyapp.com/) samt [dette Android-problem](https://issuetracker.google.com/issues/122098785) for yderligere information.
|
||||
|
||||
|
|
@ -751,7 +765,7 @@ Deaktivering af batterioptimering (opsætningstrin 4) reducerer chancen for, at
|
|||
<a name="faq17"></a>
|
||||
**~~(17) Hvorfor fungerer manuel synkronisering ikke?~~**
|
||||
|
||||
~~Hvis menuen *Synkronisér nu* er nedtonet, er der ingen forbindelse til kontoen.~~
|
||||
~~Er menuen *Synkronisér nu* er nedtonet, er der ingen forbindelse til kontoen.~~
|
||||
|
||||
~~Se foregående spørgsmål for yderligere information.~~
|
||||
|
||||
|
|
@ -760,7 +774,7 @@ Deaktivering af batterioptimering (opsætningstrin 4) reducerer chancen for, at
|
|||
<a name="faq18"></a>
|
||||
**(18) Hvorfor vises beskedforhåndsvisning ikke altid?**
|
||||
|
||||
Beskedforhåndsvisningen kan ikke vises, såfremt beskedbrødteksten endnu ikke er downloadet. Se også [denne FAQ](#user-content-faq15).
|
||||
Beskedforhåndsvisningen kan ikke vises, hvis beskedbrødteksten endnu ikke er downloadet. Tjek også [denne FAQ](#user-content-faq15).
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -776,78 +790,78 @@ Det rigtige spørgsmål er, "*hvorfor der er så mange skatter og afgifter?*":
|
|||
|
||||
Så dét, der er tilbage til udvikleren, er blot en brøkdel af dét, du betaler.
|
||||
|
||||
Bemærk, at det kun er nødvendigt at købe visse bekvemmeligheds- og avancerede funktioner, hvilket betyder, at FairEmail grundlæggende er gratis at anvende.
|
||||
Bemærk, at det kun er nødvendigt at købe visse bekvemmeligheds- og avancerede funktioner, hvilket betyder, at FairEmail grundlæggende er gratis at benytte.
|
||||
|
||||
Bemærk også, at de fleste gratis apps ser ud til ikke at være bæredygtige i længden, hvorimod FairEmail vedligeholdes og understøttes korrekt, samt at gratis apps kan have faldgruber, såsom at de lækker fortrolige oplysninger via Internet.
|
||||
|
||||
Jeg har arbejdet på FairEmail næsten dagligt i mere end et halvt år, så jeg synes, at prisen er mere end rimelig. Af samme årsag vil der heller ikke være rabatter.
|
||||
Jeg har arbejdet på FairEmail næsten dagligt i flere end to år, så jeg synes, at prisen er mere end rimelig. Af samme årsag vil der heller ikke være rabatter.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq20"></a>
|
||||
**(20) Kan jeg få refusion?**
|
||||
|
||||
Hvis en købt Pro-funktion ikke fungerer som tilsigtet, og dette ikke skyldes et problem i de gratis funktioner, og jeg ikke kan løse problemet rettidigt, så kan du få en refusion. I alle øvrigee tilfælde er refusion ikke mulig. Under ingen omstændigheder er der mulighed for refusion for noget problem relateret til de gratis funktioner, da der ikke blev betalt noget for dem, og da de kan evalueres uden nogen begrænsning. Jeg tager ansvar som sælger for at levere dét, der er blevet lovet, og jeg forventer, at du tager ansvar for at informere dig om, hvad det er, du køber.
|
||||
Hvis en (købt) Pro-funktion ikke fungerer som tilsigtet, og dette ikke skyldes et problem i de gratis funktioner, og jeg ikke kan løse problemet rettidigt, så kan du få en refusion. I alle øvrigee tilfælde er refusion ikke mulig. Der er under ingen omstændigheder refusionmulighed for noget problem relateret til de gratis funktioner, da der intet er betalt for disse, og da de kan evalueres uden nogen begrænsning. Jeg tager som sælger ansvar for at levere dét, der er blevet lovet, og jeg forventer, at du tager ansvar for at informere dig om, hvad det er, du køber.
|
||||
|
||||
<a name="faq21"></a>
|
||||
**(21) Hvordan aktiveres notifikationslyset?**
|
||||
|
||||
Før Android 8 Oreo: Der findes en avanceret indstilling i opsætningen til dette.
|
||||
|
||||
Android 8 Oreo og senere: Tjek [hér](https://developer.android.com/training/notify-user/channels), hvordan du opsætter notifikationskanaler. Du kan benytte knappen *Håndtér notifikationer* i opsætningen for at gå direkte til Android-notifikationsindstillingerne. Bemærk, at apps ikke længere kan ændre notifikationsindstillinger, herunder indstillinger for notifikationslys, på Android 8 Oreo og senere. Apps designet og målrettet ældre Android-versioner kan muligvis stadig styre indholdet af notifikationer, men sådanne apps kan ikke længere opdatere, og nyere Android-versioner viser en advarsel om, at sådanne apps er forældede.
|
||||
Android 8 Oreo og senere: Tjek [hér](https://developer.android.com/training/notify-user/channels), hvordan du opsætter notifikationskanaler. Du kan benytte knappen *Håndtér notifikationer* i opsætningen for at gå direkte til Android-notifikationsindstillingerne. Note that apps cannot change notification settings, including the notification light setting, on Android 8 Oreo and later anymore. Apps designed and targeting older Android versions might still be able to control the contents of notifications, but such apps cannot be updated anymore and recent Android versions will show a warning that such apps are outdated.
|
||||
|
||||
Undertiden er det nødvendigt at deaktivere indstillingen *Vis beskedforhåndsvisning i notifikationer* eller at aktivere indstillingerne *Vis kun notifikationer med en forhåndsvisningstekst* for at omgå en fejl i Android. Dette gælder muligvis også notifikationslyde og vibrationer.
|
||||
Sometimes it is necessary to disable the setting *Show message preview in notifications* or to enable the settings *Show notifications with a preview text only* to workaround a bug in Android. This might apply to notification sounds and vibrations too.
|
||||
|
||||
Indstilling af lys-farven før Android 8 understøttes ikke og er ikke muligt på Android 8 og senere.
|
||||
Setting a light color before Android 8 is not supported and on Android 8 and later not possible.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq22"></a>
|
||||
**(22) Hvad betyder konto-/mappefejl ...?**
|
||||
**(22) What does account/folder error ... mean?**
|
||||
|
||||
FairEmail skjuler ikke fejl (hvilket lignende apps ofte gør), så det er lettere at diagnosticere problemer.
|
||||
FairEmail does not hide errors like similar apps often do, so it is easier to diagnose problems.
|
||||
|
||||
FairEmail forsøger automatisk at genoprette forbindelse efter en forsinkelse. Denne forsinkelse fordobles efter hvert mislykket forsøg for at forhindre batteridræning samt at blive låst ude permanent.
|
||||
FairEmail will automatically try to connect again after a delay. This delay will be doubled after each failed attempt to prevent draining the battery and to prevent from being locked out permanently.
|
||||
|
||||
Der er generelle såvel som specifikke fejl for Gmail-konti (se nedenfor).
|
||||
There are general errors and errors specific to Gmail accounts (see below).
|
||||
|
||||
**Generelle fejl**
|
||||
**General errors**
|
||||
|
||||
Fejlen *... Godkendelse mislykkedes ...* eller *... GODKENDELSE mislykkedes ...* skyldes sandsynligvis forkert brugernavn/adgangskode. Viss udbydere forventer som brugernavn blot *brugernavn* og andre din fulde e-mail *brugernavn@eksempel.dk*. Benyttes kopiér/indsæt til angivelse af brugernavn/adgangskode kan der muligvis medtages usynlige tegn, hvilket også kan forårsage denne fejl. Visse adgangskodehåndteringer er kendt for at gøre dette forkert også. Brugernavnet kan være minuskel/versal sensitivt, så prøv kun med minuskler. Adgangskoden er fortrinsvis minuskel/versal sensitivt. Visse udbydere kræver brug af en app-adgangskode i stedet for kontoadgangskoden, så tjek din leverandørs dokumentation. Det nogle gange nødvendigt først at muliggøre ekstern adgang (IMAP/SMTP) på udbyderens websted. Øvrige mulige årsager er, at kontoen er blokeret, eller at indlogning er administrativt begrænset på en eller anden måde, f.eks. ved kun at tillade indlogning fra bestemte netværk/IP-adresser.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
Fejlen *... For mange fejlede godkendelsesforsøg ...*betyder sandsynligvis, at du bruger en Yahoo-kontoadgangskode i stedet for en app ditto. Se [denne FAQ](#user-content-faq88) vedr. opsætning af en Yahoo-konto.
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
Meddelelsen *... +OK ...* betyder sandsynligvis, at en POP3-port (normalt portnummer 995) anvendes til en IMAP-konto (normalt ellers portnummer 993).
|
||||
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
|
||||
|
||||
Fejlene *... ugyldig hilsen ...*, *... kræver gyldig adresse ...* og *... Parameter til HELO overholder ikke RFC-syntaks ...* kan sandsynligvis løses ved at ændre den avancerede identitetsindstilling *Anvend lokal IP-adresse i stedet for værtsnavn*.
|
||||
The errors *... invalid greeting ...*, *... requires valid address ...* and *... Parameter to HELO does not conform to RFC syntax ...* can likely be solved by changing the advanced identity setting *Use local IP address instead of host name*.
|
||||
|
||||
Fejlene *... Kunne ikke oprette forbindelse til vært ...*, *... Forbindelse nægtet ...* eller *... Netværk kan ikke nås ...* betyder, at FairEmail ikke kunne oprette forbindelse til e-mailserveren.
|
||||
Fejlene *... Couldn't connect to host ...*, *... Connection refused ...* or *... Network unreachable ...* mean that FairEmail was not able to connect to the email server.
|
||||
|
||||
Fejlen *... Vært er uopløst ...* eller "*... Kan ikke opløse vært ...* betyder, at e-mailserverens værtsadressen ikke kunne opløses/udredes. Dette kan forårsages af annonceblokering, eller en utilgængelig eller ikke korrekt fungerende [DNS-server](https://en.wikipedia.org/wiki/Domain_Name_System).
|
||||
Fejlen *... Host is unresolved ...* or "*... Unable to resolve host ...* means that the address of the email server could not be resolved. This might be caused by ad blocking or an unreachable or not properly working [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
|
||||
|
||||
Fejlen *... Software forårsaget forbindelsesafbrydelse ...* betyder, at e-mailserveren, eller noget mellem FairEmail og denne, aktivt afsluttede en eksisterende forbindelse. Dette kan f.eks. ske, når tilslutningen pludselig blev mistet. Et typisk eksempel er aktivering af Flytilstand.
|
||||
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
|
||||
|
||||
Fejlene *... BYE, logger ud ...*, *... Forbindelse nulstillet af peer ... * betyder, at e-mailserveren aktivt afsluttede en eksisterende forbindelse.
|
||||
The errors *... BYE Logging out ...*, *... Connection reset by peer ...* mean that the email server actively terminated an existing connection.
|
||||
|
||||
Fejlen *... Forbindelse lukket af peer ...* kan forårsages af en ikke-opdateret Exchange-server, se [hér](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for yderligere oplysninger.
|
||||
The error *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
|
||||
|
||||
Fejlene *... Læsefejl ...*, *... Skrivefejl ...*, *... Læsning fik timeout ...*, *... Ødelagt pipe ...* betyder, at e-mailserveren ikke længere svarer, eller at Internetforbindelsen er ringe.
|
||||
The errors *... Read error ...*, *... Write error ...*, *... Read timed out ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
|
||||
|
||||
Fejlen *... Uventet afslutning af zlib-inputstrøm ...* betyder, at ikke alle data blev modtaget, muligvis grundet en dårlig/afbrudt forbindelse.
|
||||
The error *... Unexpected end of zlib input stream ...* means that not all data was received, possibly due to a bad or interrupted connection.
|
||||
|
||||
Fejlen *... forbindelsesfejl ...* kan indikere [For mange samtidige forbindelser](#user-content-faq23).
|
||||
The error *... connection failure ...* could indicate [Too many simultaneous connections](#user-content-faq23).
|
||||
|
||||
Advarslen *... Uunderstøttet kodning ...* betyder, at beskedens tegnsæt er ukendt eller uunderstøttet. FairEmail benytter generelt ISO-8859-1 (Latin1), hvilket i de fleste tilfælde vil resultere i korrekte beskedvisninger.
|
||||
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.
|
||||
|
||||
[Se hér](#user-content-faq4) vedr. fejlene *... Ikke-betroet ... ikke i certifikat ...*, * ... Ugyldigt sikkerhedscertifikat (kan ikke bekræfte serveridentitet) ...* eller *... Betroet anker til certificeringssti ikke fundet ...*
|
||||
Please [see here](#user-content-faq4) for the errors *... Untrusted ... not in certificate ...*, *... Invalid security certificate (Can't verify identity of server) ...* or *... Trust anchor for certification path not found ...*
|
||||
|
||||
[Se hér](#user-content-faq127) vedr. fejlen *... Ét eller flere syntaktisk ugyldige HELO-argumenter ... *.
|
||||
Please [see here](#user-content-faq127) for the error *... Syntactically invalid HELO argument(s) ...*.
|
||||
|
||||
[Se hér](#user-content-faq41) vedr. fejlen *... Handshake mislykkedes ...*.
|
||||
Please [see here](#user-content-faq41) for the error *... Handshake failed ...*.
|
||||
|
||||
Se [hér](https://linux.die.net/man/3/connect) ang. betydningen af fejlkoder såsom EHOSTUNREACH og ETIMEDOUT.
|
||||
See [here](https://linux.die.net/man/3/connect) for what error codes like EHOSTUNREACH and ETIMEDOUT mean.
|
||||
|
||||
Mulige årsager:
|
||||
Possible causes are:
|
||||
|
||||
* Firewall eller router blokerer forbindelser til serveren
|
||||
* Værtsnavnet eller portnummeret er ugyldigt
|
||||
|
|
@ -857,127 +871,127 @@ Mulige årsager:
|
|||
* E-mai-serveren nægter at acceptere en besked, fordi den f.eks. er for stor eller indeholder uacceptable links
|
||||
* Der er for mange forbindelser til serveren, se også næste spørgsmål
|
||||
|
||||
Mange offentlige Wi-Fi netværk blokerer udgående e-mail for at forhindre spam. Dette kan af og til omgås ved brug af en anden SMTP-port. Se leverandørdokumentationen ang. anvendelige portnumre.
|
||||
Many public Wi-Fi networks block outgoing email to prevent spam. Sometimes you can workaround this by using another SMTP port. See the documentation of the provider for the usable port numbers.
|
||||
|
||||
Benytter du et [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), kan VPN-udbyderen muligvis blokere forbindelsen, hvis den for aggressivt forsøger at forhindre spam. Bemærk, at [Google Fi](https://fi.google.com/) også benytter et VPN.
|
||||
If you are using a [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), the VPN provider might block the connection because it is too aggressively trying to prevent spam. Note that [Google Fi](https://fi.google.com/) is using a VPN too.
|
||||
|
||||
**Afsendelsesfejl**
|
||||
**Send errors**
|
||||
|
||||
SMTP-servere kan afvise beskeder [af forskellige årsager](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes). For store beskeder og udløsning af en e-mailservers spamfilteret er de mest almindelige årsager.
|
||||
SMTP servers can reject messages for [a variety of reasons](https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes). Too large messages and triggering the spam filter of an email server are the most common reasons.
|
||||
|
||||
* Gmails størrelsesbegrænsning for vedhæftninger [udgør 25 MB](https://support.google.com/mail/answer/6584)
|
||||
* Outlooks og Office 365' størrelsesbegrænsning for vedhæftninger [udgør 20 MB](https://support.microsoft.com/en-us/help/2813269/attachment-size-exceeds-the-allowable-limit-error-when-you-add-a-large)
|
||||
* Yahoos størrelsesbegrænsning for vedhæftninger [udgør 25 MB](https://help.yahoo.com/kb/SLN5673.html)
|
||||
* For *554 5.7.1 Tjeneste utilgængelig; Klient vært xxx.xxx.xxx.xxx blokeret*, tjek venligst [hér](https://docs.gandi.net/en/gandimail/faq/error_types/554_5_7_1_service_unavailable.html)
|
||||
|
||||
**Gmail-fejl**
|
||||
**Gmail errors**
|
||||
|
||||
Godkendelsen af Gmail-kontiopsætninger vha. hurtigguiden skal periodisk opfriskes via [Android-kontohåndteringen](https://developer.android.com/reference/android/accounts/AccountManager). Dette kræver kontakt-/konto-tilladelser samt Internetforbindelse.
|
||||
The authorization of Gmail accounts setup with the quick wizard needs to be periodically refreshed via the [Android account manager](https://developer.android.com/reference/android/accounts/AccountManager). This requires contact/account permissions and internet connectivity.
|
||||
|
||||
Fejlen *... Godkendelse mislykkedes ... Konto ikke fundet ...* betyder, at en tidligere godkendt Gmail-konto er blevet fjernet fra enheden.
|
||||
Fejlen *... Godkendelse mislykkedes ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
|
||||
|
||||
Fejlene *... Godkendelse mislykkedes ... Ingen token ved opfriskning ...* betyder, at Android-kontohåndteringen ikke kunne opfriske godkendelsen af en Gmail-konto.
|
||||
The errors *... Authentication failed ... No token on refresh ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
|
||||
|
||||
Fejlen *... Godkendelse mislykkedes ... Ugyldige akkreditiverer ... netværksfejl ...* betyder, at Android-kontohåndteringen var ude af stand til at opfriske godkendelsen af en Gmail-konto grundet Internetforbindelsesproblemer
|
||||
The error *... Authentication failed ... Invalid credentials ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
|
||||
|
||||
Fejlen *... Godkendelse mislykkedes ... Ugyldige akkreditiver ...* kan forårsages af tilbagekaldelse af de krævede konto-/kontakter-tilladelser. Start blot guiden (men vælg ikke en konto) for at tildele de krævede tilladelser igen.
|
||||
The error *... Authentication failed ... Invalid credentials ...* could be caused by having revoked the required account/contacts permissions. Just start the wizard (but do not select an account) to grant the required permissions again.
|
||||
|
||||
Fejlen *... ServiceDisabled ...* kan skyldes din tilmelding til [Avanceret Beskyttelsesprogram](https://landing.google.com/advancedprotection/): "*For at læse din e-mails, skal du benytte Gmail - Du kan ikke benytte din Google-konto med apps og tjenester, som kræver adgang til følsomme data såsom dine e-mails*", tjek [hér](https://support.google.com/accounts/answer/7519408?hl=en&ref_topic=9264881).
|
||||
The eror *... ServiceDisabled ...* might be caused by enrolling in the [Advanced Protection Program](https://landing.google.com/advancedprotection/): "*To read your email, you can (must) use Gmail - You won’t be able to use your Google Account with some (all) apps & services that require access to sensitive data like your emails*", see [here](https://support.google.com/accounts/answer/7519408?hl=en&ref_topic=9264881).
|
||||
|
||||
Hvis du er i tvivl, kan du anmode om [support](#user-content-support).
|
||||
When in doubt, you can ask for [support](#user-content-support).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq23"></a>
|
||||
**(23) Hvorfor ses advarslen ... ?**
|
||||
**(23) Why do I get alert ... ?**
|
||||
|
||||
*Generelt*
|
||||
*General*
|
||||
|
||||
Avarsler er advarselsmeddelelser sendt af e-mailservere.
|
||||
Alerts are warning messages sent by email servers.
|
||||
|
||||
*For mange samtidige forbindelser* eller *Maksimalt antal forbindelser overskredet*
|
||||
*Too many simultaneous connections* or *Maximum number of connections exceeded*
|
||||
|
||||
Denne advarsel afsendes ved for mange mappeforbindelser til den samme e-mailkonto på samme tid.
|
||||
This alert will be sent when there are too many folder connections for the same email account at the same time.
|
||||
|
||||
Mulige årsager:
|
||||
Possible causes are:
|
||||
|
||||
* Adskillige e-mailklienter er forbundet til den samme konto
|
||||
* Samme e-mailklient er forbundet adskillige gange til den samme konto
|
||||
* Tidligere forbindelser blev brat afsluttet, f.eks. ved en pludselig mistet Internetforbindelse
|
||||
|
||||
Prøv først at afvente lidt for at se, om problemet løser sig selv, ellers:
|
||||
First try to wait some time to see if the problem resolves itself, else:
|
||||
|
||||
* Skift enten til periodisk tjek for beskeder i modtagelsesindstillingerne, hvilket resulterer i, at mapper åbnes én ad gangen
|
||||
* eller indstil nogle mapper til polling i stedet for at synkronisation (langt tryk på mappen i mappelisten, Redigér egenskaber)
|
||||
|
||||
Det maksimale antal samtidige mappeforbindelser til Gmail udgør 15, så du kan synkronisere maks. 15 mapper samtidigt på tværs af *alle* dine enheder. Af samme grund er Gmail-*brugermapper* som standard opsat til polling fremfor altid at synkronisere. Om nødvendigt, eller ønsket, kan dette ændres vha. langt tryk på en mappe i mappelisten og vælge *Redigér egenskaber*. Tjek oplysningerne [hér](https://support.google.com/mail/answer/7126229).
|
||||
The maximum number of simultaneous folder connections for Gmail is 15, so you can synchronize at most 15 folders simultaneously on *all* your devices at the same time. For this reason Gmail *user* folders are set to poll by default instead of synchronize always. When needed or desired, you can change this by long pressing a folder in the folder list and selecting *Edit properties*. See [here](https://support.google.com/mail/answer/7126229) for details.
|
||||
|
||||
Ved brug af en Dovecot-server, skal indstillingen [mail_max_userip_connections](https://doc.dovecot.org/settings/dovecot_core_settings/#mail-max-userip-connections) muligvis ændres.
|
||||
When using a Dovecot server, you might want to change the setting [mail_max_userip_connections](https://doc.dovecot.org/settings/dovecot_core_settings/#mail-max-userip-connections).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq24"></a>
|
||||
**(24) Hvad betyder gennemse beskeder på serveren?**
|
||||
**(24) What is browse messages on the server?**
|
||||
|
||||
Gennemse beskeder på serveren henter beskeder fra e-mailserveren i realtid, når du kommer til slutningen af listen over synkroniserede beskeder, også når mappen er indstillet til ikke at synkronisere. Du kan deaktivere denne funktion under Avancerede kontoindstillinger.
|
||||
Browse messages on the server will fetch messages from the email server in real time when you reach the end of the list of synchronized messages, even when the folder is set to not synchronize. You can disable this feature in the advanced account settings.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq25"></a>
|
||||
**(25) Hvorfor kan der ikke vælges/åbnes/gemmes et billede, vedhæftning eller fil?**
|
||||
**(25) Why can't I select/open/save an image, attachment or a file?**
|
||||
|
||||
Når et menupunkt til at vælge/åbne/gemme en fil er deaktiveret (nedtonet), eller når du ser meddelelsen *Lageradgangs-framework ikke tilgængelig*, så er [lageradgangs-framework'en](https://developer.android.com/guide/topics/providers/document-provider), er en standard Android-komponent, sandsynligvis ikke til stede. Dette kan skyldes, at din tilpassede ROM ikke inkluderer den, eller at den er blevet fjernet (debloated).
|
||||
When a menu item to select/open/save a file is disabled (dimmed) or when you get the message *Storage access framework not available*, the [storage access framework](https://developer.android.com/guide/topics/providers/document-provider), a standard Android component, is probably not present. This might be because your custom ROM does not include it or because it was actively removed (debloated).
|
||||
|
||||
FairEmail anmoder ikke om lagerpladstilladelser, så dette framework kræves for at kunne vælge filer og mapper. Ingen app, undtagen måske filhåndteringer målrettet Android 4.4 KitKat eller senere, bør anmode om lagerpladstilladelser, da denne giver adgang til *alle* filer.
|
||||
FairEmail does not request storage permissions, so this framework is required to select files and folders. No app, except maybe file managers, targeting Android 4.4 KitKat or later should ask for storage permissions because it would allow access to *all* files.
|
||||
|
||||
Framework'en for lagerpladsadgang leveres af pakken *com.android.documentsui*, der er synlig som *Filer*-app i visse Android-versioner (specifikt OxygenOS).
|
||||
The storage access framework is provided by the package *com.android.documentsui*, which is visible as *Files* app on some Android versions (notable OxygenOS).
|
||||
|
||||
Du kan aktivere framework'en for lagerpladsadgang (igen) med denne adb-kommando:
|
||||
You can enable the storage access framework (again) with this adb command:
|
||||
|
||||
```
|
||||
pm install -k --user 0 com.android.documentsui
|
||||
```
|
||||
|
||||
Alternativt kan du muligvis aktivere *Filer*-appen igen vha. Android app-indstillingerne.
|
||||
Alternatively, you might be able to enable the *Files* app again using the Android app settings.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq26"></a>
|
||||
**(26) Kan jeg hjælpe med at oversætte FairEmail til mit sprog?**
|
||||
**(26) Can I help to translate FairEmail in my own language?**
|
||||
|
||||
Ja, du kan oversætte FairEmail-teksterne til dit sprog [via Crowdin](https://crowdin.com/project/open-source-email). Tilmelding er gratis.
|
||||
Yes, you can translate the texts of FairEmail in your own language [on Crowdin](https://crowdin.com/project/open-source-email). Registration is free.
|
||||
|
||||
Ønsker du dit navn/alias inkluderet på listen over bidragsydere i appens *Om*-afsnit, så [kontakt mig](https://contact.faircode.eu/?product=fairemailsupport) venligst.
|
||||
If you would like your name or alias to be included in the list of contributors in *About* the app, please [contact me](https://contact.faircode.eu/?product=fairemailsupport).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq27"></a>
|
||||
**(27) Hvordan skelnes mellem indlejrede eller eksterne billeder?**
|
||||
**(27) How can I distinguish between embedded and external images?**
|
||||
|
||||
Eksternt billede:
|
||||
External image:
|
||||
|
||||
|
||||
|
||||
|
||||
Indlejret billede:
|
||||
Embedded image:
|
||||
|
||||
|
||||
|
||||
|
||||
Ødelagt billede:
|
||||
Broken image:
|
||||
|
||||
|
||||
|
||||
|
||||
Bemærk, at download af eksterne billeder fra en fjernserver kan bruges til at registrere, at du har set en besked, hvilket du sandsynligvis ikke ønsker, såfremt beskeden er spam eller ondsindet.
|
||||
Note that downloading external images from a remote server can be used to record you did see a message, which you likely don't want if the message is spam or malicious.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq28"></a>
|
||||
**(28) Hvordan håndteres statusbjælkenotifikationer?**
|
||||
**(28) How can I manage status bar notifications?**
|
||||
|
||||
I opsætningen findes knappen *Håndtér notifikationer *til at gå direkte til Android-notifikationsindstillingerne for FairEmail.
|
||||
In the setup you'll find a button *Manage notifications* to directly navigate to the Android notifications settings for FairEmail.
|
||||
|
||||
I Android 8.0 Oreo og senere kan du håndtere egenskaberne for de individuelle notifikationskanaler, f.eks. indstilling af en bestemt notifikationslyd eller visning af notifikationer på låseskærmen.
|
||||
On Android 8.0 Oreo and later you can manage the properties of the individual notification channels, for example to set a specific notification sound or to show notifications on the lock screen.
|
||||
|
||||
FairEmail har flg. notifikationskanaler:
|
||||
FairEmail has the following notification channels:
|
||||
|
||||
* Tjeneste: Benytttes til notifikation om synkroniseringstjenesten, se også [denne FAQ](#user-content-faq2)
|
||||
* Send: Benyttes til sendetjenestenotiifikation
|
||||
|
|
@ -985,65 +999,65 @@ FairEmail har flg. notifikationskanaler:
|
|||
* Advarsel: Benyttes til advarselsnotifikationer
|
||||
* Fejl: Benyttes til notifikationer om fejl
|
||||
|
||||
Tjek [hér](https://developer.android.com/guide/topics/ui/notifiers/notifications#ManageChannels) for detaljer om notifikationskanaler. Kort sagt: Tryk på notifikationskanalens navn for at tilgå kanalindstillingerne.
|
||||
See [here](https://developer.android.com/guide/topics/ui/notifiers/notifications#ManageChannels) for details on notification channels. In short: tap on the notification channel name to access the channel settings.
|
||||
|
||||
På Android før Android 8 Oreo kan du opsætte notifikationslyden i indstillingerne.
|
||||
On Android before Android 8 Oreo you can set the notification sound in the settings.
|
||||
|
||||
Tjek [denne FAQ](#user-content-faq21), hvis din enhed har et notifikationslys.
|
||||
See [this FAQ](#user-content-faq21) if your device has a notification light.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq29"></a>
|
||||
**(29) Hvordan fås notifikationer om nye beskeder for andre mapper?**
|
||||
**(29) How can I get new message notifications for other folders?**
|
||||
|
||||
Benyt blot et langt tryk på en mappe, vælg *Redigér egenskaber*, og aktivér enten *Vis i den fælles indbakke* eller *Notificér om nye beskeder* (kun tilgængelig på Android 7 Nougat og senere) og tryk på *Gem*.
|
||||
Just long press a folder, select *Edit properties*, and enable either *Show in unified inbox* or *Notify new messages* (available on Android 7 Nougat and later only) and tap *Save*.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq30"></a>
|
||||
**(30) Hvordan kan de medfølgende hurtige indstillinger benyttes?**
|
||||
**(30) How can I use the provided quick settings?**
|
||||
|
||||
Der findes hurtige indstillinger (indstillingsfliser) for:
|
||||
There are quick settings (settings tiles) available to:
|
||||
|
||||
* globalt aktivere/deaktivere synkronisering
|
||||
* vise antallet af nye beskeder og markér dem som set (ikke læst)
|
||||
|
||||
Hurtige indstillinger kræver Android 7.0 Nougat eller senere. Brug af indstillingsfliserne forklares [hér](https://support.google.com/android/answer/9083864).
|
||||
Quick settings require Android 7.0 Nougat or later. The usage of settings tiles is explained [here](https://support.google.com/android/answer/9083864).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq31"></a>
|
||||
**(31) Hvordan kan de medfølgende genveje benyttes?**
|
||||
**(31) How can I use the provided shortcuts?**
|
||||
|
||||
Der findes genveje til:
|
||||
There are shortcuts available to:
|
||||
|
||||
* skrive en ny besked til en favoritkontakt
|
||||
* opsætte konti, identiteter mv.
|
||||
|
||||
Genveje kræver Android 7.1 Nougat eller senere. Brug af genveje forklares [hér](https://support.google.com/android/answer/2781850).
|
||||
Shortcuts require Android 7.1 Nougat or later. The usage of shortcuts is explained [here](https://support.google.com/android/answer/2781850).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq32"></a>
|
||||
**(32) Hvordan tjekkes, om læsning af e-mails virkelig er sikkert?**
|
||||
**(32) How can I check if reading email is really safe?**
|
||||
|
||||
Man kan benytte [E-mail Fortrolighedstester](https://www.emailprivacytester.com/) til dette.
|
||||
You can use the [Email Privacy Tester](https://www.emailprivacytester.com/) for this.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq33"></a>
|
||||
**(33) Hvorfor fungerer redigerede afsenderadresser ikke?**
|
||||
**(33) Why are edited sender addresses not working?**
|
||||
|
||||
For at forhindre spam accepterer de fleste udbydere kun bekræftede adresser ved afsendelser.
|
||||
Most providers accept validated addresses only when sending messages to prevent spam.
|
||||
|
||||
F.eks. ændrer Google beskedhoveder for *ikke-bekræftede* adresser på flg. vis:
|
||||
For example Google modifies the message headers like this for *unverified* addresses:
|
||||
|
||||
```
|
||||
Fra: Nogen <somebody@example.org>
|
||||
X-Google-Originale-Fra: Nogen <somebody+extra@example.org>
|
||||
From: Somebody <somebody@example.org>
|
||||
X-Google-Original-From: Somebody <somebody+extra@example.org>
|
||||
```
|
||||
|
||||
Dette betyder, at den redigerede afsenderadresse automatisk erstattes af en bekræftet adresse inden bekedafsendelsen.
|
||||
This means that the edited sender address was automatically replaced by a verified address before sending the message.
|
||||
|
||||
Note that this is independent of receiving messages.
|
||||
|
||||
|
|
@ -1210,7 +1224,7 @@ The following information is needed:
|
|||
<provider
|
||||
name="Gmail"
|
||||
link="https://support.google.com/mail/answer/7126229" // link to the instructions of the provider
|
||||
type="com.google"> // dette kræves ikke
|
||||
type="com.google"> // this is not needed
|
||||
<imap
|
||||
host="imap.gmail.com"
|
||||
port="993"
|
||||
|
|
|
|||
|
|
@ -695,12 +695,26 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Das Verwenden des Suchindex ist eine Pro-Funktion.
|
||||
|
||||
Die Suche nach Nachrichten auf dem Gerät ist eine kostenlose Funktion, die Suche nach Nachrichten auf dem Server ist jedoch eine Pro-Funktion.
|
||||
Ab Version 1.1315 ist es möglich, Suchausdrücke wie folgt zu verwenden:
|
||||
|
||||
```
|
||||
Apfel +Banane -Kirsche ?Nüsse
|
||||
```
|
||||
|
||||
Dies führt zu dem folgenden Suchergebnis:
|
||||
|
||||
```
|
||||
("Apfel" UND "Banane" UND NICHT "Kirsche") ODER "Nüsse"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq14"></a>
|
||||
**(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?**
|
||||
**(14) How can I set up an Outlook / Live / Hotmail account?**
|
||||
|
||||
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
|
||||
|
||||
|
|
@ -713,7 +727,7 @@ For setting up an Office 365 account, please see [this FAQ](#user-content-faq156
|
|||
<br />
|
||||
|
||||
<a name="faq15"></a>
|
||||
**(15) Warum wird der Nachrichtentext immer noch geladen?**
|
||||
**(15) Why does the message text keep loading?**
|
||||
|
||||
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and need to be fetched on opening the message. The message text will keep loading if there is no connection to the account, see also the next question.
|
||||
|
||||
|
|
@ -726,7 +740,7 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
**(16) Why are messages not being synchronized?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
|
||||
|
|
@ -749,7 +763,7 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq17"></a>
|
||||
**~~(17) Warum funktioniert die manuelle Synchronisation nicht?~~**
|
||||
**~~(17) Why does manual synchronize not work?~~**
|
||||
|
||||
~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
|
||||
|
||||
|
|
@ -758,39 +772,39 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq18"></a>
|
||||
**(18) Warum wird die Nachrichtenvorschau nicht immer angezeigt?**
|
||||
**(18) Why is the message preview not always shown?**
|
||||
|
||||
Die Vorschau des Nachrichtentextes kann nicht angezeigt werden, wenn der Nachrichtentext noch nicht heruntergeladen wurde. Siehe auch [diese F&A](#user-content-faq15).
|
||||
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
**(19) Why are the pro features so expensive?**
|
||||
|
||||
Die richtige Frage ist: »*Warum gibt es so viele Steuern und Gebühren?*«:
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
|
||||
Beachten Sie, dass nur einige Vorteile und erweiterte Funktionen erworben werden müssen, was bedeutet, dass FairEmail grundsätzlich frei zu verwenden ist.
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
Beachten Sie auch, dass die meisten kostenlosen Apps am Ende nicht langfristig einsetzbar sind, während FairEmail ordnungsgemäß gewartet und unterstützt wird, und dass kostenlose Anwendungen einen Haken haben können, wie z.B. das Senden vertraulicher Informationen ins Internet.
|
||||
Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
|
||||
|
||||
Ich arbeite seit mehr als zwei Jahren fast jeden Tag an FairEmail, daher halte ich den Preis für mehr als angemessen. Aus diesem Grund gibt es auch keine Rabatte.
|
||||
I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq20"></a>
|
||||
**(20) Kann ich eine Rückerstattung erhalten?**
|
||||
**(20) Can I get a refund?**
|
||||
|
||||
Wenn eine gekaufte Pro-Funktion nicht wie vorgesehen funktioniert und dies wird nicht durch ein Problem in den kostenlosen Funktionen verursacht und ich das Problem nicht rechtzeitig beheben kann, können Sie eine Rückerstattung beantragen. In all other cases there is no refund possible. Unter keinen Umständen ist eine Rückerstattung für Probleme im Zusammenhang mit den kostenlosen Funktionen möglich, da diese nicht kostenpflichtig sind und diese uneingeschränkt genutzt werden können. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
If a purchased pro feature doesn't work as intended and this isn't caused by a problem in the free features and I cannot fix the problem in a timely manner, you can get a refund. In all other cases there is no refund possible. In no circumstances there is a refund possible for any problem related to the free features, since there wasn't paid anything for them and because they can be evaluated without any limitation. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
|
||||
<a name="faq21"></a>
|
||||
**(21) Wie aktiviere ich das Benachrichtigungslicht?**
|
||||
**(21) How do I enable the notification light?**
|
||||
|
||||
Before Android 8 Oreo: there is an advanced option in the setup for this.
|
||||
|
||||
|
|
@ -813,7 +827,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... „Authentifizierung fehlgeschlagen …”* bedeutet wahrscheinlich, dass Ihr Benutzername oder Passwort ungültig war. Einige Anbieter erwarten als Benutzername nur den *Benutzernamen* und andere jedoch Ihre vollständige E-Mail-Adresse *benutzername@beispiel.de*. Beim Kopieren/Einfügen eines Benutzernamens oder Passworts können unsichtbare Zeichen kopiert werden, was auch zu diesem Problem führen kann. Einige Passwortmanager sind dafür bekannt, dies ebenfalls fehlerhaft zu tun. Beim Benutzernamen wird möglicherweise die Groß- und Kleinschreibung berücksichtigt, versuchen Sie außerdem nur Kleinbuchstaben. Das Passwort unterscheidet fast immer zwischen Groß- und Kleinschreibung. Einige Anbieter benötigen statt des regulären Passworts ein App-spezfisches Passwort. Bitte überprüfen Sie die Dokumentation des Anbieters. In einigen Fällen ist es erforderlich, zuerst den externen Zugang (IMAP/SMTP) auf der Website des Anbieters zu erlauben. Andere mögliche Ursachen können eine Kontensperrung sein oder eine Anmeldebeschränkung in sonstiger/administrativer Hinsicht. Eine Anmeldung kann z. B. auf bestimmte Netzwerke oder IP-Adressen beschränkt sein.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -889,9 +903,9 @@ When in doubt, you can ask for [support](#user-content-support).
|
|||
<br />
|
||||
|
||||
<a name="faq23"></a>
|
||||
**(23) Warum bekomme ich einen Alarm?**
|
||||
**(23) Why do I get alert ... ?**
|
||||
|
||||
*Allgemein*
|
||||
*General*
|
||||
|
||||
Alerts are warning messages sent by email servers.
|
||||
|
||||
|
|
|
|||
|
|
@ -695,12 +695,26 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Das Verwenden des Suchindex ist eine Pro-Funktion.
|
||||
|
||||
Die Suche nach Nachrichten auf dem Gerät ist eine kostenlose Funktion, die Suche nach Nachrichten auf dem Server ist jedoch eine Pro-Funktion.
|
||||
Ab Version 1.1315 ist es möglich, Suchausdrücke wie folgt zu verwenden:
|
||||
|
||||
```
|
||||
Apfel +Banane -Kirsche ?Nüsse
|
||||
```
|
||||
|
||||
Dies führt zu dem folgenden Suchergebnis:
|
||||
|
||||
```
|
||||
("Apfel" UND "Banane" UND NICHT "Kirsche") ODER "Nüsse"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq14"></a>
|
||||
**(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?**
|
||||
**(14) How can I set up an Outlook / Live / Hotmail account?**
|
||||
|
||||
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
|
||||
|
||||
|
|
@ -713,7 +727,7 @@ For setting up an Office 365 account, please see [this FAQ](#user-content-faq156
|
|||
<br />
|
||||
|
||||
<a name="faq15"></a>
|
||||
**(15) Warum wird der Nachrichtentext immer noch geladen?**
|
||||
**(15) Why does the message text keep loading?**
|
||||
|
||||
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and need to be fetched on opening the message. The message text will keep loading if there is no connection to the account, see also the next question.
|
||||
|
||||
|
|
@ -726,7 +740,7 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
**(16) Why are messages not being synchronized?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
|
||||
|
|
@ -749,7 +763,7 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq17"></a>
|
||||
**~~(17) Warum funktioniert die manuelle Synchronisation nicht?~~**
|
||||
**~~(17) Why does manual synchronize not work?~~**
|
||||
|
||||
~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
|
||||
|
||||
|
|
@ -758,39 +772,39 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq18"></a>
|
||||
**(18) Warum wird die Nachrichtenvorschau nicht immer angezeigt?**
|
||||
**(18) Why is the message preview not always shown?**
|
||||
|
||||
Die Vorschau des Nachrichtentextes kann nicht angezeigt werden, wenn der Nachrichtentext noch nicht heruntergeladen wurde. Siehe auch [diese F&A](#user-content-faq15).
|
||||
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
**(19) Why are the pro features so expensive?**
|
||||
|
||||
Die richtige Frage ist: »*Warum gibt es so viele Steuern und Gebühren?*«:
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
|
||||
Beachten Sie, dass nur einige Vorteile und erweiterte Funktionen erworben werden müssen, was bedeutet, dass FairEmail grundsätzlich frei zu verwenden ist.
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
Beachten Sie auch, dass die meisten kostenlosen Apps am Ende nicht langfristig einsetzbar sind, während FairEmail ordnungsgemäß gewartet und unterstützt wird, und dass kostenlose Anwendungen einen Haken haben können, wie z.B. das Senden vertraulicher Informationen ins Internet.
|
||||
Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
|
||||
|
||||
Ich arbeite seit mehr als zwei Jahren fast jeden Tag an FairEmail, daher halte ich den Preis für mehr als angemessen. Aus diesem Grund gibt es auch keine Rabatte.
|
||||
I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq20"></a>
|
||||
**(20) Kann ich eine Rückerstattung erhalten?**
|
||||
**(20) Can I get a refund?**
|
||||
|
||||
Wenn eine gekaufte Pro-Funktion nicht wie vorgesehen funktioniert und dies wird nicht durch ein Problem in den kostenlosen Funktionen verursacht und ich das Problem nicht rechtzeitig beheben kann, können Sie eine Rückerstattung beantragen. In all other cases there is no refund possible. Unter keinen Umständen ist eine Rückerstattung für Probleme im Zusammenhang mit den kostenlosen Funktionen möglich, da diese nicht kostenpflichtig sind und diese uneingeschränkt genutzt werden können. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
If a purchased pro feature doesn't work as intended and this isn't caused by a problem in the free features and I cannot fix the problem in a timely manner, you can get a refund. In all other cases there is no refund possible. In no circumstances there is a refund possible for any problem related to the free features, since there wasn't paid anything for them and because they can be evaluated without any limitation. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
|
||||
<a name="faq21"></a>
|
||||
**(21) Wie aktiviere ich das Benachrichtigungslicht?**
|
||||
**(21) How do I enable the notification light?**
|
||||
|
||||
Before Android 8 Oreo: there is an advanced option in the setup for this.
|
||||
|
||||
|
|
@ -813,7 +827,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... „Authentifizierung fehlgeschlagen …”* bedeutet wahrscheinlich, dass Ihr Benutzername oder Passwort ungültig war. Einige Anbieter erwarten als Benutzername nur den *Benutzernamen* und andere jedoch Ihre vollständige E-Mail-Adresse *benutzername@beispiel.de*. Beim Kopieren/Einfügen eines Benutzernamens oder Passworts können unsichtbare Zeichen kopiert werden, was auch zu diesem Problem führen kann. Einige Passwortmanager sind dafür bekannt, dies ebenfalls fehlerhaft zu tun. Beim Benutzernamen wird möglicherweise die Groß- und Kleinschreibung berücksichtigt, versuchen Sie außerdem nur Kleinbuchstaben. Das Passwort unterscheidet fast immer zwischen Groß- und Kleinschreibung. Einige Anbieter benötigen statt des regulären Passworts ein App-spezfisches Passwort. Bitte überprüfen Sie die Dokumentation des Anbieters. In einigen Fällen ist es erforderlich, zuerst den externen Zugang (IMAP/SMTP) auf der Website des Anbieters zu erlauben. Andere mögliche Ursachen können eine Kontensperrung sein oder eine Anmeldebeschränkung in sonstiger/administrativer Hinsicht. Eine Anmeldung kann z. B. auf bestimmte Netzwerke oder IP-Adressen beschränkt sein.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -889,9 +903,9 @@ When in doubt, you can ask for [support](#user-content-support).
|
|||
<br />
|
||||
|
||||
<a name="faq23"></a>
|
||||
**(23) Warum bekomme ich einen Alarm?**
|
||||
**(23) Why do I get alert ... ?**
|
||||
|
||||
*Allgemein*
|
||||
*General*
|
||||
|
||||
Alerts are warning messages sent by email servers.
|
||||
|
||||
|
|
|
|||
|
|
@ -695,12 +695,26 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Das Verwenden des Suchindex ist eine Pro-Funktion.
|
||||
|
||||
Die Suche nach Nachrichten auf dem Gerät ist eine kostenlose Funktion, die Suche nach Nachrichten auf dem Server ist jedoch eine Pro-Funktion.
|
||||
Ab Version 1.1315 ist es möglich, Suchausdrücke wie folgt zu verwenden:
|
||||
|
||||
```
|
||||
Apfel +Banane -Kirsche ?Nüsse
|
||||
```
|
||||
|
||||
Dies führt zu dem folgenden Suchergebnis:
|
||||
|
||||
```
|
||||
("Apfel" UND "Banane" UND NICHT "Kirsche") ODER "Nüsse"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq14"></a>
|
||||
**(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?**
|
||||
**(14) How can I set up an Outlook / Live / Hotmail account?**
|
||||
|
||||
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
|
||||
|
||||
|
|
@ -713,7 +727,7 @@ For setting up an Office 365 account, please see [this FAQ](#user-content-faq156
|
|||
<br />
|
||||
|
||||
<a name="faq15"></a>
|
||||
**(15) Warum wird der Nachrichtentext immer noch geladen?**
|
||||
**(15) Why does the message text keep loading?**
|
||||
|
||||
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and need to be fetched on opening the message. The message text will keep loading if there is no connection to the account, see also the next question.
|
||||
|
||||
|
|
@ -726,7 +740,7 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
**(16) Why are messages not being synchronized?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
|
||||
|
|
@ -749,7 +763,7 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq17"></a>
|
||||
**~~(17) Warum funktioniert die manuelle Synchronisation nicht?~~**
|
||||
**~~(17) Why does manual synchronize not work?~~**
|
||||
|
||||
~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
|
||||
|
||||
|
|
@ -758,39 +772,39 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq18"></a>
|
||||
**(18) Warum wird die Nachrichtenvorschau nicht immer angezeigt?**
|
||||
**(18) Why is the message preview not always shown?**
|
||||
|
||||
Die Vorschau des Nachrichtentextes kann nicht angezeigt werden, wenn der Nachrichtentext noch nicht heruntergeladen wurde. Siehe auch [diese F&A](#user-content-faq15).
|
||||
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
**(19) Why are the pro features so expensive?**
|
||||
|
||||
Die richtige Frage ist: »*Warum gibt es so viele Steuern und Gebühren?*«:
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
|
||||
Beachten Sie, dass nur einige Vorteile und erweiterte Funktionen erworben werden müssen, was bedeutet, dass FairEmail grundsätzlich frei zu verwenden ist.
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
Beachten Sie auch, dass die meisten kostenlosen Apps am Ende nicht langfristig einsetzbar sind, während FairEmail ordnungsgemäß gewartet und unterstützt wird, und dass kostenlose Anwendungen einen Haken haben können, wie z.B. das Senden vertraulicher Informationen ins Internet.
|
||||
Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
|
||||
|
||||
Ich arbeite seit mehr als zwei Jahren fast jeden Tag an FairEmail, daher halte ich den Preis für mehr als angemessen. Aus diesem Grund gibt es auch keine Rabatte.
|
||||
I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq20"></a>
|
||||
**(20) Kann ich eine Rückerstattung erhalten?**
|
||||
**(20) Can I get a refund?**
|
||||
|
||||
Wenn eine gekaufte Pro-Funktion nicht wie vorgesehen funktioniert und dies wird nicht durch ein Problem in den kostenlosen Funktionen verursacht und ich das Problem nicht rechtzeitig beheben kann, können Sie eine Rückerstattung beantragen. In all other cases there is no refund possible. Unter keinen Umständen ist eine Rückerstattung für Probleme im Zusammenhang mit den kostenlosen Funktionen möglich, da diese nicht kostenpflichtig sind und diese uneingeschränkt genutzt werden können. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
If a purchased pro feature doesn't work as intended and this isn't caused by a problem in the free features and I cannot fix the problem in a timely manner, you can get a refund. In all other cases there is no refund possible. In no circumstances there is a refund possible for any problem related to the free features, since there wasn't paid anything for them and because they can be evaluated without any limitation. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
|
||||
<a name="faq21"></a>
|
||||
**(21) Wie aktiviere ich das Benachrichtigungslicht?**
|
||||
**(21) How do I enable the notification light?**
|
||||
|
||||
Before Android 8 Oreo: there is an advanced option in the setup for this.
|
||||
|
||||
|
|
@ -813,7 +827,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... „Authentifizierung fehlgeschlagen …”* bedeutet wahrscheinlich, dass Ihr Benutzername oder Passwort ungültig war. Einige Anbieter erwarten als Benutzername nur den *Benutzernamen* und andere jedoch Ihre vollständige E-Mail-Adresse *benutzername@beispiel.de*. Beim Kopieren/Einfügen eines Benutzernamens oder Passworts können unsichtbare Zeichen kopiert werden, was auch zu diesem Problem führen kann. Einige Passwortmanager sind dafür bekannt, dies ebenfalls fehlerhaft zu tun. Beim Benutzernamen wird möglicherweise die Groß- und Kleinschreibung berücksichtigt, versuchen Sie außerdem nur Kleinbuchstaben. Das Passwort unterscheidet fast immer zwischen Groß- und Kleinschreibung. Einige Anbieter benötigen statt des regulären Passworts ein App-spezfisches Passwort. Bitte überprüfen Sie die Dokumentation des Anbieters. In einigen Fällen ist es erforderlich, zuerst den externen Zugang (IMAP/SMTP) auf der Website des Anbieters zu erlauben. Andere mögliche Ursachen können eine Kontensperrung sein oder eine Anmeldebeschränkung in sonstiger/administrativer Hinsicht. Eine Anmeldung kann z. B. auf bestimmte Netzwerke oder IP-Adressen beschränkt sein.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -889,9 +903,9 @@ When in doubt, you can ask for [support](#user-content-support).
|
|||
<br />
|
||||
|
||||
<a name="faq23"></a>
|
||||
**(23) Warum bekomme ich einen Alarm?**
|
||||
**(23) Why do I get alert ... ?**
|
||||
|
||||
*Allgemein*
|
||||
*General*
|
||||
|
||||
Alerts are warning messages sent by email servers.
|
||||
|
||||
|
|
|
|||
|
|
@ -695,12 +695,26 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Das Verwenden des Suchindex ist eine Pro-Funktion.
|
||||
|
||||
Die Suche nach Nachrichten auf dem Gerät ist eine kostenlose Funktion, die Suche nach Nachrichten auf dem Server ist jedoch eine Pro-Funktion.
|
||||
Ab Version 1.1315 ist es möglich, Suchausdrücke wie folgt zu verwenden:
|
||||
|
||||
```
|
||||
Apfel +Banane -Kirsche ?Nüsse
|
||||
```
|
||||
|
||||
Dies führt zu dem folgenden Suchergebnis:
|
||||
|
||||
```
|
||||
("Apfel" UND "Banane" UND NICHT "Kirsche") ODER "Nüsse"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq14"></a>
|
||||
**(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?**
|
||||
**(14) How can I set up an Outlook / Live / Hotmail account?**
|
||||
|
||||
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
|
||||
|
||||
|
|
@ -713,7 +727,7 @@ For setting up an Office 365 account, please see [this FAQ](#user-content-faq156
|
|||
<br />
|
||||
|
||||
<a name="faq15"></a>
|
||||
**(15) Warum wird der Nachrichtentext immer noch geladen?**
|
||||
**(15) Why does the message text keep loading?**
|
||||
|
||||
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and need to be fetched on opening the message. The message text will keep loading if there is no connection to the account, see also the next question.
|
||||
|
||||
|
|
@ -726,7 +740,7 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
**(16) Why are messages not being synchronized?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
|
||||
|
|
@ -749,7 +763,7 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq17"></a>
|
||||
**~~(17) Warum funktioniert die manuelle Synchronisation nicht?~~**
|
||||
**~~(17) Why does manual synchronize not work?~~**
|
||||
|
||||
~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
|
||||
|
||||
|
|
@ -758,39 +772,39 @@ Disabling battery optimizations (setup step 4) reduces the chance Android will s
|
|||
<br />
|
||||
|
||||
<a name="faq18"></a>
|
||||
**(18) Warum wird die Nachrichtenvorschau nicht immer angezeigt?**
|
||||
**(18) Why is the message preview not always shown?**
|
||||
|
||||
Die Vorschau des Nachrichtentextes kann nicht angezeigt werden, wenn der Nachrichtentext noch nicht heruntergeladen wurde. Siehe auch [diese F&A](#user-content-faq15).
|
||||
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
**(19) Why are the pro features so expensive?**
|
||||
|
||||
Die richtige Frage ist: »*Warum gibt es so viele Steuern und Gebühren?*«:
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
|
||||
Beachten Sie, dass nur einige Vorteile und erweiterte Funktionen erworben werden müssen, was bedeutet, dass FairEmail grundsätzlich frei zu verwenden ist.
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
Beachten Sie auch, dass die meisten kostenlosen Apps am Ende nicht langfristig einsetzbar sind, während FairEmail ordnungsgemäß gewartet und unterstützt wird, und dass kostenlose Anwendungen einen Haken haben können, wie z.B. das Senden vertraulicher Informationen ins Internet.
|
||||
Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
|
||||
|
||||
Ich arbeite seit mehr als zwei Jahren fast jeden Tag an FairEmail, daher halte ich den Preis für mehr als angemessen. Aus diesem Grund gibt es auch keine Rabatte.
|
||||
I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq20"></a>
|
||||
**(20) Kann ich eine Rückerstattung erhalten?**
|
||||
**(20) Can I get a refund?**
|
||||
|
||||
Wenn eine gekaufte Pro-Funktion nicht wie vorgesehen funktioniert und dies wird nicht durch ein Problem in den kostenlosen Funktionen verursacht und ich das Problem nicht rechtzeitig beheben kann, können Sie eine Rückerstattung beantragen. In all other cases there is no refund possible. Unter keinen Umständen ist eine Rückerstattung für Probleme im Zusammenhang mit den kostenlosen Funktionen möglich, da diese nicht kostenpflichtig sind und diese uneingeschränkt genutzt werden können. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
If a purchased pro feature doesn't work as intended and this isn't caused by a problem in the free features and I cannot fix the problem in a timely manner, you can get a refund. In all other cases there is no refund possible. In no circumstances there is a refund possible for any problem related to the free features, since there wasn't paid anything for them and because they can be evaluated without any limitation. I take my responsibility as seller to deliver what has been promised and I expect that you take responsibility for informing yourself of what you are buying.
|
||||
|
||||
<a name="faq21"></a>
|
||||
**(21) Wie aktiviere ich das Benachrichtigungslicht?**
|
||||
**(21) How do I enable the notification light?**
|
||||
|
||||
Before Android 8 Oreo: there is an advanced option in the setup for this.
|
||||
|
||||
|
|
@ -813,7 +827,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... „Authentifizierung fehlgeschlagen …”* bedeutet wahrscheinlich, dass Ihr Benutzername oder Passwort ungültig war. Einige Anbieter erwarten als Benutzername nur den *Benutzernamen* und andere jedoch Ihre vollständige E-Mail-Adresse *benutzername@beispiel.de*. Beim Kopieren/Einfügen eines Benutzernamens oder Passworts können unsichtbare Zeichen kopiert werden, was auch zu diesem Problem führen kann. Einige Passwortmanager sind dafür bekannt, dies ebenfalls fehlerhaft zu tun. Beim Benutzernamen wird möglicherweise die Groß- und Kleinschreibung berücksichtigt, versuchen Sie außerdem nur Kleinbuchstaben. Das Passwort unterscheidet fast immer zwischen Groß- und Kleinschreibung. Einige Anbieter benötigen statt des regulären Passworts ein App-spezfisches Passwort. Bitte überprüfen Sie die Dokumentation des Anbieters. In einigen Fällen ist es erforderlich, zuerst den externen Zugang (IMAP/SMTP) auf der Website des Anbieters zu erlauben. Andere mögliche Ursachen können eine Kontensperrung sein oder eine Anmeldebeschränkung in sonstiger/administrativer Hinsicht. Eine Anmeldung kann z. B. auf bestimmte Netzwerke oder IP-Adressen beschränkt sein.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -889,9 +903,9 @@ When in doubt, you can ask for [support](#user-content-support).
|
|||
<br />
|
||||
|
||||
<a name="faq23"></a>
|
||||
**(23) Warum bekomme ich einen Alarm?**
|
||||
**(23) Why do I get alert ... ?**
|
||||
|
||||
*Allgemein*
|
||||
*General*
|
||||
|
||||
Alerts are warning messages sent by email servers.
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -2428,7 +2442,7 @@ The error *User is authenticated but not connected* might occur if:
|
|||
The shared mailbox alias will mostly be the email address of the shared account, like this:
|
||||
|
||||
```
|
||||
vous@exemple.com\partage@exemple.com
|
||||
you@example.com\shared@example.com
|
||||
```
|
||||
|
||||
Note that it should be a backslash and not a forward slash.
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -780,7 +794,7 @@ Note that only some convenience and advanced features need to be purchased which
|
|||
|
||||
Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
|
||||
|
||||
Estiven a traballar en FairEmail case cada día durante máis de dous anos, polo que penso que o prezo e máis que razoable. For this reason there won't be discounts either.
|
||||
I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -813,7 +827,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. É sabido que algúns xestores de contrasinais tamén o fan incorrectamente. O nome de usuario podería ten en conta as maiúsculas/minúsculas, polo que é aconsellable probar unicamente con minúsculas. Os contrasinais case sempre distinguen as maiúsculas e minúsculas. Algúns provedores requiren un contrasinal de aplicación no canto do contrasinal de conta; por favor, comprobe as instrucións do seu provedor de correo. Algunhas veces é preciso activar o acceso externo (IMAP/SMTP) na páxina web do provedor previamente. Outras causas poderían ser que a conta estea bloqueada ou que o acceso estea restrinxido de algunha maneira pola administración, por exemplo unicamente permitindo o acceso desde certas redes ou enderezos IP.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
@ -954,17 +968,17 @@ If you would like your name or alias to be included in the list of contributors
|
|||
<a name="faq27"></a>
|
||||
**(27) How can I distinguish between embedded and external images?**
|
||||
|
||||
Imaxe externa:
|
||||
External image:
|
||||
|
||||
|
||||
|
||||
|
||||
Imaxe incorporada:
|
||||
Embedded image:
|
||||
|
||||
|
||||
|
||||
|
||||
Imaxe corrupta:
|
||||
Broken image:
|
||||
|
||||
|
||||
|
||||
|
||||
Note that downloading external images from a remote server can be used to record you did see a message, which you likely don't want if the message is spam or malicious.
|
||||
|
||||
|
|
@ -1015,7 +1029,7 @@ Quick settings require Android 7.0 Nougat or later. The usage of settings tiles
|
|||
<a name="faq31"></a>
|
||||
**(31) How can I use the provided shortcuts?**
|
||||
|
||||
Hai atallos dispoñibles para:
|
||||
There are shortcuts available to:
|
||||
|
||||
* compose a new message to a favorite contact
|
||||
* setup accounts, identities, etc
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -1210,7 +1224,7 @@ The following information is needed:
|
|||
<provider
|
||||
name="Gmail"
|
||||
link="https://support.google.com/mail/answer/7126229" // link to the instructions of the provider
|
||||
type="com.google"> // to nie jest potrzebne
|
||||
type="com.google"> // this is not needed
|
||||
<imap
|
||||
host="imap.gmail.com"
|
||||
port="993"
|
||||
|
|
@ -1688,16 +1702,16 @@ Note that disabling an account will hide the account and all associated folders
|
|||
You can automatically send commands with for example [Tasker](https://tasker.joaoapps.com/userguide/en/intents.html):
|
||||
|
||||
```
|
||||
Nowe zadanie: Coś rozpoznawalnego
|
||||
Kategoria akcji: Różne / Wyślij zamiar
|
||||
Działanie: eu.faircode.email.ENABLE
|
||||
Cel: usługa
|
||||
New task: Something recognizable
|
||||
Action Category: Misc/Send Intent
|
||||
Action: eu.faircode.email.ENABLE
|
||||
Target: Service
|
||||
```
|
||||
|
||||
To enable/disable an account with the name *Gmail*:
|
||||
|
||||
```
|
||||
Dodatki: konto:Gmail
|
||||
Extras: account:Gmail
|
||||
```
|
||||
|
||||
Account names are case sensitive.
|
||||
|
|
@ -1955,10 +1969,10 @@ You can synchronize Gmail categories by creating filters to label categorized me
|
|||
Possible categories:
|
||||
|
||||
```
|
||||
kategoria: społeczna
|
||||
kategoria: aktualizacje
|
||||
kategoria: fora
|
||||
kategoria: promocje
|
||||
category:social
|
||||
category:updates
|
||||
category:forums
|
||||
category:promotions
|
||||
```
|
||||
|
||||
Unfortunately, this is not possible for snoozed messages folder.
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -780,7 +794,7 @@ Note that only some convenience and advanced features need to be purchased which
|
|||
|
||||
Also note that most free apps will appear not to be sustainable in the end, whereas FairEmail is properly maintained and supported, and that free apps may have a catch, like sending privacy sensitive information to the internet.
|
||||
|
||||
Я работаю над FairEmail почти каждый день более двух лет, поэтому я думаю, что цена более чем разумна. For this reason there won't be discounts either.
|
||||
I have been working on FairEmail almost every day for more than two years, so I think the price is more than reasonable. For this reason there won't be discounts either.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -813,7 +827,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Некоторые менеджеры паролей также делают это неправильно. Имя пользователя может быть чувствительным к регистру, поэтому попробуйте использовать только строчные буквы. Пароль почти всегда чувствителен к регистру. Некоторые провайдеры требуют использования пароля приложения вместо пароля учетной записи, поэтому проверьте документацию провайдера. Иногда необходимо сначала включить внешний доступ (IMAP/SMTP) на сайте провайдера. Другими возможными причинами являются то, что учетная запись заблокирована или вход был заблокирован в административном порядке, например, позволяя входить только с определенных сетей / IP адресов.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
@ -813,7 +827,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
|
||||
**General errors**
|
||||
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Vissa lösenordshanterare är kända för att göra detta felaktigt. Användarnamnet kan vara skiftlägeskänsligt, så försök endast med små bokstäver. Lösenordet är nästan alltid skiftlägeskänsligt. Vissa leverantörer kräver att du använder ett applösenord istället för kontots lösenord, så kontrollera dokumentationen av leverantören. Ibland är det nödvändigt att aktivera extern åtkomst (IMAP/SMTP) på leverantörens webbplats först. Andra möjliga orsaker är att kontot blockeras eller att inloggningen på något sätt har begränsats administrativt. till exempel genom att tillåta inloggning från vissa nätverk/IP-adresser.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to setup a Yahoo account.
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
|
|
@ -695,7 +695,21 @@ This means that searching for a message text requires that files containing the
|
|||
|
||||
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
|
||||
|
||||
Searching messages on the device is a free feature, searching messages on the server is a pro feature.
|
||||
From version 1.1315 it is possible to use search expressions like this:
|
||||
|
||||
```
|
||||
apple +banana -cherry ?nuts
|
||||
```
|
||||
|
||||
This will result in searching like this:
|
||||
|
||||
```
|
||||
("apple" AND "banana" AND NOT "cherry") OR "nuts"
|
||||
```
|
||||
|
||||
Search expressions can be used for searching on the device via the search index and for searching on the email server, but not for searching on the device without search index for performance reasons.
|
||||
|
||||
Searching on the device is a free feature, using the search index and searching on the server is a pro feature.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue