Mirrors/FairEmail
1
0
Fork 0
mirror of https://github.com/M66B/FairEmail.git synced 2026-01-04 03:43:55 +01:00
Code Issues Packages Projects Releases Wiki Activity

Crowdin sync

Browse Source
This commit is contained in:
M66B
2020-10-03 14:49:57 +02:00
parent a2a7c7fc5a
commit 8d9153a7a6
76 changed files with 452 additions and 124 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/FAQ-gl-rES.md
View File

@@ -1611,6 +1611,11 @@ If you want to forward a message, consider to use the move action instead. This
Since message headers are not downloaded and stored by default to save on battery and data usage and to save storage space it is not possible to preview which messages would match a header rule condition.
Some common header conditions (regex):
* *.*Auto-Submitted:.** [RFC3834](https://tools.ietf.org/html/rfc3834)
* *.*Content-Type: multipart/report.** [RFC3462](https://tools.ietf.org/html/rfc3462)
In the three-dots *more* message menu there is an item to create a rule for a received message with the most common conditions filled in.
The POP3 protocol does not support setting keywords and moving or copying messages.
@@ -2201,7 +2206,7 @@ Note that:
* 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
* As compras do Play Store non se poden usar sen a Play Store, o que tampouco está permitido polas regras do Play Store
* 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.
@@ -2445,8 +2450,8 @@ In fact this Microsoft Exchange specific error is an incorrect error message cau
The error *User is authenticated but not connected* might occur if:
* A detección de novas mensaxes (push) está activada para demasiados cartafoles: vexa [esta pregunta frecuente](#user-content-faq23) para máis información é unha solución
* O contrasinal da conta foi cambiado: cambialo tamén en FairEmail debería solucionar este problema
* 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*