|
|
@ -723,6 +723,9 @@ but only for signed and encrypted messages because too many email servers have p
|
|
|
|
Note that the most secure way to start an encrypted email exchange is by sending signed messages first.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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,
|
|
|
|
Inline encrypted PGP in received messages is supported, but inline PGP signatures and inline PGP in outgoing messages is not supported,
|
|
|
|