-
Notifications
You must be signed in to change notification settings - Fork 45
Not decrypting? #145
Comments
If the message has been sent with the coding "PGP/MIME" you see this message. The two codings PGP/MIME and PGP/INLINE differ in the handling of attachements. Using PGP/MIME the attachements are encrypted/signed together with the message itself so without password for the decryption key the recipient doesn't have any information about attachements. If you use PGP/LINE you can attache files without encryption (plain MIME attachements) or you can encrypt/sign the attachements in separated PGP-messages which are transported together with the encrypted/signed message in one mail body - but in this case the recipient can see (also without password for decryption key) that there are attachements, and he can also see the name of attachements. The content itself is only visible with correct password for the decryption key. |
Understood, and I can definitely confirm that I'm getting this message with the PGP/MIME coding. On the other hand, the question still remains: how do I decrypt messages sent with PGP/MIME? Such messages decrypt normally with the enigmail plugin on Thunderbird, and they decrypt well using the normal PGP mechanisms on mutt. How do I proceed using the roundcube plugin? |
Same issue here, there doesn't seem to be much documentation.. I'll update you if I solve this tel2 |
I'm having the same issue, emails send encrypted (and I can decrypt them using a desktop client) but in roundcube there is no option to decrypt |
May be the wrong place to post this, but I don't see a logical alternative. Is there a button to decrypt messages? Private keys are imported, and I can easily encrypt and sign messages (so I know the private keys are working), but when I receive an encrypted message, I only get the usual "This is an encrypted message and can not be displayed. Sorry!" message.
If there's a button to decrypt, maybe we can make it more obvious. On the other hand, if this is supposed to happen automatically, it doesn't seem to be doing so (at least for me.)
The text was updated successfully, but these errors were encountered: