User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Build ID: 20120215223356 Steps to reproduce: 1. I search a message via the global search by typing in a email id, I choose the right id from the offered list and press enter. 2. search results show a list of messages, I click on one of them, the message itself and the list of its related preceding and following messages opens 3. I click in the text area of the open message, press ctrl-a to select the complete message text and press ctrl-c to copy it to the clipboard (in order to use it in an other application such as a word processor). 4. I return to the inbox of Thunderbird, select a message in the list WITHOUT opening it, press reply button in the toolbar 5. Thunderbird opens a new message window for the reply, the text area contains the right "On x/x/xx XXX wrote:" but the WRONG quote, e.g., the text which had been put to the clipboard a minute ago. Actual results: As described above, Thunderbird puts in the reply message the text that had been sent to the clipboard from a different message. It is not the clipboard content itself that is quoted. It is the text of the "copy to clipboard" operation. This only appears when copying from a message which has been searched via the global search and when replying from the inbox without opening the message before. It's an excellent way of sending confidential information to the wrong people or at least producing embarrassing message :( I encountered this effect several times until I found out how this happens exactly. It is reproducible constantly. Rebuilding the index did not help. I'm using the German version. Expected results: The new reply message should quote the text of the inbox message.

(In reply to info from comment #0) I cannot search by message-id. How can you reach "Global Search"?

Sorry. I wasn't precise enough. It's not a message id. I type in an email address to the global search text box ("Seach all messages ...").

(In reply to info from comment #2) I followed the steps you described, but I couldn't reproduce the issue. When I reply to a message, the quoted text belongs to that message, not the content in the clipboard. User Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 Application Build ID: 20120216022139

Konstantin - does it also happens in -safe-mode ?

Ludovic, I tried save mode. I then had to add the reply button to the toolbar first (since this is not the default setting). Then the same effect occured, i.e. wrong text in the reply message. I also tried to reply via the pop-up menu. But then there is no malfunction. Therefore it seems to have to do with the toolbar reply button. BTW I upgraded to TB 11 but there is no change in this behaviour, unfortunately.

I made a screencast: http://www.youtube.com/watch?v=D5kmVK-BO5s

Hum very very interesting. I'm not reproducing on 14. Hashem , Wayne do you see this ?

(In reply to Ludovic Hirlimann [:Usul] from comment #7) > Hum very very interesting. I'm not reproducing on 14. > > Hashem , Wayne do you see this ? No, I don't have this issue.

Icannot repro

I can reproduce it on two installations (11.0.1). Has anyone tried it on a German version or a non-English version respectively?

There is a detail I just came across: I order to reproduce the bug, the message in the inbox needs to be selected/focused before doing a global search. The bug does _not_ appear if I change the selected/focused message in the inbox before pressing Reply (step 4) or if there was no message selected/focused so I first have to click on a message before pressing Reply. Does this help?

We definitely have issues in this corner, see similar bug 507501 which I just reproduced. Also, bug 539648 is even more similar to this one, but I couldn't reproduce that. I think these might all be related.

comment 12 refers to bug 507541. duplicate of bug 507541?

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #13) > comment 12 refers to bug 507541. duplicate of bug 507541? Yes, good catch. This looks like a duplicate, but we should probably verify all scenarios from these bugs and/or ask reporters for confirmation before we declare this fixed. This is a pretty bad bug by the way.