User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:18.104.22.168) Gecko/2009060214 Firefox/3.0.11 Build Identifier: Thunderbird 22.214.171.124 When deleting an attachment to a message on an IMAP server by right clicking in the attachment pane of the current message, the attachment actually deleted does not belong to the current message. Rather a previously viewed message attachment is deleted. There is no warning, however a dialog box does name the actual attachment being deleted, but by then there is no recovery. Reproducible: Always Steps to Reproduce: 1. Select a message having an attachment. 2. Open or save attachment (correct attachment used) 3. Select another message having an attachment. 4. Correct message displays in message pane. 5. Correct message attachment appears in attachment pane. 6. Right click on attachment and select delete from pull-down menu. 7. Dialog box indicates different attachment is being deleted. 8. Attachment pane shows current message attachment is still on server. 9. Select the first/previous message and the attachment pane shows that message was actually deleted. Actual Results: The wrong attachment is permanently deleted from the IMAP server. Expected Results: The attachment of the currently displayed message should have been deleted. This doesn't happen consistently, however I now will look for another mail program to use on my Mac because of this bugs severity. I have not noticed this behavior on Thunderbird on my Windows or Linux boxes.
Anything in tools -> Error console when this happens
Fred, same as bug 534850?
I'd think this might be a duplicate of bug 533921, which could explain both bug 534850 and bug 503125. The only tiny detail in which this bug 503125 differs is Step 6, where this bug says "Right click on attachment" instead of "right-click on attachment pane blank space". But then comment 0 also says it "doesn't happen consistently", so maybe STR have this detail wrong. Which would make it a dupe of bug 533921.
While I don't mean to diminish any pain that these bugs may have caused you in the past, it is impossible to triage, assess, or fix these bugs without more information. Since this necessary information is lacking, I am forced to close these reports; if you can provide the information, please comment in the bug so it may be reopened.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.