This is a Mac only problem (all OS versions). Kai mentioned that he has yet to receive a Mac, so we need some mac help on this. Forwarding encrypted messages inline results in the attachment of a p7m file (an encrypted block) and no viewable text within the inline message. Replying and forwardingas attachments have no problem.

Steps: 1. create/find an encrypted message and send it to yourself (if creating it). 2. select the message and choose to forward as inline (notice the p7m attachment and the inability to see what you are forwarding) 3. Send it to yourself 4. view the forwarded message. The same view in the compose window is the view seen in the viewing pane. Expected behavior: When composing and viewing, there should be no attachment, and the entire body should be viewable.

I can look into it...

Reading the bug description, it looks very similar to bug 141730. Bug 141730 is known and happens on all platforms. Charles, you say you only see this on Mac now?

Let me correct my comment 1. Kai is correct in many respects - the behavior I am describing is 141730 and happens on all platforms and is the more serious issue. Here is the mac specific problem, which might be less of an issue since I am forwarding the message to myself. On linux and Windows, you can view the contents of the forwarded message since all messages contained are encrypted with my cert. On the Mac, I can only see the outermost envelope. So it appears that the mac behavior is to treat the inline message as a black box whether or not you have the cert to decrypt it. On linux/windows, nested decryption appears to be taking place (i think).

The Mac has some specific code to decode apple double patr, maybe it somehow interferes with smime!

I have ported back from Nova missing code to make forward inline of encrypted message works again. I found that if I forward inline an encrypted message and then forward inline the forwarded message, it crash!

I think the patch I posted is more for bug 141730! Also the crash occurs when I first forward as attachment an encrypted message and then forward the new message inline. Looks like I overwrite the memory which give me some random crash...

Comment on attachment 91197 [details] [diff] [review] Proposed fix, v1 (need more work) this patch has been moved into bug 141730

If I understand correctly, this bug will be fixed once we have correctly fixed bugs 141730?

I am not sure. But me must first fix bug 141730...

Charles, can you please test whether this is fixed with today's trunk build?

as far I can tell, this is fixed for me.

Fixed and verified with the fix for bug 141730.

.

Reopening this - as it is really bug 141730 for the Mac. Using the 20021204 OSX Trunk build, this problem has resurfaced. Replies appear to still be working.

Verifying again. Not reopened.

.