As a regular user of https://delta.chat, https://thunderbird.net, https://k9mail.app, https://email.faircode.eu, I strongly wish autocrypt would be supported by Proton.me when it comes to not stripping headers when using the bridge in desktop context for instance.

Please see https://support.delta.chat/t/delta-chat-to-protonmail-user/993/10

It currently prevents me from migrating existing mailboxes to proton.me and I'm sure the delta.chat community at large would enjoy being able to benefit from strong security incentives promoted by Proton's team and the usability concerns one might have with regard to reusing one's mailbox for other legitimate purposes.

Spread the goodness with interop

I agree with everyone. Please implement autocrypt in to your system - asap.

Thunderbird with Enigmail with Autocrypt, can send encrypted mail for proton user without knowing his public key. TB can ask your keyserver to obtain the public key. TB send can attach also sender's key, but Proton can not answer with encrypted email until import of a sender's key into contact :(

I know protonmail has stated objections against autocrypt due to security reasons. I however think the team should also look at it from a usability point of view. To be able to securely exchange emails with other users (without a technical background), an automated process to get end-to-end encrypted messages directly to the enduser is inevitable. Some degree of interoperability should be incorporated (if not autocrypt, something else). It is just plain annoying that services like proton mail and Tutanota are unable to communicate securely with each other. Without pointing fingers as to where it goes wrong, as end user you should simply be able to communicate with each other, regardless of the service the other side uses (otherwise we get a similar situation again as we have with whatsapp vs signal vs telegram).

Protonmail in principle supports encrypted communication with non-proton and non-pgp users, but that system is very sensitive to human error. You set a password on the initial thread, receive a reply, and want to send a reply back again. The password is no longer automatically set, and without any warning, suddenly your message is sent back without encryption (there's a different feature request for this somewhere).

All in all, I would like to urge the developers to stop inventing all kinds of new tools/products, but to properly implement these kinds of features into the proton mail solution. It would make encrypted email way more user-friendly.

Dup of https://protonmail.uservoice.com/forums/284483-feedback/suggestions/32845105-support-autocrypt-for-messaging-with-non-protonmai

makes for key exchange also dead simple via autocrypt headers
Enigmail for thunderbird already supports...

This seems like a no-brainer in terms of utility!
Please implement as soon as possible!

People can do this by using Pgp or gpg4win, and create own keys, I don't understand why it is not imputted now!

Being able to message encrypted with non-protonmail users is paramount. Please make this happen.