<stringname="title_advanced_color_threshold">Mezní hodnota barvy písmena: %1$s %%</string>
<stringname="title_advanced_name_email">Zobrazit jména a e-mailové adresy</string>
<stringname="title_advanced_replace_name">Preferovat jméno z kontaktu namísto z hlavičky</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Zobrazit pouze jména kontaktů</string>
<stringname="title_advanced_only_name">Zobrazit pouze jména kontaktů</string>
<stringname="title_advanced_distinguish_contacts">Podtrhnout odesílatele, je-li známý jako lokální „komu“ kontakt</string>
<stringname="title_advanced_show_recipients">Zobrazit příjemce v hlavičce zprávy</string>
<stringname="title_advanced_font_size_sender">Velikost textu odesílatele</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Vis kun kontaktnavne</string>
<stringname="title_advanced_only_name">Vis kun kontaktnavne</string>
<stringname="title_advanced_distinguish_contacts">Understreg afsender, når denne er kendt som lokal \'Til\'-kontakt</string>
<stringname="title_advanced_show_recipients">Vis modtagere i beskedhoved</string>
<stringname="title_advanced_sync_folders_hint">Deaktivering af dette reducerer data- og strømforbruget noget, men deaktiverer også mappelisteopdatering</string>
<stringname="title_advanced_lookup_mx_hint">Dette tjekker, om der findes DNS MX-poster</string>
<stringname="title_advanced_sync_delay_hint">Dette vil forøge beskedsynkroniseringstiden</string>
<stringname="title_advanced_suggest_names_hint">Hvis deaktiveret, bruges kun e-mailadresser ved valg af kontakter</string>
<stringname="title_advanced_suggest_local_hint">Ud over kontakter fra Android. Kontaktdata gemmes kun for nyligt afsendte eller modtagne beskeder, når aktiveret.</string>
<stringname="title_advanced_usenet_hint">Indsæt \'-- \' mellem teksten og signaturen</string>
<stringname="title_advanced_send_reminders_hint">Vis en advarsel, når beskedtekst eller emne er tomt, eller en vedhæftet fil muligvis mangler</string>
<stringname="title_advanced_name_email">Namen und E-Mail-Adressen anzeigen</string>
<stringname="title_advanced_replace_name">Einen Kontaktnamen gegenüber einem gesendeten Namen bevorzugen</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Nur Kontaktnamen anzeigen</string>
<stringname="title_advanced_distinguish_contacts">Den Sender unterstrichen darstellen, wenn er ein bekannter lokaler An-Kontakt ist</string>
<stringname="title_advanced_show_recipients">Empfänger im Nachrichtenkopf anzeigen</string>
<stringname="title_advanced_font_size_sender">Schriftgröße für den Absender</string>
@ -476,6 +477,7 @@
<stringname="title_advanced_check_reply_hint">Überprüft, ob die Domain des Absenders und der Antwort-An-Adresse gleich sind</string>
<stringname="title_advanced_lookup_mx_hint">Überprüft, ob DNS-MX-Einträge vorhanden sind</string>
<stringname="title_advanced_sync_delay_hint">Dies verzögert die Synchronisierung von Nachrichten</string>
<stringname="title_advanced_suggest_names_hint">Wenn deaktiviert, werden nur E-Mail-Adressen bei der Auswahl von Kontakten verwendet</string>
<stringname="title_advanced_suggest_local_hint">Zusätzlich zu den von Android bereitgestellten Kontakten werden weitere Kontaktdaten für neue gesendete oder erhaltene Nachrichten nur dann gespeichert, wenn dies aktiviert ist.</string>
<stringname="title_advanced_usenet_hint">Signaturtrenner »-- « zwischen Text und Signatur einfügen</string>
<stringname="title_advanced_send_reminders_hint">Eine Warnung anzeigen, wenn der Nachrichtentext oder der Betreff leer ist oder wenn ein Anhang zu fehlen scheint</string>
<stringname="title_advanced_highlight_hint">Die Akzentfarbe des Designs wird zur Hervorhebung verwendet</string>
<stringname="title_advanced_gravatars_hint">Es könnte ein Datenschutzrisiko geben</string>
@ -530,7 +533,7 @@
<stringname="title_advanced_english_hint">Dadurch wird die App neu gestartet</string>
<stringname="title_advanced_experiments_hint">Liste der aktuellen experimentellen Funktionen</string>
<stringname="title_advanced_protocol_hint">Dadurch wird der Akku- und Speicherplatzverbrauch erheblich erhöht!</string>
<stringname="title_advanced_debug_hint">Dadurch werden an verschiedenen Stellen unschöne Debug-Informationen angezeigt</string>
<stringname="title_advanced_debug_hint">Dadurch werden an verschiedenen Stellen unschöne Fehlersuchinformationen angezeigt</string>
<stringname="title_advanced_cleanup_attachments_hint">Beim manuellen Bereinigen werden Anhänge von Nachrichten entfernt, die nicht mehr synchronisiert werden</string>
<stringname="title_advanced_cleanup_hint">Dies löscht alle temporären Dateien</string>
<stringname="title_advanced_name_email">Namen und E-Mail-Adressen anzeigen</string>
<stringname="title_advanced_replace_name">Einen Kontaktnamen gegenüber einem gesendeten Namen bevorzugen</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Nur Kontaktnamen anzeigen</string>
<stringname="title_advanced_distinguish_contacts">Den Sender unterstrichen darstellen, wenn er ein bekannter lokaler An-Kontakt ist</string>
<stringname="title_advanced_show_recipients">Empfänger im Nachrichtenkopf anzeigen</string>
<stringname="title_advanced_font_size_sender">Schriftgröße für den Absender</string>
@ -476,6 +477,7 @@
<stringname="title_advanced_check_reply_hint">Überprüft, ob die Domain des Absenders und der Antwort-An-Adresse gleich sind</string>
<stringname="title_advanced_lookup_mx_hint">Überprüft, ob DNS-MX-Einträge vorhanden sind</string>
<stringname="title_advanced_sync_delay_hint">Dies verzögert die Synchronisierung von Nachrichten</string>
<stringname="title_advanced_suggest_names_hint">Wenn deaktiviert, werden nur E-Mail-Adressen bei der Auswahl von Kontakten verwendet</string>
<stringname="title_advanced_suggest_local_hint">Zusätzlich zu den von Android bereitgestellten Kontakten werden weitere Kontaktdaten für neue gesendete oder erhaltene Nachrichten nur dann gespeichert, wenn dies aktiviert ist.</string>
<stringname="title_advanced_usenet_hint">Signaturtrenner »-- « zwischen Text und Signatur einfügen</string>
<stringname="title_advanced_send_reminders_hint">Eine Warnung anzeigen, wenn der Nachrichtentext oder der Betreff leer ist oder wenn ein Anhang zu fehlen scheint</string>
<stringname="title_advanced_highlight_hint">Die Akzentfarbe des Designs wird zur Hervorhebung verwendet</string>
<stringname="title_advanced_gravatars_hint">Es könnte ein Datenschutzrisiko geben</string>
@ -530,7 +533,7 @@
<stringname="title_advanced_english_hint">Dadurch wird die App neu gestartet</string>
<stringname="title_advanced_experiments_hint">Liste der aktuellen experimentellen Funktionen</string>
<stringname="title_advanced_protocol_hint">Dadurch wird der Akku- und Speicherplatzverbrauch erheblich erhöht!</string>
<stringname="title_advanced_debug_hint">Dadurch werden an verschiedenen Stellen unschöne Debug-Informationen angezeigt</string>
<stringname="title_advanced_debug_hint">Dadurch werden an verschiedenen Stellen unschöne Fehlersuchinformationen angezeigt</string>
<stringname="title_advanced_cleanup_attachments_hint">Beim manuellen Bereinigen werden Anhänge von Nachrichten entfernt, die nicht mehr synchronisiert werden</string>
<stringname="title_advanced_cleanup_hint">Dies löscht alle temporären Dateien</string>
<stringname="title_advanced_name_email">Namen und E-Mail-Adressen anzeigen</string>
<stringname="title_advanced_replace_name">Einen Kontaktnamen gegenüber einem gesendeten Namen bevorzugen</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Nur Kontaktnamen anzeigen</string>
<stringname="title_advanced_distinguish_contacts">Den Sender unterstrichen darstellen, wenn er ein bekannter lokaler An-Kontakt ist</string>
<stringname="title_advanced_show_recipients">Empfänger im Nachrichtenkopf anzeigen</string>
<stringname="title_advanced_font_size_sender">Schriftgröße für den Absender</string>
@ -476,6 +477,7 @@
<stringname="title_advanced_check_reply_hint">Überprüft, ob die Domain des Absenders und der Antwort-An-Adresse gleich sind</string>
<stringname="title_advanced_lookup_mx_hint">Überprüft, ob DNS-MX-Einträge vorhanden sind</string>
<stringname="title_advanced_sync_delay_hint">Dies verzögert die Synchronisierung von Nachrichten</string>
<stringname="title_advanced_suggest_names_hint">Wenn deaktiviert, werden nur E-Mail-Adressen bei der Auswahl von Kontakten verwendet</string>
<stringname="title_advanced_suggest_local_hint">Zusätzlich zu den von Android bereitgestellten Kontakten werden weitere Kontaktdaten für neue gesendete oder erhaltene Nachrichten nur dann gespeichert, wenn dies aktiviert ist.</string>
<stringname="title_advanced_usenet_hint">Signaturtrenner »-- « zwischen Text und Signatur einfügen</string>
<stringname="title_advanced_send_reminders_hint">Eine Warnung anzeigen, wenn der Nachrichtentext oder der Betreff leer ist oder wenn ein Anhang zu fehlen scheint</string>
<stringname="title_advanced_highlight_hint">Die Akzentfarbe des Designs wird zur Hervorhebung verwendet</string>
<stringname="title_advanced_gravatars_hint">Es könnte ein Datenschutzrisiko geben</string>
@ -530,7 +533,7 @@
<stringname="title_advanced_english_hint">Dadurch wird die App neu gestartet</string>
<stringname="title_advanced_experiments_hint">Liste der aktuellen experimentellen Funktionen</string>
<stringname="title_advanced_protocol_hint">Dadurch wird der Akku- und Speicherplatzverbrauch erheblich erhöht!</string>
<stringname="title_advanced_debug_hint">Dadurch werden an verschiedenen Stellen unschöne Debug-Informationen angezeigt</string>
<stringname="title_advanced_debug_hint">Dadurch werden an verschiedenen Stellen unschöne Fehlersuchinformationen angezeigt</string>
<stringname="title_advanced_cleanup_attachments_hint">Beim manuellen Bereinigen werden Anhänge von Nachrichten entfernt, die nicht mehr synchronisiert werden</string>
<stringname="title_advanced_cleanup_hint">Dies löscht alle temporären Dateien</string>
<stringname="title_advanced_suggest_sent">Προτείνονται διευθύνσεις που βρέθηκαν σε απεσταλμένα μηνύματα</string>
<stringname="title_advanced_suggest_received">Προτείνονται διευθύνσεις που βρέθηκαν σε μηνύματα που έχουν ληφθεί</string>
@ -312,7 +313,7 @@
<stringname="title_advanced_color_threshold">Κατώφλι για τον καθορισμό του χρώματος του γράμματος: %1$s%%</string>
<stringname="title_advanced_name_email">Να προβάλλονται τα ονόματα και οι διευθύνσεις ηλεκτρονικού ταχυδρομείου</string>
<stringname="title_advanced_replace_name">Να προτιμάται το όνομα της επαφής αντί για το όνομα του αποστολέα</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Να προβάλλονται μόνο τα ονόματα των επαφών</string>
<stringname="title_advanced_only_name">Να προβάλλονται μόνο τα ονόματα των επαφών</string>
<stringname="title_advanced_distinguish_contacts">Να υπογραμμίζεται ο αποστολέας όταν ο αποστολέας είναι γνωστός ως τοπική επαφή</string>
<stringname="title_advanced_show_recipients">Να προβάλλονται οι παραλήπτες στην κεφαλίδα του μηνύματος</string>
<stringname="title_advanced_font_size_sender">Μέγεθος γραμματοσειράς για το πεδίο \"Αποστολέας\"</string>
@ -473,6 +474,7 @@
<stringname="title_advanced_check_reply_hint">Ελέγχει αν το το όνομα τομέα του αποστολέα και η διεύθυνση απάντησης είναι ίδια</string>
<stringname="title_advanced_lookup_mx_hint">Ελέγχει αν υπάρχουν καταγραφές DNS MX</string>
<stringname="title_advanced_sync_delay_hint">Η επιλογή αυτή θα επιβραδύνει τον συγχρονισμό των μηνυμάτων</string>
<stringname="title_advanced_suggest_names_hint">Εάν απενεργοποιηθεί, θα χρησιμοποιούνται μόνο διευθύνσεις ηλ. ταχυδρομείου κατά την επιλογή επαφών</string>
<stringname="title_advanced_suggest_local_hint">Επιπρόσθετα στις παρεχόμενες από το Android επαφές, θα αποθηκεύονται πληροφορίες επαφών για πρόσφατα απεσταλμένα ή ειλημμένα μηνύματα, μόνον εφόσον οι σχετικές δυνατότητες έχουν ενεργοποιηθεί.</string>
<stringname="title_advanced_usenet_hint">Να παρεμβάλλεται ένα \'-- \' ανάμεσα στο κείμενο και την υπογραφή</string>
<stringname="title_advanced_send_reminders_hint">Να προβάλλεται μια προειδοποίηση όταν το κείμενο του μηνύματος ή το θέμα είναι κενό ή όταν φαίνεται πως ένα συνημμένο λείπει</string>
<stringname="title_advanced_suggest_sent">Sugerir direcciones encontradas en mensajes enviados</string>
<stringname="title_advanced_suggest_received">Sugerir direcciones encontradas en mensajes recibidos</string>
@ -312,7 +313,7 @@
<stringname="title_advanced_color_threshold">Umbral de color de letras: %1$s %%</string>
<stringname="title_advanced_name_email">Mostrar nombres y direcciones de correo electrónico</string>
<stringname="title_advanced_replace_name">Preferir un nombre de contacto sobre un nombre enviado</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Mostrar sólo nombres de contactos</string>
<stringname="title_advanced_only_name">Mostrar sólo nombres de contactos</string>
<stringname="title_advanced_distinguish_contacts">Subrayar el remitente cuando el remitente es conocido como contacto \'a:\' local</string>
<stringname="title_advanced_show_recipients">Mostrar destinatarios en el encabezado del mensaje</string>
<stringname="title_advanced_font_size_sender">Tamaño de fuente de remitente</string>
@ -475,6 +476,7 @@
<stringname="title_advanced_check_reply_hint">Esto comprobará si el nombre de dominio del remitente y la dirección de respuesta son los mismos</string>
<stringname="title_advanced_lookup_mx_hint">Esto comprobará si existen registros DNS MX</string>
<stringname="title_advanced_sync_delay_hint">Esto ralentizará la sincronización de mensajes</string>
<stringname="title_advanced_suggest_names_hint">Si está desactivado, sólo se usarán direcciones de correo electrónico al seleccionar contactos</string>
<stringname="title_advanced_suggest_local_hint">Además de los contactos proporcionados por Android, los datos de contactos se almacenarán para nuevos mensajes enviados o recibidos sólo cuando esté activado.</string>
<stringname="title_advanced_usenet_hint">Insertar \'-- \' entre el texto y la firma</string>
<stringname="title_advanced_send_reminders_hint">Mostrar una advertencia cuando el texto del mensaje o el asunto estén vacíos o cuando un archivo adjunto pueda estar ausente</string>
@ -491,6 +493,7 @@
<stringname="title_advanced_beige_hint">Sólo temas claros</string>
<stringname="title_advanced_date_hint">Los mensajes sólo se agrupan por fecha si se ordenan por antigüedad</string>
<stringname="title_advanced_navbar_colorize_hint">Que esto funcione dependerá de la versión y variante de Android</string>
<stringname="title_advanced_split_hint">Esto dividirá la pantalla en partes</string>
<stringname="title_advanced_threading_hint">Agrupar mensajes relacionados entre sí</string>
<stringname="title_advanced_highlight_hint">El color de acento del tema se utilizará para resaltar</string>
<stringname="title_advanced_gravatars_hint">Puede haber un riesgo para la privacidad</string>
<stringname="title_advanced_tune_keep_alive">Ajuster automatiquement l\'intervalle de connexion</string>
<stringname="title_advanced_keyboard">Afficher le clavier par défaut</string>
<stringname="title_advanced_keyboard_no_fullscreen">Ne pas afficher le clavier en plein écran</string>
<stringname="title_advanced_suggest_names">Utiliser les noms et les adresses courriel</string>
<stringname="title_advanced_suggest_local">Suggérer les contacts stockés localement</string>
<stringname="title_advanced_suggest_sent">Suggérer les adresses trouvées dans les messages envoyés</string>
<stringname="title_advanced_suggest_received">Suggérer les adresses trouvées dans les messages reçus</string>
@ -312,7 +313,7 @@
<stringname="title_advanced_color_threshold">Seuil de couleur de lettre : %1$s %%</string>
<stringname="title_advanced_name_email">Afficher les noms et les adresses courriel</string>
<stringname="title_advanced_replace_name">Préférer un nom de contact à un nom d’envoi</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Afficher uniquement le nom des contacts</string>
<stringname="title_advanced_only_name">Afficher uniquement le nom des contacts</string>
<stringname="title_advanced_distinguish_contacts">Souligner l’expéditeur quand il est connu comme contact local</string>
<stringname="title_advanced_show_recipients">Afficher les destinataires dans l’en-tête du message</string>
<stringname="title_advanced_font_size_sender">Taille de police du champ «Expéditeur»</string>
@ -475,6 +476,7 @@
<stringname="title_advanced_check_reply_hint">Ceci vérifiera si le nom de domaine de l\'expéditeur et l\'adresse de réponse sont les mêmes</string>
<stringname="title_advanced_lookup_mx_hint">Ceci vérifiera si des enregistrements MX DNS existent</string>
<stringname="title_advanced_sync_delay_hint">Ceci ralentira la synchronisation des messages</string>
<stringname="title_advanced_suggest_names_hint">Si désactivé, seules les adresses courriel seront utilisées lors de la sélection des contacts</string>
<stringname="title_advanced_suggest_local_hint">En plus des contacts fournis par Android. Les données de contact seront stockées pour les messages récemment envoyés ou reçus uniquement lorsque ceci est activé.</string>
<stringname="title_advanced_usenet_hint">Insérer -- entre le texte et la signature</string>
<stringname="title_advanced_send_reminders_hint">Afficher un avertissement quand le texte du message ou l’objet sont vides ou quand une pièce jointe semble avoir été oubliée</string>
<stringname="title_advanced_tune_keep_alive">Ajuster automatiquement l\'intervalle de connexion</string>
<stringname="title_advanced_keyboard">Afficher le clavier par défaut</string>
<stringname="title_advanced_keyboard_no_fullscreen">Ne pas afficher le clavier en plein écran</string>
<stringname="title_advanced_suggest_names">Utiliser les noms et les adresses e-mail</string>
<stringname="title_advanced_suggest_local">Suggérer les contacts stockés localement</string>
<stringname="title_advanced_suggest_sent">Suggérer les adresses trouvées dans les messages envoyés</string>
<stringname="title_advanced_suggest_received">Suggérer les adresses trouvées dans les messages reçus</string>
@ -312,7 +313,7 @@
<stringname="title_advanced_color_threshold">Seuil de couleur de lettre : %1$s %%</string>
<stringname="title_advanced_name_email">Afficher les noms et les adresses e-mail</string>
<stringname="title_advanced_replace_name">Préférer un nom de contact à un nom d\'envoi</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Afficher uniquement le nom des contacts</string>
<stringname="title_advanced_only_name">Afficher uniquement le nom des contacts</string>
<stringname="title_advanced_distinguish_contacts">Souligner l\'expéditeur lorsqu\'il est connu comme contact local</string>
<stringname="title_advanced_show_recipients">Afficher les destinataires dans l\'en-tête du message</string>
<stringname="title_advanced_font_size_sender">Taille de police du champ «Expéditeur»</string>
@ -475,6 +476,7 @@
<stringname="title_advanced_check_reply_hint">Ceci vérifiera si le nom de domaine de l\'expéditeur et l\'adresse de réponse sont les mêmes</string>
<stringname="title_advanced_lookup_mx_hint">Ceci vérifiera l’existence d’enregistrements DNS mail exchanger (MX)</string>
<stringname="title_advanced_sync_delay_hint">Ceci ralentira la synchronisation des messages</string>
<stringname="title_advanced_suggest_names_hint">Si désactivé, seules les adresses e-mail seront utilisées lors de la sélection des contacts</string>
<stringname="title_advanced_suggest_local_hint">En plus des contacts fournis par Android. Les informations des contacts seront stockées pour les messages récemment envoyés ou reçus seulement si ceci est activé.</string>
<stringname="title_advanced_usenet_hint">Insérer \'-- \' entre le texte et la signature</string>
<stringname="title_advanced_send_reminders_hint">Afficher un avertissement quand le texte du message ou l’objet sont vides ou quand une pièce jointe semble avoir été oubliée</string>
<stringname="title_advanced_color_threshold">Limiar da cor das letras: %1$s %%</string>
<stringname="title_advanced_name_email">Mostrar nomes e enderezos de email</string>
<stringname="title_advanced_replace_name">Preferir o nome de contacto ao nome do envío</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Só mostrar o nome dos contactos</string>
<stringname="title_advanced_only_name">Só mostrar o nome dos contactos</string>
<stringname="title_advanced_distinguish_contacts">Suliñar o remitente cando este é recoñecido como un destinatario local</string>
<stringname="title_advanced_show_recipients">Mostrar os destinatarios nas cabeceiras das mensaxes</string>
<stringname="title_advanced_font_size_sender">Tamaño do texto do remitente</string>
<stringname="title_advanced_name_email">Toon namen en e-mailadressen</string>
<stringname="title_advanced_replace_name">Geef de voorkeur aan een contactnaam boven een verzonden naam</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Alleen contactnamen weergeven</string>
<stringname="title_advanced_check_reply_hint">Hiermee wordt gecontroleerd of de domeinnaam van de afzender en het antwoordadres hetzelfde zijn</string>
<stringname="title_advanced_lookup_mx_hint">Dit zal controleren of DNS MX records bestaan</string>
<stringname="title_advanced_sync_delay_hint">Dit zal de synchronisatie van berichten vertragen</string>
<stringname="title_advanced_suggest_names_hint">Indien uitgeschakeld, worden alleen e-mailadressen gebruikt bij het selecteren van contacten</string>
<stringname="title_advanced_suggest_local_hint">Naast contacten die door Android worden geleverd. Contactgegevens worden alleen opgeslagen voor nieuw verzonden of ontvangen berichten wanneer ingeschakeld.</string>
<stringname="title_advanced_usenet_hint">Voeg \'-- \' in tussen de tekst en de handtekening</string>
<stringname="title_advanced_send_reminders_hint">Toon een waarschuwing wanneer de berichttekst of het onderwerp leeg is of wanneer een bijlage zou kunnen ontbreken</string>
<stringname="title_advanced_name_email">Pokaż nazwy i adresy e-mail</string>
<stringname="title_advanced_replace_name">Preferuj nazwę kontaktu nad nazwą wysłaną</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Wyświetlaj tylko nazwy kontaktów</string>
<stringname="title_advanced_only_name">Wyświetlaj tylko nazwy kontaktów</string>
<stringname="title_advanced_distinguish_contacts">Podkreśl nadawcę, gdy znany jest jako lokalny kontakt „do”</string>
<stringname="title_advanced_show_recipients">Pokaż odbiorców w nagłówku wiadomości</string>
<stringname="title_advanced_font_size_sender">Rozmiar tekstu nadawcy</string>
@ -496,6 +497,7 @@
<stringname="title_advanced_check_reply_hint">Spowoduje to sprawdzenie, czy nazwa domeny nadawcy i adres odpowiedzi są takie same</string>
<stringname="title_advanced_lookup_mx_hint">To sprawdzi, czy istnieją rekordy MX DNS</string>
<stringname="title_advanced_sync_delay_hint">Wydłuży to synchronizację wiadomości</string>
<stringname="title_advanced_suggest_names_hint">Jeśli wyłączone, tylko adresy e-mail będą używane podczas wybierania kontaktów</string>
<stringname="title_advanced_suggest_local_hint">Oprócz kontaktów dostarczanych przez Androida. Dane kontaktowe będą przechowywane dla nowo wysłanych lub odebranych wiadomości tylko kiedy włączone.</string>
<stringname="title_advanced_usenet_hint">Wstaw \'-- \' między tekstem a podpisem</string>
<stringname="title_advanced_send_reminders_hint">Pokaż ostrzeżenie, gdy tekst wiadomości lub temat jest pusty lub gdy może brakować załącznika</string>
<stringname="title_advanced_name_email">Показывать имена и адреса электронной почты</string>
<stringname="title_advanced_replace_name">Предпочитать имя контакта вместо имени отправителя</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Показывать только имена контактов</string>
<stringname="title_advanced_only_name">Показывать только имена контактов</string>
<stringname="title_advanced_distinguish_contacts">Подчёркивать отправителя, если он известен как локальный контакт \"Кому\"</string>
<stringname="title_advanced_show_recipients">Показывать получателей в заголовке сообщения</string>
<stringname="title_advanced_font_size_sender">Размера текста поля \"Отправитель\"</string>
@ -497,6 +498,7 @@
<stringname="title_advanced_check_reply_hint">Проверяет, совпадает ли доменное имя отправителя и адреса для ответа</string>
<stringname="title_advanced_lookup_mx_hint">Проверка наличия записей DNS MX</string>
<stringname="title_advanced_suggest_names_hint">Если отключено, при выборе контактов будут использоваться только адреса электронной почты</string>
<stringname="title_advanced_suggest_local_hint">В дополнение к контактам, предоставляемым Android. Контактные данные будут сохранены только для вновь отправленных или полученных сообщений при включении этой функции.</string>
<stringname="title_advanced_usenet_hint">Вставлять \'-- \' между текстом и подписью</string>
<stringname="title_advanced_send_reminders_hint">Показывать предупреждение, если отсутствует текст сообщения, тема или, возможно, отсутствует вложение</string>
<stringname="title_advanced_color_threshold">Поріг для кольору літери: %1$s %%</string>
<stringname="title_advanced_name_email">Показати імена та адреси електронної пошти</string>
<stringname="title_advanced_replace_name">Віддавати перевагу імені контакту над надісланим іменем</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">Показувати тільки імена контактів</string>
<stringname="title_advanced_only_name">Показувати тільки імена контактів</string>
<stringname="title_advanced_distinguish_contacts">Підкреслювати відправника в полі \'to\', коли відправник відомий як місцевий контакт</string>
<stringname="title_advanced_show_recipients">Показувати отримувачів в заголовку повідомлення</string>
<stringname="title_advanced_font_size_sender">Розмір тексту в полі відправник</string>
<stringname="title_advanced_only_name"comment="title_advanced_only_name Title for option to show names from the Android address book only">仅显示联系人姓名</string>
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
Vil/kan der ikke bruges en enhedsbaseret Gmail-konto på f.eks. nyere Huawei-enheder, aktivér da enten adgang for "mindre sikre apps" med brug af kontoadgangskode (ikke anbefalet), eller tofaktorgodkendelse med brug af en app-specifik adgangskode. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Manglende krypteringsnøgle*: Der er sandsynligvis valgt en nøgle i FairEmail, der ikke længere forefindes i OpenKeychain-appen. Nulstilling af nøglen (se ovenfor) løser sandsynligvis dette problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Verschlüsselungsschlüssel fehlt*: es wurde wahrscheinlich in FairEmail ein Schlüssel ausgewählt, der in der OpenKeychain-App nicht mehr vorhanden ist. Das Zurücksetzen des Schlüssels (siehe oben) wird dieses Problem eventuell beheben.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br/>
@ -882,7 +896,7 @@ The error *... **Authentication failed** ...* or *... AUTHENTICATE failed ...* l
If needed, you can update a password in the account settings: navigation menu (left side menu), tap *Settings*, tap *Manual setup and more options*, tap *Accounts* and tap on the account. Changing the account password will in most cases automatically change the password of related identities too. If the account was authorized with OAuth via the quick setup wizard instead of with a password, you can run the quick setup wizard again and tick *Authorize existing account again* to authenticate the account again. Note that this requires a recent version of the app.
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.
Der Fehler *… Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to set up a Yahoo account.
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
@ -890,9 +904,9 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
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.
Der Fehler *… Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
The error *... 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.
Der Fehler *… 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.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Verschlüsselungsschlüssel fehlt*: es wurde wahrscheinlich in FairEmail ein Schlüssel ausgewählt, der in der OpenKeychain-App nicht mehr vorhanden ist. Das Zurücksetzen des Schlüssels (siehe oben) wird dieses Problem eventuell beheben.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br/>
@ -882,7 +896,7 @@ The error *... **Authentication failed** ...* or *... AUTHENTICATE failed ...* l
If needed, you can update a password in the account settings: navigation menu (left side menu), tap *Settings*, tap *Manual setup and more options*, tap *Accounts* and tap on the account. Changing the account password will in most cases automatically change the password of related identities too. If the account was authorized with OAuth via the quick setup wizard instead of with a password, you can run the quick setup wizard again and tick *Authorize existing account again* to authenticate the account again. Note that this requires a recent version of the app.
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.
Der Fehler *… Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to set up a Yahoo account.
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
@ -890,9 +904,9 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
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.
Der Fehler *… Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
The error *... 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.
Der Fehler *… 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.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Verschlüsselungsschlüssel fehlt*: es wurde wahrscheinlich in FairEmail ein Schlüssel ausgewählt, der in der OpenKeychain-App nicht mehr vorhanden ist. Das Zurücksetzen des Schlüssels (siehe oben) wird dieses Problem eventuell beheben.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br/>
@ -882,7 +896,7 @@ The error *... **Authentication failed** ...* or *... AUTHENTICATE failed ...* l
If needed, you can update a password in the account settings: navigation menu (left side menu), tap *Settings*, tap *Manual setup and more options*, tap *Accounts* and tap on the account. Changing the account password will in most cases automatically change the password of related identities too. If the account was authorized with OAuth via the quick setup wizard instead of with a password, you can run the quick setup wizard again and tick *Authorize existing account again* to authenticate the account again. Note that this requires a recent version of the app.
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.
Der Fehler *… Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to set up a Yahoo account.
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
@ -890,9 +904,9 @@ The errors *... invalid greeting ...*, *... requires valid address ...* and *...
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.
Der Fehler *… Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
The error *... 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.
Der Fehler *… 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.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Falta la clave para el cifrado*: probablemente hay una clave seleccionada en FairEmail que ya no existe en la aplicación OpenKeychain. Restablecer la clave (ver arriba) probablemente solucione este problema.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
@ -669,7 +675,7 @@ Public keys are stored by FairEmail and can be imported when verifying a signatu
FairEmail verifies both the signature and the complete certificate chain.
Yleiset virheet:
Common errors:
* *No certificate found matching targetContraints*: this likely means you are using an old version of FairEmail
* *unable to find valid certification path to requested target*: basically this means one or more intermediate or root certificates were not found
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
Si vous avez une question, veuillez d'abord consulter ci-dessous la liste des questions fréquemment posées. [En bas](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), vous trouverez comment poser d'autres questions, demander des fonctionnalités et signaler des bogues.
Wenn Sie eine Frage haben, überprüfen Sie bitte zuerst die nachstehenden häufig gestellten Fragen (FAQ). [Ganz unten erfahren Sie](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), wie Sie weitere Fragen stellen, Funktionen anfordern und Fehler melden können.
Si vous avez une question, veuillez d'abord consulter la Foire aux questions (FAQ) ci-dessous. [ En bas ](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), vous trouverez comment poser d'autres questions, demander des fonctions et signaler des erreurs.
## Index
@ -469,7 +469,7 @@ Certaines personnes demandent :
Si vous utilisez la version Play Store ou GitHub de FairEmail, vous pouvez utiliser l'assistant de configuration rapide pour configurer facilement un compte Gmail et une identité. L'assistant de configuration rapide de Gmail n'est pas disponible pour les versions tierces, comme la version F-Droid, parce que Google n'a approuve l'utilisation d'OAuth que pour les versions officielles.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. Pour utiliser un mot de passe, vous devrez configurer manuellement un compte et une identité au lieu de l’assistant de configuration rapide.
Si vous ne voulez pas ou ne pouvez pas utiliser un compte Google sur votre appareil, par exemple sur les appareils Huawei récents, vous pouvez soit activer l'accès pour les «applications moins sécurisées» et utiliser le mot de passe de votre compte (non conseillé), soit activer l'authentification en deux étapes et utiliser un mot de passe spécifique à l'application. Pour utiliser un mot de passe, vous devrez configurer manuellement un compte et une identité au lieu de l’assistant de configuration rapide.
**Important**: parfois Google publie cette alerte :
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Clé manquante pour le chiffrement*: il y a probablement une clé sélectionnée dans FairEmail qui n'existe plus dans l'application OpenKeychain. La réinitialisation de la clé (voir ci-dessus) résoudra probablement ce problème.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br/>
<aname="faq13"></a>
**(13) Comment fonctionne la recherche sur l'appareil /sur le serveur ?**
**(13) How does search on device/server work?**
You can start searching for messages on sender (from), recipient (to, cc, bcc), subject, keywords or message text by using the magnify glass in the action bar of a folder. You can also search from any app by selecting *Search email* in the copy/paste popup menu.
@ -752,7 +766,7 @@ Searching on the device is a free feature, using the search index and searching
<br/>
<aname="faq14"></a>
**(14) Comment puis-je configurer un compte Outlook / Live / Hotmail ?**
**(14) How can I set up an Outlook / Live / Hotmail account?**
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
@ -765,7 +779,7 @@ For setting up an Office 365 account, please see [this FAQ](#user-content-faq156
<br/>
<aname="faq15"></a>
**(15) Pourquoi le texte du message continue-t-il de se charger indéfiniment ?**
**(15) Why does the message text keep loading?**
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and will be fetched on demand on expanding a message. The message text will keep loading if there is no connection to the account, see also the next question, or if there other operations, like synchronizing messages, are being executed.
@ -780,7 +794,7 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
<br/>
<aname="faq16"></a>
**(16) Pourquoi les messages ne sont-ils pas synchronisés ?**
**(16) Why are messages not being synchronized?**
Possible causes of messages not being synchronized (sent or received) are:
@ -805,7 +819,7 @@ In case of successive connection errors, FairEmail will hold off increasingly lo
<br/>
<aname="faq17"></a>
**~~(17) Pourquoi la synchronisation manuelle ne fonctionne pas ?~~**
**~~(17) Why does manual synchronize not work?~~**
~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
@ -814,14 +828,14 @@ In case of successive connection errors, FairEmail will hold off increasingly lo
<br/>
<aname="faq18"></a>
**(18) Pourquoi l'aperçu du message ne s'affiche pas toujours ?**
**(18) Why is the message preview not always shown?**
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
<br/>
<aname="faq19"></a>
**(19) Pourquoi les fonctionnalités pro sont-elles si chères ?**
**(19) Why are the pro features so expensive?**
First of all, **FairEmail is basically free to use** and only some advanced features need to be purchased.
Si vous avez une question, veuillez d'abord consulter ci-dessous la liste des questions fréquemment posées. [En bas](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), vous trouverez comment poser d'autres questions, demander des fonctionnalités et signaler des bogues.
Wenn Sie eine Frage haben, überprüfen Sie bitte zuerst die nachstehenden häufig gestellten Fragen (FAQ). [Ganz unten erfahren Sie](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), wie Sie weitere Fragen stellen, Funktionen anfordern und Fehler melden können.
Si vous avez une question, veuillez d'abord consulter la Foire aux questions (FAQ) ci-dessous. [ En bas ](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), vous trouverez comment poser d'autres questions, demander des fonctions et signaler des erreurs.
## Sommaire
@ -469,7 +469,7 @@ Certaines personnes demandent :
Si vous utilisez la version Play Store ou GitHub de FairEmail, vous pouvez utiliser l'assistant de configuration rapide pour configurer facilement un compte Gmail et une identité. L'assistant de configuration rapide de Gmail n'est pas disponible pour les versions tierces, comme la version F-Droid, parce que Google n'a approuve l'utilisation d'OAuth que pour les versions officielles.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. Pour utiliser un mot de passe, vous devrez configurer manuellement un compte et une identité au lieu de l’assistant de configuration rapide.
Si vous ne voulez pas ou ne pouvez pas utiliser un compte Google sur votre appareil, par exemple sur les appareils Huawei récents, vous pouvez soit activer l'accès pour les «applications moins sécurisées» et utiliser le mot de passe de votre compte (non conseillé), soit activer l'authentification en deux étapes et utiliser un mot de passe spécifique à l'application. Pour utiliser un mot de passe, vous devrez configurer manuellement un compte et une identité au lieu de l’assistant de configuration rapide.
**Important**: parfois Google publie cette alerte :
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Clé manquante pour le chiffrement*: il y a probablement une clé sélectionnée dans FairEmail qui n'existe plus dans l'application OpenKeychain. La réinitialisation de la clé (voir ci-dessus) résoudra probablement ce problème.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br/>
<aname="faq13"></a>
**(13) Comment fonctionne la recherche sur l'appareil /sur le serveur ?**
**(13) How does search on device/server work?**
You can start searching for messages on sender (from), recipient (to, cc, bcc), subject, keywords or message text by using the magnify glass in the action bar of a folder. You can also search from any app by selecting *Search email* in the copy/paste popup menu.
@ -752,7 +766,7 @@ Searching on the device is a free feature, using the search index and searching
<br/>
<aname="faq14"></a>
**(14) Comment puis-je configurer un compte Outlook / Live / Hotmail ?**
**(14) How can I set up an Outlook / Live / Hotmail account?**
An Outlook / Live / Hotmail account can be set up via the quick setup wizard and selecting *Outlook*.
@ -765,7 +779,7 @@ For setting up an Office 365 account, please see [this FAQ](#user-content-faq156
<br/>
<aname="faq15"></a>
**(15) Pourquoi le texte du message continue-t-il de se charger indéfiniment ?**
**(15) Why does the message text keep loading?**
The message header and message body are fetched separately from the server. The message text of larger messages is not being pre-fetched on metered connections and will be fetched on demand on expanding a message. The message text will keep loading if there is no connection to the account, see also the next question, or if there other operations, like synchronizing messages, are being executed.
@ -780,7 +794,7 @@ Mobile connections are almost always metered and some (paid) Wi-Fi hotspots are
<br/>
<aname="faq16"></a>
**(16) Pourquoi les messages ne sont-ils pas synchronisés ?**
**(16) Why are messages not being synchronized?**
Possible causes of messages not being synchronized (sent or received) are:
@ -805,7 +819,7 @@ In case of successive connection errors, FairEmail will hold off increasingly lo
<br/>
<aname="faq17"></a>
**~~(17) Pourquoi la synchronisation manuelle ne fonctionne pas ?~~**
**~~(17) Why does manual synchronize not work?~~**
~~If the *Synchronize now* menu is dimmed, there is no connection to the account.~~
@ -814,14 +828,14 @@ In case of successive connection errors, FairEmail will hold off increasingly lo
<br/>
<aname="faq18"></a>
**(18) Pourquoi l'aperçu du message ne s'affiche pas toujours ?**
**(18) Why is the message preview not always shown?**
The preview of the message text cannot be shown if the message body has not been downloaded yet. See also [this FAQ](#user-content-faq15).
<br/>
<aname="faq19"></a>
**(19) Pourquoi les fonctionnalités pro sont-elles si chères ?**
**(19) Why are the pro features so expensive?**
First of all, **FairEmail is basically free to use** and only some advanced features need to be purchased.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Falta a chave de cifrado*: é probable que a chave seleccionada en FairEmail xa non exista na aplicación OpenKeychain. Pode que o problema se amañe reiniciando a chave (vexa arriba).
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Chiave mancante per la crittografia*: c'è probabilmente una chiave selezionata in FairEmail che non esiste più nell'applicazione OpenKeychain. Resettare la chiave (vedi sopra) probabilmente risolverà questo problema.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official builds only.
If you don't want to use an on-device Gmail account, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
If you don't want to use or can't use an on-device Google account, for example on recent Huawei devices, you can either enable access for "less secure apps" and use your account password (not advised) or enable two factor authentication and use an app specific password. To use a password you'll need to set up an account and identity via the manual setup instead of via the quick setup wizard.
**Important**: sometimes Google issues this alert:
@ -591,6 +591,8 @@ See [this FAQ](#user-content-faq33) on editing the username of email addresses.
Communication with email servers is always encrypted, unless you explicitly turned this off. This question is about optional end-to-end encryption with PGP or S/MIME. The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br/>
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -615,6 +617,8 @@ In the encryption settings you can select the default encryption method (PGP or
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br/>
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first. FairEmail was tested with OpenKeychain version 5.4. Later versions will most likely be compatible, but earlier versions might not be.
@ -651,6 +655,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br/>
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br/>
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this. Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
<br/>
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
M66B
4 years ago