I saw this problem with another bug report, since I have having the same problem on on a mega scale I though I would validate the issue as reported. I had 2842 emails that continued to show up everytime I restarted tbird. these emails were from up to 6 months ago, I tried deleting individually, by blocks, and all at once, emptied trash and junk, restarted cpu. They would show up again. Finally, I moved the 800 or so emails I wanted to keep in my inbox to a new folder and deleted the inbox from the profile folder, and then restarted tbird. So far the offending emails have not remanefested themselved in my inbox. This is a critical issue, I spent half a day trying to fix this problem. Are the emails actually deleted? If so, how do they reappear, I checked they are NOT on our mail server. Thanks, Craig
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.