>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:

   > OK, I see what the bug is now -- my previous patch always added a
   > Content-type header to the decrypted message.  This helped with a test
   > case I had where the decrypted message didn't have one, and the parsing
   > failed there.

   > With the added header, it instead fails if the decrypted message does
   > already have a Content-type header, as all encrypted messages from
   > Message has.

I came that far, then I simply tried not to insert that header but then
I could not encrypt those message, but I don't even understand the whole code.
   > So I think the fix here is to just check before adding...