Autocrypt-capable MUAs level 1 implementation status

Last updated: 2024-11-17

Note that the below table is not complete and not up-to-date. Many more mail user agents support at least a subset of Autocrypt.

You are very welcome to submit a PR to update the below information, thanks!

MUA/project

header parsing

keygen

peer state

header inject

recommend

encrypt

setup message

setup process

gossip

uid decorative

_images/deltachat.png

delta.chat

_images/evo.png

evolution

_images/tbird.png

thunderbird

_images/k9.png

K-9 Mail

branch

branch

_images/Mutt.gif

Mutt

_images/neomutt.png

Neomutt

Letterbox

_images/balsa.jpg

Balsa

_images/notmuch.png

notmuch

branch

_images/mailpile.png

mailpile

gmime

≥3.0.4

N/A

N/A

≥3.0.4

N/A

N/A

_images/emacs.png

Emacs

_images/fairemail.png

FairEmail

_images/lttrs.png

Ltt.rs

Logos are copyright their respective owners.

Legend:

  • MUA/project: denotes a mail app, library or tool.

  • header parsing: compliant parsing of the Autocrypt header

  • keygen: secret key generation follows Autocrypt UI guidance

  • peerstate: state is kept according to spec

  • header inject: proper creation of outgoing Autocrypt header

  • recommend: implements Autocrypt recommendation

  • encrypt: encrypts outgoing messages properly

  • setup message: proper generation and processing of Autocrypt Setup Message

  • setup process: follows guidance with respect to Autocrypt account setup

_ gossip: sends out Autocrypt-Gossip headers

  • uid decorative: UID in key data is only used for decorative purposes, and in particular not for looking up keys for an e-mail address.

For developers

Source code: