![]() The original mail and makes Thunderbird display that? The decryption/verification is implemented.Īm I right in my assumption, that Enigmail (for certain cases)Ĭreates a new mail with the decrypted parts and copied headers from The decryption is initiated by messageDecryptCb.Īs you found correctly, we differentiate 3 different cases (inline-PGP, The only reason this is done is to determine if there areĮmbedded PGP/MIME messages. Job, but it handles a lot of different cases and I am unsure whereĪll that MsgHdrToMimeMessage does is to parse a message and return a ![]() Way would be to pass aMsgHdr to MsgHdrToMimeMessage and to decrypt ![]() While this is notĮncoding related, I believe it is a consequence of how TB-Convįrom what I understood in enigmailMessengerOverlay.js, this correct pgp mime signed mails do not show up as signed.The sameĬould happen in principle with inline-PGP messages. Quoted-printable, which means that you'll need to decode this. Also UTF-8 chars areĭisplayed like =E2=80=9E=E2=80=9C due to the missing decoding.Ĭheck the "Content-Transfer-Encoding" header. Headers contained within the encrypted part are not parsed andĭisplayed alongside the normal mail body. * pgp mime messages will beĭisplayed decrypted, but not decoded At least for me the additional Is not really a problem though, because two calls toĬonvertUnicode fix this isse. The current way of handing the message to cryptMessageĪnd replacing it with whatever decryptMessage outputs has severalĭrawbacks: * for inline utf-8 messages, utf-8 will be garbled. I'm working on fixing some encoding/decryption issues in EnigmailĪnd Thunderbird Conversations. I'll quote the mail in full for future reference (still not sure when I'll be able to work on this again, though :/) As suggested, I contacted Patrick who gave some useful hints.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |