All users were logged out of Bugzilla on October 13th, 2018
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:126.96.36.199) Gecko/20070309 Firefox/188.8.131.52 Build Identifier: Thunderbird 184.108.40.206, Mac OS X I made a filter rule with "if any matches" while it should be "if all matches" rule, after seconds I realized that it copies all messages from my Inbox to the folder it should copy emails using the filter rule. I canceled filters activity and realized that all messages from my Inbox disappeared, there was also none in the folder. I moved Inbox.msf file hoping to get messages back, but after turning Thunderbird on I got only 75, that were spam. If it is possible to get them back I'd be grateful for help, those were important ones. Reproducible: Didn't try Steps to Reproduce: 1. Make a filter rule to copy all messages from Inbox to the Folder 2. Run a filter rule and cancel it while runing 3. Realize that messages disappeared Actual Results: Messages disappeared, went into the void, dev/nulled themselves...! Expected Results: Messages should be backed up in some way while running filter rules and other activities. I tried to move Inbox.msf file to different place. The result was that after turning Thunderbird on again there was 75 messages (before >100) and all of those were spam. I tried the same with the Folder, it didn't change anything, it's content was the same as before (just few messages).
I'll have a look if I could reproduce this behavior later. Meanwhile some information for you. All the moved messages should still exist inside the inbox. They are only marked as deleted. You have to recover them by hand. Information can be found here: http://www.eyrich-net.org/mozilla/X-Mozilla-Status.html?en
Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies? (The latest supported Thunderbird version 2 is now 220.127.116.11)
Whiteboard: closeme 2008-08-28
I didn't try again to loose all my e-mails -- sorry ; )
Resolving incomplete due to lack of information as mentioned in comment #3.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.