User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Build ID: 20110928134238 Steps to reproduce: Reply to a message with an image attached. Have digital signing turned on by default. Using IMAP Actual results: When I hit 'send' (or if it tries to autosave to IMAP), the window hangs with 'attaching' message. Have to quit the send and either turn off signing or remove the image Expected results: The message should have sent successfully.

Do you have synchronization enabled in Tools > Account Settings > (account) > Synchronization & Storage? ("Keep messages..." checked) This may make difference to determine whether it's a caching or a possible offline storage issue.

Yes, I do. BTW, it doesn't reproduce on all messages, but the ones it does, it seems to reproduce 100%

Maybe an incomplete synchronization of the image, but I wouldn't know how this relates to the digital signing. Let's see if one of the IMAP experts has an idea.

(In reply to rsx11m from comment #3) > Maybe an incomplete synchronization of the image, but I wouldn't know how > this relates to the digital signing. Let's see if one of the IMAP experts > has an idea. I can't guarantee that it's specific to IMAP, I just don't have any accounts that use POP

(In reply to dan3ny from comment #2) > Yes, I do. BTW, it doesn't reproduce on all messages, but the ones it does, > it seems to reproduce 100% Is that message sharable ? This WFM with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0a2) Gecko/20111109 Thunderbird/10.0a2

I have the problem even when I don't have images attached, or using digital signing. Just a plain jane reply. Nor has the attachment reminder been activated by any words in my email. I also have this problem on some forwards as well. I don't have synchronization enabled. It may be a time or conflict issue. I have noticed it more when I'm doing a complicated email and switching back and forth between different programs it seems to happen more often. I tried to reproduce it on the email that just gave me problems, it wouldn't reproduce the problem.

I was about to create an identical bug and found this one. I have the exact same problem on the latest thunderbird (13.0.1) on the latest version of windows 7. I have a better description of how to reproduce the problem. I am not using IMAP. I use gmail's POP server. However, the connection to the mail server is actually irrelevant. The problem happens before sending. The embedded images in the sender's original message fail to attach when attempting to reply to their message. This happens after the first time a draft is saved (whether automatically or by clicking save in the file menu). If you attempt to save a 2nd draft or send the message AFTER the first draft is made, the images no longer function and they become white outlined boxes. At this point, the message can't be sent unless you delete the white outlined boxes. I believe the bug is a failure to store the embedded images properly in the draft message. I'm not a technical expert with the thunderbird source code. I'm just a user. All you need to do to reproduce this bug is attempt to save a draft twice with the digital signature feature enabled for the account. I additionally isolated the bug by confirming that the same email can be saved as a draft when the digital signature is not enabled. The moment I re-enable the digital signature and save a draft, the images immediately stop functioning. I use a smart card to sign the email. The smart card is the feitian epass2003 using its native feitian drivers. This smart card does function correctly for the other purposes such as firefox client certificates. Please let me know if you need additional information or help testing this. Thanks for this excellent software.

xref bug 532395

duplicate of bug 468159 ?

(In reply to Thomas M. from comment #9) > duplicate of bug 468159 ? Thomas thank you. We might have a lot of other duplicate would you be interested to help us mark them duplicates ?

Closing as dup of bug 532395. If duping is wrong, please re-open with detailed explanation about difference of your case from that bug.