![]() In doing so, it also loses the Content-Disposition headers (and adds an incorrect Content-Disposition to the version) which I think is what is causing the emails to no longer be detected as encrypted by my recipients' email clients. Looking at the email source, Proton is dropping the "This is an OpenPGP/MIME encrypted message (RFC 48)" part, and turning the version identification and encrypted message parts into attachments. ![]() ProtonMail uses client-side encryption to protect email contents and user data before they are sent to. Thunderbird records the email as it was sent, and I am able to decrypt it as expected, while the one that lands in my inbox I am not. ProtonMail is an end-to-end encrypted email service. Users can securely send emails to non-ProtonMail Users by enabling the Encrypt for Outside for an. I've been able to replicate this issue by sending encrypted emails to myself. ProtonMail relies on zero-access, end-to-end encryption. Instead they get the encrypted message as attachments and have to download and decrypt them manually with gpg. However the encrypted emails that I send end up being mangled where the email clients are no longer able to automatically encrypt them. My recipients generally use mail clients like Thunderbird which can detect, decrypt, and render such emails. I use Thunderbird via Proton Bridge and am trying to send encrypted emails.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |