mirror of https://github.com/M66B/FairEmail.git
Crowdin sync
This commit is contained in:
M66B
parent
2f7ac1b2f8
commit
b32960a828
|
|
@ -140,6 +140,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_setup_gmail_rationale">Bitte erteilen Sie die Berechtigung, ein Konto auszuwählen und Ihren Namen zu lesen</string>
|
||||
<string name="title_setup_gmail_permissions">Google wird Sie um Erlaubnis bitten, alle Ihre E-Mails zu lesen, zu verfassen, zu senden und dauerhaft zu löschen. FairEmail löscht niemals Ihre Nachrichten ohne Ihre ausdrückliche Zustimmung.</string>
|
||||
<string name="title_setup_gmail_drafts">Wenn der Entwürfe-Ordner über IMAP nicht zugänglich ist, kann dies in den Gmail Label-Einstellungen korrigiert werden</string>
|
||||
<string name="title_setup_office_remark">Microsoft bietet diese Art der Autorisierung nicht für Outlook, Live, Hotmail, etc.</string>
|
||||
<string name="title_setup_office_auth">Der Fehler »AUTHENTICATE failed« kann dadurch verursacht werden, dass IMAP/SMTP vom Systemverwalter deaktiviert wurde</string>
|
||||
<string name="title_setup_oauth_rationale">Zugriff auf Ihr %1$s -Konto autorisieren</string>
|
||||
<string name="title_setup_oauth_authorize">Autorisieren</string>
|
||||
|
|
|
|||
|
|
@ -140,6 +140,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_setup_gmail_rationale">Bitte erteilen Sie die Berechtigung, ein Konto auszuwählen und Ihren Namen zu lesen</string>
|
||||
<string name="title_setup_gmail_permissions">Google wird Sie um Erlaubnis bitten, alle Ihre E-Mails zu lesen, zu verfassen, zu senden und dauerhaft zu löschen. FairEmail löscht niemals Ihre Nachrichten ohne Ihre ausdrückliche Zustimmung.</string>
|
||||
<string name="title_setup_gmail_drafts">Wenn der Entwürfe-Ordner über IMAP nicht zugänglich ist, kann dies in den Gmail Label-Einstellungen korrigiert werden</string>
|
||||
<string name="title_setup_office_remark">Microsoft bietet diese Art der Autorisierung nicht für Outlook, Live, Hotmail, etc.</string>
|
||||
<string name="title_setup_office_auth">Der Fehler »AUTHENTICATE failed« kann dadurch verursacht werden, dass IMAP/SMTP vom Systemverwalter deaktiviert wurde</string>
|
||||
<string name="title_setup_oauth_rationale">Zugriff auf Ihr %1$s -Konto autorisieren</string>
|
||||
<string name="title_setup_oauth_authorize">Autorisieren</string>
|
||||
|
|
|
|||
|
|
@ -140,6 +140,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_setup_gmail_rationale">Bitte erteilen Sie die Berechtigung, ein Konto auszuwählen und Ihren Namen zu lesen</string>
|
||||
<string name="title_setup_gmail_permissions">Google wird Sie um Erlaubnis bitten, alle Ihre E-Mails zu lesen, zu verfassen, zu senden und dauerhaft zu löschen. FairEmail löscht niemals Ihre Nachrichten ohne Ihre ausdrückliche Zustimmung.</string>
|
||||
<string name="title_setup_gmail_drafts">Wenn der Entwürfe-Ordner über IMAP nicht zugänglich ist, kann dies in den Gmail Label-Einstellungen korrigiert werden</string>
|
||||
<string name="title_setup_office_remark">Microsoft bietet diese Art der Autorisierung nicht für Outlook, Live, Hotmail, etc.</string>
|
||||
<string name="title_setup_office_auth">Der Fehler »AUTHENTICATE failed« kann dadurch verursacht werden, dass IMAP/SMTP vom Systemverwalter deaktiviert wurde</string>
|
||||
<string name="title_setup_oauth_rationale">Zugriff auf Ihr %1$s -Konto autorisieren</string>
|
||||
<string name="title_setup_oauth_authorize">Autorisieren</string>
|
||||
|
|
|
|||
|
|
@ -140,6 +140,7 @@ Protokolle, die dem Standard nicht entsprechen, wie „Microsoft Exchange Web Se
|
|||
<string name="title_setup_gmail_rationale">Bitte erteilen Sie die Berechtigung, ein Konto auszuwählen und Ihren Namen zu lesen</string>
|
||||
<string name="title_setup_gmail_permissions">Google wird Sie um Erlaubnis bitten, alle Ihre E-Mails zu lesen, zu verfassen, zu senden und dauerhaft zu löschen. FairEmail löscht niemals Ihre Nachrichten ohne Ihre ausdrückliche Zustimmung.</string>
|
||||
<string name="title_setup_gmail_drafts">Wenn der Entwürfe-Ordner über IMAP nicht zugänglich ist, kann dies in den Gmail Label-Einstellungen korrigiert werden</string>
|
||||
<string name="title_setup_office_remark">Microsoft bietet diese Art der Autorisierung nicht für Outlook, Live, Hotmail, etc.</string>
|
||||
<string name="title_setup_office_auth">Der Fehler »AUTHENTICATE failed« kann dadurch verursacht werden, dass IMAP/SMTP vom Systemverwalter deaktiviert wurde</string>
|
||||
<string name="title_setup_oauth_rationale">Zugriff auf Ihr %1$s -Konto autorisieren</string>
|
||||
<string name="title_setup_oauth_authorize">Autorisieren</string>
|
||||
|
|
|
|||
|
|
@ -139,6 +139,7 @@
|
|||
<string name="title_setup_gmail_rationale">Veuillez accorder les autorisations pour sélectionner un compte et lire votre nom</string>
|
||||
<string name="title_setup_gmail_permissions">Google vous demandera l’autorisation de lire, rédiger, envoyer et supprimer définitivement tous vos courriels. FairEmail ne supprimera jamais vos messages sans votre approbation.</string>
|
||||
<string name="title_setup_gmail_drafts">Si le dossier brouillons n’est pas accessible par IMAP, ceci peut être corrigé dans les paramètres de libellé Gmail</string>
|
||||
<string name="title_setup_office_remark">Microsoft ne fournit pas ce type d\'autorisation pour les comptes Outlook, Live, Hotmail, etc</string>
|
||||
<string name="title_setup_office_auth">L’erreur \'AUTHENTICATE failed\' peut être due à la désactivation d’IMAP/SMTP par l’administrateur</string>
|
||||
<string name="title_setup_oauth_rationale">Autoriser l’accès à votre compte %1$s</string>
|
||||
<string name="title_setup_oauth_authorize">Autoriser</string>
|
||||
|
|
|
|||
|
|
@ -138,6 +138,7 @@
|
|||
<string name="title_setup_gmail_rationale">Geef a.u.b. toestemming om een account te selecteren en uw naam te lezen</string>
|
||||
<string name="title_setup_gmail_permissions">Google zal machtigingen vragen om al uw e-mail te lezen, op te stellen, te verzenden en definitief te verwijderen. FairEmail zal uw berichten nooit verwijderen zonder uw expliciete toestemming.</string>
|
||||
<string name="title_setup_gmail_drafts">Als de conceptmap niet toegankelijk is voor IMAP, dan kan dit worden opgelost in de Gmail label instellingen</string>
|
||||
<string name="title_setup_office_remark">Microsoft biedt dit type autorisatie niet aan voor Outlook, Live, Hotmail, etc accounts</string>
|
||||
<string name="title_setup_office_auth">De fout \'AUTHENTICATE failed\' kan worden veroorzaakt doordat IMAP/SMTP door de systeemadministrator is uitgeschakeld</string>
|
||||
<string name="title_setup_oauth_rationale">Autoriseer toegang tot uw %1$s account</string>
|
||||
<string name="title_setup_oauth_authorize">Autoriseren</string>
|
||||
|
|
|
|||
|
|
@ -1052,6 +1052,8 @@ Nastavenie vždy toto kompenzuje neustálym sledovaním zmien.</string>
|
|||
<string name="title_legend_section_compose">Napísať správuNapísať</string>
|
||||
<string name="title_legend_section_keyboard">Klávesnica</string>
|
||||
<string name="title_legend_oauth">Autorizácia OAuth</string>
|
||||
<string name="title_legend_folder_connected">Priečinok pripojený</string>
|
||||
<string name="title_legend_folder_disconnected">Priečinok odpojený</string>
|
||||
<string name="title_legend_download_on">Automaticky prevziať obsah správy</string>
|
||||
<string name="title_legend_download_off">Prevziať obsah správy na vyžiadanie</string>
|
||||
<string name="title_legend_synchronize_on">Aktívna synchronizácia</string>
|
||||
|
|
@ -1160,6 +1162,7 @@ Nastavenie vždy toto kompenzuje neustálym sledovaním zmien.</string>
|
|||
<string name="title_hint_battery">Keďže FairEmail v predvolenej konfigurácii neustále prijíma správy, operačný systém bude aplikáciu považovať za vždy aktívnu. Môže sa zdať, že FairEmail neustále vybíja batériu, aj keď v skutočnosti to tak nie je.</string>
|
||||
<string name="title_hint_reformat">V predvolenej konfigurácii FairEmail zobrazuje preformátované správy s cieľom zachovať maximálnu bezpečnosť a chrániť vaše súkromie. Klepnutím na ikonu \'Celá obrazovka\' nad telom textu zobrazíte pôvodnú správu.</string>
|
||||
<string name="title_hint_design">Dizajn je schválne navrhnutý, aby ostal čo možno najlepšie funkčný a bol najmenej vtieravý. Dostupných je množstvo volieb na prispôsobenie vzhľadu, ale pochopte prosím, že nie je možné úplne vyhovieť všetkým.</string>
|
||||
<string name="title_hint_junk">Filtrovanie nevyžiadanej pošty by malo byť zabezpečené na servery, pretože filtrovanie na zariadení napájanom z batérie s obmedzenými možnosťami nemusí fungovať dostatočne spoľahlivo.</string>
|
||||
<string name="title_hint_contact_actions">Možnosti zobrazíte dlhým stlačením</string>
|
||||
<string name="title_hint_eml">Toto je náhľad obsahu surového súboru so správou. Ak chcete zobraziť celý obsah, klepnite na tlačidlo \'Uložiť\' v lište akcií.</string>
|
||||
<string name="title_open_link">Otvoriť odkaz</string>
|
||||
|
|
|
|||
|
|
@ -139,6 +139,7 @@
|
|||
<string name="title_setup_gmail_rationale">Vänligen bevilja behörigheter för att välja ett konto och läsa ditt namn</string>
|
||||
<string name="title_setup_gmail_permissions">Google kommer att be om behörighet att läsa, komponera, skicka och permanent ta bort all din e-post. FairEmail kommer aldrig att ta bort dina meddelanden utan ditt uttryckliga medgivande.</string>
|
||||
<string name="title_setup_gmail_drafts">Om mappen för utkast inte är åtkomlig för IMAP kan detta lösas under inställningarna för Gmail-etiketten</string>
|
||||
<string name="title_setup_office_remark">Microsoft tillhandahåller inte denna typ av auktorisering för Outlook, Live, Hotmail, etc konton</string>
|
||||
<string name="title_setup_office_auth">Felet \"AUTHENTICATE failed\" kan orsakas av att IMAP/SMTP inaktiveras av systemadministratören</string>
|
||||
<string name="title_setup_oauth_rationale">Auktorisera åtkomst till ditt %1$s konto</string>
|
||||
<string name="title_setup_oauth_authorize">Auktorisera</string>
|
||||
|
|
|
|||
|
|
@ -647,7 +647,7 @@
|
|||
<string name="title_folder_drafts">草稿箱</string>
|
||||
<string name="title_folder_trash">回收站</string>
|
||||
<string name="title_folder_junk">垃圾邮件</string>
|
||||
<string name="title_folder_sent">已发送邮件</string>
|
||||
<string name="title_folder_sent">已发送</string>
|
||||
<string name="title_folder_system">系统</string>
|
||||
<string name="title_folder_user">用户</string>
|
||||
<string name="title_folder_user_only">仅用户文件夹</string>
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Související dotazy:
|
|||
* Posun na interně odkazovanou pozici v původních zprávách nefunguje. Toto nelze opravit, protože zobrazení původní zprávy je uvnitř posuvného náhledu.
|
||||
* Náhled textu zprávy se na Samsung hodinkách někdy (nikdy) nezobrazí, protože [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) se zdá být ignorován. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. Viz také [tento nejčastější dotaz](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Plánované funkce
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Relaterede spørgsmål:
|
|||
* Rulning ned til en internt linket position i originalbeskeder fungerer ikke. Dette kan ikke rettes, da originalbeskedvisningen udgør en del af selve rulningsvisningen.
|
||||
* En forhåndsvisning af en beskedtekst vises ikke (altid) på Samsung-ure, da [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean))-parameteren synes at blive ignoreret. Beskedforhåndsvisningstekster bliver vist korrekt på Pebble- 2, Fitbit Charge 3- og Mi band 3-wearables. Se også [denne FAQ](#user-content-faq126).
|
||||
* En [fejl i Android](https://issuetracker.google.com/issues/37068143) medfører af og til et nedbrud med "*... Ugyldig forskydning... Gyldigt område er ...* når tekst er valgt og der trykkes uden for den valgte tekst. Denne fejl er rettet i Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planlagte funktioner
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Verwandte Fragen:
|
|||
* Der Bildlauf zu einer intern verknüpften Stelle in Originalnachrichten funktioniert nicht. Dies kann nicht behoben werden, da die Original-Nachrichten-Ansicht in einer Scroll-Ansicht enthalten ist.
|
||||
* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3” und „Mi Band 3” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
|
||||
* Ein [Fehler in Android 6.0](https://issuetracker.google.com/issues/37068143) verursacht einen Absturz mit * … Ungültiger Offset: ... Der gültige Bereich ist …* wenn Text ausgewählt ist und außerhalb des ausgewählten Textes angetippt wird. Dieser Fehler wurde in Android 6.0.1 behoben.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Geplante Funktionen
|
||||
|
||||
|
|
@ -126,10 +127,10 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(5) Wie kann ich die Nachrichtenansicht anpassen?](#user-content-faq5)
|
||||
* [(6) Wie kann ich mich bei Gmail / G Suite anmelden?](#user-content-faq6)
|
||||
* [(7) Warum werden gesendete Nachrichten nicht (direkt) im Gesendet-Ordner angezeigt?](#user-content-faq7)
|
||||
* [(8) Kann ich ein Microsoft Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(8) Kann ich ein Microsoft-Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(9) Was sind Identitäten / Wie füge ich einen Alias hinzu?](#user-content-faq9)
|
||||
* [~~(11) Warum wird POP nicht unterstützt?~~](#user-content-faq11)
|
||||
* [~~(10) Was bedeutet "UIDPLUS nicht unterstützt"?~~](#user-content-faq10)
|
||||
* [~~(10) Was bedeutet »UIDPLUS nicht unterstützt«?~~](#user-content-faq10)
|
||||
* [(12) Wie funktioniert die Ver- und Entschlüsselung?](#user-content-faq12)
|
||||
* [(13) Wie funktioniert die Suche auf dem Gerät bzw. auf den Servern?](#user-content-faq13)
|
||||
* [(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?](#user-content-faq14)
|
||||
|
|
@ -140,7 +141,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(19) Warum sind die Pro-Funktionen so teuer?](#user-content-faq19)
|
||||
* [(20) Kann ich eine Rückerstattung erhalten?](#user-content-faq20)
|
||||
* [(21) Wie aktiviere ich das Benachrichtigungslicht?](#user-content-faq21)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler ... ?](#user-content-faq22)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler …?](#user-content-faq22)
|
||||
* [(23) Warum bekomme ich einen Alarm? ?](#user-content-faq23)
|
||||
* [(24) Was bedeutet das Anzeigen / Suchen von Nachrichten auf dem Server?](#user-content-faq24)
|
||||
* [(25) Warum kann ich ein Bild, einen Anhang oder eine Datei nicht auswählen, öffnen oder speichern?](#user-content-faq25)
|
||||
|
|
@ -170,7 +171,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(50) Kann man eine Option hinzufügen, um alle Nachrichten zu synchronisieren?](#user-content-faq50)
|
||||
* [(51) Wie werden die Ordner sortiert?](#user-content-faq51)
|
||||
* [(52) Wieso dauert es so lange Zeit, um sich wieder mit einem Konto zu verbinden?](#user-content-faq52)
|
||||
* [(53) Kann ich die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [(53) Können Sie die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [~~(54) Wie benutze ich ein Namensraumpräfix?~~](#user-content-faq54)
|
||||
* [(55) Wie kann ich alle Nachrichten als gelesen markieren, verschieben oder löschen?](#user-content-faq55)
|
||||
* [(56) Können Sie Unterstützung für JMAP hinzufügen?](#user-content-faq56)
|
||||
|
|
@ -181,15 +182,15 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(61) Warum werden einige Nachrichten verdunkelt angezeigt?](#user-content-faq61)
|
||||
* [(62) Welche Authentifizierungsmethoden werden unterstützt?](#user-content-faq62)
|
||||
* [(63) Wie werden Bilder für die Anzeige auf den Bildschirmen skaliert?](#user-content-faq63)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links/Rechts-Wischen hinzufügen?~~](#user-content-faq64)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links-/Rechtswischen hinzufügen?~~](#user-content-faq64)
|
||||
* [(65) Warum werden einige Anhänge abgedunkelt angezeigt?](#user-content-faq65)
|
||||
* [(66) Gibt es FairMail in der Google Play Familienmediathek?](#user-content-faq66)
|
||||
* [(67) Wie kann ich Konversationen stumm schalten?](#user-content-faq67)
|
||||
* [~~(68) Warum kann Adobe Acrobat Reader keine PDF-Anhänge öffnen / Microsoft-Apps keine angehängten Dokumente öffnen?~~](#user-content-faq68)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben scrollen«?](#user-content-faq69)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben rollen«?](#user-content-faq69)
|
||||
* [(70) Wann werden Nachrichten automatisch erweitert?](#user-content-faq70)
|
||||
* [(71) Wie verwende ich Filterregeln?](#user-content-faq71)
|
||||
* [(72) Was sind Primärkonten/Identitäten?](#user-content-faq72)
|
||||
* [(72) Was sind Hauptkonten/-identitäten?](#user-content-faq72)
|
||||
* [(73) Ist das Verschieben von Nachrichten zwischen verschiedenen Konten sicher/effizient?](#user-content-faq73)
|
||||
* [(74) Wieso sehe ich Nachrichten doppelt?](#user-content-faq74)
|
||||
* [(75) Können Sie eine iOS-, Windows-, Linux- usw. Version erstellen?](#user-content-faq75)
|
||||
|
|
@ -213,7 +214,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(94) Was bedeutet der rot-orangefarbene Streifen am Ende des Nachrichtenkopfes?](#user-content-faq94)
|
||||
* [(95) Warum werden nicht alle Apps angezeigt, wenn ein Anhang oder ein Bild ausgewählt wird?](#user-content-faq95)
|
||||
* [(96) Wo finde ich die IMAP- und SMTP-Einstellungen?](#user-content-faq96)
|
||||
* [(97) Was ist "Aufräumen" ?](#user-content-faq97)
|
||||
* [(97) Was ist »Bereinigen« ?](#user-content-faq97)
|
||||
* [(98) Warum kann ich immer noch Kontakte auswählen, nachdem ich Kontaktberechtigungen entzogen habe?](#user-content-faq98)
|
||||
* [(99) Gibt es einen Rich-Text- oder Markdown-Editor?](#user-content-faq99)
|
||||
* [(100) Wie kann ich Google Mail-Kategorien synchronisieren?](#user-content-faq100)
|
||||
|
|
@ -225,57 +226,57 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(106) Welche Launcher können die Anzahl der ungelesenen Nachrichten als Plakette anzeigen?](#user-content-faq106)
|
||||
* [(107) Wie verwende ich farbige Sterne?](#user-content-faq107)
|
||||
* [(108) Kann man Nachrichten aus beliebigen Ordnern dauerhaft löschen?](#user-content-faq108)
|
||||
* [~~(109) Warum ist 'Konto auswählen' nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [~~(109) Warum ist »Konto auswählen« nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [(110) Warum sind (einige) Nachrichten leer und/oder Anhänge beschädigt?](#user-content-faq110)
|
||||
* [(111) Wird OAuth unterstützt?](#user-content-faq111)
|
||||
* [(112) Welchen E-Mail-Provider empfehlen Sie?](#user-content-faq112)
|
||||
* [(113) Wie funktioniert die biometrische Authentifizierung?](#user-content-faq113)
|
||||
* [(114) Kann man die Einstellungen anderer E-Mail-Apps importieren?](#user-content-faq114)
|
||||
* [(115) Können E-Mail-Adressen-Chips hinzufügt werden?](#user-content-faq115)
|
||||
* [(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen?~](#user-content-faq116)
|
||||
* [~~(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen? ~~](#user-content-faq116)
|
||||
* [Können Sie mir helfen, meinen Kauf wiederherzustellen?](#user-content-faq117)
|
||||
* [(118) Was bedeutet »Nachverfolgungsparameter entfernen« genau?](#user-content-faq118)
|
||||
* [(119) Können Sie dem Sammeleingang-Widget für Post Farben hinzufügen?](#user-content-faq119)
|
||||
* [~~(119) Können Sie Farben dem Sammeleingangs-Widget hinzufügen?~~](#user-content-faq119)
|
||||
* [(120) Warum werden neue Nachrichten beim Öffnen der App nicht entfernt?](#user-content-faq120)
|
||||
* [(121) Wie werden Nachrichten zu einer Konversation gruppiert?](#user-content-faq121)
|
||||
* [~~(122) Warum wird Empfängername/E-Mail-Adresse mit einer Warnfarbe angezeigt?~~](#user-content-faq122)
|
||||
* [(123) Was geschieht, wenn FairEmail keine Verbindung zu einem E-Mail-Server herstellen kann?](#user-content-faq123)
|
||||
* [(124) Warum erhalte ich den Hinweis 'Nachricht zu groß oder zu komplex, um sie anzuzeigen'?](#user-content-faq124)
|
||||
* [(124) Warum erhalte ich den Hinweis »Nachricht zu groß oder zu komplex, um sie anzuzeigen«?](#user-content-faq124)
|
||||
* [(125) Was sind die aktuellen experimentellen Eigenschaften?](#user-content-faq125)
|
||||
* [(126) Können Nachrichtenvorschauen an mein Wearable gesendet werden?](#user-content-faq126)
|
||||
* [(127) Wie kann ich den Fehler 'Syntaktisch ungültige HELO-Argumente(n)' beheben?](#user-content-faq127)
|
||||
* [(127) Wie kann ich den Fehler »Syntaktisch ungültige HELO-Argumente« beheben?](#user-content-faq127)
|
||||
* [(128) Wie kann ich die gestellten Fragen zurücksetzen, zum Beispiel um Bilder zu zeigen?](#user-content-faq128)
|
||||
* [(129) Wird ProtonMail, Tutanota unterstützt?](#user-content-faq129)
|
||||
* [(130) Was bedeutet die Meldung 'Fehler ...'?](#user-content-faq130)
|
||||
* [(130) Was bedeutet die Meldung »Fehler …«?](#user-content-faq130)
|
||||
* [(131) Kann man die Richtung für das Wischen für vorherige/nächste Nachricht ändern?](#user-content-faq131)
|
||||
* [(132) Warum sind Benachrichtigungen für neue Nachrichten stumm?](#user-content-faq132)
|
||||
* [(133) Warum wird ActiveSync nicht unterstützt?](#user-content-faq133)
|
||||
* [(134) Wie kann ich Nachrichten nur in der App löschen?](#user-content-faq134)
|
||||
* [(135) Warum werden gelöschte Nachrichten oder Entwürfe in Konversationen angezeigt?](#user-content-faq135)
|
||||
* [(136) Wie kann ich ein Konto/Identität/Ordner löschen?](#user-content-faq136)
|
||||
* [(137) Wie kann ich 'Nicht erneut fragen' zurücksetzen?](#user-content-faq137)
|
||||
* [(137) Wie kann ich »Nicht erneut fragen« zurücksetzen?](#user-content-faq137)
|
||||
* [(138) Gibt es die Funktionen Kalender/Kontaktmanagement/Synchronisation?](#user-content-faq138)
|
||||
* [(139) Wie behebe ich 'Benutzer ist angemeldet, aber nicht verbunden'?](#user-content-faq139)
|
||||
* [(139) Wie behebe ich »Benutzer ist angemeldet, aber nicht verbunden«?](#user-content-faq139)
|
||||
* [(140) Warum enthält der Nachrichtentext seltsame Zeichen?](#user-content-faq140)
|
||||
* [(141) Wie kann ich 'Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden' beheben?](#user-content-faq141)
|
||||
* [(141) Wie kann ich »Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden« beheben?](#user-content-faq141)
|
||||
* [(142) Wie kann ich gesendete Nachrichten im Posteingang speichern?](#user-content-faq142)
|
||||
* [~~(143) Gibt es einen Papierkorb für POP3-Konten? ~~](#user-content-faq143)
|
||||
* [(144) Wie kann ich Sprachnotizen aufnehmen?](#user-content-faq144)
|
||||
* [(145) Wie kann ich einen Benachrichtigungston für ein Konto, einen Ordner oder einen Absender festlegen?](#user-content-faq145)
|
||||
* [(146) Wie kann ich falsche Zeiten von Nachrichten beheben?](#user-content-faq146)
|
||||
* [(147) Was sollte ich über Drittanbieter-Versionen wissen?](#user-content-faq147)
|
||||
* [(148) Wie kann ich ein Apple iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(148) Wie kann ich ein Apple-iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(149) Wie funktioniert das Widget für ungelesene Nachrichten?](#user-content-faq149)
|
||||
* [(150) Gibt es eine Möglichkeit zum Ablehnen von Kalendereinladungen?](#user-content-faq150)
|
||||
* [(151) Gibt es eine Datensicherung/Wiederherstellung von Nachrichten?](#user-content-faq151)
|
||||
* [(152) Wie kann ich eine Kontaktgruppe einfügen?](#user-content-faq152)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Google Mail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Gmail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [~~(154) Kann man Favicons als Kontaktfotos verwenden?~~](#user-content-faq154)
|
||||
* [(155) Was ist eine winmail.dat-Datei?](#user-content-faq155)
|
||||
* [(156) Wie kann ich ein Office365-Konto einrichten?](#user-content-faq156)
|
||||
* [(157) Wie kann ich ein Free.fr-Konto einrichten?](#user-content-faq157)
|
||||
* [(158) Welche/r Kamera/Audiorekorder ist empfehlenswert?](#user-content-faq158)
|
||||
* [(159) Was sind Disconnect Trackingschutz-Listen?](#user-content-faq159)
|
||||
* [(159) Was sind Disconnects Tracker-Schutzlisten?](#user-content-faq159)
|
||||
|
||||
[Ich habe eine weitere Frage.](#user-content-support)
|
||||
|
||||
|
|
@ -747,9 +748,9 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Why are messages not being synchronized?**
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
Mögliche Ursachen dafür, dass Nachrichten nicht synchronisiert (gesendet oder empfangen) werden, sind:
|
||||
|
||||
* Konto oder Ordner(e) sind nicht zum Synchronisieren gesetzt
|
||||
* Die Anzahl der Tage, für die die Nachricht synchronisiert werden soll, ist zu niedrig gesetzt
|
||||
|
|
@ -757,13 +758,13 @@ Possible causes of messages not being synchronized (sent or received) are:
|
|||
* Der E-Mail-Server ist vorübergehend nicht verfügbar
|
||||
* Android hat die Synchronisation gestoppt
|
||||
|
||||
So, check your account and folder settings and check if the accounts/folders are connected (see the legend in the navigation menu for the meaning of the icons).
|
||||
Überprüfen Sie also Ihre Konto- und Ordnereinstellungen und überprüfen Sie, ob die Konten/Ordner verbunden sind (siehe die Legende in der Navigation zur Bedeutung der Symbole).
|
||||
|
||||
If there are any error messages, please see [this FAQ](#user-content-faq22).
|
||||
Wenn es irgendwelche Fehlermeldungen gibt, lesen Sie bitte [diese FAQ](#user-content-faq22).
|
||||
|
||||
On some devices, where there are lots of applications competing for memory, Android may stop the synchronization service as a last resort.
|
||||
Auf einigen Geräten, wo es viele Anwendungen gibt, die um Speicher konkurrieren, kann Android den Synchronisierungsdienst als letzte Möglichkeit stoppen.
|
||||
|
||||
Some Android versions stop apps and services too aggressively. See [this dedicated website](https://dontkillmyapp.com/) and [this Android issue](https://issuetracker.google.com/issues/122098785) for more information.
|
||||
Einige Android-Versionen stoppen Apps und Dienste zu aggressiv. Siehe [diese spezielle Webseite](https://dontkillmyapp.com/) und [dieses Android-Problem](https://issuetracker.google.com/issues/122098785) für weitere Informationen.
|
||||
|
||||
Disabling battery optimizations (setup step 4) reduces the chance Android will stop the synchronization service.
|
||||
|
||||
|
|
@ -786,16 +787,16 @@ The preview of the message text cannot be shown if the message body has not been
|
|||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Why are the pro features so expensive?**
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
Die richtige Frage ist: "*Warum gibt es so viele Steuern und Gebühren?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Verwandte Fragen:
|
|||
* Der Bildlauf zu einer intern verknüpften Stelle in Originalnachrichten funktioniert nicht. Dies kann nicht behoben werden, da die Original-Nachrichten-Ansicht in einer Scroll-Ansicht enthalten ist.
|
||||
* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3” und „Mi Band 3” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
|
||||
* Ein [Fehler in Android 6.0](https://issuetracker.google.com/issues/37068143) verursacht einen Absturz mit * … Ungültiger Offset: ... Der gültige Bereich ist …* wenn Text ausgewählt ist und außerhalb des ausgewählten Textes angetippt wird. Dieser Fehler wurde in Android 6.0.1 behoben.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Geplante Funktionen
|
||||
|
||||
|
|
@ -126,10 +127,10 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(5) Wie kann ich die Nachrichtenansicht anpassen?](#user-content-faq5)
|
||||
* [(6) Wie kann ich mich bei Gmail / G Suite anmelden?](#user-content-faq6)
|
||||
* [(7) Warum werden gesendete Nachrichten nicht (direkt) im Gesendet-Ordner angezeigt?](#user-content-faq7)
|
||||
* [(8) Kann ich ein Microsoft Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(8) Kann ich ein Microsoft-Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(9) Was sind Identitäten / Wie füge ich einen Alias hinzu?](#user-content-faq9)
|
||||
* [~~(11) Warum wird POP nicht unterstützt?~~](#user-content-faq11)
|
||||
* [~~(10) Was bedeutet "UIDPLUS nicht unterstützt"?~~](#user-content-faq10)
|
||||
* [~~(10) Was bedeutet »UIDPLUS nicht unterstützt«?~~](#user-content-faq10)
|
||||
* [(12) Wie funktioniert die Ver- und Entschlüsselung?](#user-content-faq12)
|
||||
* [(13) Wie funktioniert die Suche auf dem Gerät bzw. auf den Servern?](#user-content-faq13)
|
||||
* [(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?](#user-content-faq14)
|
||||
|
|
@ -140,7 +141,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(19) Warum sind die Pro-Funktionen so teuer?](#user-content-faq19)
|
||||
* [(20) Kann ich eine Rückerstattung erhalten?](#user-content-faq20)
|
||||
* [(21) Wie aktiviere ich das Benachrichtigungslicht?](#user-content-faq21)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler ... ?](#user-content-faq22)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler …?](#user-content-faq22)
|
||||
* [(23) Warum bekomme ich einen Alarm? ?](#user-content-faq23)
|
||||
* [(24) Was bedeutet das Anzeigen / Suchen von Nachrichten auf dem Server?](#user-content-faq24)
|
||||
* [(25) Warum kann ich ein Bild, einen Anhang oder eine Datei nicht auswählen, öffnen oder speichern?](#user-content-faq25)
|
||||
|
|
@ -170,7 +171,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(50) Kann man eine Option hinzufügen, um alle Nachrichten zu synchronisieren?](#user-content-faq50)
|
||||
* [(51) Wie werden die Ordner sortiert?](#user-content-faq51)
|
||||
* [(52) Wieso dauert es so lange Zeit, um sich wieder mit einem Konto zu verbinden?](#user-content-faq52)
|
||||
* [(53) Kann ich die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [(53) Können Sie die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [~~(54) Wie benutze ich ein Namensraumpräfix?~~](#user-content-faq54)
|
||||
* [(55) Wie kann ich alle Nachrichten als gelesen markieren, verschieben oder löschen?](#user-content-faq55)
|
||||
* [(56) Können Sie Unterstützung für JMAP hinzufügen?](#user-content-faq56)
|
||||
|
|
@ -181,15 +182,15 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(61) Warum werden einige Nachrichten verdunkelt angezeigt?](#user-content-faq61)
|
||||
* [(62) Welche Authentifizierungsmethoden werden unterstützt?](#user-content-faq62)
|
||||
* [(63) Wie werden Bilder für die Anzeige auf den Bildschirmen skaliert?](#user-content-faq63)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links/Rechts-Wischen hinzufügen?~~](#user-content-faq64)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links-/Rechtswischen hinzufügen?~~](#user-content-faq64)
|
||||
* [(65) Warum werden einige Anhänge abgedunkelt angezeigt?](#user-content-faq65)
|
||||
* [(66) Gibt es FairMail in der Google Play Familienmediathek?](#user-content-faq66)
|
||||
* [(67) Wie kann ich Konversationen stumm schalten?](#user-content-faq67)
|
||||
* [~~(68) Warum kann Adobe Acrobat Reader keine PDF-Anhänge öffnen / Microsoft-Apps keine angehängten Dokumente öffnen?~~](#user-content-faq68)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben scrollen«?](#user-content-faq69)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben rollen«?](#user-content-faq69)
|
||||
* [(70) Wann werden Nachrichten automatisch erweitert?](#user-content-faq70)
|
||||
* [(71) Wie verwende ich Filterregeln?](#user-content-faq71)
|
||||
* [(72) Was sind Primärkonten/Identitäten?](#user-content-faq72)
|
||||
* [(72) Was sind Hauptkonten/-identitäten?](#user-content-faq72)
|
||||
* [(73) Ist das Verschieben von Nachrichten zwischen verschiedenen Konten sicher/effizient?](#user-content-faq73)
|
||||
* [(74) Wieso sehe ich Nachrichten doppelt?](#user-content-faq74)
|
||||
* [(75) Können Sie eine iOS-, Windows-, Linux- usw. Version erstellen?](#user-content-faq75)
|
||||
|
|
@ -213,7 +214,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(94) Was bedeutet der rot-orangefarbene Streifen am Ende des Nachrichtenkopfes?](#user-content-faq94)
|
||||
* [(95) Warum werden nicht alle Apps angezeigt, wenn ein Anhang oder ein Bild ausgewählt wird?](#user-content-faq95)
|
||||
* [(96) Wo finde ich die IMAP- und SMTP-Einstellungen?](#user-content-faq96)
|
||||
* [(97) Was ist "Aufräumen" ?](#user-content-faq97)
|
||||
* [(97) Was ist »Bereinigen« ?](#user-content-faq97)
|
||||
* [(98) Warum kann ich immer noch Kontakte auswählen, nachdem ich Kontaktberechtigungen entzogen habe?](#user-content-faq98)
|
||||
* [(99) Gibt es einen Rich-Text- oder Markdown-Editor?](#user-content-faq99)
|
||||
* [(100) Wie kann ich Google Mail-Kategorien synchronisieren?](#user-content-faq100)
|
||||
|
|
@ -225,57 +226,57 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(106) Welche Launcher können die Anzahl der ungelesenen Nachrichten als Plakette anzeigen?](#user-content-faq106)
|
||||
* [(107) Wie verwende ich farbige Sterne?](#user-content-faq107)
|
||||
* [(108) Kann man Nachrichten aus beliebigen Ordnern dauerhaft löschen?](#user-content-faq108)
|
||||
* [~~(109) Warum ist 'Konto auswählen' nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [~~(109) Warum ist »Konto auswählen« nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [(110) Warum sind (einige) Nachrichten leer und/oder Anhänge beschädigt?](#user-content-faq110)
|
||||
* [(111) Wird OAuth unterstützt?](#user-content-faq111)
|
||||
* [(112) Welchen E-Mail-Provider empfehlen Sie?](#user-content-faq112)
|
||||
* [(113) Wie funktioniert die biometrische Authentifizierung?](#user-content-faq113)
|
||||
* [(114) Kann man die Einstellungen anderer E-Mail-Apps importieren?](#user-content-faq114)
|
||||
* [(115) Können E-Mail-Adressen-Chips hinzufügt werden?](#user-content-faq115)
|
||||
* [(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen?~](#user-content-faq116)
|
||||
* [~~(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen? ~~](#user-content-faq116)
|
||||
* [Können Sie mir helfen, meinen Kauf wiederherzustellen?](#user-content-faq117)
|
||||
* [(118) Was bedeutet »Nachverfolgungsparameter entfernen« genau?](#user-content-faq118)
|
||||
* [(119) Können Sie dem Sammeleingang-Widget für Post Farben hinzufügen?](#user-content-faq119)
|
||||
* [~~(119) Können Sie Farben dem Sammeleingangs-Widget hinzufügen?~~](#user-content-faq119)
|
||||
* [(120) Warum werden neue Nachrichten beim Öffnen der App nicht entfernt?](#user-content-faq120)
|
||||
* [(121) Wie werden Nachrichten zu einer Konversation gruppiert?](#user-content-faq121)
|
||||
* [~~(122) Warum wird Empfängername/E-Mail-Adresse mit einer Warnfarbe angezeigt?~~](#user-content-faq122)
|
||||
* [(123) Was geschieht, wenn FairEmail keine Verbindung zu einem E-Mail-Server herstellen kann?](#user-content-faq123)
|
||||
* [(124) Warum erhalte ich den Hinweis 'Nachricht zu groß oder zu komplex, um sie anzuzeigen'?](#user-content-faq124)
|
||||
* [(124) Warum erhalte ich den Hinweis »Nachricht zu groß oder zu komplex, um sie anzuzeigen«?](#user-content-faq124)
|
||||
* [(125) Was sind die aktuellen experimentellen Eigenschaften?](#user-content-faq125)
|
||||
* [(126) Können Nachrichtenvorschauen an mein Wearable gesendet werden?](#user-content-faq126)
|
||||
* [(127) Wie kann ich den Fehler 'Syntaktisch ungültige HELO-Argumente(n)' beheben?](#user-content-faq127)
|
||||
* [(127) Wie kann ich den Fehler »Syntaktisch ungültige HELO-Argumente« beheben?](#user-content-faq127)
|
||||
* [(128) Wie kann ich die gestellten Fragen zurücksetzen, zum Beispiel um Bilder zu zeigen?](#user-content-faq128)
|
||||
* [(129) Wird ProtonMail, Tutanota unterstützt?](#user-content-faq129)
|
||||
* [(130) Was bedeutet die Meldung 'Fehler ...'?](#user-content-faq130)
|
||||
* [(130) Was bedeutet die Meldung »Fehler …«?](#user-content-faq130)
|
||||
* [(131) Kann man die Richtung für das Wischen für vorherige/nächste Nachricht ändern?](#user-content-faq131)
|
||||
* [(132) Warum sind Benachrichtigungen für neue Nachrichten stumm?](#user-content-faq132)
|
||||
* [(133) Warum wird ActiveSync nicht unterstützt?](#user-content-faq133)
|
||||
* [(134) Wie kann ich Nachrichten nur in der App löschen?](#user-content-faq134)
|
||||
* [(135) Warum werden gelöschte Nachrichten oder Entwürfe in Konversationen angezeigt?](#user-content-faq135)
|
||||
* [(136) Wie kann ich ein Konto/Identität/Ordner löschen?](#user-content-faq136)
|
||||
* [(137) Wie kann ich 'Nicht erneut fragen' zurücksetzen?](#user-content-faq137)
|
||||
* [(137) Wie kann ich »Nicht erneut fragen« zurücksetzen?](#user-content-faq137)
|
||||
* [(138) Gibt es die Funktionen Kalender/Kontaktmanagement/Synchronisation?](#user-content-faq138)
|
||||
* [(139) Wie behebe ich 'Benutzer ist angemeldet, aber nicht verbunden'?](#user-content-faq139)
|
||||
* [(139) Wie behebe ich »Benutzer ist angemeldet, aber nicht verbunden«?](#user-content-faq139)
|
||||
* [(140) Warum enthält der Nachrichtentext seltsame Zeichen?](#user-content-faq140)
|
||||
* [(141) Wie kann ich 'Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden' beheben?](#user-content-faq141)
|
||||
* [(141) Wie kann ich »Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden« beheben?](#user-content-faq141)
|
||||
* [(142) Wie kann ich gesendete Nachrichten im Posteingang speichern?](#user-content-faq142)
|
||||
* [~~(143) Gibt es einen Papierkorb für POP3-Konten? ~~](#user-content-faq143)
|
||||
* [(144) Wie kann ich Sprachnotizen aufnehmen?](#user-content-faq144)
|
||||
* [(145) Wie kann ich einen Benachrichtigungston für ein Konto, einen Ordner oder einen Absender festlegen?](#user-content-faq145)
|
||||
* [(146) Wie kann ich falsche Zeiten von Nachrichten beheben?](#user-content-faq146)
|
||||
* [(147) Was sollte ich über Drittanbieter-Versionen wissen?](#user-content-faq147)
|
||||
* [(148) Wie kann ich ein Apple iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(148) Wie kann ich ein Apple-iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(149) Wie funktioniert das Widget für ungelesene Nachrichten?](#user-content-faq149)
|
||||
* [(150) Gibt es eine Möglichkeit zum Ablehnen von Kalendereinladungen?](#user-content-faq150)
|
||||
* [(151) Gibt es eine Datensicherung/Wiederherstellung von Nachrichten?](#user-content-faq151)
|
||||
* [(152) Wie kann ich eine Kontaktgruppe einfügen?](#user-content-faq152)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Google Mail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Gmail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [~~(154) Kann man Favicons als Kontaktfotos verwenden?~~](#user-content-faq154)
|
||||
* [(155) Was ist eine winmail.dat-Datei?](#user-content-faq155)
|
||||
* [(156) Wie kann ich ein Office365-Konto einrichten?](#user-content-faq156)
|
||||
* [(157) Wie kann ich ein Free.fr-Konto einrichten?](#user-content-faq157)
|
||||
* [(158) Welche/r Kamera/Audiorekorder ist empfehlenswert?](#user-content-faq158)
|
||||
* [(159) Was sind Disconnect Trackingschutz-Listen?](#user-content-faq159)
|
||||
* [(159) Was sind Disconnects Tracker-Schutzlisten?](#user-content-faq159)
|
||||
|
||||
[Ich habe eine weitere Frage.](#user-content-support)
|
||||
|
||||
|
|
@ -747,9 +748,9 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Why are messages not being synchronized?**
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
Mögliche Ursachen dafür, dass Nachrichten nicht synchronisiert (gesendet oder empfangen) werden, sind:
|
||||
|
||||
* Konto oder Ordner(e) sind nicht zum Synchronisieren gesetzt
|
||||
* Die Anzahl der Tage, für die die Nachricht synchronisiert werden soll, ist zu niedrig gesetzt
|
||||
|
|
@ -757,13 +758,13 @@ Possible causes of messages not being synchronized (sent or received) are:
|
|||
* Der E-Mail-Server ist vorübergehend nicht verfügbar
|
||||
* Android hat die Synchronisation gestoppt
|
||||
|
||||
So, check your account and folder settings and check if the accounts/folders are connected (see the legend in the navigation menu for the meaning of the icons).
|
||||
Überprüfen Sie also Ihre Konto- und Ordnereinstellungen und überprüfen Sie, ob die Konten/Ordner verbunden sind (siehe die Legende in der Navigation zur Bedeutung der Symbole).
|
||||
|
||||
If there are any error messages, please see [this FAQ](#user-content-faq22).
|
||||
Wenn es irgendwelche Fehlermeldungen gibt, lesen Sie bitte [diese FAQ](#user-content-faq22).
|
||||
|
||||
On some devices, where there are lots of applications competing for memory, Android may stop the synchronization service as a last resort.
|
||||
Auf einigen Geräten, wo es viele Anwendungen gibt, die um Speicher konkurrieren, kann Android den Synchronisierungsdienst als letzte Möglichkeit stoppen.
|
||||
|
||||
Some Android versions stop apps and services too aggressively. See [this dedicated website](https://dontkillmyapp.com/) and [this Android issue](https://issuetracker.google.com/issues/122098785) for more information.
|
||||
Einige Android-Versionen stoppen Apps und Dienste zu aggressiv. Siehe [diese spezielle Webseite](https://dontkillmyapp.com/) und [dieses Android-Problem](https://issuetracker.google.com/issues/122098785) für weitere Informationen.
|
||||
|
||||
Disabling battery optimizations (setup step 4) reduces the chance Android will stop the synchronization service.
|
||||
|
||||
|
|
@ -786,16 +787,16 @@ The preview of the message text cannot be shown if the message body has not been
|
|||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Why are the pro features so expensive?**
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
Die richtige Frage ist: "*Warum gibt es so viele Steuern und Gebühren?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Verwandte Fragen:
|
|||
* Der Bildlauf zu einer intern verknüpften Stelle in Originalnachrichten funktioniert nicht. Dies kann nicht behoben werden, da die Original-Nachrichten-Ansicht in einer Scroll-Ansicht enthalten ist.
|
||||
* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3” und „Mi Band 3” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
|
||||
* Ein [Fehler in Android 6.0](https://issuetracker.google.com/issues/37068143) verursacht einen Absturz mit * … Ungültiger Offset: ... Der gültige Bereich ist …* wenn Text ausgewählt ist und außerhalb des ausgewählten Textes angetippt wird. Dieser Fehler wurde in Android 6.0.1 behoben.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Geplante Funktionen
|
||||
|
||||
|
|
@ -126,10 +127,10 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(5) Wie kann ich die Nachrichtenansicht anpassen?](#user-content-faq5)
|
||||
* [(6) Wie kann ich mich bei Gmail / G Suite anmelden?](#user-content-faq6)
|
||||
* [(7) Warum werden gesendete Nachrichten nicht (direkt) im Gesendet-Ordner angezeigt?](#user-content-faq7)
|
||||
* [(8) Kann ich ein Microsoft Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(8) Kann ich ein Microsoft-Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(9) Was sind Identitäten / Wie füge ich einen Alias hinzu?](#user-content-faq9)
|
||||
* [~~(11) Warum wird POP nicht unterstützt?~~](#user-content-faq11)
|
||||
* [~~(10) Was bedeutet "UIDPLUS nicht unterstützt"?~~](#user-content-faq10)
|
||||
* [~~(10) Was bedeutet »UIDPLUS nicht unterstützt«?~~](#user-content-faq10)
|
||||
* [(12) Wie funktioniert die Ver- und Entschlüsselung?](#user-content-faq12)
|
||||
* [(13) Wie funktioniert die Suche auf dem Gerät bzw. auf den Servern?](#user-content-faq13)
|
||||
* [(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?](#user-content-faq14)
|
||||
|
|
@ -140,7 +141,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(19) Warum sind die Pro-Funktionen so teuer?](#user-content-faq19)
|
||||
* [(20) Kann ich eine Rückerstattung erhalten?](#user-content-faq20)
|
||||
* [(21) Wie aktiviere ich das Benachrichtigungslicht?](#user-content-faq21)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler ... ?](#user-content-faq22)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler …?](#user-content-faq22)
|
||||
* [(23) Warum bekomme ich einen Alarm? ?](#user-content-faq23)
|
||||
* [(24) Was bedeutet das Anzeigen / Suchen von Nachrichten auf dem Server?](#user-content-faq24)
|
||||
* [(25) Warum kann ich ein Bild, einen Anhang oder eine Datei nicht auswählen, öffnen oder speichern?](#user-content-faq25)
|
||||
|
|
@ -170,7 +171,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(50) Kann man eine Option hinzufügen, um alle Nachrichten zu synchronisieren?](#user-content-faq50)
|
||||
* [(51) Wie werden die Ordner sortiert?](#user-content-faq51)
|
||||
* [(52) Wieso dauert es so lange Zeit, um sich wieder mit einem Konto zu verbinden?](#user-content-faq52)
|
||||
* [(53) Kann ich die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [(53) Können Sie die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [~~(54) Wie benutze ich ein Namensraumpräfix?~~](#user-content-faq54)
|
||||
* [(55) Wie kann ich alle Nachrichten als gelesen markieren, verschieben oder löschen?](#user-content-faq55)
|
||||
* [(56) Können Sie Unterstützung für JMAP hinzufügen?](#user-content-faq56)
|
||||
|
|
@ -181,15 +182,15 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(61) Warum werden einige Nachrichten verdunkelt angezeigt?](#user-content-faq61)
|
||||
* [(62) Welche Authentifizierungsmethoden werden unterstützt?](#user-content-faq62)
|
||||
* [(63) Wie werden Bilder für die Anzeige auf den Bildschirmen skaliert?](#user-content-faq63)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links/Rechts-Wischen hinzufügen?~~](#user-content-faq64)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links-/Rechtswischen hinzufügen?~~](#user-content-faq64)
|
||||
* [(65) Warum werden einige Anhänge abgedunkelt angezeigt?](#user-content-faq65)
|
||||
* [(66) Gibt es FairMail in der Google Play Familienmediathek?](#user-content-faq66)
|
||||
* [(67) Wie kann ich Konversationen stumm schalten?](#user-content-faq67)
|
||||
* [~~(68) Warum kann Adobe Acrobat Reader keine PDF-Anhänge öffnen / Microsoft-Apps keine angehängten Dokumente öffnen?~~](#user-content-faq68)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben scrollen«?](#user-content-faq69)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben rollen«?](#user-content-faq69)
|
||||
* [(70) Wann werden Nachrichten automatisch erweitert?](#user-content-faq70)
|
||||
* [(71) Wie verwende ich Filterregeln?](#user-content-faq71)
|
||||
* [(72) Was sind Primärkonten/Identitäten?](#user-content-faq72)
|
||||
* [(72) Was sind Hauptkonten/-identitäten?](#user-content-faq72)
|
||||
* [(73) Ist das Verschieben von Nachrichten zwischen verschiedenen Konten sicher/effizient?](#user-content-faq73)
|
||||
* [(74) Wieso sehe ich Nachrichten doppelt?](#user-content-faq74)
|
||||
* [(75) Können Sie eine iOS-, Windows-, Linux- usw. Version erstellen?](#user-content-faq75)
|
||||
|
|
@ -213,7 +214,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(94) Was bedeutet der rot-orangefarbene Streifen am Ende des Nachrichtenkopfes?](#user-content-faq94)
|
||||
* [(95) Warum werden nicht alle Apps angezeigt, wenn ein Anhang oder ein Bild ausgewählt wird?](#user-content-faq95)
|
||||
* [(96) Wo finde ich die IMAP- und SMTP-Einstellungen?](#user-content-faq96)
|
||||
* [(97) Was ist "Aufräumen" ?](#user-content-faq97)
|
||||
* [(97) Was ist »Bereinigen« ?](#user-content-faq97)
|
||||
* [(98) Warum kann ich immer noch Kontakte auswählen, nachdem ich Kontaktberechtigungen entzogen habe?](#user-content-faq98)
|
||||
* [(99) Gibt es einen Rich-Text- oder Markdown-Editor?](#user-content-faq99)
|
||||
* [(100) Wie kann ich Google Mail-Kategorien synchronisieren?](#user-content-faq100)
|
||||
|
|
@ -225,57 +226,57 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(106) Welche Launcher können die Anzahl der ungelesenen Nachrichten als Plakette anzeigen?](#user-content-faq106)
|
||||
* [(107) Wie verwende ich farbige Sterne?](#user-content-faq107)
|
||||
* [(108) Kann man Nachrichten aus beliebigen Ordnern dauerhaft löschen?](#user-content-faq108)
|
||||
* [~~(109) Warum ist 'Konto auswählen' nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [~~(109) Warum ist »Konto auswählen« nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [(110) Warum sind (einige) Nachrichten leer und/oder Anhänge beschädigt?](#user-content-faq110)
|
||||
* [(111) Wird OAuth unterstützt?](#user-content-faq111)
|
||||
* [(112) Welchen E-Mail-Provider empfehlen Sie?](#user-content-faq112)
|
||||
* [(113) Wie funktioniert die biometrische Authentifizierung?](#user-content-faq113)
|
||||
* [(114) Kann man die Einstellungen anderer E-Mail-Apps importieren?](#user-content-faq114)
|
||||
* [(115) Können E-Mail-Adressen-Chips hinzufügt werden?](#user-content-faq115)
|
||||
* [(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen?~](#user-content-faq116)
|
||||
* [~~(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen? ~~](#user-content-faq116)
|
||||
* [Können Sie mir helfen, meinen Kauf wiederherzustellen?](#user-content-faq117)
|
||||
* [(118) Was bedeutet »Nachverfolgungsparameter entfernen« genau?](#user-content-faq118)
|
||||
* [(119) Können Sie dem Sammeleingang-Widget für Post Farben hinzufügen?](#user-content-faq119)
|
||||
* [~~(119) Können Sie Farben dem Sammeleingangs-Widget hinzufügen?~~](#user-content-faq119)
|
||||
* [(120) Warum werden neue Nachrichten beim Öffnen der App nicht entfernt?](#user-content-faq120)
|
||||
* [(121) Wie werden Nachrichten zu einer Konversation gruppiert?](#user-content-faq121)
|
||||
* [~~(122) Warum wird Empfängername/E-Mail-Adresse mit einer Warnfarbe angezeigt?~~](#user-content-faq122)
|
||||
* [(123) Was geschieht, wenn FairEmail keine Verbindung zu einem E-Mail-Server herstellen kann?](#user-content-faq123)
|
||||
* [(124) Warum erhalte ich den Hinweis 'Nachricht zu groß oder zu komplex, um sie anzuzeigen'?](#user-content-faq124)
|
||||
* [(124) Warum erhalte ich den Hinweis »Nachricht zu groß oder zu komplex, um sie anzuzeigen«?](#user-content-faq124)
|
||||
* [(125) Was sind die aktuellen experimentellen Eigenschaften?](#user-content-faq125)
|
||||
* [(126) Können Nachrichtenvorschauen an mein Wearable gesendet werden?](#user-content-faq126)
|
||||
* [(127) Wie kann ich den Fehler 'Syntaktisch ungültige HELO-Argumente(n)' beheben?](#user-content-faq127)
|
||||
* [(127) Wie kann ich den Fehler »Syntaktisch ungültige HELO-Argumente« beheben?](#user-content-faq127)
|
||||
* [(128) Wie kann ich die gestellten Fragen zurücksetzen, zum Beispiel um Bilder zu zeigen?](#user-content-faq128)
|
||||
* [(129) Wird ProtonMail, Tutanota unterstützt?](#user-content-faq129)
|
||||
* [(130) Was bedeutet die Meldung 'Fehler ...'?](#user-content-faq130)
|
||||
* [(130) Was bedeutet die Meldung »Fehler …«?](#user-content-faq130)
|
||||
* [(131) Kann man die Richtung für das Wischen für vorherige/nächste Nachricht ändern?](#user-content-faq131)
|
||||
* [(132) Warum sind Benachrichtigungen für neue Nachrichten stumm?](#user-content-faq132)
|
||||
* [(133) Warum wird ActiveSync nicht unterstützt?](#user-content-faq133)
|
||||
* [(134) Wie kann ich Nachrichten nur in der App löschen?](#user-content-faq134)
|
||||
* [(135) Warum werden gelöschte Nachrichten oder Entwürfe in Konversationen angezeigt?](#user-content-faq135)
|
||||
* [(136) Wie kann ich ein Konto/Identität/Ordner löschen?](#user-content-faq136)
|
||||
* [(137) Wie kann ich 'Nicht erneut fragen' zurücksetzen?](#user-content-faq137)
|
||||
* [(137) Wie kann ich »Nicht erneut fragen« zurücksetzen?](#user-content-faq137)
|
||||
* [(138) Gibt es die Funktionen Kalender/Kontaktmanagement/Synchronisation?](#user-content-faq138)
|
||||
* [(139) Wie behebe ich 'Benutzer ist angemeldet, aber nicht verbunden'?](#user-content-faq139)
|
||||
* [(139) Wie behebe ich »Benutzer ist angemeldet, aber nicht verbunden«?](#user-content-faq139)
|
||||
* [(140) Warum enthält der Nachrichtentext seltsame Zeichen?](#user-content-faq140)
|
||||
* [(141) Wie kann ich 'Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden' beheben?](#user-content-faq141)
|
||||
* [(141) Wie kann ich »Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden« beheben?](#user-content-faq141)
|
||||
* [(142) Wie kann ich gesendete Nachrichten im Posteingang speichern?](#user-content-faq142)
|
||||
* [~~(143) Gibt es einen Papierkorb für POP3-Konten? ~~](#user-content-faq143)
|
||||
* [(144) Wie kann ich Sprachnotizen aufnehmen?](#user-content-faq144)
|
||||
* [(145) Wie kann ich einen Benachrichtigungston für ein Konto, einen Ordner oder einen Absender festlegen?](#user-content-faq145)
|
||||
* [(146) Wie kann ich falsche Zeiten von Nachrichten beheben?](#user-content-faq146)
|
||||
* [(147) Was sollte ich über Drittanbieter-Versionen wissen?](#user-content-faq147)
|
||||
* [(148) Wie kann ich ein Apple iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(148) Wie kann ich ein Apple-iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(149) Wie funktioniert das Widget für ungelesene Nachrichten?](#user-content-faq149)
|
||||
* [(150) Gibt es eine Möglichkeit zum Ablehnen von Kalendereinladungen?](#user-content-faq150)
|
||||
* [(151) Gibt es eine Datensicherung/Wiederherstellung von Nachrichten?](#user-content-faq151)
|
||||
* [(152) Wie kann ich eine Kontaktgruppe einfügen?](#user-content-faq152)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Google Mail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Gmail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [~~(154) Kann man Favicons als Kontaktfotos verwenden?~~](#user-content-faq154)
|
||||
* [(155) Was ist eine winmail.dat-Datei?](#user-content-faq155)
|
||||
* [(156) Wie kann ich ein Office365-Konto einrichten?](#user-content-faq156)
|
||||
* [(157) Wie kann ich ein Free.fr-Konto einrichten?](#user-content-faq157)
|
||||
* [(158) Welche/r Kamera/Audiorekorder ist empfehlenswert?](#user-content-faq158)
|
||||
* [(159) Was sind Disconnect Trackingschutz-Listen?](#user-content-faq159)
|
||||
* [(159) Was sind Disconnects Tracker-Schutzlisten?](#user-content-faq159)
|
||||
|
||||
[Ich habe eine weitere Frage.](#user-content-support)
|
||||
|
||||
|
|
@ -747,9 +748,9 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Why are messages not being synchronized?**
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
Mögliche Ursachen dafür, dass Nachrichten nicht synchronisiert (gesendet oder empfangen) werden, sind:
|
||||
|
||||
* Konto oder Ordner(e) sind nicht zum Synchronisieren gesetzt
|
||||
* Die Anzahl der Tage, für die die Nachricht synchronisiert werden soll, ist zu niedrig gesetzt
|
||||
|
|
@ -757,13 +758,13 @@ Possible causes of messages not being synchronized (sent or received) are:
|
|||
* Der E-Mail-Server ist vorübergehend nicht verfügbar
|
||||
* Android hat die Synchronisation gestoppt
|
||||
|
||||
So, check your account and folder settings and check if the accounts/folders are connected (see the legend in the navigation menu for the meaning of the icons).
|
||||
Überprüfen Sie also Ihre Konto- und Ordnereinstellungen und überprüfen Sie, ob die Konten/Ordner verbunden sind (siehe die Legende in der Navigation zur Bedeutung der Symbole).
|
||||
|
||||
If there are any error messages, please see [this FAQ](#user-content-faq22).
|
||||
Wenn es irgendwelche Fehlermeldungen gibt, lesen Sie bitte [diese FAQ](#user-content-faq22).
|
||||
|
||||
On some devices, where there are lots of applications competing for memory, Android may stop the synchronization service as a last resort.
|
||||
Auf einigen Geräten, wo es viele Anwendungen gibt, die um Speicher konkurrieren, kann Android den Synchronisierungsdienst als letzte Möglichkeit stoppen.
|
||||
|
||||
Some Android versions stop apps and services too aggressively. See [this dedicated website](https://dontkillmyapp.com/) and [this Android issue](https://issuetracker.google.com/issues/122098785) for more information.
|
||||
Einige Android-Versionen stoppen Apps und Dienste zu aggressiv. Siehe [diese spezielle Webseite](https://dontkillmyapp.com/) und [dieses Android-Problem](https://issuetracker.google.com/issues/122098785) für weitere Informationen.
|
||||
|
||||
Disabling battery optimizations (setup step 4) reduces the chance Android will stop the synchronization service.
|
||||
|
||||
|
|
@ -786,16 +787,16 @@ The preview of the message text cannot be shown if the message body has not been
|
|||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Why are the pro features so expensive?**
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
Die richtige Frage ist: "*Warum gibt es so viele Steuern und Gebühren?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Verwandte Fragen:
|
|||
* Der Bildlauf zu einer intern verknüpften Stelle in Originalnachrichten funktioniert nicht. Dies kann nicht behoben werden, da die Original-Nachrichten-Ansicht in einer Scroll-Ansicht enthalten ist.
|
||||
* Eine Vorschau eines Nachrichtentextes wird auf Samsung-Uhren nicht (immer) angezeigt, weil [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wohl ignoriert wird. Bisher ist nur bekannt, dass Nachrichtenvorschautexte auf den Smart-Armbändern „Pebble 2”, „Fitbit Charge 3” und „Mi Band 3” korrekt angezeigt werden. Siehe auch [diese FAQ](#user-content-faq126).
|
||||
* Ein [Fehler in Android 6.0](https://issuetracker.google.com/issues/37068143) verursacht einen Absturz mit * … Ungültiger Offset: ... Der gültige Bereich ist …* wenn Text ausgewählt ist und außerhalb des ausgewählten Textes angetippt wird. Dieser Fehler wurde in Android 6.0.1 behoben.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Geplante Funktionen
|
||||
|
||||
|
|
@ -126,10 +127,10 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(5) Wie kann ich die Nachrichtenansicht anpassen?](#user-content-faq5)
|
||||
* [(6) Wie kann ich mich bei Gmail / G Suite anmelden?](#user-content-faq6)
|
||||
* [(7) Warum werden gesendete Nachrichten nicht (direkt) im Gesendet-Ordner angezeigt?](#user-content-faq7)
|
||||
* [(8) Kann ich ein Microsoft Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(8) Kann ich ein Microsoft-Exchange-Konto verwenden?](#user-content-faq8)
|
||||
* [(9) Was sind Identitäten / Wie füge ich einen Alias hinzu?](#user-content-faq9)
|
||||
* [~~(11) Warum wird POP nicht unterstützt?~~](#user-content-faq11)
|
||||
* [~~(10) Was bedeutet "UIDPLUS nicht unterstützt"?~~](#user-content-faq10)
|
||||
* [~~(10) Was bedeutet »UIDPLUS nicht unterstützt«?~~](#user-content-faq10)
|
||||
* [(12) Wie funktioniert die Ver- und Entschlüsselung?](#user-content-faq12)
|
||||
* [(13) Wie funktioniert die Suche auf dem Gerät bzw. auf den Servern?](#user-content-faq13)
|
||||
* [(14) Wie kann ich ein Outlook-/Live-/Hotmail-Konto einrichten?](#user-content-faq14)
|
||||
|
|
@ -140,7 +141,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(19) Warum sind die Pro-Funktionen so teuer?](#user-content-faq19)
|
||||
* [(20) Kann ich eine Rückerstattung erhalten?](#user-content-faq20)
|
||||
* [(21) Wie aktiviere ich das Benachrichtigungslicht?](#user-content-faq21)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler ... ?](#user-content-faq22)
|
||||
* [(22) Was bedeutet ein Konto-/Ordnerfehler …?](#user-content-faq22)
|
||||
* [(23) Warum bekomme ich einen Alarm? ?](#user-content-faq23)
|
||||
* [(24) Was bedeutet das Anzeigen / Suchen von Nachrichten auf dem Server?](#user-content-faq24)
|
||||
* [(25) Warum kann ich ein Bild, einen Anhang oder eine Datei nicht auswählen, öffnen oder speichern?](#user-content-faq25)
|
||||
|
|
@ -170,7 +171,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(50) Kann man eine Option hinzufügen, um alle Nachrichten zu synchronisieren?](#user-content-faq50)
|
||||
* [(51) Wie werden die Ordner sortiert?](#user-content-faq51)
|
||||
* [(52) Wieso dauert es so lange Zeit, um sich wieder mit einem Konto zu verbinden?](#user-content-faq52)
|
||||
* [(53) Kann ich die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [(53) Können Sie die Aktionsleiste nach oben/unten verlagern?](#user-content-faq53)
|
||||
* [~~(54) Wie benutze ich ein Namensraumpräfix?~~](#user-content-faq54)
|
||||
* [(55) Wie kann ich alle Nachrichten als gelesen markieren, verschieben oder löschen?](#user-content-faq55)
|
||||
* [(56) Können Sie Unterstützung für JMAP hinzufügen?](#user-content-faq56)
|
||||
|
|
@ -181,15 +182,15 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(61) Warum werden einige Nachrichten verdunkelt angezeigt?](#user-content-faq61)
|
||||
* [(62) Welche Authentifizierungsmethoden werden unterstützt?](#user-content-faq62)
|
||||
* [(63) Wie werden Bilder für die Anzeige auf den Bildschirmen skaliert?](#user-content-faq63)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links/Rechts-Wischen hinzufügen?~~](#user-content-faq64)
|
||||
* [~~(64) Kann man benutzerdefinierte Aktionen zum Links-/Rechtswischen hinzufügen?~~](#user-content-faq64)
|
||||
* [(65) Warum werden einige Anhänge abgedunkelt angezeigt?](#user-content-faq65)
|
||||
* [(66) Gibt es FairMail in der Google Play Familienmediathek?](#user-content-faq66)
|
||||
* [(67) Wie kann ich Konversationen stumm schalten?](#user-content-faq67)
|
||||
* [~~(68) Warum kann Adobe Acrobat Reader keine PDF-Anhänge öffnen / Microsoft-Apps keine angehängten Dokumente öffnen?~~](#user-content-faq68)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben scrollen«?](#user-content-faq69)
|
||||
* [(69) Gibt es eine Option »Bei neuen Nachrichten automatisch nach oben rollen«?](#user-content-faq69)
|
||||
* [(70) Wann werden Nachrichten automatisch erweitert?](#user-content-faq70)
|
||||
* [(71) Wie verwende ich Filterregeln?](#user-content-faq71)
|
||||
* [(72) Was sind Primärkonten/Identitäten?](#user-content-faq72)
|
||||
* [(72) Was sind Hauptkonten/-identitäten?](#user-content-faq72)
|
||||
* [(73) Ist das Verschieben von Nachrichten zwischen verschiedenen Konten sicher/effizient?](#user-content-faq73)
|
||||
* [(74) Wieso sehe ich Nachrichten doppelt?](#user-content-faq74)
|
||||
* [(75) Können Sie eine iOS-, Windows-, Linux- usw. Version erstellen?](#user-content-faq75)
|
||||
|
|
@ -213,7 +214,7 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(94) Was bedeutet der rot-orangefarbene Streifen am Ende des Nachrichtenkopfes?](#user-content-faq94)
|
||||
* [(95) Warum werden nicht alle Apps angezeigt, wenn ein Anhang oder ein Bild ausgewählt wird?](#user-content-faq95)
|
||||
* [(96) Wo finde ich die IMAP- und SMTP-Einstellungen?](#user-content-faq96)
|
||||
* [(97) Was ist "Aufräumen" ?](#user-content-faq97)
|
||||
* [(97) Was ist »Bereinigen« ?](#user-content-faq97)
|
||||
* [(98) Warum kann ich immer noch Kontakte auswählen, nachdem ich Kontaktberechtigungen entzogen habe?](#user-content-faq98)
|
||||
* [(99) Gibt es einen Rich-Text- oder Markdown-Editor?](#user-content-faq99)
|
||||
* [(100) Wie kann ich Google Mail-Kategorien synchronisieren?](#user-content-faq100)
|
||||
|
|
@ -225,57 +226,57 @@ Das Design basiert auf vielen Diskussionen und wenn du möchtest, kannst du auch
|
|||
* [(106) Welche Launcher können die Anzahl der ungelesenen Nachrichten als Plakette anzeigen?](#user-content-faq106)
|
||||
* [(107) Wie verwende ich farbige Sterne?](#user-content-faq107)
|
||||
* [(108) Kann man Nachrichten aus beliebigen Ordnern dauerhaft löschen?](#user-content-faq108)
|
||||
* [~~(109) Warum ist 'Konto auswählen' nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [~~(109) Warum ist »Konto auswählen« nur in offiziellen Versionen verfügbar?~~](#user-content-faq109)
|
||||
* [(110) Warum sind (einige) Nachrichten leer und/oder Anhänge beschädigt?](#user-content-faq110)
|
||||
* [(111) Wird OAuth unterstützt?](#user-content-faq111)
|
||||
* [(112) Welchen E-Mail-Provider empfehlen Sie?](#user-content-faq112)
|
||||
* [(113) Wie funktioniert die biometrische Authentifizierung?](#user-content-faq113)
|
||||
* [(114) Kann man die Einstellungen anderer E-Mail-Apps importieren?](#user-content-faq114)
|
||||
* [(115) Können E-Mail-Adressen-Chips hinzufügt werden?](#user-content-faq115)
|
||||
* [(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen?~](#user-content-faq116)
|
||||
* [~~(116) Wie kann ich Bilder in Nachrichten von vertrauenswürdigen Absendern standardmäßig anzeigen? ~~](#user-content-faq116)
|
||||
* [Können Sie mir helfen, meinen Kauf wiederherzustellen?](#user-content-faq117)
|
||||
* [(118) Was bedeutet »Nachverfolgungsparameter entfernen« genau?](#user-content-faq118)
|
||||
* [(119) Können Sie dem Sammeleingang-Widget für Post Farben hinzufügen?](#user-content-faq119)
|
||||
* [~~(119) Können Sie Farben dem Sammeleingangs-Widget hinzufügen?~~](#user-content-faq119)
|
||||
* [(120) Warum werden neue Nachrichten beim Öffnen der App nicht entfernt?](#user-content-faq120)
|
||||
* [(121) Wie werden Nachrichten zu einer Konversation gruppiert?](#user-content-faq121)
|
||||
* [~~(122) Warum wird Empfängername/E-Mail-Adresse mit einer Warnfarbe angezeigt?~~](#user-content-faq122)
|
||||
* [(123) Was geschieht, wenn FairEmail keine Verbindung zu einem E-Mail-Server herstellen kann?](#user-content-faq123)
|
||||
* [(124) Warum erhalte ich den Hinweis 'Nachricht zu groß oder zu komplex, um sie anzuzeigen'?](#user-content-faq124)
|
||||
* [(124) Warum erhalte ich den Hinweis »Nachricht zu groß oder zu komplex, um sie anzuzeigen«?](#user-content-faq124)
|
||||
* [(125) Was sind die aktuellen experimentellen Eigenschaften?](#user-content-faq125)
|
||||
* [(126) Können Nachrichtenvorschauen an mein Wearable gesendet werden?](#user-content-faq126)
|
||||
* [(127) Wie kann ich den Fehler 'Syntaktisch ungültige HELO-Argumente(n)' beheben?](#user-content-faq127)
|
||||
* [(127) Wie kann ich den Fehler »Syntaktisch ungültige HELO-Argumente« beheben?](#user-content-faq127)
|
||||
* [(128) Wie kann ich die gestellten Fragen zurücksetzen, zum Beispiel um Bilder zu zeigen?](#user-content-faq128)
|
||||
* [(129) Wird ProtonMail, Tutanota unterstützt?](#user-content-faq129)
|
||||
* [(130) Was bedeutet die Meldung 'Fehler ...'?](#user-content-faq130)
|
||||
* [(130) Was bedeutet die Meldung »Fehler …«?](#user-content-faq130)
|
||||
* [(131) Kann man die Richtung für das Wischen für vorherige/nächste Nachricht ändern?](#user-content-faq131)
|
||||
* [(132) Warum sind Benachrichtigungen für neue Nachrichten stumm?](#user-content-faq132)
|
||||
* [(133) Warum wird ActiveSync nicht unterstützt?](#user-content-faq133)
|
||||
* [(134) Wie kann ich Nachrichten nur in der App löschen?](#user-content-faq134)
|
||||
* [(135) Warum werden gelöschte Nachrichten oder Entwürfe in Konversationen angezeigt?](#user-content-faq135)
|
||||
* [(136) Wie kann ich ein Konto/Identität/Ordner löschen?](#user-content-faq136)
|
||||
* [(137) Wie kann ich 'Nicht erneut fragen' zurücksetzen?](#user-content-faq137)
|
||||
* [(137) Wie kann ich »Nicht erneut fragen« zurücksetzen?](#user-content-faq137)
|
||||
* [(138) Gibt es die Funktionen Kalender/Kontaktmanagement/Synchronisation?](#user-content-faq138)
|
||||
* [(139) Wie behebe ich 'Benutzer ist angemeldet, aber nicht verbunden'?](#user-content-faq139)
|
||||
* [(139) Wie behebe ich »Benutzer ist angemeldet, aber nicht verbunden«?](#user-content-faq139)
|
||||
* [(140) Warum enthält der Nachrichtentext seltsame Zeichen?](#user-content-faq140)
|
||||
* [(141) Wie kann ich 'Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden' beheben?](#user-content-faq141)
|
||||
* [(141) Wie kann ich »Ein Entwürfe-Ordner ist erforderlich, um Nachrichten zu senden« beheben?](#user-content-faq141)
|
||||
* [(142) Wie kann ich gesendete Nachrichten im Posteingang speichern?](#user-content-faq142)
|
||||
* [~~(143) Gibt es einen Papierkorb für POP3-Konten? ~~](#user-content-faq143)
|
||||
* [(144) Wie kann ich Sprachnotizen aufnehmen?](#user-content-faq144)
|
||||
* [(145) Wie kann ich einen Benachrichtigungston für ein Konto, einen Ordner oder einen Absender festlegen?](#user-content-faq145)
|
||||
* [(146) Wie kann ich falsche Zeiten von Nachrichten beheben?](#user-content-faq146)
|
||||
* [(147) Was sollte ich über Drittanbieter-Versionen wissen?](#user-content-faq147)
|
||||
* [(148) Wie kann ich ein Apple iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(148) Wie kann ich ein Apple-iCloud-Konto verwenden?](#user-content-faq148)
|
||||
* [(149) Wie funktioniert das Widget für ungelesene Nachrichten?](#user-content-faq149)
|
||||
* [(150) Gibt es eine Möglichkeit zum Ablehnen von Kalendereinladungen?](#user-content-faq150)
|
||||
* [(151) Gibt es eine Datensicherung/Wiederherstellung von Nachrichten?](#user-content-faq151)
|
||||
* [(152) Wie kann ich eine Kontaktgruppe einfügen?](#user-content-faq152)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Google Mail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [(153) Warum funktioniert das dauerhafte Löschen von Gmail-Nachrichten nicht?](#user-content-faq153)
|
||||
* [~~(154) Kann man Favicons als Kontaktfotos verwenden?~~](#user-content-faq154)
|
||||
* [(155) Was ist eine winmail.dat-Datei?](#user-content-faq155)
|
||||
* [(156) Wie kann ich ein Office365-Konto einrichten?](#user-content-faq156)
|
||||
* [(157) Wie kann ich ein Free.fr-Konto einrichten?](#user-content-faq157)
|
||||
* [(158) Welche/r Kamera/Audiorekorder ist empfehlenswert?](#user-content-faq158)
|
||||
* [(159) Was sind Disconnect Trackingschutz-Listen?](#user-content-faq159)
|
||||
* [(159) Was sind Disconnects Tracker-Schutzlisten?](#user-content-faq159)
|
||||
|
||||
[Ich habe eine weitere Frage.](#user-content-support)
|
||||
|
||||
|
|
@ -747,9 +748,9 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
|
|||
<br />
|
||||
|
||||
<a name="faq16"></a>
|
||||
**(16) Why are messages not being synchronized?**
|
||||
**(16) Warum werden Nachrichten nicht synchronisiert?**
|
||||
|
||||
Possible causes of messages not being synchronized (sent or received) are:
|
||||
Mögliche Ursachen dafür, dass Nachrichten nicht synchronisiert (gesendet oder empfangen) werden, sind:
|
||||
|
||||
* Konto oder Ordner(e) sind nicht zum Synchronisieren gesetzt
|
||||
* Die Anzahl der Tage, für die die Nachricht synchronisiert werden soll, ist zu niedrig gesetzt
|
||||
|
|
@ -757,13 +758,13 @@ Possible causes of messages not being synchronized (sent or received) are:
|
|||
* Der E-Mail-Server ist vorübergehend nicht verfügbar
|
||||
* Android hat die Synchronisation gestoppt
|
||||
|
||||
So, check your account and folder settings and check if the accounts/folders are connected (see the legend in the navigation menu for the meaning of the icons).
|
||||
Überprüfen Sie also Ihre Konto- und Ordnereinstellungen und überprüfen Sie, ob die Konten/Ordner verbunden sind (siehe die Legende in der Navigation zur Bedeutung der Symbole).
|
||||
|
||||
If there are any error messages, please see [this FAQ](#user-content-faq22).
|
||||
Wenn es irgendwelche Fehlermeldungen gibt, lesen Sie bitte [diese FAQ](#user-content-faq22).
|
||||
|
||||
On some devices, where there are lots of applications competing for memory, Android may stop the synchronization service as a last resort.
|
||||
Auf einigen Geräten, wo es viele Anwendungen gibt, die um Speicher konkurrieren, kann Android den Synchronisierungsdienst als letzte Möglichkeit stoppen.
|
||||
|
||||
Some Android versions stop apps and services too aggressively. See [this dedicated website](https://dontkillmyapp.com/) and [this Android issue](https://issuetracker.google.com/issues/122098785) for more information.
|
||||
Einige Android-Versionen stoppen Apps und Dienste zu aggressiv. Siehe [diese spezielle Webseite](https://dontkillmyapp.com/) und [dieses Android-Problem](https://issuetracker.google.com/issues/122098785) für weitere Informationen.
|
||||
|
||||
Disabling battery optimizations (setup step 4) reduces the chance Android will stop the synchronization service.
|
||||
|
||||
|
|
@ -786,16 +787,16 @@ The preview of the message text cannot be shown if the message body has not been
|
|||
<br />
|
||||
|
||||
<a name="faq19"></a>
|
||||
**(19) Why are the pro features so expensive?**
|
||||
**(19) Warum sind die Pro-Funktionen so teuer?**
|
||||
|
||||
The right question is "*why are there so many taxes and fees?*":
|
||||
Die richtige Frage ist: "*Warum gibt es so viele Steuern und Gebühren?*":
|
||||
|
||||
* MwSt.: 25 % (je nach Land)
|
||||
* Google-Gebühr: 30 %
|
||||
* Einkommenssteuer: 50 %
|
||||
* <sub>PayPal-Gebühr: 5-10 % abhängig vom Land/Betrag</sub>
|
||||
|
||||
So, what is left for the developer is just a fraction of what you pay.
|
||||
Was also für den Entwickler übrig bleibt, ist nur ein Bruchteil dessen, was Sie bezahlen.
|
||||
|
||||
Note that only some convenience and advanced features need to be purchased which means that FairEmail is basically free to use.
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Preguntas relacionadas:
|
|||
* Desplazar a una ubicación vinculada internamente en mensajes originales no funciona. Esto no se puede arreglar porque la vista original del mensaje está contenida en una vista de desplazamiento.
|
||||
* La vista previa del texto de los mensajes no aparece (siempre) en los relojes de Samsung porque [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) parece ser ignorado. El texto de vista previa de los mensajes se muestra correctamente en Pebble 2, Fitbit Charge 3 y Mi band 3. Ver también [estas Preguntas Frecuentes](#user-content-faq126).
|
||||
* Un [error en Android 6.0](https://issuetracker.google.com/issues/37068143) causa un error con *... Offset inválido: ... El rango válido es ...* cuando el texto está seleccionado y se toca fuera del texto seleccionado. Este error ha sido corregido en Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Características planificadas
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Please see [here](#user-content-faq22) for common error messages and solutions.
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## ویژگیهای برنامهریزی شده
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Aiheeseen liittyvät kysymykset:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Suunnitellut ominaisuudet
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Questions connexes :
|
|||
* Le défilement vers un emplacement lié en interne dans les messages originaux ne fonctionne pas. Ceci ne peut pas être corrigé car la vue du message d'origine est contenue dans une vue déroulante.
|
||||
* Un aperçu d'un message texte n'apparaît pas (toujours) sur les montres Samsung car [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) semble être ignoré. Les textes de prévisualisation du message sont connus pour être affichés correctement sur Pebble 2, Fitbit Charge 3 et Mi band 3. Voir aussi [cette FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Les liens internes (ancrés) ne fonctionneront pas parce que les messages originaux sont affichés dans une WebView intégrée dans une vue défilante (la liste des conversations). Il s'agit d'une limitation Android qui ne peut être ni réparée ni contournée.
|
||||
|
||||
## Fonctionnalités prévues
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Questions connexes :
|
|||
* Le défilement vers un emplacement lié en interne dans les messages originaux ne fonctionne pas. Ceci ne peut pas être corrigé car la vue du message d'origine est contenue dans une vue déroulante.
|
||||
* Un aperçu d'un message texte n'apparaît pas (toujours) sur les montres Samsung car [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) semble être ignoré. Les textes de prévisualisation du message sont connus pour être affichés correctement sur Pebble 2, Fitbit Charge 3 et Mi band 3. Voir aussi [cette FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Fonctionnalités prévues
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Preguntas relacionadas:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Kapcsolódó kérdések:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Tervezett funkciók
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,8 @@ Domande correlate:
|
|||
* ~~La crittografia con YubiKey risulta in un ciclo infinito. Ciò sembra essere causato da un [errore in OpenKeychain](https://github.com/open-keychain/open-keychain/issues/2507).~~
|
||||
* Lo scorrimento verso una posizione collegata internamente nei messaggi originali non funziona. Ciò non può essere risolto perché la vista originale dei messaggi è contenuta in una vista a scorrimento.
|
||||
* Un'anteprima di un testo di un messaggio non (sempre) appare negli orologi Samsung perché [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) sembra venga ignorato. Le anteprime dei messaggi sono note per essere visualizzate correttamente su Pebble 2, Fitbit Charge 3 e Mi band 3. Vedi anche [queste domande frequenti](#user-content-faq126).
|
||||
* Un [errore in Android](https://issuetracker.google.com/issues/37068143) a volte provoca un crash con *... Spostamento non valido: ... L'intervallo valido è ... quando il testo è selezionato e tocca all'esterno del testo selezionato. Questo bug è stato risolto in Android 6.0.1.</li> </ul>
|
||||
* Un [errore in Android](https://issuetracker.google.com/issues/37068143) a volte provoca un crash con *... Spostamento non valido: ... L'intervallo valido è ... quando il testo è selezionato e tocca all'esterno del testo selezionato. Questo bug è stato risolto in Android 6.0.1.</li>
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.</ul>
|
||||
|
||||
## Funzionalità pianificate
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Gerelateerde vragen:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Geplande functies
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Relaterte spørsmål:
|
|||
* Å rulle til et internt koblet sted i originale meldinger fungerer ikke. Dette kan ikke løses fordi den opprinnelige meldingsvisningen finnes i en rullende visning.
|
||||
* En forhåndsvisning av en meldingstekst vises ikke (alltid) på Samsung-klokker fordi [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) ser ut til å bli ignorert. Det er kjent at forhåndsvisningstekster for meldinger vises riktig på Pebble 2, Fitbit Charge 3 og Mi band 3 wearables. Se også [denne vanlige FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planlagte funksjoner
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Relaterte spørsmål:
|
|||
* Å rulle til et internt koblet sted i originale meldinger fungerer ikke. Dette kan ikke løses fordi den opprinnelige meldingsvisningen finnes i en rullende visning.
|
||||
* En forhåndsvisning av en meldingstekst vises ikke (alltid) på Samsung-klokker fordi [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) ser ut til å bli ignorert. Det er kjent at forhåndsvisningstekster for meldinger vises riktig på Pebble 2, Fitbit Charge 3 og Mi band 3 wearables. Se også [denne vanlige FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planlagte funksjoner
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Powiązane pytania:
|
|||
* Przewijanie do wewnętrznie połączonej lokalizacji w oryginalnych wiadomościach nie działa. Nie można tego naprawić, ponieważ oryginalny widok wiadomości znajduje się w przewijanym widoku.
|
||||
* Podgląd tekstu wiadomości nie (zawsze) pojawia się na zegarku Samsung, ponieważ [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) wydaje się być ignorowany. Wiadomo, że teksty podglądu wiadomości są wyświetlane poprawnie na Pebble 2, Fitbit Charge 3 i Mi band 3. Zobacz również [ten FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planowane funkcje
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Perguntas relacionadas:
|
|||
* Rolar para um local com link interno nas mensagens originais não funciona. Não é possível corrigir porque a visualização de mensagem original é limitada na visualização de rolagem.
|
||||
* A pré-visualização do texto de uma mensagem não aparece (sempre) nos relógios Samsung porque [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) parece ser ignorado. É sabido que a pré-visualização do texto de mensagens é exibida corretamente nos relógios Pebble 2, Fitbit Charge 3, e Mi band 3. Veja também [ esse FAQ](#user-content-faq126).
|
||||
* Um [problema no Android 6.0](https://issuetracker.google.com/issues/37068143) às vezes causa um travamento com a mensagem *... Invalid offset: ... Valid range is ...* ao selecionar o texto e depois tocar fora do texto selecionado. Esse erro foi corrigido no Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Funcionalidades planejadas
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@
|
|||
* Прокрутка к внутренне привязанному местоположению в оригинальных сообщениях не работает. Это не может быть исправлено, потому что исходный вид сообщения содержится в прокрутке.
|
||||
* Предпросмотр текста сообщения (всегда) не отображается на Samsung watch, потому что [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)), похоже, игнорируется. Известно, что текст предварительного просмотра сообщений правильно отображаются на экране Pebble 2, Fitbit Charge 3 и Mi band 3. См. также [этот FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Запланированные возможности
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# FairEmail support
|
||||
# FairEmail Support
|
||||
|
||||
Om du har en fråga, vänligen kontrollera de vanliga frågorna nedan först. Längst ner kan du ta reda på hur du ställer andra frågor, begär funktioner och rapporterar buggar.
|
||||
Om du har en fråga, vänligen kontrollera de vanligaste ställda frågorna först. Längst ner kan du ta reda på hur du ställer andra frågor, begär funktioner och rapporterar buggar.
|
||||
|
||||
## Index
|
||||
|
||||
|
|
@ -77,6 +77,7 @@ Relaterade frågor:
|
|||
* Att bläddra till en internt länkad plats i originalmeddelanden fungerar inte. Detta kan inte rättas till eftersom den ursprungliga meddelandevyn finns i en rullande vy.
|
||||
* En förhandsvisning av ett meddelande visas inte (alltid) på Samsung klockor eftersom [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) verkar ignoreras. Meddelanden är kända för att visas korrekt på Pebble 2, Fitbit Charge 3 och Mi band 3 wearables. Se även [denna FAQ](#user-content-faq126).
|
||||
* En [bugg i Android 6.0](https://issuetracker.google.com/issues/37068143) orsakar en krasch med *... Ogiltig offset: ... Giltigt intervall är ...* när text är markerad och knackar utanför den valda texten. Detta fel har rättats i Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planerade funktioner
|
||||
|
||||
|
|
@ -231,7 +232,7 @@ Designen bygger på många diskussioner och om du vill kan du diskutera det [i d
|
|||
* [(112) Vilken e-postleverantör rekommenderar du?](#user-content-faq112)
|
||||
* [(113) Hur fungerar biometrisk autentisering?](#user-content-faq113)
|
||||
* [(114) Kan du lägga till en import för inställningarna för andra e-postappar?](#user-content-faq114)
|
||||
* [(115) Can you add email address chips?](#user-content-faq115)
|
||||
* [(115) Kan du lägga till e-postadresschips?](#user-content-faq115)
|
||||
* [~~(116) Hur kan jag visa bilder i meddelanden från betrodda avsändare som standard?~~](#user-content-faq116)
|
||||
* [(117) Kan du hjälpa mig att återställa mitt köp?](#user-content-faq117)
|
||||
* [(118) Vad gör "Ta bort spårningsparametrar" exakt?](#user-content-faq118)
|
||||
|
|
@ -272,7 +273,7 @@ Designen bygger på många diskussioner och om du vill kan du diskutera det [i d
|
|||
* [(153) Varför fungerar inte det att permanent radera Gmail-meddelandet?](#user-content-faq153)
|
||||
* [~~(154) Kan du lägga till favicons som kontaktbilder?~~](#user-content-faq154)
|
||||
* [(155) Vad är en winmail.dat fil?](#user-content-faq155)
|
||||
* [(156) How can I set up an Office 365 account?](#user-content-faq156)
|
||||
* [(156) Hur kan jag ställa in ett Office 365-konto?](#user-content-faq156)
|
||||
* [(157) Hur kan jag sätta upp ett Free.fr-konto?](#user-content-faq157)
|
||||
* [(158) Vilken kamera / ljudinspelare rekommenderar du?](#user-content-faq158)
|
||||
* [(159) Vad är Disconnect's spårningsskyddslistor?](#user-content-faq159)
|
||||
|
|
@ -291,11 +292,11 @@ Följande Android-behörigheter behövs:
|
|||
* *förhindra enheten från att sova* (WAKE_LOCK): för att hålla enheten vaken vid synkronisering av meddelanden
|
||||
* *i-app fakturering* (BILLING): för att tillåta i-app köp
|
||||
* Valfritt: *läs dina kontakter* (READ_CONTACTS): för att automatiskt fylla på adresser och för att visa foton
|
||||
* Optional: *read the contents of your SD card* (READ_EXTERNAL_STORAGE): to accept files from other, outdated apps, see also [this FAQ](#user-content-faq49)
|
||||
* Optional: *use fingerprint hardware* (USE_FINGERPRINT) and use *biometric hardware* (USE_BIOMETRIC): to use biometric authentication
|
||||
* Optional: *find accounts on the device* (GET_ACCOUNTS): to select an account when using the Gmail quick setup
|
||||
* Android 5.1 Lollipop and before: *use accounts on the device* (USE_CREDENTIALS): to select an account when using the Gmail quick setup (not requested on later Android versions)
|
||||
* Android 5.1 Lollipop and before: *Read profile* (READ_PROFILE): to read your name when using the Gmail quick setup (not requested on later Android versions)
|
||||
* Valfritt: *läs innehållet på ditt SD-kort* (READ_EXTERNAL_STORAGE): för att acceptera filer från andra, ej uppdaterade appar, se även [denna FAQ](#user-content-faq49)
|
||||
* Valfritt: *använd maskinvara för fingeravtryck* (USE_FINGERPRINT) och använd *biometrisk hårdvara* (USE_BIOMETRIC): för att använda biometrisk autentisering
|
||||
* Valfritt: *hitta konton på enheten* (GET_ACCOUNTS): för att välja ett konto när du använder Gmail snabbinställning
|
||||
* Android 5. Lollipop och tidigare: *använda konton på enheten* (USE_CREDENTIALS): för att välja ett konto när du använder Gmail snabbinställning (inte begärt på senare Android-versioner)
|
||||
* Android 5. Lollipop och tidigare: *Läs profil* (READ_PROFILE): för att läsa ditt namn när du använder Gmail snabbinställning (inte begärt på senare Android-versioner)
|
||||
|
||||
[Valfria behörigheter](https://developer.android.com/training/permissions/requesting) stöds endast på Android 6 Marshmallow och senare. På tidigare Android-versioner kommer du att bli ombedd att bevilja de valfria behörigheterna vid installation av FairEmail.
|
||||
|
||||
|
|
@ -318,23 +319,23 @@ Följande behörigheter behövs för att visa antalet olästa meddelanden som et
|
|||
* *me.everything.badger.permission.BADGE_COUNT_READ*
|
||||
* *me.everything.badger.permission.BADGE_COUNT_WRITE*
|
||||
|
||||
FairEmail will keep a list of addresses you receive messages from and send messages to and will use this list for contact suggestions when no contacts permissions is granted to FairEmail. This means you can use FairEmail without the Android contacts provider (address book). Note that you can still pick contacts without granting contacts permissions to FairEmail, only suggesting contacts won't work without contacts permissions.
|
||||
FairEmail kommer att skapa en lista över adresser som du tar emot meddelanden från och skickar meddelanden till och kommer att använda denna lista för kontaktförslag när inga kontaktbehörigheter beviljas till FairEmail. Detta innebär att du kan använda FairEmail utan tillgång till Android-kontakter (adressbok). Observera att du fortfarande kan välja kontakter utan att ge FairEmail tillåtelse att läsa kontakter, endast föreslå kontakter fungerar inte utan behörigheter för kontakter.
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq2"></a>
|
||||
**(2) Varför visas en permanent avisering?**
|
||||
|
||||
A low priority permanent status bar notification with the number of accounts being monitored and the number of operations pending (see the next question) is shown to prevent Android from killing the service that takes care of continuous receiving email. This was [already necessary](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), but with the introduction of [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) in Android 6 Marshmallow this is more than ever necessary. Doze mode will stop all apps when the screen is off for some time, unless the app did start a foreground service, which requires showing a status bar notification.
|
||||
En avisering med låg prioritet permanent statusfält med antalet konton som övervakas och antalet pågående åtgärder (se nästa fråga) visas för att förhindra Android från att döda tjänsten som tar hand om kontinuerligt mottagande e-post. Detta var [redan nödvändigt](https://developer.android.com/reference/android/app/Service.html#startForeground(int,%20android.app.Notification)), men med införandet av [doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) i Android 6 Marshmallow är detta mer än någonsin nödvändigt. Doze mode kommer att stoppa alla appar när skärmen är avstängd under en tid, om inte appen startade en förgrundstjänst, vilket kräver att en statusfältsnotis visas.
|
||||
|
||||
Most, if not all, other email apps don't show a notification with the "side effect" that new messages are often not or late being reported and that messages are not or late being sent.
|
||||
De flesta, om inte alla, andra e-postappar visar inte en avisering med "sidoeffekter" att nya meddelanden ofta inte eller är sena att rapporteras och att meddelanden inte eller är sena att skickas.
|
||||
|
||||
Android shows icons of high priority status bar notifications first and will hide the icon of FairEmail's notification if there is no space to show icons anymore. In practice this means that the status bar notification doesn't take space in the status bar, unless there is space available.
|
||||
Android visar ikoner med hög prioritet statusfältet meddelanden först och kommer att dölja ikonen för FairEmail's aviseringar om det inte finns något utrymme att visa ikoner längre. I praktiken innebär detta att aviseringen i statusfältet inte tar plats i statusfältet, om det inte finns utrymme tillgängligt.
|
||||
|
||||
The status bar notification can be disabled via the notification settings of FairEmail:
|
||||
Aviseringen i statusfältet kan inaktiveras via inställningarna för FairEmail:
|
||||
|
||||
* Android 8 Oreo and later: tap the *Receive channel* button and disable the channel via the Android settings (this won't disable new message notifications)
|
||||
* Android 7 Nougat and before: enabled *Use background service to synchronize messages*, but be sure to read the remark below the setting
|
||||
* Android 8 Oreo och senare: tryck på *Receive channel* -knappen och inaktivera kanalen via Android-inställningarna (detta kommer inte att inaktivera nya meddelanden)
|
||||
* Android 7 Nougat och tidigare: aktiverat *Använd bakgrundstjänst för att synkronisera meddelanden*, men se till att läsa anmärkningen under inställningen
|
||||
|
||||
You can switch to periodically synchronization of messages in the receive settings to remove the notification, but be aware that this might use more battery power. See [here](#user-content-faq39) for more details about battery usage.
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Sıkça rastlanan hata iletileri ve çözümleri için [burayı](#user-content-f
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planlanan özellikler
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## 计划添加的功能
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,7 @@ Related questions:
|
|||
* Scrolling to an internally linked location in original messages does not work. This can't be fixed because the original message view is contained in a scrolling view.
|
||||
* A preview of a message text doesn't (always) appear on Samsung watches because [setLocalOnly](https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder.html#setLocalOnly(boolean)) seem to be ignored. Message preview texts are known to be displayed correctly on Pebble 2, Fitbit Charge 3, and Mi band 3 wearables. See also [this FAQ](#user-content-faq126).
|
||||
* A [bug in Android 6.0](https://issuetracker.google.com/issues/37068143) causes a crash with *... Invalid offset: ... Valid range is ...* when text is selected and tapping outside of the selected text. This bug has been fixed in Android 6.0.1.
|
||||
* Internal (anchor) links will not work because original messages are shown in an embedded WebView in a scrolling view (the conversation list). This is an Android limitation which cannot be fixed or worked around.
|
||||
|
||||
## Planned features
|
||||
|
||||
|
|
@ -1213,7 +1214,7 @@ The error '*Handshake failed ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either c
|
|||
|
||||
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
|
||||
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
|
||||
|
||||
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue