User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 After opening the mail, I pressed the "Get Msgs" button. During the downloading of the messages, my system unfortunately crashed. When booting back again, I found that the messages have not been stored on the local inbox, and they have been deleted already from the server. This happened, to my opinion, because the mail donload engine issued a command to remove messages to the server without making *absolutely sure* that the mails have been written down. I'm not sure that Windows has any APIs to check that file writing has succeeded, but I find it more or less a must. Reproducible: Didn't try Steps to Reproduce: 1. Open the "Mail&News" window 2. Download new mail (POP) 3. Crash the machine 4. Reboot and behold! The messages are gone Actual Results: The new messages are nowhere to be found. Expected Results: In such a case, the messages should be somewhere - either locally or at the server. I would say that in case of doubt, there should be preference to have the mail duplicated rather than having it missing in both places.
This happens whenever Mozilla is at fault of a crash (that forces a reboot). After a reboot, Mozilla behaves as if was installed for the first time. Settings, preferences, and stored files (mail, bookmarks, etc) are gone. Don't know what causes this but it's a nasty bug. This has happened on my Win98/2000 machine.
i to have seem this bug on mozilla for windows 95
I've seen this Bug @ MacOSX+POP3 i thought it was gone, changed (to be secure) ti IMAP now I have the Problem under Win XP. The Computer chrashes and the mails are gone (have to be downloaded again)
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.