Closed
Bug 775856
Opened 12 years ago
Closed 12 years ago
Message typed attached to one conversation were sent to another. New version 14, installed today. Macintosh OSX
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 646225
People
(Reporter: tony, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347
Steps to reproduce:
entered an email from the reply box at the end of the newest message in a conversation. I thought at first I had made an error, but when I attempted to send it to the correct recipient, it happened again indicating a problem with Thunderbird..
Actual results:
The message went to another conversation which caused a major problem.
Expected results:
The message I typed should have gone to the correct recipient.
Comment 1•12 years ago
|
||
I'm going to unhide this. Not that it doesn't have security implications but I think it's unlikely that an intentional attacker can put you into this state and by hiding the bug we cut off access to a lot of folks who might be able to help puzzle out the mystery here. You may also want to seek help at https://support.mozillamessaging.com/
Does this happen with other messages, or only if you reply to a specific one?
When it happened the second time was it the same (wrong) list of people, or was it a different list of recipients? If it was the same list, is there any relationship that you noticed between the message you replied to and the list of names (for example, did it instead take the names from a message near it in the list)?
I'm not actually sure what you mean by a "reply box" in a "conversation". When I open a message in a conversation (Cmd-Shift-O) I don't see a reply box anywhere. If I click the reply-all button a separate message composition window pops up.
Do you have any add-ons? If you disable them and restart do you still have the problem?
Group: core-security
It happened 3 times, I was in conversation threaded, my Thunderbird was updated this morning and this was the first set of messages I had done.
The first time I was sending to Chris. The message actually ended up on a sourceforge list for all to see. This was the address at the TOP of my coversation list. I then wrote it again to Chris using a new message, not the reply panel on the conversation. The message was successful. I then tried to contact Helen and did it from the reply box, as I thought the issue had gone away. It had not and the message again went to the sourceforge list. Being a little thick I thought I had made another mistake and tried again and it went again to sourceforge.
I have now disconnected the conversation and threading and I can see the email address so am sure it is going to the correct place.
When I have conversation and threading ticked, there is a large reply button immediately below the last message which if pressed produces a message box to fill in. This is the one that I think causes the problem as it does not show any header material and I would think it is out of sequence somewhere and autofills in the wrong address.
I have some extensions and plugins which were accepted by the new update this morning. I have not tried disconnecting them, and will do so later and report back.
Tony
Comment 3•12 years ago
|
||
Do you have the conversation extension ?
Yes I have the Conversation extension V2.4.3.
I am not using conversations and the mail system is working fine. I have not been prepared to try the conversations again to see if it is still a problem.
Tony
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Comment 6•12 years ago
|
||
Hi Tony,
Thanks for reporting. This bug is a known issue in one of the core subsystems of Thunderbird which the Conversations extension relies on, so using Conversations makes this issue much more obvious to the end-user. Unfortunately, I don't have the time to fix this, and I don't think anyone else does.
Thanks,
jonathan
You need to log in
before you can comment on or make changes to this bug.
Description
•