Configurar FairEmail es bastante sencillo. Deberá añadir al menos una cuenta para recibir correo electrónico y al menos una identidad si quiere enviarlo. The quick setup will add an account and an identity in one go for most major providers.
Configurar FairEmail es bastante sencillo. Deberá añadir al menos una cuenta para recibir correo electrónico y al menos una identidad si quiere enviarlo. La configuración rápida añadirá una cuenta y una identidad en un solo paso para la mayoría de los proveedores principales.
## Requisitos
@ -18,7 +18,7 @@ Si la configuración rápida no funciona, necesitará configurar una cuenta y un
Para añadir una cuenta, toque *Configuración manual y más opciones*, toque *Cuentas* y toque el botón 'más' en la parte inferior y seleccione IMAP (o POP3). Seleccione un proveedor de la lista, introduzca su nombre de usuario (que es por lo general su dirección de correo) e introduzca su contraseña. Pulse *Comprobar* para permitir que FairEmail se conecte al servidor de correo y obtenga una lista de carpetas de sistema. Luego de revisar la selección de carpetas de sistema puede añadir la cuenta pulsando *Guardar*.
If your provider is not in the list of providers, there are thousands of providers, select *Custom*. Introduzca el nombre de dominio, por ejemplo *gmail.com* y pulse *Obtener configuración*. Si su proveedor soporta [auto-descubrimiento](https://tools.ietf.org/html/rfc6186), FairEmail completará el nombre de host y el número de puerto. En caso contrario compruebe el nombre de host IMAP, número de puerto, y protocolo (SSL/TLS o STARTTLS) en las instrucciones de configuración de su proveedor. Para más información, por favor vea [aquí](https://github.com/M66B/FairEmail/blob/master/FAQ.md#authorizing-accounts).
Si su proveedor no está en la lista de proveedores, hay miles de proveedores, selecciona *Personalizado*. Introduzca el nombre de dominio, por ejemplo *gmail.com* y seleccione *Obtener configuración*. Si su proveedor soporta [auto-descubrimiento](https://tools.ietf.org/html/rfc6186), FairEmail completará el nombre de host y el número de puerto, de lo contrario compruebe el nombre de host IMAP, número de puerto, y protocolo (SSL/TLS o STARTTLS) en las instrucciones de configuración de su proveedor. Para más información, por favor vea [aquí](https://github.com/M66B/FairEmail/blob/master/FAQ.md#authorizing-accounts).
## Configurar identidad - para enviar correo
@ -34,7 +34,7 @@ Si desea buscar direcciones de correo electrónico, que se muestren fotos de con
## Configurar optimizaciones de batería - para recibir correo continuamente
En versiones recientes de Android, éste pondrá aplicaciones a dormir cuando la pantalla esté apagada durante algún tiempo para reducir el uso de batería. Si desea recibir nuevos correos sin retrasos, debería desactivar las optimizaciones de batería para FairEmail. Tap *Manage* and follow the instructions.
En versiones recientes de Android, éste pondrá aplicaciones a dormir cuando la pantalla esté apagada durante algún tiempo para reducir el uso de batería. Si desea recibir nuevos correos sin retrasos, debería desactivar las optimizaciones de batería para FairEmail. Seleccione *Administrar* y sigua las instrucciones.
@ -539,7 +539,7 @@ Note that the desciption of FairEmail starts with the remark that non-standard p
Please see [here](https://support.office.com/en-us/article/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) for the Microsoft documentation about configuring an email client. There is also a section about common connection errors and solutions.
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Please see [this FAQ](#user-content-faq110) for a workaround.
Some older Exchange server versions have a bug causing empty message and corrupt attachments. Pro provizorní řešení se prosím podívejte na [tento nejčastější dotaz](#user-content-faq110).
Please see [this FAQ](#user-content-faq133) about ActiveSync support.
@ -922,7 +922,7 @@ Possible causes are:
* The email server is refusing to accept a message, for example because it is too large or contains unacceptable links
* There are too many connections to the server, see also the next question
Many public Wi-Fi networks block outgoing email to prevent spam. Sometimes you can workaround this by using another SMTP port. See the documentation of the provider for the usable port numbers.
Many public Wi-Fi networks block outgoing email to prevent spam. Někdy to lze obejít použitím jiného SMTP portu. See the documentation of the provider for the usable port numbers.
If you are using a [VPN](https://en.wikipedia.org/wiki/Virtual_private_network), the VPN provider might block the connection because it is too aggressively trying to prevent spam. Note that [Google Fi](https://fi.google.com/) is using a VPN too.
@ -1240,7 +1240,7 @@ FairEmail will by default synchronize the folder list on each connection. Since
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.
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.
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). Toto lze obejít snížením intervalu udržování spojení v pokročilém nastavení účtu, např. na 9 nebo 15 minut. Note that battery optimizations need to be disabled in setup step 3 to reliably keep connections alive.
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.
@ -1295,7 +1295,7 @@ The error '*Handshake failed ... HANDSHAKE_FAILURE_ON_CLIENT_HELLO ...*' might b
The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION ...*' might be caused by enabling hardening connections in the connection settings or by Android not supporting older protocols anymore, like SSLv3.
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something).
Android 8 Oreo and later [do not support](https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all) SSLv3 anymore. Neexistuje způsob, jak chybějící podporu RC4 a SSLv3 obejít, neboť byla z Androidu zcela odstraněna (což by o něčem mělo vypovídat).
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.
@ -1387,7 +1387,7 @@ Please see [this FAQ](#user-content-faq141) for some more information.
You likely selected or sent an attachment or image with an outdated file manager or an outdated app which assumes all apps still have storage permissions. For security and privacy reasons modern apps like FairEmail have no full access to all files anymore. This can result into the error message *An outdated app sent a file path instead of a file stream* if a file name instead of a file stream is being shared with FairEmail because FairEmail cannot randomly open files.
You can fix this by switching to an up-to-date file manager or an app designed for recent Android versions. Alternatively, you can grant FairEmail read access to the storage space on your device in the Android app settings. Note that this workaround [won't work on Android Q](https://developer.android.com/preview/privacy/scoped-storage) anymore.
You can fix this by switching to an up-to-date file manager or an app designed for recent Android versions. Alternatively, you can grant FairEmail read access to the storage space on your device in the Android app settings. [Na Androidu Q již toto provizorní řešení nefunguje](https://developer.android.com/preview/privacy/scoped-storage).
See also [question 25](#user-content-faq25) and [what Google writes about it](https://developer.android.com/training/secure-file-sharing/share-file#RespondToRequest).
@ -2199,7 +2199,7 @@ Some email clients use IMAP keywords for colors. However, not all servers suppor
<aname="faq110"></a>
**(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:
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. Většinou to lze obejít zakázáním volby *Částečné načtení* v pokročilých nastaveních účtu:
Settings > Manual setup and more options > Accounts > tap account > tap advanced > Partial fetch > uncheck
@ -2444,7 +2444,7 @@ A series of lines with orangish or red texts with technical information means th
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 *... ParseException ...* means that there is a problem with a received message, likely caused by a bug in the sending software. FairEmail toto ve většině případů obejde, tedy lze tuto zprávu považovat spíše za varování než za chybu.
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.
If you have a question, please check the following frequently asked questions first. [At the bottom](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), you can find out how to ask other questions, request features, and report bugs.
Si tienes alguna pregunta, por favor comprueba primero las preguntas frecuentes. [En la parte inferior](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), puedes averiguar cómo hacer otras preguntas, solicitar características, y reportar errores.
Wenn Sie eine Frage haben, überprüfen Sie bitte zuerst die nachstehenden häufig gestellten Fragen (FAQ). [Ganz unten erfahren Sie](https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support), wie Sie weitere Fragen stellen, Funktionen anfordern und Fehler melden können.
M66B
4 years ago