mirror of https://github.com/M66B/FairEmail.git
Crowdin sync
This commit is contained in:
M66B
parent
c21e17e9ed
commit
6778a970d7
|
|
@ -1,7 +1,7 @@
|
|||
apply plugin: 'com.android.application'
|
||||
apply plugin: 'com.bugsnag.android.gradle'
|
||||
|
||||
def getVersionCode = { -> return 1492 }
|
||||
def getVersionCode = { -> return 1493 }
|
||||
def getReleaseName = { -> return "\"Kaatedocus\"" }
|
||||
// https://en.wikipedia.org/wiki/List_of_dinosaur_genera
|
||||
|
||||
|
|
|
|||
|
|
@ -567,7 +567,6 @@
|
|||
<string name="title_duplicate_in">Дублиращо съобщение в %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Бутони</string>
|
||||
<string name="title_seen">Отбелязвам като прочетено</string>
|
||||
<string name="title_unseen">Отбелязвам като непрочетено</string>
|
||||
<string name="title_hide">Скриване</string>
|
||||
|
|
|
|||
|
|
@ -5,13 +5,17 @@
|
|||
<string name="app_welcome">FairEmail és una aplicació de correu electrònic de codi obert centrada en la privadesa i la seguretat. Per aquesta raó, algunes funcions poden funcionar de manera diferent a la que estàs acostumat.</string>
|
||||
<string name="app_crash">FairMail no és compatible en aquest dispositiu perquè els errors a Android causen bloqueigs</string>
|
||||
<string name="app_exit">Premeu «Enrere» novament per sortir</string>
|
||||
<string name="app_cake">Espai d’emmagatzematge insuficient</string>
|
||||
<string name="channel_service">Rebre</string>
|
||||
<string name="channel_send">Enviar</string>
|
||||
<string name="channel_notification">Correu electrònic</string>
|
||||
<string name="channel_update">Actualitzacions</string>
|
||||
<string name="channel_warning">Advertències</string>
|
||||
<string name="channel_error">Errors</string>
|
||||
<string name="channel_alert">Alertes de servidor</string>
|
||||
<string name="channel_group_contacts">Contactes</string>
|
||||
<string name="channel_send_description">Enviant missatges</string>
|
||||
<string name="channel_notification_description">Nova notificació de missatge</string>
|
||||
<plurals name="page_conversation">
|
||||
<item quantity="one">Conversa</item>
|
||||
<item quantity="other">Conversa</item>
|
||||
|
|
@ -66,6 +70,7 @@
|
|||
<string name="title_block_domain">Bloquejar el domini complet del remitent</string>
|
||||
<string name="title_block_sender_hint">Si bloqueges un remitent, es crearà una regla per traslladar automàticament els missatges futurs a la carpeta de correu brossa.
|
||||
La creació i l\'ús de regles és una característica professional. </string>
|
||||
<string name="title_junk_filter">Utilitza el filtre local d\'SPAM</string>
|
||||
<string name="title_notification_sending">Enviant missatge</string>
|
||||
<string name="title_notification_waiting">S\'està esperant la connexió</string>
|
||||
<string name="title_notification_idle">Inactiu</string>
|
||||
|
|
@ -91,7 +96,8 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="menu_rate">Puntua l\'aplicació</string>
|
||||
<string name="title_welcome">Benvingut/da</string>
|
||||
<string name="title_eula">Contracte de Llicència d’usuari final</string>
|
||||
<string name="title_agree">D’acordo https://accounts.crowdin.com/password/reset https://accounts.crowdin.com/password/reset</string>
|
||||
<string name="title_contributors">Contribuïdors</string>
|
||||
<string name="title_agree">D’acord</string>
|
||||
<string name="title_disagree">No hi estic d\'acord</string>
|
||||
<string name="title_version">Versió %1$s</string>
|
||||
<string name="title_list_accounts">Comptes</string>
|
||||
|
|
@ -102,11 +108,17 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_setup">Preferències</string>
|
||||
<string name="title_setup_help">Ajuda</string>
|
||||
<string name="title_setup_quick">Configuració ràpida</string>
|
||||
<string name="title_setup_quick_accounts">Afegir comptes</string>
|
||||
<string name="title_setup_quick_hint">La configuració ràpida aconseguirà informació de configuració a autoconfig.thunderbird.net</string>
|
||||
<string name="title_setup_quick_imap">Servidor IMAP per rebre missatges</string>
|
||||
<string name="title_setup_quick_smtp">Servidor SMTP per enviar missatges</string>
|
||||
<string name="title_setup_wizard">Assistent</string>
|
||||
<string name="title_setup_account_remark">Rebre correu electrònic</string>
|
||||
<string name="title_setup_identity_remark">Enviar un correu electrònic</string>
|
||||
<string name="title_setup_accounts">Comptes</string>
|
||||
<string name="title_setup_identities">Identitats</string>
|
||||
<string name="title_setup_other">Altres proveïdors</string>
|
||||
<string name="title_setup_pop3">Compte POP3</string>
|
||||
<string name="title_setup_gmail_support">Com que Android comprova les firmes dels aplicatius, es podran autoritzar comptes de Google des des les versions oficials</string>
|
||||
<string name="title_setup_gmail_rationale">Doneu permís per seleccionar un compte i llegir el vostre nom</string>
|
||||
<string name="title_setup_gmail_permissions">Google sol·licitarà permisos per llegir, compondre, enviar i suprimir tot el vostre correu electrònic. FairEmail mai suprimirà els vostres missatges sense el vostre consentiment explícit.</string>
|
||||
|
|
@ -119,22 +131,26 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_setup_no_settings">No s\'ha trobat cap configuració pel domini \'%1$s\'</string>
|
||||
<string name="title_setup_no_auth_hint">Comproveu la vostra adreça de correu electrònic i la contrasenya i assegureu-vos que l’accés extern (IMAP/SMTP) estigui habilitat per al vostre compte</string>
|
||||
<string name="title_setup_app_password_hint">Aquest proveïdor necessita una contrasenya de l’aplicació en lloc de la contrasenya del compte, consulteu les instruccions del proveïdor</string>
|
||||
<string name="title_setup_no_inbox">No s\'ha trobat la bustia</string>
|
||||
<string name="title_setup_manage">Gestiona</string>
|
||||
<string name="title_setup_grant">Permet</string>
|
||||
<string name="title_setup_grant_again">Concedeix els permisos requerits</string>
|
||||
<string name="title_setup_identity_what">Què és una identitat?</string>
|
||||
<string name="title_setup_permissions">Concedeix permisos</string>
|
||||
<string name="title_setup_permissions_remark">Per accedir informació de contacte (opcional)</string>
|
||||
<string name="title_setup_doze">Inhabilita les optimitzacions de bateria</string>
|
||||
<string name="title_setup_doze_instructions">En el següent diàleg, selecciona \"totes les apps\" a dalt, selecciona aquesta aplicació i polsa i confirma «no optimitzis la bateria»</string>
|
||||
<string name="title_setup_doze_battery">Ús de bateria elevat?</string>
|
||||
<string name="title_setup_doze_stopped">S\'ha aturat la sincronització?</string>
|
||||
<string name="title_setup_data">L\'estalvi de dades està activat</string>
|
||||
<string name="title_setup_advanced_options">Mostra les opcions avançades</string>
|
||||
<string name="title_setup_inbox">Vés a la Safata d\'Entrada</string>
|
||||
<string name="title_setup_go">Vés-hi</string>
|
||||
<string name="title_setup_to_do">Per fer</string>
|
||||
<string name="title_setup_done">Fet</string>
|
||||
<string name="title_setup_still">Encara queda per fer</string>
|
||||
<string name="title_setup_error">Error</string>
|
||||
<string name="title_setup_configuring">Configurant compte …</string>
|
||||
<string name="title_setup_export">Exporta la configuració</string>
|
||||
<string name="title_setup_import">Importa una configuració</string>
|
||||
<string name="title_setup_import_do">Els comptes importats s’afegiran sense sobreescriure els ja existents</string>
|
||||
|
|
@ -161,16 +177,20 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_setup_theme_red_green">Vermell/verd</string>
|
||||
<string name="title_setup_theme_grey">Gris</string>
|
||||
<string name="title_setup_theme_black">Negre</string>
|
||||
<string name="title_setup_theme_black_and_white">Negre i blanc</string>
|
||||
<string name="title_setup_theme_reverse">Intercanvia colors</string>
|
||||
<string name="title_setup_theme_light">Clar</string>
|
||||
<string name="title_setup_theme_dark">Fosc</string>
|
||||
<string name="title_setup_theme_system">Segueix el sistema</string>
|
||||
<string name="title_setup_theme_black_background">Fons negre</string>
|
||||
<string name="title_setup_theme_system_hint">Això canviarà automàticament a un tema clar/fosc en mode dia/nit, si és compatible amb Android</string>
|
||||
<string name="title_setup_theme_more_colors">Vull més colors</string>
|
||||
<string name="title_setup_advanced">Avançat</string>
|
||||
<string name="title_setup_options">Opcions</string>
|
||||
<string name="title_setup_defaults">Restaura els valors per defecte</string>
|
||||
<string name="title_setup_reset_questions">Restableix les preguntes</string>
|
||||
<string name="title_advanced_hint_title">Més opcions avançades</string>
|
||||
<string name="title_advanced_section_main">Començar</string>
|
||||
<string name="title_advanced_section_synchronize">Rebre</string>
|
||||
<string name="title_advanced_section_send">Enviar</string>
|
||||
<string name="title_advanced_section_connection">Connexió</string>
|
||||
|
|
@ -201,6 +221,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_advanced_suggest_sent">Suggeriu adreces trobades als missatges enviats</string>
|
||||
<string name="title_advanced_suggest_received">Suggeriu adreces trobades als missatges rebuts</string>
|
||||
<string name="title_advanced_suggest_frequently">Ordena les adreces suggerides en funció de la freqüència d’ús</string>
|
||||
<string name="title_advanced_compose_font">Tipus de lletra per defecte</string>
|
||||
<string name="title_advanced_prefix_once">El prefix de l\'assumpte només una vegada a la resposta o al reenviament</string>
|
||||
<string name="title_advanced_extended_reply">Utilitza resposta estesa/capçalera de reenviament</string>
|
||||
<string name="title_advanced_quote_reply">Text amb resposta a la cita</string>
|
||||
|
|
@ -221,6 +242,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_advanced_roaming">Baixeu missatges i fitxers adjunts en itinerància</string>
|
||||
<string name="title_advanced_rlah">Itinerant com a casa</string>
|
||||
<string name="title_advanced_timeout">Temps d\'espera de la connexió (segons)</string>
|
||||
<string name="title_advanced_prefer_ip4">Prefereix IPv4 per sobre de IPv6</string>
|
||||
<string name="title_advanced_ssl_harden">Connexions SSL \"endurides\"</string>
|
||||
<string name="title_advanced_manage_connectivity">Gestiona la connectivitat</string>
|
||||
<string name="title_advanced_caption_general">General</string>
|
||||
|
|
@ -247,6 +269,8 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_advanced_generated_icons">Mostra les icones generades</string>
|
||||
<string name="title_advanced_identicons">Mostra identicons</string>
|
||||
<string name="title_advanced_circular">Mostra icones rodones</string>
|
||||
<string name="title_advanced_color_saturation">Saturació: %1$s %%</string>
|
||||
<string name="title_advanced_color_value">Brillantor %1$s %%</string>
|
||||
<string name="title_advanced_name_email">Mostra els noms i les adreces de correu</string>
|
||||
<string name="title_advanced_replace_name">Preferiu el nom de contacte que el nom enviat</string>
|
||||
<string name="title_advanced_distinguish_contacts">Subratlla l’emissor quan el remitent es coneix com a contacte “a” local</string>
|
||||
|
|
@ -357,6 +381,8 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_advanced_shortcuts">Mostra els contactes més freqüents al menú de compartició d\'Android</string>
|
||||
<string name="title_advanced_fts">Construint índex de cerca</string>
|
||||
<string name="title_advanced_fts_indexed">%1$d / %2$d missatges indexats (%3$s)</string>
|
||||
<string name="title_advanced_language">Idioma</string>
|
||||
<string name="title_advanced_language_system">Sistema</string>
|
||||
<string name="title_advanced_watchdog">Comproveu periòdicament si FairEmail està actiu</string>
|
||||
<string name="title_advanced_optimize">Optimitzar automàticament</string>
|
||||
<string name="title_advanced_experiments">Prova característiques experimentals</string>
|
||||
|
|
@ -421,6 +447,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_advanced_cleanup_attachments_hint">Si es neteja manualment, s\'eliminen els fitxers adjunts dels missatges que ja no es sincronitzen</string>
|
||||
<string name="title_advanced_cleanup_hint">S\'eliminaran tots els fitxers temporals</string>
|
||||
<string name="title_advanced_never_favorite">Mai preferit</string>
|
||||
<string name="title_advanced_edit_name">Edita el nom</string>
|
||||
<string name="title_advanced_swipe_actions">Estableix accions de lliscament</string>
|
||||
<string name="title_advanced_swipe_actions_hint">D’aquesta manera, establireu l’acció lliscant cap a l’esquerra i la dreta per a tots els comptes IMAP</string>
|
||||
<string name="title_select">Selecciona …</string>
|
||||
|
|
@ -453,6 +480,8 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_provider">Proveïdor</string>
|
||||
<string name="title_custom">Personalitzat</string>
|
||||
<string name="title_host">Nom del servidor</string>
|
||||
<string name="title_encryption">Xifratge</string>
|
||||
<string name="title_encryption_none">Cap</string>
|
||||
<string name="title_allow_insecure">Permet connexions no segures</string>
|
||||
<string name="title_insecure_remark">Les connexions insegures només s’han de permetre en xarxes de confiança i mai en xarxes públiques</string>
|
||||
<string name="title_port">Número de port</string>
|
||||
|
|
@ -503,6 +532,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_advanced_browse">Busca missatges en el servidor remot</string>
|
||||
<string name="title_advanced_expand_read">Marca els missatges llegits en expandir-se</string>
|
||||
<string name="title_synchronize_now">Sincronitza ara</string>
|
||||
<string name="title_synchronize_subfolders">Subcarpetes</string>
|
||||
<string name="title_synchronize_enabled">Sincronitza</string>
|
||||
<string name="title_delete_local">Esborra els missatges locals</string>
|
||||
<string name="title_delete_browsed">Suprimeix els missatges cercats/navegats</string>
|
||||
|
|
@ -565,13 +595,13 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_folder_user_only">Només carpetes d\'usuari</string>
|
||||
<string name="title_folder_primary">Carpetes del compte primari</string>
|
||||
<string name="title_folders_unified">Carpetes unificades de la safata d\'entrada</string>
|
||||
<string name="title_folder_local_drafts">Esborranys locals</string>
|
||||
<string name="title_no_folders">No carpetes</string>
|
||||
<string name="title_no_messages">No hi ha missatges</string>
|
||||
<string name="title_filters_active">S\'han activat un o més filtres</string>
|
||||
<string name="title_duplicate_in">Missatge duplicat a %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Rv: %1$s</string>
|
||||
<string name="title_buttons">Botons</string>
|
||||
<string name="title_seen">Marca com a llegit</string>
|
||||
<string name="title_unseen">Marca com a no llegit</string>
|
||||
<string name="title_hide">Amaga</string>
|
||||
|
|
@ -611,6 +641,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_spam">Correu brossa</string>
|
||||
<string name="title_move">Mou</string>
|
||||
<string name="title_copy_btn">Copia</string>
|
||||
<string name="title_keywords_btn">Paraules en clau</string>
|
||||
<string name="title_unsubscribe">Cancel·lar la subscripció</string>
|
||||
<string name="title_message_rule">Crea una regla</string>
|
||||
<string name="title_no_junk">No es correu brossa</string>
|
||||
|
|
@ -660,6 +691,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_ask_delete_rule">Esborrar regla per sempre?</string>
|
||||
<string name="title_ask_discard">Voleu rebutjar l\'esborrany?</string>
|
||||
<string name="title_ask_show_html">Si es mostra el missatge original es pot filtrar informació sensible a la privadesa</string>
|
||||
<string name="title_ask_show_html_dark">Utilitza un tema fosc</string>
|
||||
<string name="title_ask_show_html_remark">No es pot mostrar el missatge original amb un fons fosc perquè pot provocar imatges i textos foscos invisibles</string>
|
||||
<string name="title_ask_show_html_images">Mostrar sempre les imatges al mostrar els missatges originals</string>
|
||||
<string name="title_ask_show_image">Si es mostra imatges, es pot filtrar informació sensible a la privadesa</string>
|
||||
|
|
@ -707,6 +739,11 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_style_size_medium">Mitjà</string>
|
||||
<string name="title_style_size_large">Gran</string>
|
||||
<string name="title_style_color">Color …</string>
|
||||
<string name="title_style_align">Alineació</string>
|
||||
<string name="title_style_align_start">Comença</string>
|
||||
<string name="title_style_align_center">Centre</string>
|
||||
<string name="title_style_align_end">Fi</string>
|
||||
<string name="title_style_list">Llistat</string>
|
||||
<string name="title_style_font">Font</string>
|
||||
<string name="title_style_font_default">Per defecte</string>
|
||||
<string name="title_style_clear">Esborra el format</string>
|
||||
|
|
@ -755,6 +792,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_queued">Enviant missatge</string>
|
||||
<string name="title_queued_at">El missatge s\'enviarà al voltant de %1$s</string>
|
||||
<string name="title_sign">Signar</string>
|
||||
<string name="title_verify">Verifica</string>
|
||||
<string name="title_encrypt">Xifra</string>
|
||||
<string name="title_decrypt">Desxifra</string>
|
||||
<string name="title_resync">Resincronitza</string>
|
||||
|
|
@ -892,6 +930,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_rule_tts_prefix">Missatge nou</string>
|
||||
<string name="title_rule_tts_from">De</string>
|
||||
<string name="title_rule_tts_subject">Assumpte</string>
|
||||
<string name="title_rule_tts_content">Text</string>
|
||||
<string name="title_legend_section_synchronize">Sincronitza</string>
|
||||
<string name="title_legend_section_folders">Carpetes</string>
|
||||
<string name="title_legend_section_messages">Missatges</string>
|
||||
|
|
@ -1021,6 +1060,7 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_add">Afegir</string>
|
||||
<string name="title_browse">Obre amb</string>
|
||||
<string name="title_info">Informació</string>
|
||||
<string name="title_download">Descarrega</string>
|
||||
<string name="title_report">Informa</string>
|
||||
<string name="title_fix">Repara</string>
|
||||
<string name="title_enable">Habilita</string>
|
||||
|
|
@ -1068,6 +1108,10 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_log">Registres</string>
|
||||
<string name="title_auto_scroll">Desplaçament automàtic</string>
|
||||
<string name="title_log_clear">Netejar</string>
|
||||
<string name="title_rules_export">Exporta regles</string>
|
||||
<string name="title_rules_import">Importa regles</string>
|
||||
<string name="title_rules_delete_all">Esborra totes les regles</string>
|
||||
<string name="title_rules_delete_junk">Esborra totes les regles d\'SPAM</string>
|
||||
<string name="title_debug_info">Informació de depuració</string>
|
||||
<string name="title_debug_info_remark">Per favor descriu el problema i indica quan en el que va ocorre:</string>
|
||||
<string name="title_crash_info_remark">Per favor descriu què estaves fent quan l\'aplicació va fallar:</string>
|
||||
|
|
@ -1102,6 +1146,10 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<string name="title_accessibility_expand">Expandeix</string>
|
||||
<string name="title_accessibility_view_contact">Mostra el contacte</string>
|
||||
<string name="title_accessibility_show_authentication_result">Mostra el resultat de l\'autenticació</string>
|
||||
<string name="title_accessibility_view_help">Mostra l\'ajuda</string>
|
||||
<string name="title_accessibility_selected">Seleccionat</string>
|
||||
<string name="title_accessibility_scroll_down">Desplaça avall</string>
|
||||
<string name="title_accessibility_scroll_up">Desplaça cap amunt</string>
|
||||
<string name="title_accessibility_edit">Editar</string>
|
||||
<string name="title_accessibility_show_addresses">Mostra adreces</string>
|
||||
<string name="title_accessibility_hide_addresses">Amaga les adreces</string>
|
||||
|
|
@ -1200,11 +1248,28 @@ La creació i l\'ús de regles és una característica professional. </string
|
|||
<item>Només signar S/MIME</item>
|
||||
<item>Signar i xifrar S/MIME</item>
|
||||
</string-array>
|
||||
<string-array name="sizeNames">
|
||||
<item>0 B</item>
|
||||
<item>256 KB</item>
|
||||
<item>512 KB</item>
|
||||
<item>1 MB</item>
|
||||
<item>2 MB</item>
|
||||
<item>5 MB</item>
|
||||
<item>10 MB</item>
|
||||
<item>20 MB</item>
|
||||
<item>50 MB</item>
|
||||
</string-array>
|
||||
<string-array name="undoNames">
|
||||
<item>Off</item>
|
||||
<item>Desactivat</item>
|
||||
<item>2,5 s</item>
|
||||
<item>5 s</item>
|
||||
<item>7,5 s</item>
|
||||
<item>10 s</item>
|
||||
</string-array>
|
||||
<string-array name="fontNameNames">
|
||||
<item>Cursiva</item>
|
||||
<item>Serif</item>
|
||||
<item>Sans-serif</item>
|
||||
<item>Monospace</item>
|
||||
</string-array>
|
||||
</resources>
|
||||
|
|
|
|||
|
|
@ -179,6 +179,7 @@
|
|||
<string name="title_setup_manage">Spravovat</string>
|
||||
<string name="title_setup_grant">Udělit</string>
|
||||
<string name="title_setup_grant_again">Udělit požadovaná oprávnění</string>
|
||||
<string name="title_setup_exchange_support">Je podporován Microsoft Exchange?</string>
|
||||
<string name="title_setup_identity_what">Co je to identita?</string>
|
||||
<string name="title_setup_permissions">Udělit oprávnění</string>
|
||||
<string name="title_setup_permissions_remark">Pro přístup k údajům kontaktů (nepovinné)</string>
|
||||
|
|
@ -230,6 +231,7 @@
|
|||
<string name="title_setup_theme_system">Podle systému</string>
|
||||
<string name="title_setup_theme_black_background">Černé pozadí</string>
|
||||
<string name="title_setup_theme_system_hint">Podporuje-li to Android, motiv „podle systému“ se ve dne/noci automaticky přepne na světlé/tmavé zobrazení</string>
|
||||
<string name="title_setup_theme_more_colors">Chci více barev</string>
|
||||
<string name="title_setup_advanced">Pokročilé</string>
|
||||
<string name="title_setup_options">Možnosti</string>
|
||||
<string name="title_setup_defaults">Obnovit výchozí</string>
|
||||
|
|
@ -311,6 +313,7 @@
|
|||
<string name="title_advanced_startup">Na úvodní obrazovce zobrazit</string>
|
||||
<string name="title_advanced_cards">Použít styl karet namísto tabulkového zobrazení</string>
|
||||
<string name="title_advanced_cards_beige">Použít béžové pozadí při zobrazení stylem karet</string>
|
||||
<string name="title_advanced_cards_shadow">Použít stín pro nepřečtené zprávy, při zobrazení stylem karet</string>
|
||||
<string name="title_advanced_date_header">Seskupit podle data</string>
|
||||
<string name="title_advanced_threading">Vlákna konverzací</string>
|
||||
<string name="title_advanced_threading_unread">Zobrazit počet nepřečtených zpráv v konverzacích</string>
|
||||
|
|
@ -505,6 +508,7 @@
|
|||
<string name="title_advanced_gravatars_hint">Může dojít k ohrožení soukromí</string>
|
||||
<string name="title_advanced_name_email_hint">Při vypnutí se zobrazí pouze jména, budou-li k dispozici</string>
|
||||
<string name="title_advanced_preview_hint">K dispozici pouze pokud byl stažen text zprávy</string>
|
||||
<string name="title_advanced_preview_lines_hint">Maximálně %s znaků celkem</string>
|
||||
<string name="title_advanced_preview_issue">Je-li počet řádků větší než jeden, může být posouvání pomalé díky chybě v některých verzích Androidu</string>
|
||||
<string name="title_advanced_overview_mode_hint">Může mít za následek velmi malé písmo</string>
|
||||
<string name="title_advanced_placeholders_hint">Platí pouze pro přeformátované zprávy</string>
|
||||
|
|
@ -616,6 +620,7 @@
|
|||
<string name="title_no_inbox">Složka \"Doručené\" nenalezena</string>
|
||||
<string name="title_no_drafts">Žádná složka konceptů</string>
|
||||
<string name="title_no_junk_folder">Pro tento účet není zvolena žádná složka pro nevyžádanou poštu</string>
|
||||
<string name="title_default_composable">Výchozí e-mailová adresa je určena výchozí identitou hlavního účtu</string>
|
||||
<string name="title_no_composable">Odesílání e-mailů vyžaduje nastavenou identitu a zvolit složku pro koncepty v nastavení účtu</string>
|
||||
<string name="title_no_standard">Tento poskytovatel používá proprietární e-mailový protokol, a proto není možné použít e-mailové klienty třetích stran</string>
|
||||
<string name="title_no_idle">Tento poskytovatel nepodporuje okamžité zprávy. Následkem bude opožděný příjem nových zpráv a zvýšená spotřeba baterie.</string>
|
||||
|
|
@ -727,7 +732,6 @@
|
|||
<string name="title_duplicate_in">Duplikát zprávy v %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Tlačítka</string>
|
||||
<string name="title_seen">Označit přečtené</string>
|
||||
<string name="title_unseen">Označit nepřečtené</string>
|
||||
<string name="title_toggle_seen">Označit ne/přečteno</string>
|
||||
|
|
@ -786,6 +790,7 @@
|
|||
<string name="title_reply_to_all">Odpovědět všem</string>
|
||||
<string name="title_reply_list">Odpovědět seznamu</string>
|
||||
<string name="title_reply_receipt">Odeslat potvrzení o přečtení</string>
|
||||
<string name="title_reply_hard_bounce">Odeslat oznámení o nedoručitelnosti</string>
|
||||
<string name="title_reply_template">Odpovědět šablonou</string>
|
||||
<string name="title_move_undo">Přesouvání do %1$s (%2$d)</string>
|
||||
<string name="title_open_with">Otevřít v aplikaci</string>
|
||||
|
|
@ -863,6 +868,7 @@
|
|||
<string name="title_send_now">Odeslat nyní</string>
|
||||
<string name="title_send_via">Odeslat přes</string>
|
||||
<string name="title_send_at">Odeslat později …</string>
|
||||
<string name="title_send_auto_archive">Archivovat odpovězené zprávy</string>
|
||||
<string name="title_send_encryption">Šifrování</string>
|
||||
<string name="title_send_priority">Priorita</string>
|
||||
<string name="title_no_server">Nenalezen žádný server na „%1$s“</string>
|
||||
|
|
@ -918,17 +924,20 @@
|
|||
<string name="title_key_missing">Není klíč pro %1$s</string>
|
||||
<string name="title_send_reminder_remark">Připomenutí lze znovu zapnout v nastavení odesílání</string>
|
||||
<string name="title_send_plain_text">Pouze prostý text</string>
|
||||
<string name="title_send_dsn">Hlášení o stavu</string>
|
||||
<string name="title_send_receipt">Požádat o potvrzení</string>
|
||||
<string name="title_send_receipt_remark">Většina poskytovatelů a e-mailových klientů ignoruje žádosti o potvrzení</string>
|
||||
<string name="title_from_missing">Chybí odesílatel</string>
|
||||
<string name="title_extra_missing">Chybí uživatelské jméno</string>
|
||||
<string name="title_to_missing">Chybí příjemce</string>
|
||||
<string name="title_pgp_reminder">PGP klíče k dispozici</string>
|
||||
<string name="title_smime_reminder">S/MIME klíče k dispozici</string>
|
||||
<string name="title_subject_reminder">Chybí předmět</string>
|
||||
<string name="title_text_reminder">Zpráva je prázdná</string>
|
||||
<string name="title_attachment_keywords">příloha,přílohy,příloze,přílohu,přiložené,přiloženém,přiložený,přiložená,připojené,připojeném,připojený,připojená</string>
|
||||
<string name="title_attachment_reminder">Měl jste v úmyslu přidat přílohu?</string>
|
||||
<string name="title_plain_reminder">Veškeré formátování bude ztraceno</string>
|
||||
<string name="title_dsn_reminder">Oznámení o nedoručitelnosti (hard bounce) poškozují e-mailovou reputaci původního odesílatele!</string>
|
||||
<string name="title_size_reminder">Zpráva (%1$s) je větší než limit serveru (%2$s)</string>
|
||||
<string name="title_attachments_missing">Nebyly staženy všechny přílohy</string>
|
||||
<string name="title_dialog_hint">Toto dialogové okno může být znovu zapnuto v menu s třemi tečkami horní liště akcí</string>
|
||||
|
|
|
|||
|
|
@ -716,7 +716,6 @@
|
|||
<string name="title_duplicate_in">Dubletbeskeder i %1$s</string>
|
||||
<string name="title_subject_reply">Sv: %1$s</string>
|
||||
<string name="title_subject_forward">Vs: %1$s</string>
|
||||
<string name="title_buttons">Knapper</string>
|
||||
<string name="title_seen">Markér som læst</string>
|
||||
<string name="title_unseen">Markér som ulæst</string>
|
||||
<string name="title_toggle_seen">Slå læst til/fra</string>
|
||||
|
|
@ -853,7 +852,7 @@
|
|||
<string name="title_send_now">Send nu</string>
|
||||
<string name="title_send_via">Send via</string>
|
||||
<string name="title_send_at">Sendt kl. …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Arkivér besvarede beskeder</string>
|
||||
<string name="title_send_auto_archive">Arkivér besvarede beskeder</string>
|
||||
<string name="title_send_encryption">Kryptering</string>
|
||||
<string name="title_send_priority">Prioritet</string>
|
||||
<string name="title_no_server">Ingen server fundet på \'%1$s\'</string>
|
||||
|
|
|
|||
|
|
@ -291,6 +291,7 @@
|
|||
<string name="title_advanced_startup">Auf Startbildschirm anzeigen:</string>
|
||||
<string name="title_advanced_cards">Ordner und Unterhaltungen mit Rahmen (breit) statt in Tabellendesign (schmal) zeigen</string>
|
||||
<string name="title_advanced_cards_beige">Beigefarbenen Hintergrund bei Kartendarstellung verwenden</string>
|
||||
<string name="title_advanced_cards_shadow">Schatten für ungelesene Nachrichten verwenden, wenn Kartenstil verwendet wird</string>
|
||||
<string name="title_advanced_date_header">Nach Datum gruppieren</string>
|
||||
<string name="title_advanced_threading">Themenbaum</string>
|
||||
<string name="title_advanced_threading_unread">Anzahl ungelesener Nachrichten in Unterhaltungen anzeigen</string>
|
||||
|
|
@ -716,7 +717,6 @@
|
|||
<string name="title_duplicate_in">Doppelte Nachricht in %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Schaltflächen</string>
|
||||
<string name="title_seen">Gelesen</string>
|
||||
<string name="title_unseen">Als ungelesen kennzeichnen</string>
|
||||
<string name="title_toggle_seen">Gelesen umschalten</string>
|
||||
|
|
@ -853,7 +853,7 @@
|
|||
<string name="title_send_now">Sofort</string>
|
||||
<string name="title_send_via">Senden über</string>
|
||||
<string name="title_send_at">Später senden …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Beantwortete Nachricht archivieren</string>
|
||||
<string name="title_send_auto_archive">Beantwortete Nachricht archivieren</string>
|
||||
<string name="title_send_encryption">Verschlüsselung</string>
|
||||
<string name="title_send_priority">Priorität</string>
|
||||
<string name="title_no_server">Kein Server gefunden bei \'%1$s\'</string>
|
||||
|
|
@ -916,6 +916,7 @@
|
|||
<string name="title_extra_missing">Benutzername fehlt</string>
|
||||
<string name="title_to_missing">Empfänger fehlt</string>
|
||||
<string name="title_pgp_reminder">PGP-Schlüssel verfügbar</string>
|
||||
<string name="title_smime_reminder">S/MIME-Schlüssel verfügbar</string>
|
||||
<string name="title_subject_reminder">Betreff ist leer</string>
|
||||
<string name="title_text_reminder">Nachricht ist leer</string>
|
||||
<string name="title_attachment_keywords">angehängt,Anhang,Anhänge,beigefügt,Anlage,Anlagen,anbei</string>
|
||||
|
|
|
|||
|
|
@ -291,6 +291,7 @@
|
|||
<string name="title_advanced_startup">Auf Startbildschirm anzeigen:</string>
|
||||
<string name="title_advanced_cards">Ordner und Unterhaltungen mit Rahmen (breit) statt in Tabellendesign (schmal) zeigen</string>
|
||||
<string name="title_advanced_cards_beige">Beigefarbenen Hintergrund bei Kartendarstellung verwenden</string>
|
||||
<string name="title_advanced_cards_shadow">Schatten für ungelesene Nachrichten verwenden, wenn Kartenstil verwendet wird</string>
|
||||
<string name="title_advanced_date_header">Nach Datum gruppieren</string>
|
||||
<string name="title_advanced_threading">Themenbaum</string>
|
||||
<string name="title_advanced_threading_unread">Anzahl ungelesener Nachrichten in Unterhaltungen anzeigen</string>
|
||||
|
|
@ -716,7 +717,6 @@
|
|||
<string name="title_duplicate_in">Doppelte Nachricht in %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Schaltflächen</string>
|
||||
<string name="title_seen">Gelesen</string>
|
||||
<string name="title_unseen">Als ungelesen kennzeichnen</string>
|
||||
<string name="title_toggle_seen">Gelesen umschalten</string>
|
||||
|
|
@ -853,7 +853,7 @@
|
|||
<string name="title_send_now">Sofort</string>
|
||||
<string name="title_send_via">Senden über</string>
|
||||
<string name="title_send_at">Später senden …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Beantwortete Nachricht archivieren</string>
|
||||
<string name="title_send_auto_archive">Beantwortete Nachricht archivieren</string>
|
||||
<string name="title_send_encryption">Verschlüsselung</string>
|
||||
<string name="title_send_priority">Priorität</string>
|
||||
<string name="title_no_server">Kein Server gefunden bei \'%1$s\'</string>
|
||||
|
|
@ -916,6 +916,7 @@
|
|||
<string name="title_extra_missing">Benutzername fehlt</string>
|
||||
<string name="title_to_missing">Empfänger fehlt</string>
|
||||
<string name="title_pgp_reminder">PGP-Schlüssel verfügbar</string>
|
||||
<string name="title_smime_reminder">S/MIME-Schlüssel verfügbar</string>
|
||||
<string name="title_subject_reminder">Betreff ist leer</string>
|
||||
<string name="title_text_reminder">Nachricht ist leer</string>
|
||||
<string name="title_attachment_keywords">angehängt,Anhang,Anhänge,beigefügt,Anlage,Anlagen,anbei</string>
|
||||
|
|
|
|||
|
|
@ -291,6 +291,7 @@
|
|||
<string name="title_advanced_startup">Auf Startbildschirm anzeigen:</string>
|
||||
<string name="title_advanced_cards">Ordner und Unterhaltungen mit Rahmen (breit) statt in Tabellendesign (schmal) zeigen</string>
|
||||
<string name="title_advanced_cards_beige">Beigefarbenen Hintergrund bei Kartendarstellung verwenden</string>
|
||||
<string name="title_advanced_cards_shadow">Schatten für ungelesene Nachrichten verwenden, wenn Kartenstil verwendet wird</string>
|
||||
<string name="title_advanced_date_header">Nach Datum gruppieren</string>
|
||||
<string name="title_advanced_threading">Themenbaum</string>
|
||||
<string name="title_advanced_threading_unread">Anzahl ungelesener Nachrichten in Unterhaltungen anzeigen</string>
|
||||
|
|
@ -716,7 +717,6 @@
|
|||
<string name="title_duplicate_in">Doppelte Nachricht in %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Schaltflächen</string>
|
||||
<string name="title_seen">Gelesen</string>
|
||||
<string name="title_unseen">Als ungelesen kennzeichnen</string>
|
||||
<string name="title_toggle_seen">Gelesen umschalten</string>
|
||||
|
|
@ -853,7 +853,7 @@
|
|||
<string name="title_send_now">Sofort</string>
|
||||
<string name="title_send_via">Senden über</string>
|
||||
<string name="title_send_at">Später senden …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Beantwortete Nachricht archivieren</string>
|
||||
<string name="title_send_auto_archive">Beantwortete Nachricht archivieren</string>
|
||||
<string name="title_send_encryption">Verschlüsselung</string>
|
||||
<string name="title_send_priority">Priorität</string>
|
||||
<string name="title_no_server">Kein Server gefunden bei \'%1$s\'</string>
|
||||
|
|
@ -916,6 +916,7 @@
|
|||
<string name="title_extra_missing">Benutzername fehlt</string>
|
||||
<string name="title_to_missing">Empfänger fehlt</string>
|
||||
<string name="title_pgp_reminder">PGP-Schlüssel verfügbar</string>
|
||||
<string name="title_smime_reminder">S/MIME-Schlüssel verfügbar</string>
|
||||
<string name="title_subject_reminder">Betreff ist leer</string>
|
||||
<string name="title_text_reminder">Nachricht ist leer</string>
|
||||
<string name="title_attachment_keywords">angehängt,Anhang,Anhänge,beigefügt,Anlage,Anlagen,anbei</string>
|
||||
|
|
|
|||
|
|
@ -157,6 +157,7 @@
|
|||
<string name="title_setup_manage">Διαχείριση</string>
|
||||
<string name="title_setup_grant">Παραχώρηση δικαιώματος</string>
|
||||
<string name="title_setup_grant_again">Παραχώρηση απαιτούμενων δικαιωμάτων</string>
|
||||
<string name="title_setup_exchange_support">Υποστηρίζεται το Microsoft Exchange;</string>
|
||||
<string name="title_setup_identity_what">Τι είναι μια ταυτότητα;</string>
|
||||
<string name="title_setup_permissions">Απαιτούμενα δικαιώματα</string>
|
||||
<string name="title_setup_permissions_remark">Για πρόσβαση στις πληροφορίες επαφών (προαιρετικό)</string>
|
||||
|
|
@ -290,6 +291,7 @@
|
|||
<string name="title_advanced_startup">Εμφάνιση στην οθόνη έναρξης</string>
|
||||
<string name="title_advanced_cards">Προβολή σε στιλ κάρτας αντί σε στιλ πίνακα</string>
|
||||
<string name="title_advanced_cards_beige">Χρήση μπεζ φόντου όταν χρησιμοποιείται το στιλ κάρτας</string>
|
||||
<string name="title_advanced_cards_shadow">Σκίαση μη αναγνωσμένων μηνυμάτων κατά τη χρήση στιλ κάρτας</string>
|
||||
<string name="title_advanced_date_header">Ομαδοποίηση κατά ημερομηνία</string>
|
||||
<string name="title_advanced_threading">Ομαδοποίηση συζητήσεων σε νήματα</string>
|
||||
<string name="title_advanced_threading_unread">Προβολή αριθμού μη αναγνωσμένων μηνυμάτων στις συζητήσεις</string>
|
||||
|
|
@ -714,7 +716,6 @@
|
|||
<string name="title_duplicate_in">Διπλότυπο μήνυμα σε %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Κουμπιά</string>
|
||||
<string name="title_seen">Σήμανση ως αναγνωσμένο</string>
|
||||
<string name="title_unseen">Σήμανση ως μη αναγνωσμένο</string>
|
||||
<string name="title_toggle_seen">(Μη) αναγνωσμένο</string>
|
||||
|
|
@ -851,7 +852,7 @@
|
|||
<string name="title_send_now">Αποστολή τώρα</string>
|
||||
<string name="title_send_via">Αποστολή μέσω</string>
|
||||
<string name="title_send_at">Αποστολή στις …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Αρχειοθέτηση απαντημένου μηνύματος</string>
|
||||
<string name="title_send_auto_archive">Αρχειοθέτηση απαντημένου μηνύματος</string>
|
||||
<string name="title_send_encryption">Κρυπτογράφηση</string>
|
||||
<string name="title_send_priority">Προτεραιότητα</string>
|
||||
<string name="title_no_server">Δε βρέθηκε διακομιστής στο \'%1$s\'</string>
|
||||
|
|
@ -914,6 +915,7 @@
|
|||
<string name="title_extra_missing">Λείπει όνομα χρήστη</string>
|
||||
<string name="title_to_missing">Λείπει παραλήπτης</string>
|
||||
<string name="title_pgp_reminder">Κλειδιά PGP διαθέσιμα</string>
|
||||
<string name="title_smime_reminder">Κλειδιά S/MIME διαθέσιμα</string>
|
||||
<string name="title_subject_reminder">Το θέμα είναι κενό</string>
|
||||
<string name="title_text_reminder">Το μήνυμα είναι κενό</string>
|
||||
<string name="title_attachment_keywords">συνημμένο, συνημμένα, επισυνάπτω, επισυνάπτεται, επισυνάπονται, έγγραφο, έγγραφα, αρχείο, αρχεία, έντυπο, έντυπα, δικαιολογητικό, δικαιολογητικά, πιστοποιητικό, πιστοποιητικά, βιογραφικό, συνοδευτική επιστολή</string>
|
||||
|
|
|
|||
|
|
@ -157,6 +157,7 @@
|
|||
<string name="title_setup_manage">Administrar</string>
|
||||
<string name="title_setup_grant">Conceder</string>
|
||||
<string name="title_setup_grant_again">Otorgar permisos requeridos</string>
|
||||
<string name="title_setup_exchange_support">¿Es compatible con Microsoft Exchange?</string>
|
||||
<string name="title_setup_identity_what">¿Qué es una identidad?</string>
|
||||
<string name="title_setup_permissions">Conceder permisos</string>
|
||||
<string name="title_setup_permissions_remark">Para acceder a información de contactos (opcional)</string>
|
||||
|
|
@ -290,6 +291,7 @@
|
|||
<string name="title_advanced_startup">Mostrar en pantalla de inicio</string>
|
||||
<string name="title_advanced_cards">Usar estilo de tarjeta en lugar del estilo tabular</string>
|
||||
<string name="title_advanced_cards_beige">Usar fondo beige al usar el estilo de tarjeta</string>
|
||||
<string name="title_advanced_cards_shadow">Usar sombra para mensajes no leídos al usar estilo de tarjeta</string>
|
||||
<string name="title_advanced_date_header">Agrupar por fecha</string>
|
||||
<string name="title_advanced_threading">Hilos de conversación</string>
|
||||
<string name="title_advanced_threading_unread">Mostrar número de mensajes no leídos en conversaciones</string>
|
||||
|
|
@ -716,7 +718,6 @@
|
|||
<string name="title_duplicate_in">Mensaje duplicado en %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Botones</string>
|
||||
<string name="title_seen">Marcar como leído</string>
|
||||
<string name="title_unseen">Marcar como no leído</string>
|
||||
<string name="title_toggle_seen">Cambiar leído</string>
|
||||
|
|
@ -853,7 +854,7 @@
|
|||
<string name="title_send_now">Enviar ahora</string>
|
||||
<string name="title_send_via">Enviar vía</string>
|
||||
<string name="title_send_at">Enviar a …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Archivar mensaje respondido</string>
|
||||
<string name="title_send_auto_archive">Archivar mensaje respondido</string>
|
||||
<string name="title_send_encryption">Cifrado</string>
|
||||
<string name="title_send_priority">Prioridad</string>
|
||||
<string name="title_no_server">No se encontró ningún servidor en \'%1$s\'</string>
|
||||
|
|
@ -916,6 +917,7 @@
|
|||
<string name="title_extra_missing">Falta el nombre de usuario</string>
|
||||
<string name="title_to_missing">Falta destinatario</string>
|
||||
<string name="title_pgp_reminder">Claves PGP disponibles</string>
|
||||
<string name="title_smime_reminder">Claves S/MIME disponibles</string>
|
||||
<string name="title_subject_reminder">El asunto está vacío</string>
|
||||
<string name="title_text_reminder">El mensaje está vacío</string>
|
||||
<string name="title_attachment_keywords">adjunto,adjunta,adjuntos,incluido,incluida,adjuntas</string>
|
||||
|
|
|
|||
|
|
@ -587,7 +587,6 @@
|
|||
<string name="title_duplicate_in">Mezu bikoiztua %1$s-(a)n</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Botoiak</string>
|
||||
<string name="title_seen">Markatu irakurria</string>
|
||||
<string name="title_unseen">Markatu irakurri gabeko gisa</string>
|
||||
<string name="title_hide">Ezkutatu</string>
|
||||
|
|
|
|||
|
|
@ -503,7 +503,6 @@
|
|||
<string name="title_duplicate_in">پیام را در %1$s تکثیر کن</string>
|
||||
<string name="title_subject_reply">پاسخ: %1$s</string>
|
||||
<string name="title_subject_forward">هدایت: %1$s</string>
|
||||
<string name="title_buttons">دکمهها</string>
|
||||
<string name="title_seen">علامت زدن به عنوان خوانده شده</string>
|
||||
<string name="title_unseen">علامت زدن به عنوان خوانده نشده</string>
|
||||
<string name="title_hide">پنهان کردن</string>
|
||||
|
|
|
|||
|
|
@ -156,6 +156,7 @@
|
|||
<string name="title_setup_manage">Muokkaa</string>
|
||||
<string name="title_setup_grant">Myönnä</string>
|
||||
<string name="title_setup_grant_again">Myönnä vaaditut oikeudet</string>
|
||||
<string name="title_setup_exchange_support">Onko Microsoft Exchange tuettu?</string>
|
||||
<string name="title_setup_identity_what">Mikä on identiteetti?</string>
|
||||
<string name="title_setup_permissions">Myönnä käyttöoikeudet</string>
|
||||
<string name="title_setup_permissions_remark">Laitteen yhteystietoihin pääsemiseksi (valinnainen)</string>
|
||||
|
|
@ -289,6 +290,7 @@
|
|||
<string name="title_advanced_startup">Näytä aloitusnäytössä</string>
|
||||
<string name="title_advanced_cards">Käytä korttityyliä taulukkotyylin sijaan</string>
|
||||
<string name="title_advanced_cards_beige">Käytä beigeä taustaa korttityylissä</string>
|
||||
<string name="title_advanced_cards_shadow">Käytä varjoa lukemattomiin viesteihin korttityylissä</string>
|
||||
<string name="title_advanced_date_header">Ryhmittely päivämäärän mukaan</string>
|
||||
<string name="title_advanced_threading">Keskustelujen ketjuttaminen</string>
|
||||
<string name="title_advanced_threading_unread">Näytä lukemattomien viestien lukumäärä keskusteluissa</string>
|
||||
|
|
@ -714,7 +716,6 @@
|
|||
<string name="title_duplicate_in">Tee viestistä kopio kansioon %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Painikkeet</string>
|
||||
<string name="title_seen">Merkitse luetuksi</string>
|
||||
<string name="title_unseen">Merkitse lukemattomaksi</string>
|
||||
<string name="title_toggle_seen">Vaihda luettu</string>
|
||||
|
|
@ -851,7 +852,7 @@
|
|||
<string name="title_send_now">Lähetä heti</string>
|
||||
<string name="title_send_via">Lähetä kautta</string>
|
||||
<string name="title_send_at">Lähetysaika …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Arkistoi vastattu viesti</string>
|
||||
<string name="title_send_auto_archive">Arkistoi vastattu viesti</string>
|
||||
<string name="title_send_encryption">Salaus</string>
|
||||
<string name="title_send_priority">Tärkeysjärjestys</string>
|
||||
<string name="title_no_server">Palvelinta ei löytynyt osoitteesta \'%1$s\'</string>
|
||||
|
|
@ -914,6 +915,7 @@
|
|||
<string name="title_extra_missing">Käyttäjätunnus puuttuu</string>
|
||||
<string name="title_to_missing">Vastaanottaja puuttuu</string>
|
||||
<string name="title_pgp_reminder">PGP-avaimet saatavilla</string>
|
||||
<string name="title_smime_reminder">S/MIME-avaimet saatavilla</string>
|
||||
<string name="title_subject_reminder">Aihe puuttuu</string>
|
||||
<string name="title_text_reminder">Viesti on tyhjä</string>
|
||||
<string name="title_attachment_keywords">liite,liitteet,liitetty,liitetyt,sisällytetty,lisätty,liitin,sisällytin,lisäsin</string>
|
||||
|
|
|
|||
|
|
@ -157,6 +157,7 @@
|
|||
<string name="title_setup_manage">Gérer</string>
|
||||
<string name="title_setup_grant">Autoriser</string>
|
||||
<string name="title_setup_grant_again">Accorder les autorisations requises</string>
|
||||
<string name="title_setup_exchange_support">Microsoft Exchange est-il pris en charge ?</string>
|
||||
<string name="title_setup_identity_what">Qu\'est-ce qu\'une identité?</string>
|
||||
<string name="title_setup_permissions">Accorder les autorisations</string>
|
||||
<string name="title_setup_permissions_remark">Pour accéder aux informations de contact (facultatif)</string>
|
||||
|
|
@ -290,6 +291,7 @@
|
|||
<string name="title_advanced_startup">Afficher sur l’écran de démarrage</string>
|
||||
<string name="title_advanced_cards">Utiliser le style carte au lieu du style tableau</string>
|
||||
<string name="title_advanced_cards_beige">Utiliser un arrière-plan beige pour le style carte</string>
|
||||
<string name="title_advanced_cards_shadow">Utiliser une ombre autour des messages non lus pour le style carte</string>
|
||||
<string name="title_advanced_date_header">Grouper par date</string>
|
||||
<string name="title_advanced_threading">Afficher en mode conversation</string>
|
||||
<string name="title_advanced_threading_unread">Afficher le nombre de messages non lus dans les conversations</string>
|
||||
|
|
@ -716,7 +718,6 @@
|
|||
<string name="title_duplicate_in">Message en double dans %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Tr: %1$s</string>
|
||||
<string name="title_buttons">Boutons</string>
|
||||
<string name="title_seen">Marquer comme lu</string>
|
||||
<string name="title_unseen">Marquer comme non lu</string>
|
||||
<string name="title_toggle_seen">Marquer lu/non lu</string>
|
||||
|
|
@ -853,7 +854,7 @@
|
|||
<string name="title_send_now">Env. maint.</string>
|
||||
<string name="title_send_via">Envoyer avec</string>
|
||||
<string name="title_send_at">Envoyer à…</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Archiver un message avec réponse</string>
|
||||
<string name="title_send_auto_archive">Archiver un message avec réponse</string>
|
||||
<string name="title_send_encryption">Chiffrement</string>
|
||||
<string name="title_send_priority">Priorité</string>
|
||||
<string name="title_no_server">Aucun serveur trouvé à \'%1$s\'</string>
|
||||
|
|
@ -916,6 +917,7 @@
|
|||
<string name="title_extra_missing">Nom d’utilisateur manquant</string>
|
||||
<string name="title_to_missing">Destinataire manquant</string>
|
||||
<string name="title_pgp_reminder">Clés PGP disponibles</string>
|
||||
<string name="title_smime_reminder">Clés S/MIME disponibles</string>
|
||||
<string name="title_subject_reminder">L’objet est vide</string>
|
||||
<string name="title_text_reminder">Le message est vide</string>
|
||||
<string name="title_attachment_keywords">joint,jointe,joints,jointes,ci-joint,ci-jointe,ci-joints,ci-jointes,attaché,attachés,attachée,attachées,lettre de motivation,cv</string>
|
||||
|
|
|
|||
|
|
@ -157,6 +157,7 @@
|
|||
<string name="title_setup_manage">Gérer</string>
|
||||
<string name="title_setup_grant">Autoriser</string>
|
||||
<string name="title_setup_grant_again">Accorder les autorisations requises</string>
|
||||
<string name="title_setup_exchange_support">Microsoft Exchange est-il pris en charge ?</string>
|
||||
<string name="title_setup_identity_what">Qu\'est-ce qu\'une identité ?</string>
|
||||
<string name="title_setup_permissions">Accorder les autorisations</string>
|
||||
<string name="title_setup_permissions_remark">Pour accéder aux informations des contacts (facultatif)</string>
|
||||
|
|
@ -290,6 +291,7 @@
|
|||
<string name="title_advanced_startup">Afficher sur l\'écran de démarrage</string>
|
||||
<string name="title_advanced_cards">Utiliser le style carte au lieu du style tableau</string>
|
||||
<string name="title_advanced_cards_beige">Utiliser un arrière-plan beige pour le style carte</string>
|
||||
<string name="title_advanced_cards_shadow">Utiliser une ombre autour des messages non lus pour le style carte</string>
|
||||
<string name="title_advanced_date_header">Grouper par date</string>
|
||||
<string name="title_advanced_threading">Afficher en mode conversation</string>
|
||||
<string name="title_advanced_threading_unread">Afficher le nombre de messages non lus dans les conversations</string>
|
||||
|
|
@ -716,7 +718,6 @@
|
|||
<string name="title_duplicate_in">Message en double dans %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Tr: %1$s</string>
|
||||
<string name="title_buttons">Boutons</string>
|
||||
<string name="title_seen">Marquer comme lu</string>
|
||||
<string name="title_unseen">Marquer comme non lu</string>
|
||||
<string name="title_toggle_seen">Marquer lu/non lu</string>
|
||||
|
|
@ -853,7 +854,7 @@
|
|||
<string name="title_send_now">Env. maint.</string>
|
||||
<string name="title_send_via">Envoyer via</string>
|
||||
<string name="title_send_at">Envoyer à…</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Archiver un message avec réponse</string>
|
||||
<string name="title_send_auto_archive">Archiver un message avec réponse</string>
|
||||
<string name="title_send_encryption">Chiffrement</string>
|
||||
<string name="title_send_priority">Priorité</string>
|
||||
<string name="title_no_server">Aucun serveur trouvé à \'%1$s\'</string>
|
||||
|
|
@ -916,6 +917,7 @@
|
|||
<string name="title_extra_missing">Nom d\'utilisateur manquant</string>
|
||||
<string name="title_to_missing">Destinataire manquant</string>
|
||||
<string name="title_pgp_reminder">Clés PGP disponibles</string>
|
||||
<string name="title_smime_reminder">Clés S/MIME disponibles</string>
|
||||
<string name="title_subject_reminder">L\'objet est vide</string>
|
||||
<string name="title_text_reminder">Le message est vide</string>
|
||||
<string name="title_attachment_keywords">joint,jointe,joints,jointes,ci-joint,ci-jointe,ci-joints,ci-jointes,attaché,attachés,attachée,attachées,lettre de motivation,cv</string>
|
||||
|
|
|
|||
|
|
@ -673,7 +673,6 @@
|
|||
<string name="title_duplicate_in">Berjocht duplisearje yn %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Foarút: %1$s</string>
|
||||
<string name="title_buttons">Knoppen</string>
|
||||
<string name="title_seen">Mark lêzen</string>
|
||||
<string name="title_unseen">Markearje as net lêzen</string>
|
||||
<string name="title_toggle_seen">Wikselje lêze</string>
|
||||
|
|
|
|||
|
|
@ -692,7 +692,6 @@
|
|||
<string name="title_duplicate_in">Mensaxe duplicada en %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Botóns</string>
|
||||
<string name="title_seen">Marcar como lida</string>
|
||||
<string name="title_unseen">Marcar como non lida</string>
|
||||
<string name="title_toggle_seen">Trocar lido/non lido</string>
|
||||
|
|
|
|||
|
|
@ -682,7 +682,6 @@
|
|||
<string name="title_duplicate_in">Duplikált üzenet a(z) %1$s mappában</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Gombok</string>
|
||||
<string name="title_seen">Megjelölés olvasottként</string>
|
||||
<string name="title_unseen">Megjelölés olvasatlanként</string>
|
||||
<string name="title_toggle_seen">Megjelölés olvasottként</string>
|
||||
|
|
|
|||
|
|
@ -654,7 +654,6 @@
|
|||
<string name="title_duplicate_in">Pesan duplikat dalam %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Tombol</string>
|
||||
<string name="title_seen">Tandai sudah dibaca</string>
|
||||
<string name="title_unseen">Tandai belum dibaca</string>
|
||||
<string name="title_toggle_seen">Alihkan ke mode baca</string>
|
||||
|
|
|
|||
|
|
@ -716,7 +716,6 @@
|
|||
<string name="title_duplicate_in">Duplica messaggio in %1$s</string>
|
||||
<string name="title_subject_reply">R: %1$s</string>
|
||||
<string name="title_subject_forward">I: %1$s</string>
|
||||
<string name="title_buttons">Pulsanti</string>
|
||||
<string name="title_seen">Segna come letto</string>
|
||||
<string name="title_unseen">Segna come non letto</string>
|
||||
<string name="title_toggle_seen">Attiva/disattiva lettura</string>
|
||||
|
|
@ -853,7 +852,7 @@
|
|||
<string name="title_send_now">Invia ora</string>
|
||||
<string name="title_send_via">Invia tramite</string>
|
||||
<string name="title_send_at">Invia alle …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Archivia il messaggio con risposta</string>
|
||||
<string name="title_send_auto_archive">Archivia il messaggio con risposta</string>
|
||||
<string name="title_send_encryption">Crittografia</string>
|
||||
<string name="title_send_priority">Priorità</string>
|
||||
<string name="title_no_server">Nessun server trovato in \'%1$s\'</string>
|
||||
|
|
|
|||
|
|
@ -702,7 +702,6 @@
|
|||
<string name="title_duplicate_in">%1$sのメッセージが重複しています</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">ボタン</string>
|
||||
<string name="title_seen">既読にする</string>
|
||||
<string name="title_unseen">未読にします</string>
|
||||
<string name="title_toggle_seen">読み取りの切り替え</string>
|
||||
|
|
|
|||
|
|
@ -157,6 +157,7 @@
|
|||
<string name="title_setup_manage">Beheer</string>
|
||||
<string name="title_setup_grant">Verlenen</string>
|
||||
<string name="title_setup_grant_again">Verleen de vereiste machtigingen</string>
|
||||
<string name="title_setup_exchange_support">Wordt Microsoft Exchange ondersteund?</string>
|
||||
<string name="title_setup_identity_what">Wat is een identiteit?</string>
|
||||
<string name="title_setup_permissions">Toestemmingen verlenen</string>
|
||||
<string name="title_setup_permissions_remark">Voor toegang tot contactinformatie (optioneel)</string>
|
||||
|
|
@ -289,7 +290,8 @@
|
|||
<string name="title_advanced_landscape3">Navigatiemenu standaard in liggende modus weergeven</string>
|
||||
<string name="title_advanced_startup">Toon op het startscherm</string>
|
||||
<string name="title_advanced_cards">Gebruik kaart-stijl in plaats van tabulaire stijl</string>
|
||||
<string name="title_advanced_cards_beige">Gebruik beige achtergrond bij gebruik van kaart-stijl</string>
|
||||
<string name="title_advanced_cards_beige">Gebruik beige achtergrond bij gebruik van kaartstijl</string>
|
||||
<string name="title_advanced_cards_shadow">Gebruik schaduw voor ongelezen berichten bij gebruik van kaartstijl</string>
|
||||
<string name="title_advanced_date_header">Op datum groeperen</string>
|
||||
<string name="title_advanced_threading">Gesprekken groeperen</string>
|
||||
<string name="title_advanced_threading_unread">Toon aantal ongelezen berichten in gesprekken</string>
|
||||
|
|
@ -716,7 +718,6 @@
|
|||
<string name="title_duplicate_in">Dubbel bericht in %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Knoppen</string>
|
||||
<string name="title_seen">Markeer als gelezen</string>
|
||||
<string name="title_unseen">Markeer als ongelezen</string>
|
||||
<string name="title_toggle_seen">Lezen schakelen</string>
|
||||
|
|
@ -750,6 +751,8 @@
|
|||
<string name="title_download_all">Alles downloaden</string>
|
||||
<string name="title_save_all">Alles opslaan</string>
|
||||
<string name="title_save_eml">Ruw bericht opslaan</string>
|
||||
<string name="title_buttons">Selecteer knoppen</string>
|
||||
<string name="title_configure_buttons">Configureer knoppen …</string>
|
||||
<string name="title_trash">Prullenbak</string>
|
||||
<string name="title_copy">Kopieer …</string>
|
||||
<string name="title_copy_to">Kopieer naar …</string>
|
||||
|
|
@ -853,7 +856,7 @@
|
|||
<string name="title_send_now">Nu verzenden</string>
|
||||
<string name="title_send_via">Verzenden via</string>
|
||||
<string name="title_send_at">Verzenden om …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Archiveer beantwoord bericht</string>
|
||||
<string name="title_send_auto_archive">Archiveer beantwoord bericht</string>
|
||||
<string name="title_send_encryption">Versleuteling</string>
|
||||
<string name="title_send_priority">Prioriteit</string>
|
||||
<string name="title_no_server">Geen server gevonden op \'%1$s\'</string>
|
||||
|
|
@ -916,6 +919,7 @@
|
|||
<string name="title_extra_missing">Gebruikersnaam ontbreekt</string>
|
||||
<string name="title_to_missing">Ontvanger ontbreekt</string>
|
||||
<string name="title_pgp_reminder">PGP-sleutels beschikbaar</string>
|
||||
<string name="title_smime_reminder">S/MIME-sleutels beschikbaar</string>
|
||||
<string name="title_subject_reminder">Onderwerp is leeg</string>
|
||||
<string name="title_text_reminder">Bericht is leeg</string>
|
||||
<string name="title_attachment_keywords">bijlage,bijlagen</string>
|
||||
|
|
|
|||
|
|
@ -677,7 +677,6 @@
|
|||
<string name="title_duplicate_in">Dupliser melding i %1$s</string>
|
||||
<string name="title_subject_reply">Sv: %1$s</string>
|
||||
<string name="title_subject_forward">Videresend: %1$s</string>
|
||||
<string name="title_buttons">Knapper</string>
|
||||
<string name="title_seen">Merk som lest</string>
|
||||
<string name="title_unseen">Merk som ulest</string>
|
||||
<string name="title_toggle_seen">Skru av/på \"lest\"</string>
|
||||
|
|
|
|||
|
|
@ -677,7 +677,6 @@
|
|||
<string name="title_duplicate_in">Dupliser melding i %1$s</string>
|
||||
<string name="title_subject_reply">Sv: %1$s</string>
|
||||
<string name="title_subject_forward">Videresend: %1$s</string>
|
||||
<string name="title_buttons">Knapper</string>
|
||||
<string name="title_seen">Merk som lest</string>
|
||||
<string name="title_unseen">Merk som ulest</string>
|
||||
<string name="title_toggle_seen">Skru av/på \"lest\"</string>
|
||||
|
|
|
|||
|
|
@ -178,6 +178,7 @@
|
|||
<string name="title_setup_manage">Zarządzaj</string>
|
||||
<string name="title_setup_grant">Zezwól</string>
|
||||
<string name="title_setup_grant_again">Udziel wymaganych uprawnień</string>
|
||||
<string name="title_setup_exchange_support">Czy Microsoft Exchange jest wspierany?</string>
|
||||
<string name="title_setup_identity_what">Czym jest tożsamość?</string>
|
||||
<string name="title_setup_permissions">Przyznaj uprawnienia</string>
|
||||
<string name="title_setup_permissions_remark">Dostęp do kontaktów (opcjonalnie)</string>
|
||||
|
|
@ -311,6 +312,7 @@
|
|||
<string name="title_advanced_startup">Pokaż na ekranie początkowym</string>
|
||||
<string name="title_advanced_cards">Użyj stylu karty zamiast stylu tabelarycznego</string>
|
||||
<string name="title_advanced_cards_beige">Użyj beżowego tła, jeśli używasz stylu karty</string>
|
||||
<string name="title_advanced_cards_shadow">Użyj cienia do nieprzeczytanych wiadomości, jeśli używasz stylu karty</string>
|
||||
<string name="title_advanced_date_header">Grupuj według daty</string>
|
||||
<string name="title_advanced_threading">Konwersacje w wątkach</string>
|
||||
<string name="title_advanced_threading_unread">Pokaż liczbę nieprzeczytanych wiadomości w wątkach</string>
|
||||
|
|
@ -737,7 +739,6 @@
|
|||
<string name="title_duplicate_in">Duplikat wiadomości w %1$s</string>
|
||||
<string name="title_subject_reply">Odp: %1$s</string>
|
||||
<string name="title_subject_forward">Pd: %1$s</string>
|
||||
<string name="title_buttons">Przyciski</string>
|
||||
<string name="title_seen">Oznacz jako przeczytane</string>
|
||||
<string name="title_unseen">Oznacz jako nieprzeczytane</string>
|
||||
<string name="title_toggle_seen">Przeczytane/nieprzeczytane</string>
|
||||
|
|
@ -874,7 +875,7 @@
|
|||
<string name="title_send_now">Wyślij teraz</string>
|
||||
<string name="title_send_via">Wyślij przez</string>
|
||||
<string name="title_send_at">Wysłać o …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Archiwizuj wysłaną odpowiedź</string>
|
||||
<string name="title_send_auto_archive">Archiwizuj wysłaną odpowiedź</string>
|
||||
<string name="title_send_encryption">Szyfrowanie</string>
|
||||
<string name="title_send_priority">Priorytet</string>
|
||||
<string name="title_no_server">Nie znaleziono serwera na \'%1$s\'</string>
|
||||
|
|
@ -937,6 +938,7 @@
|
|||
<string name="title_extra_missing">Brak nazwy użytkownika</string>
|
||||
<string name="title_to_missing">Brak adresata</string>
|
||||
<string name="title_pgp_reminder">Klucze PGP dostępne</string>
|
||||
<string name="title_smime_reminder">Dostępne klucze S/MIME</string>
|
||||
<string name="title_subject_reminder">Temat jest pusty</string>
|
||||
<string name="title_text_reminder">Wiadomość jest pusta</string>
|
||||
<string name="title_attachment_keywords">załączony, załącznik, załączniki, w zestawie, w załączonym</string>
|
||||
|
|
|
|||
|
|
@ -640,7 +640,6 @@
|
|||
<string name="title_duplicate_in">Duplicar mensagem em %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Enc: %1$s</string>
|
||||
<string name="title_buttons">Botões</string>
|
||||
<string name="title_seen">Marcar como lida</string>
|
||||
<string name="title_unseen">Marcar como não lida</string>
|
||||
<string name="title_toggle_seen">Alternar status da leitura</string>
|
||||
|
|
|
|||
|
|
@ -168,6 +168,7 @@
|
|||
<string name="title_setup_manage">Gestionează</string>
|
||||
<string name="title_setup_grant">Acordă</string>
|
||||
<string name="title_setup_grant_again">Acordați permisiunile necesare</string>
|
||||
<string name="title_setup_exchange_support">Este Microsoft Exchange suportat?</string>
|
||||
<string name="title_setup_identity_what">Ce este o identitate?</string>
|
||||
<string name="title_setup_permissions">Acordă permisiuni</string>
|
||||
<string name="title_setup_permissions_remark">Pentru a obține informațiile contactelor (opțional)</string>
|
||||
|
|
@ -301,6 +302,7 @@
|
|||
<string name="title_advanced_startup">Arată pe ecranul de start</string>
|
||||
<string name="title_advanced_cards">Folosește stilul carduri în loc de cel tabular</string>
|
||||
<string name="title_advanced_cards_beige">Folosește fundalul bej când folosești stilul carduri</string>
|
||||
<string name="title_advanced_cards_shadow">Utilizează umbra pentru mesajele necitite când se folosește stilul card</string>
|
||||
<string name="title_advanced_date_header">Grupare după dată</string>
|
||||
<string name="title_advanced_threading">Aranjare mesaje în conversație</string>
|
||||
<string name="title_advanced_threading_unread">Arată numărul de mesaje necitite în conversații</string>
|
||||
|
|
@ -727,7 +729,6 @@
|
|||
<string name="title_duplicate_in">Mesaj duplicat în %1$s</string>
|
||||
<string name="title_subject_reply">Răsp: %1$s</string>
|
||||
<string name="title_subject_forward">Redir: %1$s</string>
|
||||
<string name="title_buttons">Butoane</string>
|
||||
<string name="title_seen">Marcare ca citit</string>
|
||||
<string name="title_unseen">Marcare ca necitit</string>
|
||||
<string name="title_toggle_seen">Comutare citire</string>
|
||||
|
|
@ -864,7 +865,7 @@
|
|||
<string name="title_send_now">Trimite acum</string>
|
||||
<string name="title_send_via">Trimite prin</string>
|
||||
<string name="title_send_at">Trimite la …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Arhivează mesajul citit</string>
|
||||
<string name="title_send_auto_archive">Arhivează mesajul citit</string>
|
||||
<string name="title_send_encryption">Criptare</string>
|
||||
<string name="title_send_priority">Prioritate</string>
|
||||
<string name="title_no_server">Nu există un server la \'%1$s\'</string>
|
||||
|
|
@ -927,6 +928,7 @@
|
|||
<string name="title_extra_missing">Lipsește numele de utilizator</string>
|
||||
<string name="title_to_missing">Destinatar lipsă</string>
|
||||
<string name="title_pgp_reminder">Chei PGP disponibile</string>
|
||||
<string name="title_smime_reminder">Chei S/MIME disponibile</string>
|
||||
<string name="title_subject_reminder">Subiectul este gol</string>
|
||||
<string name="title_text_reminder">Mesajul este gol</string>
|
||||
<string name="title_attachment_keywords">atasez,atasat,atasate,atsament,atașez,atașat,atașament</string>
|
||||
|
|
|
|||
|
|
@ -179,6 +179,7 @@
|
|||
<string name="title_setup_manage">Редактировать</string>
|
||||
<string name="title_setup_grant">Предоставить</string>
|
||||
<string name="title_setup_grant_again">Предоставить необходимые разрешения</string>
|
||||
<string name="title_setup_exchange_support">Поддерживается ли Microsoft Exchange?</string>
|
||||
<string name="title_setup_identity_what">Что такое идентификатор?</string>
|
||||
<string name="title_setup_permissions">Предоставить доступ</string>
|
||||
<string name="title_setup_permissions_remark">Доступ к контактной информации (необязательно)</string>
|
||||
|
|
@ -311,7 +312,8 @@
|
|||
<string name="title_advanced_landscape3">Показывать меню навигации в альбомном режиме по умолчанию</string>
|
||||
<string name="title_advanced_startup">При запуске показывать</string>
|
||||
<string name="title_advanced_cards">Использовать карточный стиль вместо табличного</string>
|
||||
<string name="title_advanced_cards_beige">Использовать бежевый фон при использовании карточного стиля</string>
|
||||
<string name="title_advanced_cards_beige">Использовать бежевый фон для карточного стиля</string>
|
||||
<string name="title_advanced_cards_shadow">Использовать тень для непрочитанных сообщений для карточного стиля</string>
|
||||
<string name="title_advanced_date_header">Группировать по дате</string>
|
||||
<string name="title_advanced_threading">Связанные диалоги</string>
|
||||
<string name="title_advanced_threading_unread">Показывать количество непрочитанных сообщений в диалогах</string>
|
||||
|
|
@ -738,7 +740,6 @@
|
|||
<string name="title_duplicate_in">Дубликат сообщения в %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Кнопки</string>
|
||||
<string name="title_seen">Отметить как прочитанное</string>
|
||||
<string name="title_unseen">Отметить как непрочитанное</string>
|
||||
<string name="title_toggle_seen">Прочитано/непрочитано</string>
|
||||
|
|
@ -875,7 +876,7 @@
|
|||
<string name="title_send_now">Отправить сейчас</string>
|
||||
<string name="title_send_via">Отправить через</string>
|
||||
<string name="title_send_at">Отправить в…</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Архивировать исходное сообщение</string>
|
||||
<string name="title_send_auto_archive">Архивировать исходное сообщение</string>
|
||||
<string name="title_send_encryption">Шифрование</string>
|
||||
<string name="title_send_priority">Приоритет</string>
|
||||
<string name="title_no_server">Сервер не найден на \"%1$s\"</string>
|
||||
|
|
@ -937,7 +938,8 @@
|
|||
<string name="title_from_missing">Отсутствует отправитель</string>
|
||||
<string name="title_extra_missing">Отсутствует имя пользователя</string>
|
||||
<string name="title_to_missing">Отсутствует получатель</string>
|
||||
<string name="title_pgp_reminder">Доступные PGP-ключи</string>
|
||||
<string name="title_pgp_reminder">Доступные ключи PGP</string>
|
||||
<string name="title_smime_reminder">Доступные ключи S/MIME</string>
|
||||
<string name="title_subject_reminder">Тема пустая</string>
|
||||
<string name="title_text_reminder">Сообщение пустое</string>
|
||||
<string name="title_attachment_keywords">attached,attachment,attachments,included,вложение,вложения,вложении,приложено</string>
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@
|
|||
<string name="app_search">Hľadanie FairEmail</string>
|
||||
<string name="app_changelog">Zoznam zmien</string>
|
||||
<string name="app_welcome">FairEmail je opensource aplikácia zameraná na súkromie a bezpečnosť. Z toho dôvodu môžu niektoré vlastnosti fungovať inak, ako ste zvyknutí.</string>
|
||||
<string name="app_limitations">Napríklad, správy sú implicitne preformátované aby sa odstránili nebezpečné elementy a zvýšila čitateľnosť, a otváranie odkazov je potrebné potvrdiť kvôli bezpečnosti. Obe nastavenia sa dajú podľa potreby vypnúť.</string>
|
||||
<string name="app_crash">FairEmail nie je podporovaný na tomto zariadení, pretože chyby v systéme spôsobujú pády</string>
|
||||
<string name="app_exit">Znova stlačte \"Späť\" pre ukončenie</string>
|
||||
<string name="app_cake">Nedostatok voľného miesta na úložisku</string>
|
||||
|
|
@ -138,12 +139,20 @@
|
|||
<string name="title_setup">Nastavenia</string>
|
||||
<string name="title_setup_help">Pomoc</string>
|
||||
<string name="title_setup_quick">Rýchle nastavenie</string>
|
||||
<string name="title_setup_quick_accounts">Pridať účty</string>
|
||||
<string name="title_setup_quick_support">Niektorí poskitovatelia.</string>
|
||||
<string name="title_setup_quick_hint">Rýchle nastavenie načíta informácie konfigurácie z autoconfig.thunderbird.net</string>
|
||||
<string name="title_setup_quick_imap">IMAP server na prijímanie správ</string>
|
||||
<string name="title_setup_quick_smtp">SMTP server na odosielanie správ</string>
|
||||
<string name="title_setup_wizard">Sprievodca</string>
|
||||
<string name="title_setup_wizard_multiple">Sprievodca môže byť použitý viac krát pre nastavenie viacerých účtov</string>
|
||||
<string name="title_setup_wizard_new">Potrebujem novú emailovú adresu</string>
|
||||
<string name="title_setup_manual">Manuálne nastavenie a viac možností</string>
|
||||
<string name="title_setup_account_remark">Obdržať email</string>
|
||||
<string name="title_setup_identity_remark">Poslať email</string>
|
||||
<string name="title_setup_account_identity_hint">Môžete nastaviť meno, farbu a akcie pre potiahnutie v nastaveniach konta, a nastaviť podpis v nastaveniach totožnosti</string>
|
||||
<string name="title_setup_accounts">Účty</string>
|
||||
<string name="title_setup_identities">Totožnosti</string>
|
||||
<string name="title_setup_oauth_permission">Poskytovateľ služby e-mail povolil autorizáciu použitím OAuth len pre oficiálne zostavenia aplikácii</string>
|
||||
<string name="title_setup_other">Iný poskytovateľ</string>
|
||||
<string name="title_setup_pop3">POP3 účet</string>
|
||||
|
|
@ -161,16 +170,20 @@
|
|||
<string name="title_setup_select_account">Vybrať účet</string>
|
||||
<string name="title_setup_instructions">Pokyny pre nastavenie</string>
|
||||
<string name="title_setup_no_settings">Neboli nájdené žiadne nastavenia pre doménu \"%1$s\"</string>
|
||||
<string name="title_setup_no_settings_hint">Skúste nastaviť účet ručne použitím nastavení poskytnutých vašim emailovým poskytovateľom</string>
|
||||
<string name="title_setup_no_auth_hint">Dvakrát skontrolujte vašu e-mailovú adresu a heslo a uistite sa, že v účte máte povolený externý prístup (protokoly IMAP a SMTP)</string>
|
||||
<string name="title_setup_app_password_hint">Tento poskytovateľ si vyžaduje použitie hesla aplikácie namiesto hesla účtu, skontrolujte pokyny vášho poskytovateľa</string>
|
||||
<string name="title_setup_no_inbox">Priečinok s doručenou poštou nebol nájdený</string>
|
||||
<string name="title_setup_advanced_protection">Ak využívate program rozšírenej ochrany Google, nie je možné používať emailových klientov tretích strán. Toto je obmedzenie stanovené samotným Googlom.</string>
|
||||
<string name="title_setup_quick_success">Účet bol úspešne pridaný</string>
|
||||
<string name="title_setup_manage">Spravovať</string>
|
||||
<string name="title_setup_grant">Udeliť</string>
|
||||
<string name="title_setup_grant_again">Udeliť požadované oprávnenia</string>
|
||||
<string name="title_setup_exchange_support">Je Microsoft Exchange podporovaný?</string>
|
||||
<string name="title_setup_identity_what">Čo je totožnosť?</string>
|
||||
<string name="title_setup_permissions">Udeliť oprávnenia</string>
|
||||
<string name="title_setup_permissions_remark">Prístup k informáciám kontaktov (voliteľné)</string>
|
||||
<string name="title_setup_doze">Vypnite optimalizáciu batérie</string>
|
||||
<string name="title_setup_doze_remark">Pre spoľahlivé prijímanie emailu</string>
|
||||
<string name="title_setup_doze_hint">Môže sa zdať, že opak je pravdou, no vypnutím optimalizácie batérie ušetríte využitie pri napájaní z batérie</string>
|
||||
<string name="title_setup_doze_instructions">V nasledujúcom dialógovom okne zvoľte \"Všetky aplikácie\" navrchu, vyberte túto aplikáciu a potvrďte \"Neoptimalizovať\"</string>
|
||||
|
|
@ -178,6 +191,7 @@
|
|||
<string name="title_setup_doze_stopped">Zastavila sa synchronizácia?</string>
|
||||
<string name="title_setup_data">Šetrenie údajov je povolené</string>
|
||||
<string name="title_setup_advanced_options">Zobraziť rozšírené možnosti</string>
|
||||
<string name="title_setup_inbox">Prejsť do schránky</string>
|
||||
<string name="title_setup_go">Spustiť</string>
|
||||
<string name="title_setup_to_do">Dokončiť</string>
|
||||
<string name="title_setup_done">Hotovo</string>
|
||||
|
|
@ -217,6 +231,7 @@
|
|||
<string name="title_setup_theme_system">Prispôsobiť sa systému</string>
|
||||
<string name="title_setup_theme_black_background">Čierne pozadie</string>
|
||||
<string name="title_setup_theme_system_hint">Táto možnosť automaticky prepne na svetlý alebo tmavý motív podľa toho, či je zariadenie v dennom alebo nočnom režime, ak sú podporované systémom</string>
|
||||
<string name="title_setup_theme_more_colors">Chcem viac farieb</string>
|
||||
<string name="title_setup_advanced">Pokročilé</string>
|
||||
<string name="title_setup_options">Možnosti</string>
|
||||
<string name="title_setup_defaults">Obnoviť predvolené</string>
|
||||
|
|
@ -700,7 +715,6 @@ Nastavenie vždy toto kompenzuje neustálym sledovaním zmien.</string>
|
|||
<string name="title_duplicate_in">Duplicitná správa v priečinku %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Tlačidlá</string>
|
||||
<string name="title_seen">Označiť ako prečítané</string>
|
||||
<string name="title_unseen">Označiť ako neprečítané</string>
|
||||
<string name="title_toggle_seen">Prepnúť prečítanie</string>
|
||||
|
|
|
|||
|
|
@ -688,7 +688,6 @@
|
|||
<string name="title_duplicate_in">Duplicerade meddelande i %1$s</string>
|
||||
<string name="title_subject_reply">Sv: %1$s</string>
|
||||
<string name="title_subject_forward">Vb: %1$s</string>
|
||||
<string name="title_buttons">Knappar</string>
|
||||
<string name="title_seen">Märk som läst</string>
|
||||
<string name="title_unseen">Märk som oläst</string>
|
||||
<string name="title_toggle_seen">Växla lästa</string>
|
||||
|
|
|
|||
|
|
@ -692,7 +692,6 @@
|
|||
<string name="title_duplicate_in">Mesajı %1$s klasörüne kopyala</string>
|
||||
<string name="title_subject_reply">Ynt: %1$s</string>
|
||||
<string name="title_subject_forward">İlet: %1$s</string>
|
||||
<string name="title_buttons">Düğmeler</string>
|
||||
<string name="title_seen">Okundu olarak işaretle</string>
|
||||
<string name="title_unseen">Okunmadı olarak işaretle</string>
|
||||
<string name="title_toggle_seen">Okumayı aç/kapat</string>
|
||||
|
|
|
|||
|
|
@ -725,7 +725,6 @@
|
|||
<string name="title_duplicate_in">Дублювати повідомлення в %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">Fwd: %1$s</string>
|
||||
<string name="title_buttons">Кнопки</string>
|
||||
<string name="title_seen">Позначити як прочитане</string>
|
||||
<string name="title_unseen">Позначити як непрочитане</string>
|
||||
<string name="title_toggle_seen">Перемкнути статус прочитано</string>
|
||||
|
|
@ -862,7 +861,7 @@
|
|||
<string name="title_send_now">Надіслати зараз</string>
|
||||
<string name="title_send_via">Надіслати через</string>
|
||||
<string name="title_send_at">Надіслати о …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">Архівувати повідомлення з відповіддю</string>
|
||||
<string name="title_send_auto_archive">Архівувати повідомлення з відповіддю</string>
|
||||
<string name="title_send_encryption">Шифрування</string>
|
||||
<string name="title_send_priority">Пріоритет</string>
|
||||
<string name="title_no_server">Сервер не знайдено на \'%1$s\'</string>
|
||||
|
|
|
|||
|
|
@ -145,6 +145,7 @@
|
|||
<string name="title_setup_manage">管理</string>
|
||||
<string name="title_setup_grant">授权</string>
|
||||
<string name="title_setup_grant_again">授予所需权限</string>
|
||||
<string name="title_setup_exchange_support">是否支持 Microsoft Exchange？</string>
|
||||
<string name="title_setup_identity_what">什么是身份？</string>
|
||||
<string name="title_setup_permissions">授予权限</string>
|
||||
<string name="title_setup_permissions_remark">获取联系人信息(可选)</string>
|
||||
|
|
@ -278,6 +279,7 @@
|
|||
<string name="title_advanced_startup">在启动屏幕上显示</string>
|
||||
<string name="title_advanced_cards">使用卡片样式而非表单样式 (即主页会话间有间隔)</string>
|
||||
<string name="title_advanced_cards_beige">开启卡片样式 (上面的选项) 时，使用米色背景</string>
|
||||
<string name="title_advanced_cards_shadow">使用卡片样式时对未读信件使用阴影</string>
|
||||
<string name="title_advanced_date_header">按日期分组</string>
|
||||
<string name="title_advanced_threading">会话线程</string>
|
||||
<string name="title_advanced_threading_unread">在对话中显示未读消息的数量</string>
|
||||
|
|
@ -704,7 +706,6 @@
|
|||
<string name="title_duplicate_in">%1$s 中的重复消息</string>
|
||||
<string name="title_subject_reply">回复：%1$s</string>
|
||||
<string name="title_subject_forward">转发：%1$s</string>
|
||||
<string name="title_buttons">按钮</string>
|
||||
<string name="title_seen">标记为已读</string>
|
||||
<string name="title_unseen">标记为未读</string>
|
||||
<string name="title_toggle_seen">切换已读状态</string>
|
||||
|
|
@ -841,7 +842,7 @@
|
|||
<string name="title_send_now">立即发送</string>
|
||||
<string name="title_send_via">发送方式</string>
|
||||
<string name="title_send_at">发送于 …</string>
|
||||
<string name="title_send_auto_archive" comment="title_send_auto_archive Title for checkbox to move replied to message to the archive folder on sending the reply. ">存档回复消息</string>
|
||||
<string name="title_send_auto_archive">存档回复消息</string>
|
||||
<string name="title_send_encryption">加密</string>
|
||||
<string name="title_send_priority">优先级</string>
|
||||
<string name="title_no_server">在 \'%1$s\' 找不到服务器</string>
|
||||
|
|
@ -904,6 +905,7 @@
|
|||
<string name="title_extra_missing">缺少用户名</string>
|
||||
<string name="title_to_missing">缺少收件人</string>
|
||||
<string name="title_pgp_reminder">PGP 密钥可用</string>
|
||||
<string name="title_smime_reminder">有 S/MIME 密钥可用</string>
|
||||
<string name="title_subject_reminder">主题为空</string>
|
||||
<string name="title_text_reminder">消息为空</string>
|
||||
<string name="title_attachment_keywords">至少包含一个附件</string>
|
||||
|
|
|
|||
|
|
@ -663,7 +663,6 @@
|
|||
<string name="title_duplicate_in">消息重複 %1$s</string>
|
||||
<string name="title_subject_reply">Re: %1$s</string>
|
||||
<string name="title_subject_forward">正向： %1$s</string>
|
||||
<string name="title_buttons">按鈕</string>
|
||||
<string name="title_seen">標記為已讀</string>
|
||||
<string name="title_unseen">標記為未讀</string>
|
||||
<string name="title_toggle_seen">切換閱讀</string>
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -166,10 +166,10 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(42) Můžete na seznam poskytovatelů přidat nového poskytovatele?](#user-content-faq42)
|
||||
* [(43) Můžete ukázat originální ... ?](#user-content-faq43)
|
||||
* [(44) Můžete zobrazit fotografie kontaktů / identikony v odeslané složce?](#user-content-faq44)
|
||||
* [(45) Jak mohu opravit 'tento klíč není k dispozici. Abyste jej mohli použít, musíte ho importovat jako jeden z vlastní!" ?](#user-content-faq45)
|
||||
* [(45) Jak mohu opravit „This key is not available. To use it, you must import it as one of your own!“ ?](#user-content-faq45)
|
||||
* [(46) Proč se seznam zpráv stále obnovuje?](#user-content-faq46)
|
||||
* [(47) Jak vyřeším chybu 'Žádný primární účet nebo žádná složka konceptů' ?](#user-content-faq47)
|
||||
* [~~(48) Jak vyřeším chybu 'Žádný primární účet nebo žádná složka konceptů' ?~~](#user-content-faq48)
|
||||
* [(47) Jak vyřeším chybu „Žádný hlavní účet nebo žádná složka konceptů“ ?](#user-content-faq47)
|
||||
* [~~(48) Jak vyřeším chybu „Žádný hlavní účet nebo žádná složka konceptů“ ?~~](#user-content-faq48)
|
||||
* [(49) How do I fix 'An outdated app sent a file path instead of a file stream' ?](#user-content-faq49)
|
||||
* [(50) Can you add an option to synchronize all messages?](#user-content-faq50)
|
||||
* [(51) Jak jsou složky řazeny?](#user-content-faq51)
|
||||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ Designet baserer sig på mange debatter, så ønsks det debatteret yderligere, t
|
|||
* [(162) Understøttes IMAP NOTIFICERING?](#user-content-faq162)
|
||||
* [(163) Hvad er beskedklassificering?](#user-content-faq163)
|
||||
* [(164) Kan der blive tilføjet tilpasselige temaer?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[Har et andet spørgsmål.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -864,7 +871,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
**General errors**
|
||||
|
||||
<a name="authfailed"></a>
|
||||
Fejlen *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to set up a Yahoo account.
|
||||
|
||||
|
|
@ -874,11 +881,11 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
|
|||
|
||||
Fejlen *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
|
||||
|
||||
Fejlen *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
|
||||
The error *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
|
||||
|
||||
Fejlen *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
|
||||
The error *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
|
||||
|
||||
Fejlen *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
|
||||
The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
|
||||
|
||||
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
|
||||
|
||||
|
|
@ -889,7 +896,7 @@ The error *... Connection closed by peer ...* might be caused by a not updated E
|
|||
The errors *... Read error ...*, *... Write error ...*, *... Read timed out ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
|
||||
|
||||
<a name="connectiondropped"></a>
|
||||
Fejlen *... Connection dropped by server? ...* means that the email server unexpectedly terminated the connection. This sometimes happen when there were too many connections in a too short time or when a wrong password was used for too many times. In this case, please make sure your password is correct and disable receiving in the receive settings for about 30 minutes and try again. If needed, see [this FAQ](#user-content-faq23) about how you can reduce the number of connections.
|
||||
The error *... Connection dropped by server? ...* means that the email server unexpectedly terminated the connection. This sometimes happen when there were too many connections in a too short time or when a wrong password was used for too many times. In this case, please make sure your password is correct and disable receiving in the receive settings for about 30 minutes and try again. If needed, see [this FAQ](#user-content-faq23) about how you can reduce the number of connections.
|
||||
|
||||
The error *... Unexpected end of zlib input stream ...* means that not all data was received, possibly due to a bad or interrupted connection.
|
||||
|
||||
|
|
@ -949,11 +956,11 @@ The authorization of Gmail accounts setup with the quick wizard needs to be peri
|
|||
|
||||
In case of errors it is possible to authorize/restore a Gmail account again via the Gmail quick setup wizard.
|
||||
|
||||
The error *... Godkendelse mislykkedes... Account not found ...* means that a previously authorized Gmail account was removed from the device.
|
||||
The error *... Authentication failed ... Account not found ...* means that a previously authorized Gmail account was removed from the device.
|
||||
|
||||
The errors *... Authentication failed ... No token ...* means that the Android account manager failed to refresh the authorization of a Gmail account.
|
||||
|
||||
Fejlen *... Authentication failed ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
|
||||
The error *... Authentication failed ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
|
||||
|
||||
The error *... Authentication failed ... Invalid credentials ...* could be caused by changing the account password or by having revoked the required account/contacts permissions. In case the account password was changed, you'll need to authenticate the Google account in the Android account settings again. In case the permissions were revoked, you can start the Gmail quick setup wizard to grant the required permissions again (you don't need to setup the account again).
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Wird IMAP NOTIFY unterstützt?](#user-content-faq162)
|
||||
* [(163) Was ist Nachrichtenklassifizierung?](#user-content-faq163)
|
||||
* [(164) Können Sie anpassbare Designs hinzufügen?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Support erhalten
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Wird IMAP NOTIFY unterstützt?](#user-content-faq162)
|
||||
* [(163) Was ist Nachrichtenklassifizierung?](#user-content-faq163)
|
||||
* [(164) Können Sie anpassbare Designs hinzufügen?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Support erhalten
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Wird IMAP NOTIFY unterstützt?](#user-content-faq162)
|
||||
* [(163) Was ist Nachrichtenklassifizierung?](#user-content-faq163)
|
||||
* [(164) Können Sie anpassbare Designs hinzufügen?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Support erhalten
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) ¿Se admite el sistema IMAP NOTIFY?](#user-content-faq162)
|
||||
* [(163) ¿Qué es la clasificación de mensajes?](#user-content-faq163)
|
||||
* [(164) ¿Puedes añadir temas personalizables?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -864,7 +871,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
**General errors**
|
||||
|
||||
<a name="authfailed"></a>
|
||||
El error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to set up a Yahoo account.
|
||||
|
||||
|
|
@ -872,11 +879,11 @@ The message *... +OK ...* likely means that a POP3 port (usually port number 995
|
|||
|
||||
The errors *... invalid greeting ...*, *... requires valid address ...* and *... Parameter to HELO does not conform to RFC syntax ...* can likely be solved by changing the advanced identity setting *Use local IP address instead of host name*.
|
||||
|
||||
El error *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
|
||||
The error *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
|
||||
|
||||
The error *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
|
||||
|
||||
El error *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
|
||||
The error *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
|
||||
|
||||
The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
|
|||
* [(162) L'IMAP NOTIFY est-il pris en charge ?](#user-content-faq162)
|
||||
* [(163) Qu'est-ce que la classification des messages ?](#user-content-faq163)
|
||||
* [(164) Pouvez-vous ajouter des thèmes personnalisables ?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[J’ai une autre question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Certains fournisseurs ne gardent pas de trace des messages envoyés ou le serveu
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Obtenir de l'aide
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ La conception est basée sur de nombreuses discussions et si vous le souhaitez,
|
|||
* [(162) L'IMAP NOTIFY est-il pris en charge ?](#user-content-faq162)
|
||||
* [(163) Qu'est-ce que la classification des messages ?](#user-content-faq163)
|
||||
* [(164) Pouvez-vous ajouter des thèmes personnalisables ?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[J’ai une autre question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Certains fournisseurs ne gardent pas de trace des messages envoyés ou le serveu
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Obtenir de l'aide
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) IMAP NOTIFY è supportato?](#user-content-faq162)
|
||||
* [(163) Cos'è la classificazione dei messaggi?](#user-content-faq163)
|
||||
* [(164) Puoi aggiungere temi personalizzabili?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -864,7 +871,7 @@ There are general errors and errors specific to Gmail accounts (see below).
|
|||
**General errors**
|
||||
|
||||
<a name="authfailed"></a>
|
||||
L'errore *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
|
||||
|
||||
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to set up a Yahoo account.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Ricevi supporto
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Wsparcie
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) Что такое классификация сообщений?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# FairEmail support
|
||||
# FairEmail podpora
|
||||
|
||||
If you have a question, please check the following frequently asked questions first. [At the bottom](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), you can find out how to ask other questions, request features, and report bugs.
|
||||
|
||||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Stöds IMAP NOTIFY?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
|
|
@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
|||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
|
|
@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
|||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
|
||||
|
||||
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
|
||||
|
|
@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
|||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
|
|
@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
|||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
|
|
@ -647,7 +654,7 @@ Common errors:
|
|||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
|
|
@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
|||
|
||||
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
|
||||
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
|
|
@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
|||
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL --es account Gmail
|
||||
```
|
||||
|
||||
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE
|
||||
```
|
||||
|
||||
To enable/disable a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
|
|
@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
|||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
|
|
@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
|||
|
||||
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
|
||||
|
||||
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
|
||||
|
||||
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
|
||||
|
||||
<br />
|
||||
|
|
@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
|||
This command can be sent to FairEmail from an automation app to update the protection lists:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISCONNECT.ME
|
||||
```
|
||||
|
||||
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
|
||||
|
|
@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
|||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
|
|
|||
Loading…
Reference in New Issue