OpenPGP

Mailocity publishes your OpenPGP public key so other people's mail apps can find it and send you encrypted mail. Encrypting, decrypting and signing happen in your mail app (Thunderbird, GnuPG with a mail client, K-9 / Thunderbird for Android with OpenKeychain, Proton's bridge...); the server never sees your private key.

Publishing your key

In webmail Settings → OpenPGP key, paste your public key (-----BEGIN PGP PUBLIC KEY BLOCK-----; export it from your app) and choose Publish key. The key must have a user ID with your mailbox's address. A private key is refused, so pasting one by mistake does no harm.

The card then shows the key's fingerprint and user IDs, Download gives it back as a file, Published takes it out of the directory (or puts it back) without deleting it, and Remove deletes it.

How others find it

Keys are published in the Web Key Directory (WKD), which Thunderbird, GnuPG (gpg --locate-keys you@example.com) and most OpenPGP apps look up automatically when you type an address:

https://openpgpkey.<domain>/.well-known/openpgpkey/<domain>/hu/... (the advanced method), once openpgpkey.<domain> points at the server: the domain's DNS list has the CNAME record (optional), and the certificate comes on the first lookup;
https://<domain>/.well-known/openpgpkey/hu/... (the direct method) when the domain itself points at the server.

Only published keys of active mailboxes are served, and only to the domain's own names.

Mail you receive

Webmail marks OpenPGP mail: Encrypted with OpenPGP (read it in a mail app with your key) and Signed with OpenPGP (not checked here). For S/MIME mail, see Signed mail.

Not yet

Encrypting, decrypting and signing in webmail itself, and keys for aliases (the key is published for the mailbox's own address).