mirror of
https://github.com/M66B/FairEmail.git
synced 2026-01-04 03:43:55 +01:00
Crowdin sync
This commit is contained in:
M66B
@@ -285,6 +285,7 @@ The design is based on many discussions and if you like you can discuss about it
|
||||
* [(162) Is IMAP NOTIFY supported?](#user-content-faq162)
|
||||
* [(163) What is message classification?](#user-content-faq163)
|
||||
* [(164) Can you add customizable themes?](#user-content-faq164)
|
||||
* [(165) Is Android Auto supported?](#user-content-faq165)
|
||||
|
||||
[I have another question.](#user-content-support)
|
||||
|
||||
@@ -530,8 +531,12 @@ Some providers do not keep track of sent messages or the used SMTP server might
|
||||
<a name="faq8"></a>
|
||||
**(8) Can I use a Microsoft Exchange account?**
|
||||
|
||||
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). So, it makes little sense to add this protocol anymore.
|
||||
|
||||
You can use a Microsoft Exchange account if it is accessible via IMAP, which is mostly the case. See [here](https://support.office.com/en-us/article/what-is-a-microsoft-exchange-account-47f000aa-c2bf-48ac-9bc2-83e5c6036793) for more information.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
@@ -606,7 +611,7 @@ To verify a signature or to decrypt a received message, open the message and jus
|
||||
|
||||
The first time you send a signed/encrypted message you might be asked for a sign key. FairEmail will automatically store the selected sign key in the used identity for the next time. If you need to reset the sign key, just save the identity or long press the identity in the list of identities and select *Reset sign key*. The selected sign key is visible in the list of identities. If need to select a key on a case by case basis, you can create multiple identities for the same account with the same email address.
|
||||
|
||||
In the privacy settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
In the encryption settings you can select the default encryption method (PGP or S/MIME), enable *Sign by default*, *Encrypt by default* and *Automatically decrypt messages*, but be aware that automatic decryption is not possible if user interaction is required, like selecting a key or reading a security token.
|
||||
|
||||
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server. If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
|
||||
|
||||
@@ -626,6 +631,8 @@ You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packa
|
||||
|
||||
FairEmail will send the [Autocrypt](https://autocrypt.org/) header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header. Note that the most secure way to start an encrypted email exchange is by sending signed messages first. Received Autocrypt headers will be sent to the OpenKeychain app for storage on verifying a signature or decrypting a message.
|
||||
|
||||
Although this shouldn't be necessary for most email clients, you can attach your public key to a message and if you use *.key* as extension, the mime type will correctly be *application/pgp-keys*.
|
||||
|
||||
All key handling is delegated to the OpenKey chain app for security reasons. This also means that FairEmail does not store PGP keys.
|
||||
|
||||
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported, see [here](https://josefsson.org/inline-openpgp-considered-harmful.html) about why not.
|
||||
@@ -647,7 +654,7 @@ Common errors:
|
||||
|
||||
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
|
||||
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the privacy settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
Private keys are stored by Android and can be imported via the Android advanced security settings. There is a shortcut (button) for this in the encryption settings. Android will ask you to set a PIN, pattern, or password if you didn't before. If you have a Nokia device with Android 9, please [read this first](https://nokiamob.net/2019/08/10/a-bug-prevents-nokia-1-owners-from-unlocking-their-screen-even-with-right-pin-pattern/).
|
||||
|
||||
Note that certificates can contains multiple keys for multiple purposes, for example for authentication, encryption and signing. Android only imports the first key, so to import all the keys, the certificate must first be split. This is not very trivial and you are advised to ask the certificate supplier for support.
|
||||
|
||||
@@ -657,7 +664,7 @@ The default encryption method is PGP, but the last used encryption method will b
|
||||
|
||||
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.
|
||||
|
||||
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).
|
||||
Public keys are stored by FairEmail and can be imported when verifying a signature for the first time or via the encryption settings (PEM or DER format).
|
||||
|
||||
FairEmail verifies both the signature and the complete certificate chain.
|
||||
|
||||
@@ -1780,27 +1787,27 @@ Note that recent Android versions allow overriding DND (Do Not Disturb) per noti
|
||||
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
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.POLL
|
||||
```
|
||||
|
||||
For a specific account:
|
||||
|
||||
```
|
||||
(adb shell) am startservice -a eu.faircode.email.POLL --es account Gmail
|
||||
(adb shell) am start-foreground-service -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
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE
|
||||
(adb shell) am start-foreground-service -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
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.ENABLE --es account Gmail
|
||||
(adb shell) am start-foreground-service -a eu.faircode.email.DISABLE --es account Gmail
|
||||
```
|
||||
|
||||
Note that disabling an account will hide the account and all associated folders and messages.
|
||||
@@ -2381,6 +2388,10 @@ For some background, see for [this Wikipedia article](https://en.wikipedia.org/w
|
||||
|
||||
<br />
|
||||
|
||||
*Background for unread messages*
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq126"></a>
|
||||
**(126) Can message previews be sent to my wearable?**
|
||||
|
||||
@@ -2468,8 +2479,6 @@ Android might rate limit the notification sound, which can cause some new messag
|
||||
|
||||
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.
|
||||
|
||||
<br />
|
||||
@@ -2829,7 +2838,7 @@ Tracking images will not be recognized when the domain is classified as '*Conten
|
||||
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
|
||||
(adb shell) am start-foreground-service -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.
|
||||
@@ -2922,6 +2931,22 @@ The theme colors are based on the color circle of [Johannes Itten](https://en.wi
|
||||
|
||||
<br />
|
||||
|
||||
<a name="faq165"></a>
|
||||
**(165) Is Android Auto supported?**
|
||||
|
||||
Yes, Android Auto is supported, but only with the GitHub version, please [see here](https://forum.xda-developers.com/t/app-5-0-fairemail-fully-featured-open-source-privacy-oriented-email-app.3824168/post-83801249) about why.
|
||||
|
||||
For notification (messaging) support you'll need to enable the following notification options:
|
||||
|
||||
* *Use Android 'messaging style' notification format*
|
||||
* Notification actions: *Direct reply* and (mark as) *Read*
|
||||
|
||||
You can enable other notification actions too, if you like, but they are not supported by Android Auto.
|
||||
|
||||
The developers guide is [here](https://developer.android.com/training/cars/messaging).
|
||||
|
||||
<br />
|
||||
|
||||
## Get support
|
||||
|
||||
FairEmail is supported on smartphones, tablets and ChromeOS only.
|
||||
|
||||
Reference in New Issue
Block a user