User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090627 Lightning/1.0pre Shredder/3.0b3pre I played with global search. I got a search result of 4 messages. I selected all of them and then hit the "Archive" button in the mail header. The "Archives" and subfolders "2008" and "2009" got created. One message got moved to 2008. Three other messages should have been moved to 2009 (and did get moved according to Activity Manager) but do not show up in 2009. They are no longer in the original location but I could not find them anywhere else. As a last resort I tried "Undo" four times and got all archived messages back to their original location. Archive Manager now shows "1 indexed message" in the original folder. This seems to indicate that the three others never left this original folder? Thanks to undo I have my messages back. Error console showed nothing during the whole operation Uploading screenshot ... Reproducible: Didn't try
Created attachment 385991 [details] screenshot describing the situation The red marked activities are the Archiving of the four messages. the green marked activities happened during or after the "Undo" actions
IMAP or POP3? If IMAP, could you generate a protocol log?
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #2) > IMAP or POP3? If IMAP, could you generate a protocol log? Instructions on how to generate such logs are available at https://wiki.mozilla.org/Thunderbird:Testing.
A protocol log is only useful in this case if it's IMAP.
I played around with this briefly and I can't reproduce it, therefore moving back to unconfirmed as we need more information e.g. the requested logs, more information about the reporter's settings etc.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Flags: blocking-thunderbird3? → blocking-thunderbird3-
hi and sorry for not getting back earlier. I'm at TB3 beta3 meanwhile and cannot reproduce the issue. Whatever it was, it did not happen again. marking as closed invalid
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.