mirror of
https://github.com/M66B/FairEmail.git
synced 2025-03-15 08:29:24 +00:00
Updated FAQ
This commit is contained in:
parent
b077ff57c5
commit
ac15b0e107
1 changed files with 5 additions and 2 deletions
7
FAQ.md
7
FAQ.md
|
@ -819,8 +819,11 @@ You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
|
|||
|
||||
*pretty Easy privacy*
|
||||
|
||||
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and hardly anyone uses this.
|
||||
Nevertheless, FairEmail can properly decode incoming p≡p messages since version 1.1519.
|
||||
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and not many people use it.
|
||||
|
||||
However, FairEmail can send and receive PGP encrypted messages, which is compatible with p≡p.
|
||||
Also, FairEmail understands incoming p≡p messages since version 1.1519,
|
||||
so the encrypted subject will be shown and the embedded message text will be shown more nicely.
|
||||
|
||||
<br />
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue