```
Dette betyder, at den redigerede afsenderadresse automatisk erstattes af en bekræftet adresse inden bekedafsendelsen.
Bemærk, at dette er uafhængigt af beskedmodtagelse.
**(34) Hvordan matches identiteter?**
Identiteter matches efter konto. For indgående beskeder tjekkes adresserne *til*, *cc*, *bcc*, *fra* og *(X-)leverede/konvolut/originale-til* (i nævnte rækkefølge), og for udgående beskeder (kladder, udbakke og sendt) tjekkes kun *fra*-adresserne. Matchende adresser har forrang frem for delvist matchende ditto, undtagen *leveret til*-adresser.
Den matchede adresse vises som *via* i adresseafsnittet på modtagne beskeder (mellem beskedhoved og -tekst).
Bemærk, at identiteter skal være aktiverede for at kunne matches, samt at identiteter for andre konti ikke tages i betragtning.
Match udføres kun én gang efter modtagelse af en besked, så evt. opsætningsændringer ændrer ikke eksisterende beskeder. Lokale beskeder kan dog ryddes ved at synkronisere beskederne igen (via langt tryk på en mappe i mappelisten).
Det er muligt at opsætte en [regex](https://en.wikipedia.org/wiki/Regular_expression) i identitetsindstillingerne for at få en e-mailadresses matchende **brugernavn** (delen før @-tegnet).
Bemærk, at domænenavnet (alt efter @) altid skal være identisk med identitetens ditto.
Vil man gerne matche en fang-alle e-mailadresse, er denne regex for det meste OK:
```
.*
```
Vil man matche e-mailadresserne til specielle formål, abc@eksemepel.dk og xyx@eksemepel.dk og også gerne have en fallback e-mailadresse, hoved@eksemepel.dk, kan noget ala dette bruges:
* Identity: abc@eksempel.dk; regex: **(?i)abc**
* Identity: xyz@eksempel.dk; regex: **(?i)xyz**
* Identity: hoved@eskempel.dk; regex: **^(?i)((?!abc|xyz).)\*$**
Matchede identiteter kan benyttes til beskedfarvekodning. Identitetsfarven har forrang over kontofarven. Brug af identitetsfarver er en Pro-funktion.
**(35) Hvorfor skal man være forsigtig med at få vist billeder, vedhæftninger, originalbeskeder samt åbne links?**
Visning af fjernlagrede billeder (tjek også [denne FAQ](#user-content-faq27)) samt åbning af links fortæller muligvis ikke kun afsenderen, at beskeden er set, men kan også lække modtagerens IP-adresse. Tjek også dette spørgsmål: [Hvorfor et e-mail link er farligere end et websøgningslink?](https://security.stackexchange.com/questions/241139/why-emails-link-is-more-dangerous-than-web-searchs-link).
Åbning af vedhæftninger eller visning af en original besked kan muligvis indlæse eksternt indhold og eksekvere scripts, hvilket ikke alene kan forårsage læk af fortrolige oplysninger, men tillige udgøre en sikkerhedsrisiko.
Bemærk, at ens kontakter, uden deres vidende, kan sende ondsindede beskeder, hvis de er malware-inficeret.
FairEmail genformaterer beskeder, hvilket får dem til at se anderledes ud end originalen, men tillige afslører phishing-links.
Bemærk, at genformaterede beskeder ofte er mere læsbare end originalerne, da margerne er fjernet, og skrifttypefarver og -størrelser er standardiserede.
Gmail-appen viser som standard billeder ved at downloade disse via en Google-proxyserver. Da billederne downloades fra kildeserveren [i realtid](https://blog.filippo.io/how-the-new-gmail-image-proxy-works-and-what-this-means-for-you/), er dette endnu mindre sikkert, da Google også er involveret.
Billeder og originale beskeder kan som standard vises for betroede afsendere fra gang til gang ved at markere *Spørg ikke igen om...*.
Ønskes standard *Åbn med* apps nulstillet, så tjek [hér](https://www.androidauthority.com/how-to-set-default-apps-android-clear-621269/).
**(36) Hvordan krypteres indstillingsfiler?**
Kort version: AES 256 bit
Lang version:
* 256 bit-nøglen genereres med *PBKDF2WithHmacSHA1* vha. en 128 bit sikker, tilfældigt salt og 65.536 iterationer
* Cipher'en er *AES/CBC/PKCS5Padding*
**(37) Hvordan lagres adgangskoder?**
Alle understøttede Android-versioner [krypterer alle brugerdata](https://source.android.com/security/encryption), så disse data, inkl. brugernavne, adgangskoder, beskeder mv., lagres krypteret.
Er enheden sikret med PIN-kode, mønster eller adgangskode, kan konto- og identitetsadgangskoder gøres synlige. Er dette er et problem, f.eks. fordi enheden deles med andre, så overvej brug af [brugerprofiler](https://www.howtogeek.com/333484/how-to-set-up-multiple-user-profiles-on-android/).
**(39) Hvordan kan FairEmails batteriforbrug reduceres?**
Som standard rapporterer nyere Android-versioner *app-brug* som en procentdel på Android-batteriindstillingssiden. **Forvirrende nok er *app-brug* ikke det samme som *batteriforbrug* og er ikke engang direkte relateret til batteriforbrug!** App-brugen (under brug) vil være meget høj, da FairEmail bruger en forgrundstjeneste, hvilket af Android tolkes som konstant app-brug. Dette betyder dog ikke, at FairEmail konstant forbruger strøm. Det reelle stømforbrug kan ses ved at gå til denne skærm:
*Android-indstillinger*, *Batteri*, trepriksmenu *Batteriforbrug*, trepriksmenu *Vis fuld enhedsforbrug*
Som en tommelfingerregel skal strømforbruget være under eller i hvert fald ikke meget højere end for *Mobilnetværksstandby*. Er dette ikke tilfældet, så aktivér *Automatisk optimering* i modtagelsesindstillingerne. Hjælper dette ikke, så [anmod om support](https://contact.faircode.eu/?product=fairemailsupport).
Det er uundgåeligt, at beskedsynkronisering forbruger strøm, da det indebærer adgang til både netværk og beskeddatabase.
Sammenlignes batteriforbruget for FairEmail med en anden e-mailklient, skal begge e-mailklienter være opsat så identisk som muligt. Det er f.eks. ikke retvisende at sammenligne kontinuerlig synk (push-beskeder) og periodisk (ikke-regelmæssig) tjek for nye beskeder.
Gentilslutninger til en e-mailserver forbruger ekstra strøm, hvilket f.eks. en ustabil Internetforbindelse vil afstedkomme. Desuden afsluutter visse e-mailservere ikke-aktive forbindelser for tidligt, selvom [standarden](https://tools.ietf.org/html/rfc2177) dikterer, at en sådan forbindelse bør holdes åben i 29 minutter. Periodisk synkronisering, f.eks. hver time, kan være at foretrække i sådanne tilfælde. Bemærk, at hyppig polling (hippigere end hvert ca. 30.-60. min) antageligt vil forbruge mere strøm end kontinuerlig synkronisering, da serverforbindelsesoprettelsen samt lokal-/fjernbeskedsmatchning er ressourcekrævende.
[På visse enheder](https://dontkillmyapp.com/) er det nødvendigt at *deaktivere* batterioptimering (opsætningstrin 4) for at holde e-mailserverforbindelser åbne. Aktiv batterioptimering kan reelt resultere i ekstra strømforbrug på alle enheder, selvom det lyder selvmodsigende!
Størstedelen af strømforbruget, fraset beskedkigninger, skyldes synkronisering (modtagelse/afsendelse) af beskeder. Indstil derfor antallet af synk-dage til en lavere værdi for at reducere strømforbruget, især hvis der er en masse friske beskeder i en mappe. Denne indstilling kan tilgås via et langt tryk på et mappenavn i mappelisten og valg af *Redigér egenskaber*.
Forefindes Internetforbindelse mindst én gang dagligt, er én besked-synk pr. dag tilstrækkeligt.
Bemærk, at det antal dage, hvori beskeder *beholdes* kan indstilles til en større værdi end til det antal dage, hvori beskeder *synkes*. Beskeder kan f.eks. indledningsvis synkes i et større antal dage, og efter at dette er sket, kan antallet af beskedsynk-dage reduceres, mens antallet af dage, hvori beskeder skal beholdes ikke ændres. Efter reducering af det antal dage, hvori beskeder beholdes, ønsker man måske via Diverse indstillinger at køre en oprydning for at fjerne gamle filer.
I modtagelsesindstillingerne kan man aktivere altid at synkre stjernemarkerede beskeder, hvilket bibeholder ældre beskeder, selvom der synkes beskeder i et begrænset antal dage.
Deaktivering af mappeindstillingen *Download automatisk beskedtekster og vedhæftninger* vil betyde mindre netværkstrafik og dermed mindre strømforbrug. Denne indstilling kan deaktiveres for f.eks. Sendt-mappen og arkivet.
Synk af beskeder om natten er sjældent nødvendigt, så der kan spares strøm ved at undlade dette. Der kan i indstillingerne vælges en tidsplan for besked-synk (dette er en Pro-funktion).
FairEmail vil som standard synke mappelisten ved hver tilslutning. Da mapper typisk ikke oprettes/omdøbes/slettes særligt hyppigt, kan netværks- og strømforbrug reduceres ved at deaktivere dette i modtagelsesindstillingerne.
Som standard vil FairEmail ved hver tilslutning tjekke, om gamle beskeder er slettet fra serveren. Gør det ikke noget, at gamle beskederr, som er blevet slettet fra serveren, stadig optræder i FairEmail, kan der spares netværks- og strømforbrug ved at deaktivere dette i modtagelsesindstillingerne.
Visse udbydere følger ikke IMAP-standarden og holder ikke forbindelserne åbne længe nok. Det tvinger FairEmail til ofte at genforbinde, hvilket medfører ekstra strømforbrug. *Loggen* kan via hovednavigeringsmenuen tjekkes for at se, om der er hyppige forbindelsesgenoprettelser (forbindelse lukket/nulstillet, læse-/skrivefejl/timeout mv.). Dette kan omgås ved i de avancerede kontoindstillinger at sænke keep-alive intervallet til f.eks. 15 eller 9 min. Bemærk, at batterioptimering skal deaktiveres i opsætningstrin 4 for pålideligt at holde forbindelserne i live.
Visse udbydere sender hvert 2. minut noget i retning af et '*Stadig her*', hvilket resulterer i netværkstrafik samt vækning af din enhed og dermed unødigt ekstra strømforbrug. *Loggen* kan tjekkes via hovednavigeringsmenuen for at se, hvorvidt udbyderen gør dette. Benytter udbyderen [Dovecot](https://www.dovecot.org/) som IMAP-server, kan udbyderen anmodes om ændre indstillingen [imap_idle_notify_interval](https://wiki.dovecot.org/Timeouts) til en højere værdi eller, endnu bedre, deaktivere denne. Er udbyderen ikke er i stand eller villig til at ændre/deaktivere denne, så overvej at skifte til periodisk i stedet for kontinuerlig synk. Dette kan ændre i modtagelsesindstillingerne.
Ses meddelelsen *Denne udbyder understøtter ikke push-beskeder* under opsætning af en konto, så overvej mhp. at reducere strømforbruget at skifte til en moderne udbyder, der understøtter push-beskeder (IMAP IDLE).
Har enheden en [AMOLED](https://en.wikipedia.org/wiki/AMOLED)-skærm, kan valg af det sorte tema spare strøm, mens der kigges beskeder.
Er autooptimering i modtagelsesindstillingerne aktiveret, omskiftes en konto automatisk til periodisk tjek for nye beskeder, når e-mailserveren:
* Sender et '*Stadig her*' inden for 3 minutter
* E-mailserveren understøtter ikke push-beskeder
* Keep-alive intervallet er kortere end 12 minutes
Desuden vil Papirkurv- og Spam-mapperne automatisk blive indstillet til at tjekke for nye beskeder efter tre successive [for mange samtidige forbindelser](#user-content-faq23)-fejl.
**(40) Hvordan kan FairEmails dataforbrug reduceres?**
Man kan grundlæggende reducere netværksforbruget på samme måde som strømforbruget. Tjek forslagene ifm. foregående spørgsmål.
Det er uundgåeligt, at data vil blive forbrugt ved meddelelses-synk.
Mistes forbindelsen til e-mail-serveren, vil FairEmail altid gen-synke beskederne for at sikre, at de alle er tilgængelige. Er forbindelsen ustabil, kan dette medføre ekstra dataforbrug. I så tilfælde er det en god idé at reducere antallet af besked-synk dage til et minimum (tjek foregående spørgsmål) eller at skifte til periodisk besked-synk (modtagelsesindstillinger).
For at reducere dataforbrug, kan disse avancerede modtagelsesindstillinger ændres:
* Tjek, om gamle beskeder er fjernet fra serveren
* Synkronisér (delte) mappelister: Deaktivér
Som standard downloader FairEmail ikke beskedtekster og vedhæftninger større end 256 KiB på takserede Internetforbindelser (mobildata/betalt Wi-Fi). Dette kan ændres i forbindelsesindstillingerne.
**(41) Hvordan rettes fejlen 'Handshake mislykkedes'?**
Der er flere mulige årsager, så tjek hele dette svar.
Fejlen '*Handshake mislykkedes ... WRONG_VERSION_NUMBER ...*' kan betyde, at der forsøges opretteet forbindelse til en IMAP- eller SMTP-server uden en krypteret forbindelse, typisk via port 143 (IMAP) og port 25 (SMTP), eller anvendelse af en forkert protokol (SSL/TLS eller STARTTLS).
De fleste udbydere leverer krypterede forbindelser vha. forskellige porte, typisk port 993 (IMAP) og port 465/587 (SMTP).
Understøtter udbyderen ikke krypterede forbindelser, bør der anmodes om, at dette muliggøres. Er dette ikke en mulighed, kan *Tillad usikre forbindelser* aktiveres i både de avancerede indstillinger OG konto-/identitetsindstillingerne.
Tjek også [denne FAQ](#user-content-faq4).
Fejlen '*Handshake mislykkedes ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' er enten forårsaget af en fejl i SSL-protokolimplementeringen eller en for kort DH-nøgle på e-mailserveren og kan desværre ikke imødegås af FairEmail.
Fejlen '*Handshake mislykkedes ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' kan forårsages af, at udbyderen stadig anvender RC4, hvilket fra [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) ikke længere understøttes.
Fejlen '*Handshake mislykkedes ... UNSUPPORTED_PROTOCOL eller TLSV1_ALERT_PROTOCOL_VERSION ...*' kan forårsages af aktivering af forbindelseshærdning i forbindelsesindstillingerne eller af, at Android ikke længere understøtter ældre protokoller (f.eks. SSLv3).
Android 8 Oreo og senere [understøtter ikke længere](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3. Manglende RC4- og SSLv3-understøttelse kan på ingen måde omgås, da disse er helt fjernet fra Android.
[Dette websted](https://ssl-tools.net/mailservers) eller [dette websted](https://www.immuniweb.com/ssl/) kan bruges til at tjekke for SSL-/TLS-problemer på e-mailservere.
**(42) Kan der blive tilføjet en ny udbyder på udbyderlisten?**
Bliver udbyderen brugt af flere end blot et par personer, så ja.
Flg. oplysninger vil være påkrævet:
```
// dette kræves ikke
```
EFF-[skrivninger](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Der er dog stadig ingen garanti for, at kommunikationen bliver krypteret, selvom STARTTLS opsættes korrekt samt et gyldigt certifikat anvendes.*"
Rene SSL-forbindelser er sikrere at anvende end [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) og foretrækkes derfor.
Sørg for at tjekke, at beskedmodtagelse/-afsendelse fungerer korrekt, før kontakt vedr. udbydertilføjelse sker.
Tjek nedenfor, hvordan jeg kontaktes.
**(43) Kan man vise den originale ... ?**
Vis original, viser den oprindelige besked, således som afsenderen har sendt den, inkl. oprindelige skrifttyper, farver, margner mv. FairEmail ændrer på ingen måde på dette, bortset fra at anmode om [TEXT_AUTOSIZING](https://developer.android.com/reference/android/webkit/WebSettings.LayoutAlgorithm), som *forsøger* at gøre en lille tekst mere læsbar.
**~~(44) Kan man få vist kontaktfotos/-identikoner i Sendt-mappen?~~**
~~Kontaktfotos og identikoner vises altid for afsenderen, da dette er nødvendigt for konversationstråde.~~ ~~At få kontaktfotos til både afsender og modtager er ikke rigtig en mulighed, da hentning af et kontaktfoto er ressourcekrævende.~~
**(45) Hvordan rettes problemet 'Denne nøgle er utilgængelig. For at bruge den, skal den importere som en af ens egne!' ?**
Man får meddelelsen *Denne nøgle er ikke tilgængelig. For at bruge den, skal den importere som en af ens egne!*, når en besked forsøges dekrypteret med en offentlig nøgle. For at løse dette, skal den private nøgle importeres.
**(46) Hvorfor genindlæses beskedlisten hele tiden?**
Ses en 'spinner' øverst på beskedlisten, synkes mappen stadig med fjernserveren. Forløbsstatus for synk kan ses i mappelisten. Tjek symbolforklaringen for betydninger af ikoner og tal.
Hastigheden på enhed og Internetforbindelse samt antal besked-synk dage bestemmer, hvor langt tid synkning tager. Bemærk, at antal besked-synk dage i de fleste tilfælde ikke bør opsættes til mere end én dag. Tjek også [denne FAQ](#user-content-faq39).
**(47) Hvordan løses fejlen 'Ingen primær konto eller udkastmappe'?**
Fejlmeddelelsen *Ingen primær konto eller udkastmappe* vises, når en besked forsøges oprettet, uden at nogen primær konto er angivet eller en udkastmappe er valgt for den primære konto. Dette kan f.eks. ske, når FairEmail startes fra en anden app mhp. at skrive en besked. FairEmail skal vide, hvor udkast skal gemmes, så det er nødvendigt at vælge en konto til at udgøre den primære konto samt/eller vælge en udkastmappe for denne.
Dette kan også ske, når man forsøger at svare på en besked, eller videresende en besked fra en konto uden udkastmappe, mens der ikke er nogen primær konto, eller når den primære konto ikke har en udkastmappe.
Tjek [denne FAQ](#user-content-faq141) for yderligere information.
**~~(48) Hvordan løses fejlen 'Ingen primær konto eller arkivmappe'?~~**
~~Fejlmeddelelsen *Ingen primær konto eller arkivmappe* ses, når der søges efter beskeder fra en anden app. FairEmail skal vide, hvor der skal søges, så det er nødvendigt at vælge en konto til at udgøre den primære konto samt/eller vælge en arkivmappe for denne.~~
**(49) Hvordan løses fejlen 'En forældet app har sendt en filsti i stedet for en fil-stream'?**
Der er sandsynligvis valgt eller afsendt en vedhæftning/billede vha. en forældet filhåndtering eller en forældet app, der antager, at alle apps stadig har lagerpladstilladelser. Af sikkerheds- og fortrolighedsårsager har moderne apps såsom FairEmail ikke længere fuld adgang til alle filer. Dette kan resultere i fejlmeddelelsen *En forældet app sendte en filsti i stedet for en filstream*, hvis et filnavn i stedet for en filstream deles med FairEmail, da denne ikke kan åbne tilfældige filer.
Dette kan løses ved at skifte til en opdateret filhåndtering/app designet til de seneste Android-versioner. Alternativt kan FairEmail tildeles læserettighed til enhedens lagerplads i Androids app-indstillinger. Bemærk, at denne omgåelse [ikke længere fungerer i Android Q](https://developer.android.com/preview/privacy/scoped-storage).
Tjek også [spørgsmål 25](#user-content-faq25) og [Googles information herom](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
**(50) Vil der kunne blive tilføjet en mulighed for at synke alle beskeder?**
Flere, eller endda alle, beskeder kan synkes via langt tryk på en mappe (indbakke) i mappelisten over en konto (tryk på kontonavnet i navigationsmenuen) og så vælge *Synkronisér flere* i popup-menuen.
**(51) Hvordan sorteres mapper?**
Mapper sorteres først efter kontorækkefølge (som standard kontonavnet) og i selve kontoen med særlige systemmapper øverst, efterfulgt af mapper opsat til synkning. Inden for hver kategori sorteres mapperne efter (visnings-)navn. Visningsnavn kan angives vha. langt tryk på en mappe i mappelisten og så vælge *Rediger egenskaber*.
Navigeringsmenuenpunktet (hamburger) *Sortér mapper* i opsætningen kan bruges til manuelt at sortere disse.
**(52) Hvorfor tager det noget tid at genforbinde til en konto?**
Der er ingen pålidelig måde at få oplyst, om en kontoforbindelse blev afsluttet tilsigtet eller utilsigtet. Forsøg på at genforbinde til en konto, hvis forbindelse for ofte er blevet afsluttet abrupt, kan resultere i problemer såsom [for mange samtidige forbindelser](#user-content-faq23) eller endda blokering af kontoen. For at forhindre sådanne problemer, venter FairEmail 90 sek., inden forbindelsesgenoprettelse igen forsøges.
Benyt langt tryk på *Indstillinger* i navigeringsmenuen for straks at genoprette forbindelsen.
**(53) Kan beskedhandlingsbjælken fastgøres øverst/nederst?**
Beskedhandlingshandlingsbjælken virker på én enkelt besked, og den nederste handlingsbjælke virker på alle beskeder i en konversation. Da der ofte er flere end én besked i en konversation, er dette ikke muligt. Desuden findes en del beskedspecifikke handlinger, f.eks. videresendelse.
Flytning af beskedhandlingbjælken til bunden af beskeden er visuelt ikke tiltalende, dai der allerede er en konversationshandlingsbjælke nederst på skærmen.
Bemærk, at der ikke er mange (om nogle) e-mail apps, som viser en konversation som en liste over udvidelige beskeder. Dette har mange fordele, men er også årsagen til behovet for beskedspecifikke handlinger.
**~~~(54) Hvordan benyttes et navneområdepræfiks? ~~**
~~Et navneområdepræfix benyttes til automatisk at fjerne de præfikser, udbydere undertiden tilføjer mappenavne.~~
~~F.eks. betegnes Gmail Spam-mappen:~~
```
[Gmail]/Spam
```
~~Ved at sætte mavneområdepræfikset til *[Gmail]*, fjerner FairEmail automatisk *[Gmail]/* fra alle mappenavne.~~
**(55) Hvordan kan man markere alle beskeder som læst/flyttet eller slette dem alle?**
Man kan bruge flervalgsmuligheden til dette. Tryk og hold på den første besked og træk, uden at løfte fingeren, ned til den sidste besked. Brug derefter treprikshandlingsknappen til at udføre den ønskede handling.
**(56) Kan der blive tilføjet understøttelse af JMAP?**
Der er næsten ingen udbydere, som tilbyder [JMAP](https://jmap.io/)-protokollen, så det er ikke umagen værd at tilføje understøttelse for denne i FairEmail.
**(57) Kan HTML benyttes i signaturer?**
Ja, [HTML](https://en.wikipedia.org/wiki/HTML) kan benyttes. I signaturredigeringsværktøjet kan man via trepriksmenuen skifte til HTML-tilstand.
Bemærk, at skiftes tilbage til teksredigeringsværktøjet, gengives alt HTML måske ikke korrekt, da Android-teksredigeringsværktøjet ikke kan gengive alt HTML. Omvendt, benyttes tekstredigerinsværktøjet, kan HTML blive ændret på uventede måder.
Ønsker man at bruge præformateret tekst, såsom [ASCII art](https://en.wikipedia.org/wiki/ASCII_art), bør teksten ombryde i et *præelement* således:
```
|\_/|
/ @ @ \
( > º < )
`>>x<<´
/ O \
```
**(58) Hvad er et åbn/luk e-mailikon?**
E-mailikonet i mappelisten kan åbnes (omrids) eller lukkes (udfyldt):
Beskedtekster og vedhæftninger downloades ikke som standard.
Beskedtekster og vedhæftninger downloades som standard.
**(59) Kan originale beskeder åbnes i browseren?**
Af sikkerhedsårsager er filerne med de originale beskedtekster ikke tilgængelige for andre apps, så dette er ikke muligt. I teorien kunne [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider) bruges til at dele disse filer, men selv Google Chrome kan ikke håndtere dette.
**(60) Vidste du ... ?**
* Vidste du, at stjernemarkerede beskeder kan synkroniseres/beholdes for altid? (dette kan aktiveres i modtagelsesindstillingerne)
* Vidste du, at du et langt tryk på ikonet 'Skriv besked' tager dig til Udkast-mappen?
* Vidste du, at der er en avanceret mulighed for at markere beskeder som læst, når de flyttes? (arkivering og kassering er også i flytning)
* Vidste du, at du kan vælge tekst (eller en e-mailadresse) i en app i de seneste Android-versioner og lade FairEmail søge efter den?
* Vidste du, at FairEmail har en tablettilstand? Rotér din enhed til liggende tilstand og konversationstråde åbnes i en 2. kolonne, hvis der er tilstrækkelig skærmplads.
* Vidste du, at et langt tryk kan bruges på en svarskabelon for at oprette en udkastbesked fra denne?
* Vidste du, at man kan trykke og holde, og dernæst stryge for at vælge en række beskeder?
* Vidste du, at man kan prøve at gensende en besked ved at bruge træk-ned-for-at-opfriske i Udbakken?
* Vidste du, at man kan stryge en konversation til venstre/højre for at gå til den næste/forrige?
* Vidste du, at man kan trykke på et billede for at se, hvorfra det downloades?
* Vidste du, at et langt tryk på mappeikonet i handlingsbjælken muliggør valg af konto?
* Vidste du, at et langt tryk på stjerneikonet i en konversationstråd muliggør valg af stjernefarve?
* Vidste du, at navigeringsskuffen kan åbnes med et stryge fra venstre, selv når man kigger på en konversation?
* Vidste du, at et langt tryk på personers ikon viser/skjuler CC-/BCC-felter samt huske synlighedstilstanden til næste gang?
* Vidste du, at man kan indsætte en Android-kontaktgruppes e-mailadresser via trepriksoverløbsmenuen?
* Vidste du, at vælger man tekst og trykker på svar, så vil kun den valgte tekst blive citeret?
* Vidste du, at med et langt tryk på papirkurvsikoner (både i beskeden og den nederste handlingsbjæle) kan man permanent slette en besked/konversation? (version 1.1368+)
* Vidste du, at et langt tryk på send-handlingen vil vise Send-dialogen, selv hvis den er deaktiveret?
* Vidste du, at man med et lang tryk på fuldskærmsikonet kan få vist originalbeskedteksten?
**(61) Hvorfor vises visse beskeder nedtonet?**
Nedtonede (gråtonet) beskeder er lokalt flyttede beskeder, hvis flytning endnu ikke er bekræftet af serveren. Dette kan opstå ifm.(midlertidig) manglende server- eller kontoforbindelse. Disse beskeder synkes, når der er etableret server- og kontoforbindelse eller, hvis dette aldrig sker, slettes, hvis de er for gamle til at blive synket.
Mappen skal muligvis synkes manuelt, f.eks. ved at trække ned fra toppen.
Disse beskeder kan ses, men de kan ikke flytte igen, før den foregående flytning er blevet bekræftet.
Afventende [operationer](#user-content-faq3) vises i operationsvisningen, tilgængelig via hovednavigeringsmenuen.
**(62) Hvilke godkendelsesmetoder understøttes?**
Flg. godkendelsesmetoder understøttes og anvendes i denne rækkefølge:
* LOGIN
* PLAIN
* CRAM-MD5
* XOAUTH2 ([Gmail](https://developers.google.com/gmail/imap/xoauth2-protocol), [Yandex](https://tech.yandex.com/oauth/))
* NTLM (ikke-testet)
Da [JavaMail til Android](https://javaee.github.io/javamail/Android) ikke understøtter SASL-godkendelsesmetoder, er disse, udover CRAM-MD4, uunderstøttede.
Kræver udbyderen en uunderstøttet godkendelsesmetode, vises fejlmeddelelsen *Godkendelse mislykkedes* sandsynligvis.
[Server Name Indication](https://en.wikipedia.org/wiki/Server_Name_Indication) understøttes af [alle understøttede Android-versioner](https://developer.android.com/training/articles/security-ssl).
**(63) Hvordan skaleres billeder til skærmvisning?**
Store indlejrede eller vedhæftede [PNG-](https://en.wikipedia.org/wiki/Portable_Network_Graphics) og [JPEG-](https://en.wikipedia.org/wiki/JPEG)billeder skaleres automatisk mhp. skærmvisning. Dette skyldes, at e-mails er begrænset i størrelse til, afhængigt af udbyderen, typisk mellem 10 og 50 MB. Billeder skaleres som standard til en maksimal bredde og højde på ca. 1.440 pixels og gemmes med et komprimeringsforhold på 90%. Billeder nedskaleres vha. heltalsfaktorer for at reducere hukommelsesforbruget samt bevare billedkvaliteten. Automatisk ændring af størrelse af indlejrede og/eller vedhæftede billeder og den maksimale målbilledstørrelse kan opsættes i Send-indstillinger.
Ønskes størrelsen på billeder ændret fra gang til gang, kan [Send Reduced](https://f-droid.org/en/packages/mobi.omegacentauri.SendReduced/), eller en lignende app, bruges.
**~~~(64) Kan der blive tilføjet tilpassede handlinger for venstre/højre strygning?~~**
~~Den mest logiske konsekvens ifm. at stryge en listepost til venstre/højre er at fjerne denne fra listen.~~ ~~Den mest logiske handling ifm. en e-mail-app er at flytte beskeden til en anden mappe.~~ ~~Mappen, der skal flyttes til, kan vælges via kontoindstillingerne.~~
~~Andre handlinger, såsom markering af beskeder som læste og slumre beskeder, er tilgængelige via multivalg.~~ ~~~Lang tryk på en besked giver adgang til multivalg. Tjek også [dette spørgsmål](#user-content-faq55).~~
~~Strygning til venstre/højre for at markere en besked som læst/ulæst er ulogisk, da beskeden først forsvinder for senere dukke op igen (med en anden status).~~ ~~Bemærk, at der er en avanceret mulighed for automatisk at markere beskeder som læste ved flytning,~~ ~~ hvilket for det meste er en perfekt erstatning for sekvensen markér som læst og flyt til anden mappe.~~ ~~Beskeder kan også markeres som læste via Nye beskeder-notifikationen.~~
~~Vil man læse en besked senere, kan den skjules indtil et bestemt tidspunkt vha. menuen *slumre*.~~
**(65) Hvorfor vises visse beskeder nedtonet?**
Indlejrede (billed-)vedhæftninger vises nedtonet. [Indlejrede vedhæftninger](https://tools.ietf.org/html/rfc2183) er begrenet på automatisk download og visning. men da FairEmail ikke altid downloader vedhæftninger automatisk (tjek også [denne FAQ](#user-content-faq40)), vises alle typer vedhæftninger. For at differentiere indlejringer og regulære vedhæftninger, vises indlejrede filer nedtonet.
**(66) Er FairEmail tilgængelig i Google Play Familie-biblioteket?**
Prisen på de få Pro-funktioner er for lav, lavere end prisen på de fleste lignende apps, og der er [for mange gebyrer og skatter](#user-content-faq19), til at begrunde en tilgængeliggørelse af FairEmail i [Google Play Familie-biblioteket](https://support.google.com/googleone/answer/7007852). Bemærk, at Google promoverer Familie-biblioteket, men samtidig lader udviklere betale for det.
**(67) Hvordan slumres konversationer?**
Vælg via multivalg én af flere konversationer (langt tryk for at tilgå multivalg), tryk på trepriksknappen og vælg *Slumre ...*. Alternativt kan *Slumre...* benyttes via den udvidede beskedvisning i trepriksmenuenpunktet 'flere' eller tidsforskydningshandlingen i den nederste handlingsbjælke. Vælg konversationsslumretid(er) og bekræft med et tryk på OK. Konversationerne skjules i det valgte tidsrum og vises derefter igen. En Ny besked-notifikation vil blive vist som påmindelse.
Det er også muligt at slumre beskeder vha, [en regel](#user-content-faq71).
Slumrede beskeder kan vises ved at afmarkerere *Bortfiltrér* > *Skjulte* i trepriksoverløbsmenuen.
Man kan trykke på det lille slumreikon for at se en konversations slumrevarighed.
Ved at angive nul som slumrevarighed, afbrydes slumringen.
**~~(68) Hvorfor kan Adobe Acrobat Reader/Microsoft-apps ikke åbne PDF-/dokumentvedhæftninger?~~**
~~Adobe Acrobat Reader og Microsoft apps forventer stadig fuld adgang til alle lagrede filer,~~ ~~selvom det for apps har krævet brug af [Storage Access Framework](https://developer.android.com/guide/topics/providers/document-provider) siden Android KitKat (2013)~~ ~~~for alene at tilgå aktivt delte filer. Dette er af fortroligheds- og sikkerhedsårsager.~~
~~Dette kan omgås ved at gemme vedhæftningen og åbne den fra Adobe Acrobat Reader/Microsoft-appen,~~ ~~, men det anbefales at installere en opdateret og helst open-source PDF-læser/dokumentfremviser,~~ ~~f.eks. en af de [hér](https://github.com/offa/android-foss#-document--pdf-viewer) anførte.~~
**(69) Kunne der blive tilføjet auto-rul op ved ny besked?**
Beskedlisten ruller automatisk op, når der navigeres fra en ny beskednotifikation eller efter manuel opfriskning. Kontinuerlig automatisk rul op ved modtagelse af nye beskeder ville forstyrre brugerens rulning, men om ønsket, kan dette aktivere i indstillingerne.
**(70) Hvornår auto-ekspanderes beskeder?**
Ved navigering til en konversation, auto-ekspanderes en besked, hvis:
* Der er kun én besked i konversationen
* Der kun er én ulæst besked i konversationen
Der er én undtagelse: Beskeden er endnu ikke downloadet, og beskeden er for stor til auto-download på en takseret forbindelse. Maks. beskedstørrelse kan opsættes/deaktiveres på fanen 'Forbindelsesindstillinger'.
Beskeder, som er dubletter (arkiverede), kasserede og udgør udkast, medregnes ikke.
Ved ekspandering auto-markeres beskeder som læste, medmindre dette er deaktiveret i de individuelle kontoindstillinger.
**(71) Hvordan benyttes filterregler?**
Filterregler kan redigere via et langt tryk på en mappe i kontomappelisten (tryk på kontonavnet i navigerings-/sidemenuen).
Nye regler effektueres for nye, modtagne beskeder i mappen, ikke for eksisterende beskeder. Reglen kan tjekkes og anvendes på eksisterende beskeder eller alternativt, via et langt tryk på regellisten, kan *Eksekvér nu* vælges.
En regel skal navngives, og rækkefølgen, for hvilken en regel skal eksekveres relativt til andre ditto, skal defineres.
En regel kan deaktiveres og udførsel af andre regler kan stoppes efter en regel er blevet eksekveret.
Flg. regelbetingelser er tilgængelige:
* Afsender indeholder
* Modtager indeholder
* Emne indeholder
* Har vedhæftninger
* Header indeholder
* Dag/tidspunkt mellem
Alle regelbetingelser skal være imødekommet for udførelse af regelhandlingen. Alle betingelser er valgfrie, men der skal være mindst én betingelse for at undgå matchning af alle beskeder. Ønskes alle afsendere eller modtagere matchet, kan @-tegnet blot anvendes som betingelse, idet alle e-mailadresser indeholder dette tegn.
Bemærk, at e-mailadresser er formateret således:
`
"Nogen" `
Man kan anvende flere regler, muligvis med et *eksekveringsstop*, for en *eller* eller en *ikke* betingelse.
Matchning er ikke versal-/minuskelfølsom undtagen for [regulære udtryk](https://en.wikipedia.org/wiki/Regular_expression). Tjek [hér](https://developer.android.com/reference/java/util/regex/Pattern) ang. dokumentation for regulære Java-udtryk. En regex kan aftestes [hér](https://regexr.com/).
Bemærk, at et regulært udtryk understøtter en *eller*-operatør, for matchning af flere afsendere om ønsket:
`
.*anette@eksempel\.org.*|.*bo@eksempel\.org.*|.*karen@eksempel\.org.*`
Bemærk, at [dot all-tilstand](https://developer.android.com/reference/java/util/regex/Pattern#DOTALL) er aktiveret for at kunne matche [udfoldede headers](https://tools.ietf.org/html/rfc2822#section-3.2.3).
En af disse handlinger kan vælges anvendt på matchende beskeder:
* Ingen handling (nyttigt for *ikke*)
* Markér som læst
* Markér som ulæst
* Skjul
* Undertryk notifikationer
* Slumre
* Tilføj stjerne
* Angiv vigtighed (lokal prioritet)
* Tilføj stikord
* Flyt
* Kopiér (Gmail: Etiket)
* Besvar/videresend (med skabelon)
* Tekst-til-tale (afsender og emne)
* Automatisering (Tasker mv.)
Regler effektueres umiddelbart efter besked-header'en er hentet, men inden beskedteksten er blevet downloadet, så brug af betingelser ift. beskedteksten er ikke muligt. Bemærk, at på takserede forbindelser downloades store beskedtekster på forlangende for at reducere dataforbruget.
Ønskes en besked videresendt, så overvej i stedet at bruge flythandlingen. Dette vil også være mere pålideligt end videresendelse, da videresendte beskeder måske opfattes som spam.
Da besked-headers som standard ikke downloades og lagres for at spare strøm- og dataforbrug samt lagerplads, er det ikke muligt at få vist, hvilke beskeder, som evt. matcher en header-regelbetingelse.
Nogle almindelige header-betingelser (regex):
* *.*Auto-Submitted:.** [RFC3834](https://tools.ietf.org/html/rfc3834)
* *.*Content Type: multipart/report.** [RFC3462](https://tools.ietf.org/html/rfc3462)
Under *Flere* i trepriksbeskedmenuen findes et element til oprettelse af en regel for en modtaget besked med de mest almindelige betingelser udfyldt.
POP3- protokollen understøtter ikke opsætning af nøgleord og beskedflytning/-kopiering.
Brug af regler er en Pro-funktion.
**(72) Hvad er primære konti/identiteter?**
Den primære konto bruges, når kontoen er tvetydig, f.eks. ved start på et nyt udkast fra den fælles indbakke.
Omvendt anvendes en kontos primære identitet, når identiteten er tvetydig.
Der kan kun være én primær konto, og der kan kun være én primær identitet pr. konto.
**(73) Er beskedflytning på tværs af konti sikkert/effektiv?**
Beskedflytning på tværs af konti er sikkert, da de rå originalbeskeder downloades og flyttes, og da kildebeskeder først slettes, efter at målbeskeder er tilføjet
Massebeskedflytning på tværs af konti er effektivt, hvis både kilde- og målmappen er opsat til synk, da FairEmail ellers vil skulle oprette mappeforbindelse(r) for hver besked.
**(74) Hvorfor optræder der dubletbeskeder'?**
Visse udbydere, især Gmail, oplister også alle beskeder i alle mapper, undtagen i papirkurven, i arkivmappen (alle beskeder). FairEmail viser alle disse beskeder på en ikke-påtrængende måde for at indikere, at de i virkeligheden er identiske.
Gmail tillader en besked at have flere etiketter, som præsenteres for FairEmail som mapper. Det betyder også, at beskeder med flere etiketter vil fremgå flere gange.
**(75) Kan der blive lavet en Windows-, Linux-, iOS-version mv.?**
En masse viden og erfaring kræves for at udvikle en velfungerende app til en bestemt platform, hvilket er grunden til, at jeg kun udvikler apps til Android.
**(76) Hvad gør 'Ryd lokale beskeder'?**
Mappemenuen *Ryd lokale beskeder* fjerner beskeder fra enheden, som også er til stede på serveren. Den sletter ikke beskeder fra serveren. Af f.eks. pladshensyn kan dette kan være nyttigt efter ændring af mappeindstillinger for ikke at downloade beskedindhold (tekst og vedhæftninger).
**(77) Hvorfor vises beskeder nogle gange med en lille forsinkelse?**
Afhængigt af enhedens hastighed (CPU-hastighed og måske især hukommelses ditto) kan beskeder blive vist med en lille forsinkelse. FairEmail er designet til dynamisk at håndtere et stort beskedantal uden at løbe tør for hukommelse. Det betyder, at beskeder skal læses fra en database, og at denne skal monitoreres for ændringer, og begge kan forårsage små forsinkelser.
Visse bekvemmelighedsfunktioner, såsom beskedgruppering for at vise konversationstråde samt bestemmelse af den foregående/næste besked, tager lidt ekstra tid. Bemærk, at der ikke er nogen *næste* besked, da der i mellemtiden kan være modtaget en ny besked.
Ved hastighedssammenligning af FairEmail med lignende apps, bør dette indgå i sammenligningen. Det er nemt at kode en lignende, hurtigere app, der blot viser en lineær beskedliste og muligvis samtidigt bruger for megen hukommelse, men det er ikke så nemt at håndtere ressourceforbrug korrekt og at tilbyde mere avancerede funktioner såsom samtaletråde.
FairEmail er baseret på de nyeste [Android-arkitekturkomponenter](https://developer.android.com/topic/libraries/architecture/), hvilket ikke giver de store muligheder for ydelsesforbedringer.
**(78) Hvordan anvendes tidsplaner?**
Man kan i modtagelsesindstillingerne aktivere tidsplanlægning og indstille en tidsperiode og ugedage for, *hvornår* beskeder skal *modtages*. Bemærk, at et sluttidspunkt lig med eller før starttidspunktet, anses for 24 timer senere.
Automatisering (tjek nedenfor) kan bruges til mere avancerede tidsplaner, såsom flere synk-perioder pr. dag eller forskellige synk-perioder på forskellige dage.
Det er muligt at installere FairEmail i flerbrugerprofiler, f.eks. en personlig og en arbejdsprofil, samt at opsætte FairEmail forskelligt i hver profil, hvilket er en anden mulighed for at have forskellige synk-tidsplaner samt synke et andet sæt konti.
Det er også muligt at oprette [filterregler](#user-content-faq71) med en tidsbetingelse og at slumre beskeder indtil sluttidspunktet for tidsbetingelsen. This way it is possible to *snooze* business related messages until the start of the business hours. This also means that the messages will be on your device for when there is (temporarily) no internet connection.
Note that recent Android versions allow overriding DND (Do Not Disturb) per notification channel and per app, which could be used to (not) silence specific (business) notifications. Please [see here](https://support.google.com/android/answer/9069335) for more information.
For more complex schemes you could set one or more accounts to manual synchronization and send this command to FairEmail to check for new messages:
```
(adb shell) am startservice -a eu.faircode.email.POLL
```
For a specific account:
```
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
```
You can also automate turning receiving messages on and off by sending these commands to FairEmail:
```
(adb shell) am startservice -a eu.faircode.email.ENABLE
(adb shell) am startservice -a eu.faircode.email.DISABLE
```
To enable/disable a specific account:
```
(adb shell) am startservice -a eu.faircode.email.ENABLE --es account Gmail
(adb shell) am startservice -a eu.faircode.email.DISABLE --es account Gmail
```
Note that disabling an account will hide the account and all associated folders and messages.
You can automatically send commands with for example [Tasker](https://tasker.joaoapps.com/userguide/en/intents.html):
```
Ny opgave: En genkendelig
Handlingskategori: Div./Send-
hensigtshandling: eu.faircode.email.ENABLE
Mål: Tjeneste
```
To enable/disable an account with the name *Gmail*:
```
Ekstra: konto:Gmail
```
Account names are case sensitive.
Scheduling is a pro feature.
**(79) How do I use synchronize on demand (manual)?**
Normally, FairEmail maintains a connection to the configured email servers whenever possible to receive messages in real-time. If you don't want this, for example to be not disturbed or to save on battery usage, just disable receiving in the receive settings. This will stop the background service which takes care of automatic synchronization and will remove the associated status bar notification.
You can also enable *Synchronize manually* in the advanced account settings if you want to manually synchronize specific accounts only.
You can use pull-down-to-refresh in a message list or use the folder menu *Synchronize now* to manually synchronize messages.
If you want to synchronize some or all folders of an account manually, just disable synchronization for the folders (but not of the account).
You'll likely want to disabled [browse on server](#user-content-faq24) too.
**~~(80) How do I fix the error 'Unable to load BODYSTRUCTURE' ?~~**
~~The error message *Unable to load BODYSTRUCTURE* is caused by bugs in the email server,~~ ~~see [here](https://javaee.github.io/javamail/FAQ#imapserverbug) for more details.~~
~~FairEmail already tries to workaround these bugs, but if this fail you'll need to ask for support from your provider.~~
**~~(81) Can you make the background of the original message dark in the dark theme?~~**
~~The original message is shown as the sender has sent it, including all colors.~~ ~~Changing the background color would not only make the original view not original anymore, it can also result in unreadable messages.~~
**(82) What is a tracking image?**
Please see [here](https://en.wikipedia.org/wiki/Web_beacon) about what a tracking image exactly is. In short tracking images keep track if you opened a message.
FairEmail will in most cases automatically recognize tracking images and replace them by this icon:
Automatic recognition of tracking images can be disabled in the privacy settings.
**(84) What are local contacts for?**
Local contact information is based on names and addresses found in incoming and outgoing messages.
The main use of the local contacts storage is to offer auto completion when no contacts permission has been granted to FairEmail.
Another use is to generate [shortcuts](#user-content-faq31) on recent Android versions to quickly send a message to frequently contacted people. This is also why the number of times contacted and the last time contacted is being recorded and why you can make a contact a favorite or exclude it from favorites by long pressing it.
The list of contacts is sorted on number of times contacted and the last time contacted.
By default only names and addresses to whom you send messages to will be recorded. You can change this in the send settings.
**(85) Why is an identity not available?**
An identity is available for sending a new message or replying or forwarding an existing message only if:
* identiteten er opsat til synkronisering (afsendte beskeder)
* den tilknyttede konto er opsat til synkronisering (modtagne beskeder)
* den tilknyttede konto har en udkastmappe
FairEmail will try to select the best identity based on the *to* address of the message replied to / being forwarded.
**~~(86) What are 'extra privacy features'?~~**
~~The advanced option *extra privacy features* enables:~~
* ~~Opslag af ejeren af IP-adressen for et link~~
* ~~Detektering og fjernelse af [sporingsbilleder](#user-content-faq82)~~
**(87) What does 'invalid credentials' mean?**
The error message *invalid credentials* means either that the user name and/or password is incorrect, for example because the password was changed or expired, or that the account authorization has expired.
If the password is incorrect/expired, you will have to update the password in the account and/or identity settings.
If the account authorization has expired, you will have to select the account again. You will likely need to save the associated identity again as well.
**(88) How can I use a Yahoo, AOL or Sky account?**
The preferred way to set up a Yahoo account is by using the quick setup wizard, which will use OAuth instead of a password and is therefore safer (and easier as well).
To authorize a Yahoo, AOL, or Sky account you will need to create an app password. For instructions, please see here:
* [til Yahoo](https://help.yahoo.com/kb/generate-third-party-passwords-sln15241.html)
* [til AOL](https://help.aol.com/articles/Create-and-manage-app-password)
* [til Sky](https://www.sky.com/help/articles/getting-started-with-sky-yahoo-mail) (under *Andre e-mail apps*)
Please see [this FAQ](#user-content-faq111) about OAuth support.
Note that Yahoo, AOL, and Sky do not support standard push messages. The Yahoo email app uses a proprietary, undocumented protocol for push messages.
Push messages require [IMAP IDLE](https://en.wikipedia.org/wiki/IMAP_IDLE) and the Yahoo email server does not report IDLE as capability:
```
Y1-EVNE
* MULIGHED FOR IMAP4rev1 ID FLYT NAVNEOMRÅDE XYMHIGHESTMODSEQ UIDPLUS LITERAL+ CHILDREN X-MSG-EXT AFMARKÉR OBJEKTID
Y1 OK MULIGHED fuldført
```
**(89) How can I send plain text only messages?**
By default FairEmail sends each message both as plain text and as HTML formatted text because almost every receiver expects formatted messages these days. If you want/need to send plain text messages only, you can enable this in the advanced identity options. You might want to create a new identity for this if you want/need to select sending plain text messages on a case-by-case basis.
**(90) Why are some texts linked while not being a link?**
FairEmail will automatically link not linked web links (http and https) and not linked email addresses (mailto) for your convenience. However, texts and links are not easily distinguished, especially not with lots of [top level domains](https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains) being words. This is why texts with dots are sometimes incorrectly recognized as links, which is better than not recognizing some links.
Links for the tel, geo, rtsp and xmpp protocols will be recognized too, but links for less usual or less safe protocols like telnet and ftp will not be recognized. The regex to recognize links is already *very* complex and adding more protocols will make it only slower and possibly cause errors.
Note that original messages are shown exactly as they are, which means also that links are not automatically added.
**~~(91) Can you add periodical synchronization to save battery power?~~**
~~Synchronizing messages is an expensive proces because the local and remote messages need to be compared,~~ ~~so periodically synchronizing messages will not result in saving battery power, more likely the contrary.~~
~~See [this FAQ](#user-content-faq39) about optimizing battery usage.~~
**(92) Can you add spam filtering, verification of the DKIM signature and SPF authorization?**
Spam filtering, verification of the [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signature and [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) authorization is a task of email servers, not of an email client. Servers generally have more memory and computing power, so they are much better suited to this task than battery-powered devices. Also, you'll want spam filtered for all your email clients, possibly including web email, not just one email client. Moreover, email servers have access to information, like the IP address, etc of the connecting server, which an email client has no access to.
Spam filtering based on message headers might have been feasible, but unfortunately this technique is [patented by Microsoft](https://patents.google.com/patent/US7543076).
Recent versions of FairEmail can filter spam to a certain extend using a message classifier. Please see [this FAQ](#user-content-faq163) for more information about this.
Of course you can report messages as spam with FairEmail, which will move the reported messages to the spam folder and train the spam filter of the provider, which is how it is supposed to work. This can be done automatically with [filter rules](#user-content-faq71) too. Blocking the sender will create a filter rule to automatically move future messages of the same sender into the spam folder.
Note that the POP3 protocol gives access to the inbox only. So, it is won't be possible to report spam for POP3 accounts.
Note that you should not delete spam messages, also not from the spam folder, because the email server uses the messages in the spam folder to "learn" what spam messages are.
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
Also, FairEmail can show a small red warning flag when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server. You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
FairEmail can show a warning flag too if the domain name of the (reply) email address of the sender does not define an MX record pointing to an email server. This can be enabled in the receive settings. Be aware that this will slow down synchronization of messages significantly.
If legitimate messages are failing authentication, you should notify the sender because this will result in a high risk of messages ending up in the spam folder. Moreover, without proper authentication there is a risk the sender will be impersonated. The sender might use [this tool](https://www.mail-tester.com/) to check authentication and other things.
**(93) Can you allow installation/data storage on external storage media (sdcard)?**
FairEmail uses services and alarms, provides widgets and listens for the boot completed event to be started on device start, so it is not possible to store the app on external storage media, like an sdcard. See also [here](https://developer.android.com/guide/topics/data/install-location).
Messages, attachments, etc stored on external storage media, like an sdcard, can be accessed by other apps and is therefore not safe. See [here](https://developer.android.com/training/data-storage) for the details.
When needed you can save (raw) messages via the three-dots menu just above the message text and save attachments by tapping on the floppy icon.
If you need to save on storage space, you can limit the number of days messages are being synchronized and kept for. You can change these settings by long pressing a folder in the folder list and selecting *Edit properties*.
**(94) What does the red/orange stripe at the end of the header mean?**
The red/orange stripe at the left side of the header means that the DKIM, SPF or DMARC authentication failed. See also [this FAQ](#user-content-faq92).
**(95) Why are not all apps shown when selecting an attachment or image?**
For privacy and security reasons FairEmail does not have permissions to directly access files, instead the Storage Access Framework, available and recommended since Android 4.4 KitKat (released in 2013), is used to select files.
If an app is listed depends on if the app implements a [document provider](https://developer.android.com/guide/topics/providers/document-provider). If the app is not listed, you might need to ask the developer of the app to add support for the Storage Access Framework.
Android Q will make it harder and maybe even impossible to directly access files, see [here](https://developer.android.com/preview/privacy/scoped-storage) and [here](https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/) for more details.
**(96) Where can I find the IMAP and SMTP settings?**
The IMAP settings are part of the (custom) account settings and the SMTP settings are part of the identity settings.
**(97) What is 'cleanup' ?**
About each four hours FairEmail runs a cleanup job that:
* Removes old message texts
* Removes old attachment files
* Removes old image files
* Removes old local contacts
* Removes old log entries
Note that the cleanup job will only run when the synchronize service is active.
**(98) Why can I still pick contacts after revoking contacts permissions?**
After revoking contacts permissions Android does not allow FairEmail access to your contacts anymore. However, picking contacts is delegated to and done by Android and not by FairEmail, so this will still be possible without contacts permissions.
**(99) Can you add a rich text or markdown editor?**
FairEmail provides common text formatting (bold, italic, underline, text size and color) via a toolbar that appears after selecting some text.
A [Rich text](https://en.wikipedia.org/wiki/Formatted_text) or [Markdown](https://en.wikipedia.org/wiki/Markdown) editor would not be used by many people on a small mobile device and, more important, Android doesn't support a rich text editor and most rich text editor open source projects are abandoned. See [here](https://forum.xda-developers.com/showpost.php?p=79061829&postcount=4919) for some more details about this.
**(100) How can I synchronize Gmail categories?**
You can synchronize Gmail categories by creating filters to label categorized messages:
* Create a new filter via Gmail > Settings (wheel) > Filters and Blocked Addresses > Create a new filter
* Enter a category search (see below) in the *Has the words* field and click *Create filter*
* Check *Apply the label* and select a label and click *Create filter*
Possible categories:
```
category:social
category:updates
category:forums
category:promotions
```
Unfortunately, this is not possible for snoozed messages folder.
You can use *Force sync* in the three-dots menu of the unified inbox to let FairEmail synchronize the folder list again and you can long press the folders to enable synchronization.
**(101) What does the blue/orange dot at the bottom of the conversations mean?**
The dot shows the relative position of the conversation in the message list. The dot will be show orange when the conversation is the first or last in the message list, else it will be blue. The dot is meant as an aid when swiping left/right to go to the previous/next conversation.
The dot is disabled by default and can be enabled with the display settings *Show relative conversation position with a dot*.
**(102) How can I enable auto rotation of images?**
Images will automatically be rotated when automatic resizing of images is enabled in the settings (enabled by default). However, automatic rotating depends on the [Exif](https://en.wikipedia.org/wiki/Exif) information to be present and to be correct, which is not always the case. Particularly not when taking a photo with a camara app from FairEmail.
Note that only [JPEG](https://en.wikipedia.org/wiki/JPEG) and [PNG](https://en.wikipedia.org/wiki/Portable_Network_Graphics) images can contain Exif information.
**(104) What do I need to know about error reporting?**
* Error reports will help improve FairEmail
* Error reporting is optional and opt-in
* Error reporting can be enabled/disabled in the settings, section miscellaneous
* Error reports will automatically be sent anonymously to [Bugsnag](https://www.bugsnag.com/)
* Bugsnag for Android is [open source](https://github.com/bugsnag/bugsnag-android)
* See [here](https://docs.bugsnag.com/platforms/android/automatically-captured-data/) about what data will be sent in case of errors
* See [here](https://docs.bugsnag.com/legal/privacy-policy/) for the privacy policy of Bugsnag
* Error reports will be sent to *sessions.bugsnag.com:443* and *notify.bugsnag.com:443*
**(105) How does the roam-like-at-home option work?**
FairEmail will check if the country code of the SIM card and the country code of the network are in the [EU roam-like-at-home countries](https://en.wikipedia.org/wiki/European_Union_roaming_regulations#Territorial_extent) and assumes no roaming if the country codes are equal and the advanced roam-like-at-home option is enabled.
So, you don't have to disable this option if you don't have an EU SIM or are not connected to an EU network.
**(106) Which launchers can show a badge count with the number of unread messages?**
Please [see here](https://github.com/leolin310148/ShortcutBadger#supported-launchers) for a list of launchers which can show the number of unread messages.
Note that the notification setting *Show launcher icon with number of new messages* needs to be enabled (default enabled).
Only *new* unread messages in folders set to show new message notifications will be counted, so messages marked unread again and messages in folders set to not show new message notification will not be counted.
Depending on what you want, the notification settings *Let the number of new messages match the number of notifications* needs to be enabled or disabled.
This feature depends on support of your launcher. FairEmail merely 'broadcasts' the number of unread messages using the ShortcutBadger library. If it doesn't work, this cannot be fixed by changes in FairEmail.
Some launchers display '1' for [the monitoring notification](#user-content-faq2), despite FairEmail explicitly requesting not to show a badge for this notification. This could be caused by a bug in the launcher app or in your Android version. Please double check if the notification dot is disabled for the receive (service) notification channel. You can go to the right notification channel settings via the notification settings of FairEmail. This might not be obvious, but you can tap on the channel name for more settings.
Note that Tesla Unread is [not supported anymore](https://forum.xda-developers.com/android/general/bad-news-tesla-unread-devoloper-t3920415).
FairEmail does send a new message count intent as well:
```
eu.faircode.email.NEW_MESSAGE_COUNT
```
The number of new, unread messages will be in an integer "*count*" parameter.
**(107) How do I use colored stars?**
You can set a colored star via the *more* message menu, via multiple selection (started by long pressing a message), by long pressing a star in a conversation or automatically by using [rules](#user-content-faq71).
You need to know that colored stars are not supported by the IMAP protocol and can therefore not be synchronized to an email server. This means that colored stars will not be visible in other email clients and will be lost on downloading messages again. However, the stars (without color) will be synchronized and will be visible in other email clients, when supported.
Some email clients use IMAP keywords for colors. However, not all servers support IMAP keywords and besides that there are no standard keywords for colors.
**~~(108) Can you add permanently delete messages from any folder?~~**
~~When you delete messages from a folder the messages will be moved to the trash folder, so you have a chance to restore the messages.~~ ~~You can permanently delete messages from the trash folder.~~ ~~Permanently delete messages from other folders would defeat the purpose of the trash folder, so this will not be added.~~
**~~(109) Why is 'select account' available in official versions only?~~**
~~Using *select account* to select and authorize Google accounts require special permission from Google for security and privacy reasons.~~ ~~This special permission can only be acquired for apps a developer manages and is responsible for.~~ ~~Third party builds, like the F-Droid builds, are managed by third parties and are the responsibility of these third parties.~~ ~~So, only these third parties can acquire the required permission from Google.~~ ~~Since these third parties do not actually support FairEmail, they are most likely not going to request the required permission.~~
~~You can solve this in two ways:~~
* ~~Switch to the official version of FairEmail, see [here](https://github.com/M66B/FairEmail/blob/master/README.md#downloads) for the options~~
* ~~Use app specific passwords, see [this FAQ](#user-content-faq6)~~
~~Using *select account* in third party builds is not possible in recent versions anymore.~~ ~~In older versions this was possible, but it will now result in the error *UNREGISTERED_ON_API_CONSOLE*.~~
**(110) Why are (some) messages empty and/or attachments corrupt?**
Empty messages and/or corrupt attachments are probably being caused by a bug in the server software. Older Microsoft Exchange software is known to cause this problem. Mostly you can workaround this by disabling *Partial fetch* in the advanced account settings:
Setup > Step 1 > Manage > Tap account > Tap advanced > Partial fetch > uncheck
After disabling this setting, you can use the message 'more' (three dots) menu to 'resync' empty messages. Alternatively, you can *Delete local messages* by long pressing the folder(s) in the folder list and synchronize all messages again.
Disabling *Partial fetch* will result in more memory usage.
**(111) Is OAuth supported?**
OAuth for Gmail is supported via the quick setup wizard. The Android account manager will be used to fetch and refresh OAuth tokens for selected on-device accounts. OAuth for non on-device accounts is not supported because Google requires a [yearly security audit](https://support.google.com/cloud/answer/9110914) ($15,000 to $75,000) for this. You can read more about this [here](https://www.theregister.com/2019/02/11/google_gmail_developer/).
OAuth for Yandex and Yahoo is supported via the quick setup wizard.
OAuth for Office 365 accounts is supported, but Microsoft does not offer OAuth for Outlook, Live and Hotmail accounts (yet?).
**(112) Which email provider do you recommend?**
FairEmail is an email client only, so you need to bring your own email address.
There are plenty of email providers to choose from. Which email provider is best for you depends on your wishes/requirements. Please see the websites of [Restore privacy](https://restoreprivacy.com/secure-email/) or [Privacy Tools](https://www.privacytools.io/providers/email/) for a list of privacy oriented email providers with advantages and disadvantages.
Some providers, like ProtonMail, Tutanota, use proprietary email protocols, which make it impossible to use third party email apps. Please see [this FAQ](#user-content-faq129) for more information.
Using your own (custom) domain name, which is supported by most email providers, will make it easier to switch to another email provider.
**(113) How does biometric authentication work?**
If your device has a biometric sensor, for example a fingerprint sensor, you can enable/disable biometric authentication in the navigation (hamburger) menu of the setup screen. When enabled FairEmail will require biometric authentication after a period of inactivity or after the screen has been turned off while FairEmail was running. Activity is navigation within FairEmail, for example opening a conversation thread. The inactivity period duration can be configured in the miscellaneous settings. When biometric authentication is enabled new message notifications will not show any content and FairEmail won't be visible on the Android recents screen.
Biometric authentication is meant to prevent others from seeing your messages only. FairEmail relies on device encryption for data encryption, see also [this FAQ](#user-content-faq37).
Biometric authentication is a pro feature.
**(114) Can you add an import for the settings of other email apps?**
The format of the settings files of most other email apps is not documented, so this is difficult. Sometimes it is possible to reverse engineer the format, but as soon as the settings format changes things will break. Also, settings are often incompatible. For example, FairEmail has unlike most other email apps settings for the number of days to synchronize messages for and for the number of days to keep messages for, mainly to save on battery usage. Moreover, setting up an account/identity with the quick setup is simple, so it is not really worth the effort.
**(115) Can you add email address chips?**
Email address [chips](https://material.io/design/components/chips.html) look nice, but cannot be edited, which is quite inconvenient when you made a typo in an email address.
Note that FairEmail will select the address only when long pressing an address, which makes it easy to delete an address.
Chips are not suitable for showing in a list and since the message header in a list should look similar to the message header of the message view it is not an option to use chips for viewing messages.
Reverted [commit](https://github.com/M66B/FairEmail/commit/2c80c25b8aa75af2287f471b882ec87d5a5a5015).
**~~(116) How can I show images in messages from trusted senders by default?~~**
~~You can show images in messages from trusted senders by default by enabled the display setting *Automatically show images for known contacts*.~~
~~Contacts in the Android contacts list are considered to be known and trusted,~~ ~~unless the contact is in the group / has the label '*Untrusted*' (case insensitive).~~
**(117) Can you help me restore my purchase?**
Google manages all purchases, so as a developer I have little control over purchases. So, basically the only thing I can do, is give some advice:
* Make sure you have an active, working internet connection
* Make sure you are logged in with the right Google account and that there is nothing wrong with your Google account
* Make sure you installed FairEmail via the right Google account if you configured multiple Google accounts on your device
* Make sure the Play store app is up to date, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Open the Play store app and wait at least a minute to give it time to synchronize with the Google servers
* Open FairEmail and navigate to the pro features screen to let FairEmail check the purchases; sometimes it help to tap the *buy* button
You can also try to clear the cache of the Play store app via the Android apps settings. Restarting the device might be necessary to let the Play store recognize the purchase correctly.
Note that:
* If you get *ITEM_ALREADY_OWNED*, the Play store app probably needs to be updated, please [see here](https://support.google.com/googleplay/answer/1050566?hl=en)
* Purchases are stored in the Google cloud and cannot get lost
* There is no time limit on purchases, so they cannot expire
* Google does not expose details (name, e-mail, etc) about buyers to developers
* An app like FairEmail cannot select which Google account to use
* It may take a while until the Play store app has synchronized a purchase to another device
* Play Store purchases cannot be used without the Play Store, which is also not allowed by Play Store rules
If you cannot solve the problem with the purchase, you will have to contact Google about it.
**(118) What does 'Remove tracking parameters' exactly?**
Checking *Remove tracking parameters* will remove all [UTM parameters](https://en.wikipedia.org/wiki/UTM_parameters) from a link.
**~~(119) Can you add colors to the unified inbox widget?~~**
~~The widget is designed to look good on most home/launcher screens by making it monochrome and by using a half transparent background.~~ ~~This way the widget will nicely blend in, while still being properly readable.~~
~~Adding colors will cause problems with some backgrounds and will cause readability problems, which is why this won't be added.~~
Due to Android limitations it is not possible to dynamically set the opacity of the background and to have rounded corners at the same time.
**(120) Why are new message notifications not removed on opening the app?**
New message notifications will be removed on swiping notifications away or on marking the associated messages read. Opening the app will not remove new message notifications. This gives you a choice to leave new message notifications as a reminder that there are still unread messages.
On Android 7 Nougat and later new message notifications will be [grouped](https://developer.android.com/training/notify-user/group). Tapping on the summary notification will open the unified inbox. The summary notification can be expanded to view individual new message notifications. Tapping on an individual new message notification will open the conversation the message it is part of. See [this FAQ](#user-content-faq70) about when messages in a conversation will be auto expanded and marked read.
**(121) How are messages grouped into a conversation?**
By default FairEmail groups messages in conversations. This can be turned of in the display settings.
FairEmail groups messages based on the standard *Message-ID*, *In-Reply-To* and *References* headers. FairEmail does not group on other criteria, like the subject, because this could result in grouping unrelated messages and would be at the expense of increased battery usage.
**~~(122) Why is the recipient name/email address show with a warning color?~~**
~~The recipient name and/or email address in the addresses section will be shown in a warning color~~ ~~when the sender domain name and the domain name of the *to* address do not match.~~ ~~Mostly this indicates that the message was received *via* an account with another email address.~~
**(123) What will happen when FairEmail cannot connect to an email server?**
If FairEmail cannot connect to an email server to synchronize messages, for example if the internet connection is bad or a firewall or a VPN is blocking the connection, FairEmail will retry two times after waiting 4 and 8 seconds while keeping the device awake (=use battery power). If this fails, FairEmail will schedule an alarm to retry after 15, 30 and eventually every 60 minutes and let the device sleep (=no battery usage).
Note that [Android doze mode](https://developer.android.com/training/monitoring-device-state/doze-standby) does not allow to wake the device earlier than after 15 minutes.
*Force sync* in the three-dots menu of the unified inbox can be used to let FairEmail attempt to reconnect without waiting.
Sending messages will be retried on connectivity changes only (reconnecting to the same network or connecting to another network) to prevent the email server from blocking the connection permanently. You can pull down the outbox to retry manually.
Note that sending will not be retried in case of authentication problems and when the server rejected the message. In this case you can pull down the outbox to try again.
**(124) Why do I get 'Message too large or too complex to display'?**
The message *Message too large or too complex to display* will be shown if there are more than 100,000 characters or more than 500 links in a message. Reformatting and displaying such messages will take too long. You can try to use the original message view, powered by the browser, instead.
**(125) What are the current experimental features?**
*Message classification (version 1.1438+)*
Please see [this FAQ](#user-content-faq163) for details.
Since this is an experimental feature, my advice is to start with just one folder.
**(126) Can message previews be sent to my wearable?**
FairEmail fetches a message in two steps:
1. Fetch message headers
1. Fetch message text and attachments
Directly after the first step new messages will be notified. However, only until after the second step the message text will be available. FairEmail updates exiting notifications with a preview of the message text, but unfortunately wearable notifications cannot be updated.
Since there is no guarantee that a message text will always be fetched directly after a message header, it is not possible to guarantee that a new message notification with a preview text will always be sent to a wearable.
If you think this is good enough, you can enable the notification option *Only send notifications with a message preview to wearables* and if this does not work, you can try to enable the notification option *Show notifications with a preview text only*. Note that this applies to wearables not showing a preview text too, even when the Android Wear app says the notification has been sent (bridged).
If you want to have the full message text sent to your wearable, you can enable the notification option *Preview all text*. Note that some wearables are known to crash with this option enabled.
If you use a Samsung wearable with the Galaxy Wearable (Samsung Gear) app, you might need to enable notifications for FairEmail when the setting *Notifications*, *Apps installed in the future* is turned off in this app.
**(127) How can I fix 'Syntactically invalid HELO argument(s)'?**
The error *... Syntactically invalid HELO argument(s) ...* means that the SMTP server rejected the local IP address or host name. You can likely fix this error by enabling or disabling the advanced indentity option *Use local IP address instead of host name*.
**(128) How can I reset asked questions, for example to show images?**
You can reset asked questions via the three dots overflow menu in the miscellaneous settings.
**(129) Are ProtonMail, Tutanota supported?**
ProtonMail uses a proprietary email protocol and [does not directly support IMAP](https://protonmail.com/support/knowledge-base/imap-smtp-and-pop3-setup/), so you cannot use FairEmail to access ProtonMail.
Tutanota uses a proprietary email protocol and [does not support IMAP](https://tutanota.com/faq/#imap), so you cannot use FairEmail to access Tutanota.
**(130) What does message error ... mean?**
A series of lines with orangish or red texts with technical information means that debug mode was enabled in the miscellaneous settings.
The warning *No server found at ...* means that there was no email server registered at the indicated domain name. Replying to the message might not be possible and might result in an error. This could indicate a falsified email address and/or spam.
The error *... ParseException ...* means that there is a problem with a received message, likely caused by a bug in the sending software. FairEmail will workaround this is in most cases, so this message can mostly be considered as a warning instead of an error.
The error *...SendFailedException...* means that there was a problem while sending a message. The error will almost always include a reason. Common reasons are that the message was too big or that one or more recipient addresses were invalid.
The warning *Message too large to fit into the available memory* means that the message was larger than 10 MiB. Even if your device has plenty of storage space Android provides limited working memory to apps, which limits the size of messages that can be handled.
Please see [here](#user-content-faq22) for other error messages in the outbox.
**(131) Can you change the direction for swiping to previous/next message?**
If you read from left to right, swiping to the left will show the next message. Similarly, if you read from right to left, swiping to the right will show the next message.
This behavior seems quite natural to me, also because it is similar to turning pages.
Anyway, there is a behavior setting to reverse the swipe direction.
**(132) Why are new message notifications silent?**
Notifications are silent by default on some MIUI versions. Please see [here](http://en.miui.com/thread-3930694-1-1.html) how you can fix this.
There is a bug in some Android versions causing [setOnlyAlertOnce](https://developer.android.com/reference/android/app/Notification.Builder#setOnlyAlertOnce(boolean)) to mute notifications. Since FairEmail shows new message notifications right after fetching the message headers and FairEmail needs to update new message notifications after fetching the message text later, this cannot be fixed or worked around by FairEmail.
Android might rate limit the notification sound, which can cause some new message notifications to be silent.
**(133) Why is ActiveSync not supported?**
The Microsoft Exchange ActiveSync protocol [is patented](https://en.wikipedia.org/wiki/Exchange_ActiveSync#Licensing) and can therefore not be supported. For this reason you won't find many, if any, other email clients supporting ActiveSync.
The Microsoft Exchange Web Services protocol [is being phased out](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-changes-to-Exchange-Web-Services-EWS-API-for-Office-365/ba-p/608055).
Note that the desciption of FairEmail starts with the remark that non-standard protocols, like Microsoft Exchange Web Services and Microsoft ActiveSync are not supported.
**(134) Can you add deleting local messages?**
*POP3*
In the account settings (Setup, step 1, Manage, tap account) you can enable *Leave deleted messages on server*.
*IMAP*
Since the IMAP protocol is meant to synchronize two ways, deleting a message from the device would result in fetching the message again when synchronizing again.
However, FairEmail supports hiding messages, either via the three-dots menu in the action bar just above the message text or by multiple selecting messages in the message list. Basically this is the same as "leave on server" of the POP3 protocol with the advantage that you can show the messages again when needed.
Note that it is possible to set the swipe left or right action to hide a message.
**(135) Why are trashed messages and drafts shown in conversations?**
Individual messages will rarely be trashed and mostly this happens by accident. Showing trashed messages in conversations makes it easier to find them back.
You can permanently delete a message using the message three-dots *delete* menu, which will remove the message from the conversation. Note that this irreversible.
Similarly, drafts are shown in conversations to find them back in the context where they belong. It is easy to read through the received messages before continuing to write the draft later.
**(136) How can I delete an account/identity/folder?**
Deleting an account/identity/folder is a little bit hidden to prevent accidents.
* Account: Setup > Step 1 > Manage > Tap account
* Identity: Setup > Step 2 > Manage > Tap identity
* Folder: Long press the folder in the folder list > Edit properties
In the three-dots overflow menu at the top right there is an item to delete the account/identity/folder.
**(137) How can I reset 'Don't ask again'?**
You can reset all questions set to be not asked again in the miscellaneous settings.
**(138) Can you add calendar/contact management/synchronizing?**
Calendar and contact management can better be done by a separate, specialized app. Note that FairEmail is a specialized email app, not an office suite.
Also, I prefer to do a few things very well, instead of many things only half. Moreover, from a security perspective, it is not a good idea to grant many permissions to a single app.
You are advised to use the excellent, open source [DAVx⁵](https://f-droid.org/packages/at.bitfire.davdroid/) app to synchronize/manage your calendars/contacts.
Most providers support exporting your contacts. Please [see here](https://support.google.com/contacts/answer/1069522) about how you can import contacts if synchronizing is not possible.
Note that FairEmail does support replying to calendar invites (a pro feature) and adding calendar invites to your personal calendar.
**(139) How do I fix 'User is authenticated but not connected'?**
In fact this Microsoft Exchange specific error is an incorrect error message caused by a bug in older Exchange server software.
The error *User is authenticated but not connected* might occur if:
* Push messages are enabled for too many folders: see [this FAQ](#user-content-faq23) for more information and a workaround
* The account password was changed: changing it in FairEmail too should fix the problem
* An alias email address is being used as username instead of the primary email address
* An incorrect login scheme is being used for a shared mailbox: the right scheme is *username@domain\SharedMailboxAlias*
The shared mailbox alias will mostly be the email address of the shared account, like this:
```
dig@eksempel.dk\delt@eksempel.dk
```
Note that it should be a backslash and not a forward slash.
**(140) Why does the message text contain strange characters?**
Displaying strange characters is almost always caused by specifying no or an invalid character encoding by the sending software. FairEmail will assume [ISO 8859-1](https://en.wikipedia.org/wiki/ISO/IEC_8859-1) when no character set or when [US-ASCII](https://en.wikipedia.org/wiki/ASCII) was specified. Other than that there is no way to reliably determine the correct character encoding automatically, so this cannot be fixed by FairEmail. The right action is to complain to the sender.
**(141) How can I fix 'A drafts folder is required to send messages'?**
To store draft messages a drafts folder is required. In most cases FairEmail will automatically select the drafts folders on adding an account based on [the attributes](https://www.iana.org/assignments/imap-mailbox-name-attributes/imap-mailbox-name-attributes.xhtml) the email server sends. However, some email servers are not configured properly and do not send these attributes. In this case FairEmail tries to identify the drafts folder by name, but this might fail if the drafts folder has an unusual name or is not present at all.
You can fix this problem by manually selecting the drafts folder in the account settings (Setup, step 1, tap account, at the bottom). If there is no drafts folder at all, you can create a drafts folder by tapping on the '+' button in the folder list of the account (tap on the account name in the navigation menu).
Some providers, like Gmail, allow enabling/disabling IMAP for individual folders. So, if a folder is not visible, you might need to enable IMAP for the folder.
Quick link for Gmail: [https://mail.google.com/mail/u/0/#settings/labels](https://mail.google.com/mail/u/0/#settings/labels)
**(142) How can I store sent messages in the inbox?**
Generally, it is not a good idea to store sent messages in the inbox because this is hard to undo and could be incompatible with other email clients.
That said, FairEmail is able to properly handle sent messages in the inbox. FairEmail will mark outgoing messages with a sent messages icon for example.
The best solution would be to enable showing the sent folder in the unified inbox by long pressing the sent folder in the folder list and enabling *Show in unified inbox*. This way all messages can stay where they belong, while allowing to see both incoming and outgoing messages at one place.
If this is not an option, you can [create a rule](#user-content-faq71) to automatically move sent messages to the inbox or set a default CC/BCC address in the advanced identity settings to send yourself a copy.
**~~(143) Can you add a trash folder for POP3 accounts?~~**
[POP3](https://en.wikipedia.org/wiki/Post_Office_Protocol) is a very limited protocol. Basically only messages can be downloaded and deleted from the inbox. It is not even possible to mark a message read.
Since POP3 does not allow access to the trash folder at all, there is no way to restore trashed messages.
Note that you can hide messages and search for hidden messages, which is similar to a local trash folder, without suggesting that trashed messages can be restored, while this is actually not possible.
Version 1.1082 added a local trash folder. Note that trashing a message will permanently remove it from the server and that trashed messages cannot be restored to the server anymore.
**(144) How can I record voice notes?**
To record voice notes you can press this icon in the bottom action bar of the message composer:
This requires a compatible audio recorder app to be installed. In particular [this common intent](https://developer.android.com/reference/android/provider/MediaStore.Audio.Media.html#RECORD_SOUND_ACTION) needs to be supported.
For example [this audio recorder](https://f-droid.org/app/com.github.axet.audiorecorder) is compatible.
Voice notes will automatically be attached.
**(145) How can I set a notification sound for an account, folder or sender?**
Account:
* Enable *Separate notifications* in the advanced account settings (Setup, step 1, Manage, tap account, tap Advanced)
* Long press the account in the account list (Setup, step 1, Manage) and select *Edit notification channel* to change the notification sound
Folder:
* Long press the folder in the folder list and select *Create notification channel*
* Long press the folder in the folder list and select *Edit notification channel* to change the notification sound
Sender:
* Open a message from the sender and expand it
* Expand the addresses section by tapping on the down arrow
* Tap on the bell icon to create or edit a notification channel and to change the notification sound
The order of precendence is: sender sound, folder sound, account sound and default sound.
Setting a notification sound for an account, folder or sender requires Android 8 Oreo or later and is a pro feature.
**(146) How can I fix incorrect message times?**
Since the sent date/time is optional and can be manipulated by the sender, FairEmail uses the server received date/time by default.
Sometimes the server received date/time is incorrect, mostly because messages were incorrectly imported from another server and sometimes due to a bug in the email server.
In these rare cases, it is possible to let FairEmail use either the date/time from the *Date* header (sent time) or from the *Received* header as a workaround. This can be changed in the advanced account settings: Setup, step 1, Manage, tap account, tap Advanced.
This will not change the time of already synchronized messages. To solve this, long press the folder(s) in the folder list and select *Delete local messages* and *Synchronize now*.
**(147) What should I know about third party versions?**
You likely came here because you are using a third party build of FairEmail.
There is **only support** on the latest Play store version, the latest GitHub release and the F-Droid build, but **only if** the version number of the F-Droid build is the same as the version number of the latest GitHub release.
F-Droid builds irregularly, which can be problematic when there is an important update. Therefore you are advised to switch to the GitHub release.
The F-Droid version is built from the same source code, but signed differently. This means that all features are available in the F-Droid version too, except for using the Gmail quick setup wizard because Google approved (and allows) one app signature only. For all other email providers, OAuth access is only available in Play Store versions and Github releases, as the email providers only permit the use of OAuth for official builds.
Note that you'll need to uninstall the F-Droid build first before you can install a GitHub release because Android refuses to install the same app with a different signature for security reasons.
Note that the GitHub version will automatically check for updates. When desired, this can be turned off in the miscellaneous settings.
Please [see here](https://github.com/M66B/FairEmail/blob/master/README.md#user-content-downloads) for all download options.
If you have a problem with the F-Droid build, please check if there is a newer GitHub version first.
**(148) How can I use an Apple iCloud account?**
There is a built-in profile for Apple iCloud, but if needed you can find the right settings [here](https://support.apple.com/en-us/HT202304).
When using two-factor authentication you might need to use an [app-specific password](https://support.apple.com/en-us/HT204397).
**(149) How does the unread message count widget work?**
The unread message count widget shows the number of unread messages either for all accounts or for a selected account, but only for the folders for which new message notifications are enabled.
Tapping on the notification will synchronize all folders for which synchronization is enabled and will open:
* the start screen when all accounts were selected
* a folder list when a specific account was selected and when new message notifications are enabled for multiple folders
* a list of messages when a specific account was selected and when new message notifications are enabled for one folder
**(150) Can you add cancelling calendar invites?**
Cancelling calendar invites (removing calendar events) requires write calendar permission, which will result in effectively granting permission to read and write *all* calendar events of *all* calendars.
Given the goal of FairEmail, privacy and security, and given that it is easy to remove a calendar event manually, it is not a good idea to request this permission for just this reason.
Inserting new calendar events can be done without permissions with special [intents](https://developer.android.com/guide/topics/providers/calendar-provider.html#intents). Unfortunately, there exists no intent to delete existing calendar events.
**(151) Can you add backup/restore of messages?**
An email client is meant to read and write messages, not to backup and restore messages. Note that breaking or losing your device, means losing your messages!
Instead, the email provider/server is responsible for backups.
If you want to make a backup yourself, you could use a tool like [imapsync](https://imapsync.lamiral.info/).
If you want to import an mbox file to an existing email account, you can use Thunderbird on a desktop computer and the [ImportExportTools](https://addons.thunderbird.net/nl/thunderbird/addon/importexporttools/) add-on.
**(152) How can I insert a contact group?**
You can insert the email addresses of all contacts in a contact group via the three dots menu of the message composer.
You can define contact groups with the Android contacts app, please see [here](https://support.google.com/contacts/answer/30970) for instructions.
**(153) Why does permanently deleting Gmail message not work?**
You might need to change [the Gmail IMAP settings](https://mail.google.com/mail/u/0/#settings/fwdandpop) on a desktop browser to make it work:
* When I mark a message in IMAP as deleted: Auto-Expunge off - Wait for the client to update the server.
* When a message is marked as deleted and expunged from the last visible IMAP folder: Immediately delete the message forever
Note that archived messages can be deleted only by moving them to the trash folder first.
Some background: Gmail seems to have an additional message view for IMAP, which can be different from the main message view.
**~~(154) Can you add favicons as contact photos?~~**
~~Besides that a [favicon](https://en.wikipedia.org/wiki/Favicon) might be shared by many email addresses with the same domain name~~ ~~and therefore is not directly related to an email address, favicons can be used to track you.~~
**(155) What is a winmail.dat file?**
A *winmail.dat* file is sent by an incorrectly configured Outlook client. It is a Microsoft specific file format ([TNEF](https://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format)) containing a message and possibly attachments.
You can find some more information about this file [here](https://support.mozilla.org/en-US/kb/what-winmaildat-attachment).
You can view it with for example the Android app [Letter Opener](https://play.google.com/store/apps/details?id=app.letteropener).
**(156) How can I set up an Office 365 account?**
An Office 365 account can be set up via the quick setup wizard and selecting *Office 365 (OAuth)*.
If the wizard ends with *AUTHENTICATE failed*, IMAP and/or SMTP might be disabled for the account. In this case you should ask the administrator to enable IMAP and SMTP. The procedure is documented [here](https://docs.microsoft.com/en-in/exchange/troubleshoot/configure-mailboxes/pop3-imap-owa-activesync-office-365).
If you've enabled *security defaults* in your organization, you might need to enable the SMTP AUTH protocol. Please [see here](https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission) about how to.
**(157) How can I set up an Free.fr account?**
Veuillez [voir ici](https://free.fr/assistance/597.html) pour les instructions.
**SMTP est désactivé par défaut**, veuillez [voir ici](https://free.fr/assistance/2406.html) comment il peut être activé.
Veuillez [voir ici](http://jc.etiemble.free.fr/abc/index.php/trucs-astuces/configurer-smtp-free-fr) pour un guide détaillé.
**(158) Which camera / audio recorder do you recommend?**
To take photos and to record audio a camera and an audio recorder app are needed. The following apps are open source cameras and audio recorders:
* [Open Camera](https://play.google.com/store/apps/details?id=net.sourceforge.opencamera) ([F-Droid](https://f-droid.org/en/packages/net.sourceforge.opencamera/))
* [Audio Recorder version 3.3.24+](https://play.google.com/store/apps/details?id=com.github.axet.audiorecorder) ([F-Droid](https://f-droid.org/packages/com.github.axet.audiorecorder/))
To record voice notes, etc, the audio recorder needs to support [MediaStore.Audio.Media.RECORD_SOUND_ACTION](https://developer.android.com/reference/android/provider/MediaStore.Audio.Media#RECORD_SOUND_ACTION). Oddly, most audio recorders seem not to support this standard Android action.
**(159) What are Disconnect's tracker protection lists?**
Please see [here](https://disconnect.me/trackerprotection) for more information about Disconnect's tracker protection lists.
After downloading the lists in the privacy settings, the lists can optionally be used:
* to warn about tracking links on opening links
* to recognize tracking images in messages
Tracking images will be disabled only if the corresponding main 'disable' option is enabled.
Tracking images will not be recognized when the domain is classified as '*Content*', see [here](https://disconnect.me/trackerprotection#trackers-we-dont-block) for more information.
This command can be sent to FairEmail from an automation app to update the protection lists:
```
(adb shell) am startservice -a eu.faircode.email.DISCONNECT.ME
```
Updating once a week will probably be sufficient, please see [here](https://github.com/disconnectme/disconnect-tracking-protection/commits/master) for recent lists changes.
**(160) Can you add permanent deletion of messages without confirmation?**
Permanent deletion means that messages will *irreversibly* be lost, and to prevent this from happening accidentally, this always needs to be confirmed. Even with a confirmation, some very angry people who lost some of their messages through their own fault contacted me, which was a rather unpleasant experience :-(
Advanced: the IMAP delete flag in combination with the EXPUNGE command is not supportable because both email servers and not all people can handle this, risking unexpected loss of messages. A complicating factor is that not all email servers support [UID EXPUNGE](https://tools.ietf.org/html/rfc4315).
**(161) Can you add a setting to change the primary and accent color?***
If I could, I would add a setting to select the primary and accent color right away, but unfortunately Android themes are fixed, see for example [here](https://stackoverflow.com/a/26511725/1794097), so this is not possible.
**(162) Is IMAP NOTIFY supported?***
Yes, [IMAP NOTIFY](https://tools.ietf.org/html/rfc5465) has been supported since version 1.1413.
IMAP NOTIFY support means that notifications for added, changed or deleted messages of all *subscribed* folders will be requested and if a notification is received for a subscribed folder, that the folder will be synchronized. Synchronization for subscribed folders can therefore be disable, saving folder connections to the email server.
**Important**: push messages (=always sync) for the inbox and subscription management (receive settings) need to be enabled.
**Important**: most email servers do not support this! You can check the log via the navigation menu if an email server supports the NOTIFY capability.
**(163) What is message classification?**
*This is an experimental feature!*
Message classification will attempt to automatically group emails into classes, based on their contents, using [Bayesian statistics](https://en.wikipedia.org/wiki/Bayesian_statistics). In the context of FairEmail, a folder is a class. So, for example, the inbox, the spam folder, a 'marketing' folder, etc, etc.
You can enable message classification in the miscellaneous settings. Dette aktiverer kun indlæringstilstand. Klassifikatoren vil som standard 'lære' af nye beskeder i indbakken og Spam-mappen. Mappeegenskaben *Klassificér nye beskeder i denne mappe* vil aktivere eller deaktivere 'indlæringstilstand' for en mappe. Lokale beskeder kan ryddes (langt tryk på en kontos mappe i mappelisten) og herefter gensynkroniseres for at klassificere beskederne.
Hver mappe har indstillingen *Flyt automatisk klassificerede beskeder til denne mappe* ('auto-klassificering', kort sagt). When this is turned on, new messages in other folders which the classifier thinks belong to that folder will be automatically moved.
The option *Use local spam filter* in the report spam dialog will turn on message classification in the miscellaneous settings and auto classification for the spam folder. Please understand that this is not a replacement for the spam filter of the email server and can result in [false positives and false negatives](https://en.wikipedia.org/wiki/False_positives_and_false_negatives). See also [this FAQ](#user-content-faq92).
A practical example: suppose there is a folder 'marketing' and auto message classification is enabled for this folder. Each time you move a message into this folder you'll train FairEmail that similar messages belong in this folder. Each time you move a message out of this folder you'll train FairEmail that similar messages do not belong in this folder. After moving some messages into the 'marketing' folder, FairEmail will start moving similar messages automatically into this folder. Or, the other way around, after moving some messages out of the 'marketing' folder, FairEmail will stop moving similar messages automatically into this folder. This will work best with messages with similar content (email addresses, subject and message text).
Classification should be considered as a best guess - it might be a wrong guess, or the classifier might not be confident enough to make any guess. If the classifier is unsure, it will simply leave an email where it is.
For at forhindre e-mailserveren i at flytte en besked til Spam-mappen igen og igen, vil auto-klassificering fra Spam-mappen ikke ske.
Beskedklassifikatoren beregner sandsynligheden for, at en besked hører til i en mappe (klasse). Der er to indstillinger i diverse indstillingerne, som styrer, om en besked auto-flyttes til en mappe, for hvilken auto-klassificering er aktiv:
* *Minimum class probability*: a message will only be moved when the confidence it belongs in a folder is greater than this value (default 20 %)
* *Minimum class difference*: a message will only be moved when the difference in confidence between one class and the next most likely class is greater than this value (default 50 %)
Begge betingelser skal være opfyldt, før en besked flyttes.
Hensyntagen til standardindstillingsværdier:
* Æbler 40% og bananer 30% vil blive tilsidesat, da forskellen på 25% ligger under et minimum på 50%
* Æbler 15% og bananer 5% vil blive tilsidesat, da sandsynligheden for æbker er under et minimum på 20%
* Æbler 50% og bananer 20% vil resultere i valg af æbler
Klassificeringen er optimeret til at bruge så få ressourcer som muligt, men vil uundgåeligt bruge ekstra strøm.
Alle klassificeringsdata kan slettes ved i diverse indstillingerne at slå klassificeringen fra tre gange.
[Filtreringsregler](#user-content-faq71) eksekveres før klassificering.
Beskedklassificering er en Pro-funktion, undtagen for Spam-mappen.
## Get support
FairEmail understøttes kun på smartphones, tablets og ChromeOS.
Kun seneste Play Butik- og GitHub-versioner understøttes. F-Droid build understøttes kun, hvis versionsnummeret er identisk med den seneste GitHub-udgivelses ditto. Dette betyder også, at nedgradering er uunderstøttet.
Der er ingen support for ting, som ikke er direkte relateret til FairEmail.
Der er ingen support til bygning og udvikling af ting fra dig selv.
Anmodede funktioner skal:
* være til gavn for flest brugere
* ikke komplicere brugen af FairEmail
* passer ind i FairMail-filosofien (fortroligheds- og sikkerhedsorienteret)
* overholde fællesstandarder (IMAP, SMTP mv.)
Funktioner, som ikke opfylder disse krav, afvises sandsynligvis. Dette er også for at muliggøre langsigtet vedligeholdelse og support.
Er der spørgsmål, funktionsønsker eller fejlindrapportering, så benyt [denne formular](https://contact.faircode.eu/?product=fairemailsupport).
GitHub-problemstillinger er deaktiveret grundet hyppigt misbrug.
Ophavsrettigheder © 2018-2021 Marcel Bokhorst.