<stringname="title_ask_show_html">Η προβολή του αρχικού μηνύματος μπορεί να προδώσει ευαίσθητα προσωπικά δεδομένα</string>
<stringname="title_ask_show_html_dark"comment="title_ask_show_html_dark Title for checkbox to display original messages with a dark theme">Use dark theme</string>
<stringname="title_ask_show_html_dark"comment="title_ask_show_html_dark Title for checkbox to display original messages with a dark theme">Χρήση σκοτεινού θέματος</string>
<stringname="title_ask_show_html_remark">Η προβολή του αρχικού μηνύματος σε σκούρο φόντο δεν είναι εφικτή, καθώς ενδέχεται να κάνει αόρατα κείμενα και εικόνες με σκούρα χρώματα</string>
<stringname="title_ask_show_html_images">Να προβάλλονται πάντοτε οι εικόνες κατά την προβολή των αρχικών μηνυμάτων</string>
<stringname="title_ask_show_image">Η προβολή των εικόνων ίσως προκαλέσει διαρροή ευαίσθητων προσωπικών δεδομένων</string>
<stringname="title_setup_doze_hint">Lehet hogy ez érdekesnek hangozhat, de az akkumulátor optimalizációk kikapcsolása esetén kevesebb lesz az akkumulátor-használat</string>
<stringname="title_setup_doze_instructions">A következő képernyőn válassza az \"Összes alkalmazás\"-t, keresse ki ezt az appot, majd válassza - és erősítse meg - a \"Ne optimalizáld\" opciót</string>
<stringname="app_search">Поиск по FairEmail</string>
<stringname="app_changelog">Что нового</string>
<stringname="app_welcome">FairEmail — это почтовое приложение с открытым исходным кодом, ориентированное на конфиденциальность и безопасность. По этой причине некоторые функции могут работать не так, как вы привыкли.</string>
<stringname="app_limitations">Например, сообщения по умолчанию переформатируются для удаления небезопасных элементов и улучшения читаемости, а открытие ссылок нуждается в подтверждении в целях безопасности. Обеопции, при желании, могут быть отключены.</string>
<stringname="app_limitations">Например, сообщения по умолчанию переформатируются для удаления небезопасных элементов и улучшения читаемости, а открытие ссылок нуждается в подтверждении в целях безопасности. Обефункции, при желании, могут быть отключены.</string>
<stringname="app_crash">FairEmail не поддерживается на этом устройстве, так как ошибки в Android вызывают сбои</string>
<stringname="app_exit">Для выхода снова перейдите \"назад\"</string>
<stringname="title_ask_show_html">Показ оригінального повідомлення може призвести до витоку конфіденційної інформації</string>
<stringname="title_ask_show_html_dark"comment="title_ask_show_html_dark Title for checkbox to display original messages with a dark theme">Use dark theme</string>
<stringname="title_ask_show_html_dark"comment="title_ask_show_html_dark Title for checkbox to display original messages with a dark theme">Використовувати темну тему</string>
<stringname="title_ask_show_html_remark">Показ оригінального повідомлення на темному тлі неможливе, оскільки воно може зробити темні тексти та зображення невидимими</string>
<stringname="title_ask_show_html_images">Завжди показувати зображення при показі оригінальних повідомлень</string>
<stringname="title_ask_show_image">Показ зображень може призвести до витоку конфіденційної інформації</string>
<stringname="title_ask_show_html_dark"comment="title_ask_show_html_dark Title for checkbox to display original messages with a dark theme">Use dark theme</string>
<stringname="title_ask_show_html_dark"comment="title_ask_show_html_dark Title for checkbox to display original messages with a dark theme">使用深色主题</string>
@ -1122,170 +1122,170 @@ Den matchede adresse vil blive vist som *via* i adresseafsnittet for modtagne be
Bemærk, at identiteter skal aktiveres for at kunne matches, samt at identiteter for andre konti ikke medtages.
Matchning udføres kun én gang efter modtagelse af en besked, så eksisterende beskeder påvirkes ikke af opsætningsændringer. You could clear local messages by long pressing a folder in the folder list and synchronize the messages again though.
Matchning udføres kun én gang efter modtagelse af en besked, så eksisterende beskeder påvirkes ikke af opsætningsændringer. Lokale beskeder kan dog ryddes vha. langt tryk på en mappe i mappelisten og dernæst synke beskeder igen.
It is possible to configure a [regex](https://en.wikipedia.org/wiki/Regular_expression) in the identity settings to match **the username** of an email address (the part before the @ sign).
Det er muligt at opsætte et [regex](https://en.wikipedia.org/wiki/Regular_expression) i identitetsindstillingerne for at få en e-mailadresses (delen før @-tegnet) matchende **brugernavn**.
Note that the domain name (the parts after the @ sign) always needs to be equal to the domain name of the identity.
Bemærk, at domænenavnet (tekst/tegn efter @) altid skal være identisk med identitetens domænenavn.
If you like to match a catch-all email address, this regex is mostly okay:
Ønskes en fang-alle e-mailadresse matchet, er dette regex for det meste OK:
```
.*
```
If you like to match the special purpose email addresses abc@example.com and xyx@example.com and like to have a fallback email address main@example.com as well, you could do something like this:
Ønskes matchning af e-mailadresserne til specielle formål, abc@eksemepel.dk og xyx@eksemepel.dk, tillige med fallback e-mailadressen hoved@eksemepel.dk, kan noget ala dette gøres:
Matched identities can be used to color code messages. The identity color takes precedence over the account color. Setting identity colors is a pro feature.
Matchede identiteter kan benyttes til beskedfarvekodning. Identitetsfarven har forrang over kontofarven. Brug af identitetsfarver er en Pro-funktion.
<br/>
<aname="faq35"></a>
**(35) Why should I be careful with viewing images, attachments, the original message, and opening links?**
**(35) Hvorfor skal man være forsigtig med at få vist billeder, vedhæftninger, originalbeskeder samt åbne links?**
Viewing remotely stored images (see also [this FAQ](#user-content-faq27)) and opening links might not only tell the sender that you have seen the message, but will also leak your IP address. See also this question: [Why email's link is more dangerous than web search's link?](https://security.stackexchange.com/questions/241139/why-emails-link-is-more-dangerous-than-web-searchs-link).
Visning af fjernlagrede billeder (tjek også [denne FAQ](#user-content-faq27)) og åbning af links fortæller muligvis ikke kun afsenderen, at beskeden er set, men lækker også ens IP-adresse. Tjek også dette spørgsmål: [Derfor 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).
Opening attachments or viewing an original message might load remote content and execute scripts, that might not only cause privacy sensitive information to leak, but can also be a security risk.
Åbning af vedhæftninger eller kigning af en original besked kan muligvis indlæse eksternt indhold og eksekvere scripts, hvilket, udover at forårsage læk af fortrolige informationer, kan udgøre en sikkerhedsrisiko.
Note that your contacts could unknowingly send malicious messages if they got infected with malware.
Bemærk, at kontakter, uden deres vidende, kan sende ondsindede beskeder i tilfælde af malware-inficering.
FairEmail formats messages again causing messages to look different from the original, but also uncovering phishing links.
FairEmail genformaterer beskeder, hvilket ændrer deres udseende ift. originalen, men samtidig også afslører phishing-links.
Note that reformatted messages are often better readable than original messages because the margins are removed, and font colors and sizes are standardized.
Bemærk, at genformaterede beskeder ofte er mere læsbare end originalerne, da margerne er fjernet, og skrifttypefarver og -størrelser er standardiserede.
The Gmail app shows images by default by downloading the images through a Google proxy server. Since the images are downloaded from the source server [in real-time](https://blog.filippo.io/how-the-new-gmail-image-proxy-works-and-what-this-means-for-you/), this is even less secure because Google is involved too without providing much benefit.
Gmail-appen viser som standard billeder ved at downloade disse via en Google-proxyserver. Da billeder 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, uden nogen større fordel, også er involveret.
You can show images and original messages by default for trusted senders on a case-by-case basis by checking *Do not ask this again for ...*.
Billeder og originalbeskeder kan som standard vises for betroede afsendere fra gang til gang ved at markere *Spørg ikke igen om ...*.
If you want to reset the default *Open with* apps, please [see here](https://www.androidauthority.com/how-to-set-default-apps-android-clear-621269/).
For nulstilling af standarden *Åbn med* apps, tjek [hér](https://www.androidauthority.com/how-to-set-default-apps-android-clear-621269/).
<br/>
<aname="faq36"></a>
**(36) How are settings files encrypted?**
**(36) Hvordan krypteres indstillingsfiler?**
Short version: AES 256 bit
Kort version: AES 256 bit
Long version:
Lang version:
* The 256 bit key is generated with *PBKDF2WithHmacSHA1* using a 128 bit secure random salt and 65536 iterations
* The cipher is *AES/CBC/PKCS5Padding*
* 256 bit nøglen genereres med *PBKDF2WithHmacSHA1* vha. en 128 bit, sikker tilfældigt salt samt 65.536 iterationer
* Cipher'en er *AES/CBC/PKCS5Padding*
<br/>
<aname="faq37"></a>
**(37) How are passwords stored?**
**(37) Hvordan lagres adgangskoder?**
All supported Android versions [encrypt all user data](https://source.android.com/security/encryption), so all data, including usernames, passwords, messages, etc, is stored encrypted.
Alle understøttede Android-versioner [krypterer alle brugerdata](https://source.android.com/security/encryption), så disse, inkl. brugernavne, adgangskoder, beskeder mv., lagres krypteret.
If the device is secured with a PIN, pattern or password, you can make the account and identity passwords visible. If this is a problem because you are sharing the device with other people, consider to use [user profiles](https://www.howtogeek.com/333484/how-to-set-up-multiple-user-profiles-on-android/).
Er enheden sikret med en PIN-kode, mønster eller adgangskode, kan konto- og identitetsadgangskoder gøres. synlige. Er dette et problem, da enheden f.eks. deles med andre, så overvej brug af [brugerprofiler](https://www.howtogeek.com/333484/how-to-set-up-multiple-user-profiles-on-android/).
<br/>
<aname="faq39"></a>
**(39) How can I reduce the battery usage of FairEmail?**
**(39) Hvordan kan FairEmails batteriforbrug reduceres?**
Recent Android versions by default report *app usage* as a percentage in the Android battery settings screen. **Confusingly, *app usage* is not the same as *battery usage* and is not even directly related to battery usage!** The app usage (while in use) will be very high because FairEmail is using a foreground service which is considered as constant app usage by Android. However, this doesn't mean that FairEmail is constantly using battery power. The real battery usage can be seen by navigating to this screen:
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 hertil!** App-brugen (under brug) vil være meget høj, da FairEmail bruger en forgrundstjeneste, hvilket af Android betragtes 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 settings*, *Battery*, three-dots menu *Battery usage*, three-dots menu *Show full device usage*
As a rule of thumb the battery usage should be below or in any case not be much higher than *Mobile network standby*. If this isn't the case, please turn on *Auto optimize* in the receive settings. If this doesn't help, please [ask for support](https://contact.faircode.eu/?product=fairemailsupport).
Som en tommelfingerregel bør strømforbruget være under, eller i hvert fald ikke meget højere end for *Mobilnetværks-standby*. Er dette ikke tilfældet, så aktivé *Automatisk optimering* i modtagelsesindstillingerne. Hjælper dette ikke, så [anmod om support](https://contact.faircode.eu/?product=fairemailsupport).
It is inevitable that synchronizing messages will use battery power because it requires network access and accessing the messages database.
Det er uundgåeligt, at besked-synkning forbruger strøm, da dette involverer adgang til både netværk og beskeddatabase.
If you are comparing the battery usage of FairEmail with another email client, please make sure the other email client is setup similarly. For example comparing always sync (push messages) and (infrequent) periodic checking for new messages is not a fair comparison.
Sammenlignes batteriforbruget for FairEmail med en anden e-mailklient, skal den anden e-mailklient er opsat på lignende vis. Det er f.eks. ikke retvisende at sammenligne kontinuerlig synk (push-beskeder) og periodisk (ikke-regelmæssig) kontrol for nye beskeder.
Reconnecting to an email server will use extra battery power, so an unstable internet connection will result in extra battery usage. Also, some email servers prematurely terminate idle connections, while [the standard](https://tools.ietf.org/html/rfc2177) says that an idle connection should be kept open for 29 minutes. In these cases you might want to synchronize periodically, for example each hour, instead of continuously. Note that polling frequently (more than every 30-60 minutes) will likely use more battery power than synchronizing always because connecting to the server and comparing the local and remote messages are expensive operations.
Gentagne gentilslutninger til en e-mailserver, f.eks. grundet en ustabil Internetforbindelse, vil øge strømforbruget. Visse e-mailservere afslutter også ikke-aktive forbindelser for tidligt, selvom [standarden](https://tools.ietf.org/html/rfc2177) dikterer, at en ikke-aktiv forbindelse bør holdes åben i 29 minutter. Periodisk synk, f.eks. hver time, kan være at foretrække i sådanne tilfælde. Bemærk, at hyppig polling (udover hvert ca. 30.-60. min) antageligt vil øge strømforbruget ift. kontinuerlig synk, da både serverforbindelsesoprettelsen samt lokal-/fjernbeskedsmatchning er ressourcekrævende.
[On some devices](https://dontkillmyapp.com/) it is necessary to *disable* battery optimizations (setup step 3) to keep connections to email servers open. In fact, leaving battery optimizations enabled can result in extra battery usage for all devices, even though this sounds contradictory!
[På visse enheder](https://dontkillmyapp.com/) er det nødvendigt at *deaktivere* batterioptimering (opsætningstrin 3) for at holde e-mailserverforbindelser åbne. Faktisk kan aktiv batterioptimering resultere i ekstra strømforbrug på alle enheder, selvom det lyder selvmodsigende!
Most of the battery usage, not considering viewing messages, is due to synchronization (receiving and sending) of messages. So, to reduce the battery usage, set the number of days to synchronize message for to a lower value, especially if there are a lot of recent messages in a folder. Long press a folder name in the folders list and select *Edit properties* to access this setting.
Størstedelen af strømforbruget, fraset at kigge beskeder, skyldes synk (modtagelse/afsendelse) af beskeder. For at reducere strømforbruget, så indstil antallet af synk-dage til en lavere værdi, især hvis der er en masse nye beskeder i en mappe. Langt tryk på et mappenavn i mappelisten, og valg af *Redigér egenskaber* giver adgang til denne indstilling.
If you have at least once a day internet connectivity, it is sufficient to synchronize messages just for one day.
Er der Internetforbindelse mindst én gang dagligt, er det tilstrækkeligt at synke beskeder blot for én dag.
Note that you can set the number of days to *keep* messages for to a higher number than to *synchronize* messages for. You could for example initially synchronize messages for a large number of days and after this has been completed reduce the number of days to synchronize messages for, but leave the number of days to keep messages for. After decreasing the number of days to keep messages for, you might want to run the cleanup in the miscellaneous settings to remove old files.
Bemærk, at det antal dage, hvori beskeder *beholdes* maksimalt kan indstilles til det antal dage, hvori beskeder *synkes*. Indledningsvis kan beskeder f.eks. synkes i mange dage, og efter at dette er fuldført reduces antallet af beskedsynkdage, mens antallet af dage, hvori beskeder skal beholdes, bevares. 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.
In the receive settings you can enable to always synchronize starred messages, which will allow you to keep older messages around while synchronizing messages for a limited number of days.
I modtagelsesindstillingerne kan man vælge altid at synke stjernemarkerede beskeder, hvilket bevarer ældre beskeder, selvom beskeder synkes i et begrænset antal dage.
Disabling the folder option *Automatically download message texts and attachments* will result in less network traffic and thus less battery usage. You could disable this option for example for the sent folder and the archive.
Deaktivering af mappeindstillingen *Download automatisk beskedtekster og vedhæftninger* vil reducere netværkstrafik og dermed strømforbrug. Denne indstilling kan deaktivere for eksempelvis Sendt-mappen og arkivet.
Synchronizing messages at night is mostly not useful, so you can save on battery usage by not synchronizing at night. In the settings you can select a schedule for message synchronization (this is a pro feature).
Synk af beskeder om natten er for det meste unødvendigt, så der kan spares strøm ved at undlade dette. En tidsplan for beskedsynk kan vælges i indstillingerne (bemærk, Pro-funktion).
FairEmail will by default synchronize the folder list on each connection. Since folders are mostly not created, renamed and deleted very often, you can save some network and battery usage by disabling this in the receive settings.
FairEmail vil som standard synke mappelisten ved hver tilslutning. Da mapper ikke særligt ofte oprettes, omdøbes og slettes, kan der spares netværks- og strømforbrug ved at deaktivere dette i modtagelsesindstillingerne.
FairEmail will by default check if old messages were deleted from the server on each connection. If you don't mind that old messages that were delete from the server are still visible in FairEmail, you can save some network and battery usage by disabling this in the receive settings.
Som standard vil FairEmail ved hver tilslutning tjekke, om gamle beskeder er slettet fra serveren. Har man intet imod, at gamle beskederr, som er slettet fra serveren, fortsat er synlige i FairEmail, kan der spares netværks- og strømforbrug ved at deaktivere dette i modtagelsesindstillingerne.
Some providers don't follow the IMAP standard and don't keep connections open long enough, forcing FairEmail to reconnect often, causing extra battery usage. You can inspect the *Log* via the main navigation menu to check if there are frequent reconnects (connection closed/reset, read/write error/timeout, etc). You can workaround this by lowering the keep-alive interval in the advanced account settings to for example 9 or 15 minutes. Note that battery optimizations need to be disabled in setup step 3 to reliably keep connections alive.
Visse udbydere følger ikke IMAP-standarden og holder ikke forbindelser åbne længe nok, hvilket tvinger FairEmail til at bruge mere strøm på ofte at genforbinde. Via hovednavigeringsmenuen kan *Loggen* 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 3 for pålideligt at holde forbindelser i live.
Some providers send every two minutes something like '*Still here*' resulting in network traffic and your device to wake up and causing unnecessary extra battery usage. You can inspect the *Log* via the main navigation menu to check if your provider is doing this. If your provider is using [Dovecot](https://www.dovecot.org/) as IMAP server, you could ask your provider to change the [imap_idle_notify_interval](https://wiki.dovecot.org/Timeouts) setting to a higher value or better yet, to disable this. If your provider is not able or willing to change/disable this, you should consider to switch to periodically instead of continuous synchronization. You can change this in the receive settings.
Visse udbydere sender hvert 2. minut noget i retning af en '*Stadig her*',-status, hvilket resulterer i netværkstrafik, vækning af enheden og samlet set et unødigt ekstra strømforbrug. *Loggen* kan tjekkes via hovednavigeringsmenuen for at se, om den anvndte udbyder gør dette. Benytter udbyderen [Dovecot](https://www.dovecot.org/) som IMAP-server, kan denne anmodes om at æ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 bemytte periodisk i stedet for kontinuerlig synk. Dette kan ændres i modtagelsesindstillingerne.
If you got the message *This provider does not support push messages* while configuring an account, consider switching to a modern provider which supports push messages (IMAP IDLE) to reduce battery usage.
Ses meddelelsen *Denne udbyder understøtter ikke push-beskeder* under en kontoopsætning, så overvej et skift til en moderne udbyder med push-beskedunderstøttelse (IMAP IDLE) for at reducere strømforbruget.
If your device has an [AMOLED](https://en.wikipedia.org/wiki/AMOLED) screen, you can save battery usage while viewing messages by switching to the black theme.
Har enheden [AMOLED](https://en.wikipedia.org/wiki/AMOLED)-skærm, kan et skift til sort tema spare strøm, mens der kigges beskeder.
If auto optimize in the receive settings is enabled, an account will automatically be switched to periodically checking for new messages when the email server:
Er autooptimering i modtagelsesindstillingerne aktiveret, skifter en konto automatisk til periodisk tjek for nye beskeder, når e-mailserveren:
* Says '*Still here*' within 3 minutes
* The email server does not support push messages
* The keep-alive interval is lower than 12 minutes
* Sender et '*Stadig her*' inden for 3 minutter
* Ikke understøtter push-beskeder
* Keep-alive intervallet er kortere end 12 min
In addition, the trash and spam folders will be automatically set to checking for new messages after three successive [too many simultaneous connections](#user-content-faq23) errors.
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.
<br/>
<aname="faq40"></a>
**(40) How can I reduce the data usage of FairEmail?**
**(40) Hvordan reduceres FairEmails dataforbrug?**
You can reduce the data usage basically in the same way as reducing battery usage, see the previous question for suggestions.
Grundlæggende reduceres netværksforbrug på samme måde som strømforbrug. Tjek forslagene ifm. foregående spørgsmål.
It is inevitable that data will be used to synchronize messages.
Data vil uundgåeligt blive forbrugt ved beskedsynk.
If the connection to the email server is lost, FairEmail will always synchronize the messages again to make sure no messages were missed. If the connection is unstable, this can result in extra data usage. In this case, it is a good idea to decrease the number of days to synchronize messages for to a minimum (see the previous question) or to switch to periodically synchronizing of messages (receive settings).
Mistes forbindelsen til e-mailserveren, vil FairEmail altid gensynke beskederne for at sikre, at de alle er tilgængelige. Er forbindelsen ustabil, medfører dette typisk ekstra dataforbrug. Det er i så fald en god idé at reducere antallet af beskedsynkdage til et minimum (tjek foregående spørgsmål) eller at skifte til periodisk beskedsynk (modtagelsesindstillinger).
To reduce data usage, you could change these advanced receive settings:
For dataforbrugsreduktion, kan disse avancerede modtagelsesindstillinger ændres:
* Check if old messages were removed from the server: disable
* Synchronize (shared) folder list: disable
* Tjek, om gamle beskeder er fjernet fra serveren
* Synk (delte) mappelister: Deaktivér
By default FairEmail does not download message texts and attachments larger than 256 KiB when there is a metered (mobile or paid Wi-Fi) internet connection. You can change this in the connection settings.
Som standard henter FairEmail ikke beskedtekster og vedhæftninger større end 256 KiB på en takseret Internetforbindelse (mobildata eller betalt Wi-Fi). Dette kan ændres i forbindelsesindstillingerne.
<br/>
<aname="faq41"></a>
**(41) How can I fix the error 'Handshake failed' ?**
**(41) Hvordan rettes fejlen 'Handshake mislykkedes'?**
There are several possible causes, so please read to the end of this answer.
Der er flere mulige årsager, så tjek slutningen af dette svar.
The error '*Handshake failed ... WRONG_VERSION_NUMBER ...*' might mean that you are trying to connect to an IMAP or SMTP server without an encrypted connection, typically using port 143 (IMAP) and port 25 (SMTP), or that a wrong protocol (SSL/TLS or STARTTLS) is being used.
Fejlen '*Handshake mislykkedes ... WRONG_VERSION_NUMBER ...*' kan betyde, at der forsøges oprettet forbindelse til en IMAP- eller SMTP-server uden forbindelseskryptering, typisk via port 143 (IMAP) og port 25 (SMTP), eller at en forkert protokol (SSL/TLS eller STARTTLS) anvendes.
Most providers provide encrypted connections using different ports, typically port 993 (IMAP) and port 465/587 (SMTP).
De fleste udbydere tilbyder krypterede forbindelser vha. forskellige porte, typisk port 993 (IMAP) og port 465/587 (SMTP).
If your provider doesn't support encrypted connections, you should ask to make this possible. If this isn't an option, you could enable *Allow insecure connections* both in the advanced settings AND the account/identity settings.
Understøtter udbyderen ikke forbindelseskryptering, bør denne anmodes om at muliggøre dette. Er dette ikke en mulighed, kan *Tillad usikre forbindelser* aktiveres i både de avancerede indstillinger OG konto-/identitetsindstillingerne.
See also [this FAQ](#user-content-faq4).
Tjek også [denne FAQ](#user-content-faq4).
Fejlen '*Handshake mislykkedes ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' is either caused by a bug in the SSL protocol implementation or by a too short DH key on the email server and can unfortunately not be fixed by FairEmail.
Fejlen '*Handshake mislykkedes ... SSLV3_ALERT_ILLEGAL_PARAMETER ...*' forårsages enten af en fejl i SSL-protokolimplementeringen eller ved en for kort DH-nøgle på e-mailserveren, hvilket FairEmail ikke kan kompensere for.
The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might be caused by the provider still using RC4, which isn't supported since [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) anymore.
Fejlen '*Handshake mislykkedes ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' kan skyldes udbyderens fortsatte brug af RC4, der siden [Android 7](https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl) ikke længere understøttes.
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Fejlen '*Handshake mislykkedes ... UNSUPPORTED_PROTOCOL eller TLSV1_ALERT_PROTOCOL_VERSION ...*' kan skyldes aktivering af forbindelseshærdning i forbindelsesindstillingerne, eller at Android ikke længere understøtter ældre protokoller såsom SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
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 ikke omgås, da begge er fjernet fra Android.
You can use [this website](https://ssl-tools.net/mailservers) or [this website](https://www.immuniweb.com/ssl/) to check for SSL/TLS problems of email servers.
Man kan bruge [dette websted](https://ssl-tools.net/mailservers) eller [dette websted](https://www.immuniweb.com/ssl/) til at tjekke for SSL-/TLS-problemer på e-mailservere.
<br/>
<aname="faq42"></a>
**(42) Can you add a new provider to the list of providers?**
**(42) Kan der blive føjet en ny udbyder til listen?**
If the provider is used by more than a few people, yes, with pleasure.
Anvendes udbyderen af flere end blot et par brugere, så ja.
The following information is needed:
Flg. oplysninger kræves:
```
<provider
@ -1303,50 +1303,50 @@ The following information is needed:
</provider>
```
The EFF [writes](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Additionally, even if you configure STARTTLS perfectly and use a valid certificate, there’s still no guarantee your communication will be encrypted.*"
EFF-[skrivelser](https://www.eff.org/nl/deeplinks/2018/06/announcing-starttls-everywhere-securing-hop-hop-email-delivery): "*Derudover er der stadig ingen garanti for, at kommunikationen krypteres, selvom STARTTLS opsættes korrekt og et gyldigt certifikat anvendes.*"
So, pure SSL connections are safer than using [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) and therefore preferred.
Rene SSL-forbindelser er derfor foretrukne grundet større sikkerhed end [STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS).
Please make sure receiving and sending messages works properly before contacting me to add a provider.
Tjek også, at beskedmodtagelse/-afsendelse fungerer korrekt, før jeg kontaktes vedr. udbydertilføjelse.
See below about how to contact me.
Tjek nedenfor vedr. kontakt.
<br/>
<aname="faq43"></a>
**(43) Can you show the original ... ?**
**(43) Kan man vise den originale ... ?**
Show original, shows the original message as the sender has sent it, including original fonts, colors, margins, etc. FairEmail does and will not alter this in any way, except for requesting [TEXT_AUTOSIZING](https://developer.android.com/reference/android/webkit/WebSettings.LayoutAlgorithm), which will *attempt* to make small text more readable.
Vis original, viser den oprindelige besked, som afsenderen har sendt den, inkl. oprindelige skrifttyper, farver, marginer 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), hvilket *forsøger* at gøre en lille tekst mere læsbar.
<br/>
<aname="faq44"></a>
**~~(44) Can you show contact photos / identicons in the sent folder?~~**
**~~(44) Kan man få vist kontaktfotos/-identikoner i Sendt-mappen?~~**
~~Contact photos and identicons are always shown for the sender because this is necessary for conversation threads.~~ ~~Getting contact photos for both the sender and receiver is not really an option because getting contact photo is an expensive operation.~~
~~Kontaktfotos og identikoner vises altid for afsenderen, da dette er nødvendigt for samtaletråde.~~ ~~At få kontaktfotos til både afsender og modtager er ikke rigtig en mulighed, da hentning af et kontaktfoto er ressourcekrævende.~~
<br/>
<aname="faq45"></a>
**(45) How can I fix 'This key is not available. To use it, you must import it as one of your own!' ?**
**(45) Hvordan løses fejlen 'Denne nøgle er utilgængelig. Før brug af den, skal den importere som en af ens egne!' ?**
You'll get the message *This key is not available. To use it, you must import it as one of your own!* when trying to decrypt a message with a public key. To fix this you'll need to import the private key.
Man ser meddelelsen *Denne nøgle er ikke tilgængelig. Før brug af den, skal den importere som en af ens egne!*, når en besked forsøges dekrypteret med en offentlig nøgle. Løsning af dettee, kræver import af den private nøgle.
<br/>
<aname="faq46"></a>
**(46) Why does the message list keep refreshing?**
**(46) Hvorfor genindlæses beskedlisten hele tiden?**
If you see a 'spinner' at the top of the message list, the folder is still being synchronized with the remote server. You can see the progress of the synchronization in the folder list. See the legend about what the icons and numbers mean.
Ses en 'spinner' (aktivitetsindikator) øverst på beskedlisten, synkes mappen stadig med fjernserveren. Forløbsstatus for den aktuelle synk kan ses i mappelisten. Tjek symbolforklaringen for betydninger af ikoner og tal.
The speed of your device and internet connection and the number of days to synchronize messages for determine how long synchronization will take. Note that you shouldn't set the number of days to synchronize messages for to more than one day in most cases, see also [this FAQ](#user-content-faq39).
Hastigheden på enheden og Internetforbindelsen samt antal beskedsynkdage afgør den samlede synkvarighed. Bemærk, at antal beskedsynkdage i de fleste tilfælde ikke bør opsættes til mere end én dag. Tjek også [denne FAQ](#user-content-faq39).
<br/>
<aname="faq47"></a>
**(47) How do I solve the error 'No primary account or no drafts folder' ?**
**(47) Hvordan løses fejlen 'Ingen primær konto/udkastmappe'?**
You'll get the error message *No primary account or no drafts folder* when trying to compose a message while there is no account set to be the primary account or when there is no drafts folder selected for the primary account. This can happen for example when you start FairEmail to compose a message from another app. FairEmail needs to know where to store the draft, so you'll need to select one account to be the primary account and/or you'll need to select a drafts folder for the primary account.
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. This can happen for example when you start FairEmail to compose a message from another app. FairEmail needs to know where to store the draft, so you'll need to select one account to be the primary account and/or you'll need to select a drafts folder for the primary account.
This can also happen when you try to reply to a message or to forward a message from an account with no drafts folder while there is no primary account or when the primary account does not have a drafts folder.
@ -646,75 +646,75 @@ Nótese que la firma S/MIME con otros algoritmos que RSA es soportada, pero te
El método de cifrado por defecto es PGP, pero el último método de cifrado utilizado será recordado para la identidad seleccionada para la próxima vez. Puede que necesite activar las opciones de envío en el menú de tres puntos de nuevo para poder seleccionar el método de cifrado.
To allow different private keys for the same email address, FairEmail will always let you select a key when there are multiple identities with the same email address for the same account.
Para permitir diferentes claves privadas para la misma dirección de correo electrónico, FairEmail siempre le permitirá seleccionar una clave cuando haya múltiples identidades con la misma dirección de correo electrónico para la misma cuenta.
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the privacy settings (PEM or DER format).
Las claves públicas son almacenadas por FairEmail y pueden ser importadas al verificar una firma por primera vez o a través de la configuración de privacidad (formatos PEM o DER).
FairEmail verifies both the signature and the complete certificate chain.
FairEmail verifica tanto la firma como la cadena completa de certificados.
Common errors:
Errores comunes:
* *No se ha encontrado ningún certificado que coincida con targetContraints*: esto seguramente significa que está usando una versión antigua de FairEmail
* *incapaz de encontrar una ruta de certificación válida para el objetivo solicitado*: básicamente esto significa que uno o más certificados intermedios o raíz no fueron encontrados
* *La clave privada no coincide con ninguna clave de cifrado*: la clave seleccionada no puede utilizarse para descifrar el mensaje, probablemente porque es la clave incorrecta
* *No hay clave privada*: no se ha seleccionado ningún certificado o no hay ningún certificado disponible en el almacén de claves Android
In case the certificate chain is incorrect, you can tap on the little info button to show the all certificates. After the certificate details the issuer or "selfSign" is shown. A certificate is self signed when the subject and the issuer are the same. Certificates from a certificate authority (CA) are marked with "[keyCertSign](https://tools.ietf.org/html/rfc5280#section-4.2.1.3)". Certificates found in the Android key store are marked with "Android".
En caso de que la cadena de certificados sea incorrecta, puede pulsar el pequeño botón de información para mostrar todos los certificados. Después de los detalles del certificado se muestra el emisor o "auto-Firmado". Un certificado es auto-Firmado cuando el sujeto y el emisor son los mismos. Los certificados de una autoridad certificadora (CA) están marcados con "[keyCertSign](https://tools.ietf.org/html/rfc5280#section-4.2.1.3)". Los certificados encontrados en el almacén de claves Android están marcados con "Android".
A valid chain looks like this:
Una cadena válida se ve así:
```
Su certificado > cero o más certificados intermedios > CA (raíz) certificado marcado con "Android"
```
Note that a certificate chain will always be invalid when no anchor certificate can be found in the Android key store, which is fundamental to S/MIME certificate validation.
Tenga en cuenta que una cadena de certificados siempre será inválida cuando no se pueda encontrar ningún certificado raíz en el almacén de claves Android, que es fundamental para la validación del certificado S/MIME.
Please see [here](https://support.google.com/pixelphone/answer/2844832?hl=en) how you can import certificates into the Android key store.
Consulte [aquí](https://support.google.com/pixelphone/answer/2844832?hl=en) cómo puede importar certificados en la tienda de claves Android.
The use of expired keys, inline encrypted/signed messages and hardware security tokens is not supported.
El uso de claves caducadas, mensajes cifrados/firmados embebidos y tokens de seguridad de hardware no está soportado.
If you are looking for a free (test) S/MIME certificate, see [here](http://kb.mozillazine.org/Getting_an_SMIME_certificate) for the options. Please be sure to [read this first](https://davidroessli.com/logs/2019/09/free-smime-certificates-in-2019/#update20191219) if you want to request an S/MIME Actalis certificate. If you are looking for a cheap S/MIME certificate, I had a good experience with [Certum](https://www.certum.eu/en/smime-certificates/).
Si está buscando un certificado S/MIME gratuito (de prueba), consulte [aquí](http://kb.mozillazine.org/Getting_an_SMIME_certificate) para ver las opciones. Por favor, asegúrese de [leer esto antes](https://davidroessli.com/logs/2019/09/free-smime-certificates-in-2019/#update20191219) si desea solicitar un certificado de S/MIME Actalis. Si está buscando un certificado S/MIME barato, he tenido buena experiencia con [Certum](https://www.certum.eu/en/smime-certificates/).
How to extract a public key from a S/MIME certificate:
Cómo extraer una clave pública de un certificado S/MIME:
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
Puede decodificar firmas S/MIME, etc, [aquí](https://lapo.it/asn1js/).
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
La firma/cifrado S/MIME es una característica pro, pero todas las demás operaciones PGP y S/MIME son gratis para usar.
<br/>
<aname="faq13"></a>
**(13) How does search on device/server work?**
**(13) ¿Cómo funciona la búsqueda en dispositivo/servidor?**
You can start searching for messages on sender (from), recipient (to, cc, bcc), subject, keywords or message text by using the magnify glass in the action bar of a folder. You can also search from any app by selecting *Search email* in the copy/paste popup menu.
Puede empezar a buscar mensajes en el remitente (de), destinatario (a, cc, cco), asunto, palabras clave o texto de mensaje mediante el uso de la lupa en la barra de acción de una carpeta. También puede buscar desde cualquier aplicación seleccionando *Buscar en FairEmail* en el menú emergente.
Searching in the unified inbox will search in all folders of all accounts, searching in the folder list will search in the associated account only and searching in a folder will search in that folder only.
Buscar en la bandeja de entrada unificada buscará en todas las carpetas de todas las cuentas, buscar en la lista de carpetas sólo buscará en la cuenta asociada y buscar en una carpeta sólo buscará en esa carpeta.
Messages will be searched for on the device first. There will be an action button with a search again icon at the bottom to continue searching on the server. You can select in which folder to continue the search.
Los mensajes se buscarán primero en el dispositivo. Habrá un botón de acción con un icono de buscar de nuevo en la parte inferior para continuar la búsqueda en el servidor. Puede seleccionar en qué carpeta continuar la búsqueda.
The IMAP protocol doesn't support searching in more than one folder at the same time. Searching on the server is an expensive operation, therefore it is not possible to select multiple folders.
El protocolo IMAP no permite buscar en más de una carpeta al mismo tiempo. Buscar en el servidor es una operación costosa, por lo tanto no es posible seleccionar múltiples carpetas.
Searching local messages is case insensitive and on partial text. The message text of local messages will not be searched if the message text was not downloaded yet. Searching on the server might be case sensitive or case insensitive and might be on partial text or whole words, depending on the provider.
La búsqueda de mensajes locales no distingue mayúsulas/minúsculas y es sobre texto parcial. El texto del mensaje de los mensajes locales no se buscará si el texto del mensaje no se ha descargado todavía. Buscar en el servidor puede ser sensible a mayúsculas o minúsculas y puede estar en texto parcial o palabras enteras, dependiendo del proveedor.
Some servers cannot handle searching in the message text when there are a large number of messages. For this case there is an option to disable searching in the message text.
Algunos servidores no pueden manejar la búsqueda en el texto del mensaje cuando hay un gran número de mensajes. Para este caso hay una opción para desactivar la búsqueda en el texto del mensaje.
It is possible to use Gmail search operators by prefixing a search command with *raw:*. If you configured just one Gmail account, you can start a raw search directly on the server by searching from the unified inbox. If you configured multiple Gmail accounts, you'll first need to navigate to the folder list or the archive (all messages) folder of the Gmail account you want to search in. Please [see here](https://support.google.com/mail/answer/7190) for the possible search operators. For example:
Es posible usar operadores de búsqueda de Gmail prefijando un comando de búsqueda con *raw:*. Si ha configurado sólo una cuenta de Gmail, puede iniciar una búsqueda directa directamente en el servidor buscando desde la bandeja de entrada unificada. Si configuró varias cuentas de Gmail, primero tendrá que navegar a la lista de carpetas o a la carpeta de archivo (todos los mensajes) de la cuenta de Gmail en la que quiere buscar. Por favor, [vea aquí](https://support.google.com/mail/answer/7190) para los posibles operadores de búsqueda. Por ejemplo:
`
raw:larger:10M`
Searching through a large number of messages on the device is not very fast because of two limitations:
Buscar a través de un gran número de mensajes en el dispositivo no es muy rápido debido a dos limitaciones:
* [sqlite](https://www.sqlite.org/), el motor de base de datos de Android tiene un límite de tamaño de registro, evitando que los mensajes de texto se almacenen en la base de datos
* Las aplicaciones Android tienen memoria limitada para trabajar, incluso si el dispositivo tiene suficiente memoria disponible
This means that searching for a message text requires that files containing the message texts need to be opened one by one to check if the searched text is contained in the file, which is a relatively expensive process.
Esto significa que la búsqueda de un texto de mensaje requiere que los archivos que contengan los textos del mensaje deban abrirse uno por uno para comprobar si el texto buscado está contenido en el archivo, que es un proceso relativamente costoso.
In the *miscellaneous settings* you can enable *Build search index* to significantly increase the speed of searching on the device, but be aware that this will increase battery and storage space usage. The search index is based on words, so searching for partial text is not possible. Searching using the search index is by default AND, so searching for *apple orange* will search for apple AND orange. Words separated by commas result in searching for OR, so for example *apple, orange* will search for apple OR orange. Both can be combined, so searching for *apple, orange banana* will search for apple OR (orange AND banana). Using the search index is a pro feature.
En la *configuración miscelánea* puede habilitar *Construir índice de búsqueda* para aumentar significativamente la velocidad de búsqueda en el dispositivo, pero tenga en cuenta que esto aumentará el uso de la batería y el espacio de almacenamiento. El índice de búsqueda se basa en palabras, por lo que no es posible buscar texto parcial. La búsqueda usando el índice de búsqueda es por defecto Y, así que buscar *manzana naranja* buscará manzana Y naranja. Las palabras separadas por comas resultan en la búsqueda de O, así que por ejemplo *manzana, naranja* buscará manzana O naranja. Ambos se pueden combinar, así que buscar *manzana, naranja banana* buscará manzana O (naranja Y banana). Using the search index is a pro feature.
From version 1.1315 it is possible to use search expressions like this:
@ -835,49 +835,49 @@ Before Android 8 Oreo: there is an advanced option in the notification settings
Android 8 Oreo and later: please see [here](https://developer.android.com/training/notify-user/channels) about how to configure notification channels. You can use the button *Default channel* in the notification settings of the app to directly go to the right Android notification channel settings.
Note that apps cannot change notification settings, including the notification light setting, on Android 8 Oreo and later anymore.
Tenga en cuenta que las aplicaciones ya no pueden cambiar los ajustes de notificación, incluyendo la configuración de la luz de notificación, en Android 8 Oreo y posteriores.
Sometimes it is necessary to disable the setting *Show message preview in notifications* or to enable the settings *Show notifications with a preview text only* to workaround bugs in Android. This might apply to notification sounds and vibrations too.
A veces es necesario desactivar la configuración *Mostrar vista previa del mensaje en las notificaciones* o habilitar *Mostrar notificaciones sólo con un texto de vista previa* para evitar un error en Android. Esto podría aplicarse también a los sonidos y vibración de notificaciones.
Setting a light color before Android 8 is not supported and on Android 8 and later not possible.
Establecer un color de luz antes de Android 8 no está soportado y no es posible en Android 8 y posteriores.
<br/>
<aname="faq22"></a>
**(22) What does account/folder error ... mean?**
**(22) ¿Qué significa el error de cuenta/carpeta?**
FairEmail does not hide errors like similar apps often do, so it is easier to diagnose problems.
FairEmail no oculta errores como las aplicaciones similares a menudo lo hacen, por lo que es más fácil diagnosticar problemas.
FairEmail will automatically try to connect again after a delay. This delay will be doubled after each failed attempt to prevent draining the battery and to prevent from being locked out permanently.
FairEmail intentará reconectarse automáticamente después de un retraso. Este retraso se duplicará tras cada intento fallido de evitar que se agote la batería y que se bloquee permanentemente el acceso.
There are general errors and errors specific to Gmail accounts (see below).
Hay errores generales y errores específicos para las cuentas de Gmail (ver abajo).
**General errors**
**Errores generales**
<aname="authfailed"></a>
The error *... Authentication failed ...* or *... AUTHENTICATE failed ...* likely means that your username or password was incorrect. Some providers expect as username just *username* and others your full email address *username@example.com*. When copying/pasting to enter a username or password, invisible characters might be copied, which could cause this problem as well. Some password managers are known to do this incorrectly too. The username might be case sensitive, so try lowercase characters only. The password is almost always case sensitive. Some providers require using an app password instead of the account password, so please check the documentation of the provider. Sometimes it is necessary to enable external access (IMAP/SMTP) on the website of the provider first. Other possible causes are that the account is blocked or that logging in has been administratively restricted in some way, for example by allowing to login from certain networks / IP addresses only.
El error *... La autenticación falló ...* o *... AUTHENTICATE falló...* probablemente significa que su nombre de usuario o contraseña era incorrecto. Algunos proveedores esperan como nombre de usuario sólo *nombre de usuario* y otros su dirección de correo electrónico completa *nombredeusuario@ejemplo.com*. Al copiar/pegar para introducir un nombre de usuario o contraseña, pueden copiarse caracteres invisibles, lo que también podría causar este problema. También se sabe que algunos administradores de contraseñas hacen esto incorrectamente. El nombre de usuario puede ser sensible a mayúsculas, así que intente sólo caracteres en minúsculas. La contraseña es casi siempre sensible a mayúsculas y minúsculas. Algunos proveedores requieren usar una contraseña de aplicación en lugar de la contraseña de la cuenta, así que por favor revise la documentación del proveedor. A veces es necesario habilitar primero el acceso externo (IMAP/SMTP) en el sitio web del proveedor. Otras posibles causas son que la cuenta está bloqueada o que el inicio de sesión ha sido restringido administrativamente de alguna manera, por ejemplo permitiendo iniciar sesión desde ciertas redes / direcciones IP solamente.
The error *... Too many bad auth attempts ...* likely means that you are using a Yahoo account password instead of an app password. Please see [this FAQ](#user-content-faq88) about how to set up a Yahoo account.
El error *... Demasiados intentos de autenticación incorrectos ...* probablemente significa que está utilizando una contraseña de cuenta Yahoo en lugar de una contraseña de la aplicación. Por favor, consulte [estas Preguntas Frecuentes](#user-content-faq88) sobre cómo configurar una cuenta Yahoo.
The message *... +OK ...* likely means that a POP3 port (usually port number 995) is being used for an IMAP account (usually port number 993).
El mensaje *... +OK ...* probablemente significa que un puerto POP3 (normalmente el número de puerto 995) está siendo usado para una cuenta IMAP (normalmente el puerto número 993).
The errors *... invalid greeting ...*, *... requires valid address ...* and *... Parameter to HELO does not conform to RFC syntax ...* can likely be solved by changing the advanced identity setting *Use local IP address instead of host name*.
Los errores *... saludo inválido ...*, *... requiere una dirección válida ...* y *... Parámetro HELO no se ajusta a la sintaxis RFC ...* puede resolverse cambiando la configuración de identidad avanzada *Utilice la dirección IP local en lugar del nombre de host*.
El error *... Couldn't connect to host ...* means that there was no response from the email server within a reasonable time (20 seconds by default). Mostly this indicates internet connectivity issues, possibly caused by a VPN or by a firewall app. You can try to increase the connection timeout in the connection settings of FairEmail, for when the email server is really slow.
El error *... No se pudo conectar al host ...* significa que no hubo respuesta del servidor de correo en un tiempo razonable (20 segundos por defecto). Esto indica principalmente problemas de conectividad a internet, posiblemente causados por una VPN o por una aplicación de firewall. Puede intentar aumentar el tiempo de espera de conexión en la configuración de conexión de FairEmail, para cuando el servidor de correo es realmente lento.
El error *... Connection refused ...* means that the email server or something between the email server and the app, like a firewall, actively refused the connection.
El error *... Conexión rechazada...* significa que el servidor de correo electrónico o algo entre el servidor de correo y la aplicación, como un cortafuegos, rechazó activamente la conexión.
The error *... Network unreachable ...* means that the email server was not reachable via the current internet connection, for example because internet traffic is restricted to local traffic only.
El error *... Red inaccesible ...* significa que el servidor de correo electrónico no fue accesible a través de la conexión a internet actual, por ejemplo, porque el tráfico de internet sólo está restringido al tráfico local.
The error *... Host is unresolved ...*, *... Unable to resolve host ...* or *... No address associated with hostname ...* means that the address of the email server could not be resolved into an IP address. This might be caused by a VPN, ad blocking or an unreachable or not properly working (local) [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) server.
El error *... Host no resuelto ...*, *... No se puede resolver el host ...* o *... Ninguna dirección asociada con el nombre de host ...* significa que la dirección del servidor de correo electrónico no se pudo resolver en una dirección IP. Esto puede ser causado por un VPN, un bloqueador de anuncios o un servidor [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) que no esté funcionando apropiadamente (local).
The error *... Software caused connection abort ...* means that the email server or something between FairEmail and the email server actively terminated an existing connection. This can for example happen when connectivity was abruptly lost. A typical example is turning on flight mode.
El error *... Software causó fin de conexión ...* significa que el servidor de correo o algo entre FairEmail y el servidor de correo terminó activamente una conexión existente. Esto puede suceder, por ejemplo, cuando la conectividad se perdió abruptamente. Un ejemplo típico es activar el modo avión.
The errors *... BYE Logging out ...*, *... Connection reset ...* mean that the email server or something between the email server and the app, for example a router or a firewall (app), actively terminated an existing connection.
Los errores *... BYE Cerrando sesión...*, *... Conexión restablecida...* significa que el servidor de correo o algo entre el servidor de correo y la aplicación, por ejemplo un router o un firewall (app), ha terminado activamente una conexión existente.
The error *... Connection closed by peer ...* might be caused by a not updated Exchange server, see [here](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) for more information.
El error *... Conexión cerrada por el par ...* podría ser causada por un servidor de Exchange no actualizado, vea [aquí](https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/) para más información.
The errors *... Read error ...*, *... Write error ...*, *... Read timed out ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
Los errores *... Error de lectura ...*, *... Error de escritura ...*, *... Tiempo de lectura agotado ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
<aname="connectiondropped"></a>
The error *... Connection dropped by server? ...* means that the email server unexpectedly terminated the connection. This sometimes happen when there were too many connections in a too short time or when a wrong password was used for too many times. In this case, please make sure your password is correct and disable receiving in the receive settings for about 30 minutes and try again. If needed, see [this FAQ](#user-content-faq23) about how you can reduce the number of connections.
@ -943,7 +943,7 @@ The errors *... Authentication failed ... No token ...* means that the Android a
The error *... Authentication failed ... network error ...* means that the Android account manager was not able to refresh the authorization of a Gmail account due to problems with the internet connection
The error *... Authentication failed ... Invalid credentials ...* could be caused by changing the account password or by having revoked the required account/contacts permissions. In case the account password was changed, you'll need to authenticate the Google account in the Android account settings again. En caso de que los permisos hayan sido revocados, puede iniciar el asistente de configuración rápida de Gmail para conceder los permisos necesarios de nuevo (no necesita configurar la cuenta de nuevo).
The error *... Authentication failed ... Credenciales inválidas ...* podría ser causado al cambiar la contraseña de la cuenta o al haber revocado los permisos de cuenta/contactos requeridos. In case the account password was changed, you'll need to authenticate the Google account in the Android account settings again. En caso de que los permisos hayan sido revocados, puede iniciar el asistente de configuración rápida de Gmail para conceder los permisos necesarios de nuevo (no necesita configurar la cuenta de nuevo).
The eror *... ServiceDisabled ...* might be caused by enrolling in the [Advanced Protection Program](https://landing.google.com/advancedprotection/): "*To read your email, you can (must) use Gmail - You won’t be able to use your Google Account with some (all) apps & services that require access to sensitive data like your emails*", see [here](https://support.google.com/accounts/answer/7519408?hl=en&ref_topic=9264881).
@ -14,9 +14,9 @@ Sie vous avez des questions, veuillez d'abord consulter la foire aux questions.
## Autorisation des comptes
In most cases, the quick setup wizard will be able to automatically identify the correct configuration.
En temps normal, l'assistant de configuration rapide sera capable d'identifier automatiquement la bonne configuration.
If the quick setup wizard fails, you'll need to manually set up an account (to receive email) and an identity (to send email). Pour ce faire, vous aurez besoin des adresses du serveur IMAP et SMTP, des numéros de port, de savoir si SSL/TLS ou STARTTLS doivent être utilisés, de votre nom d'utilisateur (habituellement votre adresse e-mail) et de votre mot de passe.
Si l'assistant de configuration rapide échoue, vous devrez configurer manuellement un compte (pour recevoir des e-mails) et une identité (pour envoyer des e-mails). Pour ce faire, vous aurez besoin des adresses du serveur IMAP et SMTP, des numéros de port, de savoir si SSL/TLS ou STARTTLS doivent être utilisés, de votre nom d'utilisateur (habituellement votre adresse e-mail) et de votre mot de passe.
Faire une recherche avec *IMAP* et le nom du fournisseur est généralement suffisant pour trouver la documentation appropriée.
@ -43,7 +43,7 @@ Questions liées:
## Comment... ?
* Change the account name: Settings, tap Manual setup and more options, tap Accounts, tap account
* Modifier le nom du compte : Paramètres, appuyez sur Configuration manuelle et plus d'options, appuyez sur Comptes, appuyez sur compte
* Changer la cible de balayage vers la gauche/droite : Paramètres, comportement de la page d'onglet, définir les actions de balayage
* Change password: Settings, tap Manual setup and more options, tap Accounts, tap account, change password
* Set a signature: Settings, tap Manual setup and more options, tap Identities, tap identity, Edit signature.
@ -14,9 +14,9 @@ Si vous avez une question, veuillez d'abord consulter ci-dessous la liste des qu
## Autorisation des comptes
In most cases, the quick setup wizard will be able to automatically identify the correct configuration.
En temps normal, l'assistant de configuration rapide sera capable d'identifier automatiquement la bonne configuration.
If the quick setup wizard fails, you'll need to manually set up an account (to receive email) and an identity (to send email). Pour ce faire, vous aurez besoin des adresses du serveur IMAP et SMTP, des numéros de port, de savoir si SSL/TLS ou STARTTLS doivent être utilisés, de votre nom d'utilisateur (habituellement votre adresse e-mail) et de votre mot de passe.
Si l'assistant de configuration rapide échoue, vous devrez configurer manuellement un compte (pour recevoir des e-mails) et une identité (pour envoyer des e-mails). Pour ce faire, vous aurez besoin des adresses du serveur IMAP et SMTP, des numéros de port, de savoir si SSL/TLS ou STARTTLS doivent être utilisés, de votre nom d'utilisateur (habituellement votre adresse e-mail) et de votre mot de passe.
Faire une recherche avec *IMAP* et le nom du fournisseur est généralement suffisant pour trouver la documentation appropriée.
@ -43,7 +43,7 @@ Questions liées:
## Comment faire pour...?
* Change the account name: Settings, tap Manual setup and more options, tap Accounts, tap account
* Modifier le nom du compte : Paramètres, appuyez sur Configuration manuelle et plus d'options, appuyez sur Comptes, appuyez sur compte
* Changer la cible de balayage vers la gauche/droite : Paramètres, comportement de la page d'onglet, définir les actions de balayage
* Change password: Settings, tap Manual setup and more options, tap Accounts, tap account, change password
* Set a signature: Settings, tap Manual setup and more options, tap Identities, tap identity, Edit signature.
M66B
4 years ago