#384 Enigmail could workaround broken signatures by MS Exchange Servers

[Steve_GPGTools]

Hi team,
we've added some workarounds to the most often occuring problems in order to display them correctly. It would be great if Enigmail would also be able to better handle these emails.

Attached you'll find one example, where an PGP MIME encrypted & signed email is not displayed correctly.

On problem is, that Exchange wraps the PGP MIME parts in a multipart/mixed part and adds another text/plain part.

What GPGMail does is to simply ignore the other parts for now, and only concentrates on the encrypted.asc file if it also finds a application/pgp-encrypted part. After decrypting the message, it replaces the entire content of the message and handles any signatures in the decrypted message.

Feel free to contact us if you have any questions.

The test eml file is encrypted with Patricks, Robs, Nicos, Ludwigs and our own pub key.

[Patrick Brunschwig]

Thanks for reminding me. I actually plan to improve the workaround such that the mails can be displayed like regular PGP/MIME messages.

From what I have seen, I believe that there is a way to do this, even though it remains a hack - but better than nothing.

[Patrick Brunschwig]

I implemented several improvements:

1. mails are automatically reprocessed to display correctly. The disadvantage is that replying, forwarding etc. results in empty messages and attachments cannot be accessed.
2. If such a mail is detected, Enigmail displays a button to repair the message. This will replace the content-type and remove the unnecessary text/plain part. The message is then a completely regular PGP/MIME message.

[joncamfield]

This button is a sanity-saver; thank you so much for it. In my current setup, clicking it causes the message to disappear from its mailbox (it reappears, repaired but also marked-as-read, upon the next folder refresh). Before I open up a new ticket, I want to see if this is because of my unique setup or if it is more wide spread.