I've only been using the mail & news component at home for about a month now. that being said, I've been enjoying it. I generally download the latest nightly each day and install on top of the existing one. After downloading Friday's, I believe my profile was corrupted in so far as mail is concerned. I downloaded 2 or 3 nightlies over the weekend and the problem persists. the email in question is a POP3 account. when I examine the settings, they appear to be correct. symptoms: 1) all my mail has disappeared 2) my 3 newsgroups are also gone 3) the "get message" icon is greyed & unusable what should I do to regain functionality, hopefully without losing the months worth of email received since switching this profile from NS 4.76?
Summary: I lost all my mail and ability to fetch net mail → I lost all my mail and ability to fetch new mail
Repoetr: Please never install a new build over an older build ! Please uninstall mozilla, delete all files that the uninstaller had not deleted and reinstall mozilla ! If that doesn't fix the problem, you can create a new profile (run "mozilla -profilemanager" and create a second additional profile) If that works and you old profile not you can create your Accounts in your new profile and copy the files Old-Profile\mail\Account.name\*.* -> new-profile\mail\Account-name\*.*
build id: 2001101503 installed atop the non-working build from Sunday without any deletions just as a first shot. I'm pleased to report that the mail component IS working and all my e's & newsgroup posts appear to be in place, various folders complete. Matthias, may I respectfully disagree? This isn't Mozilla 17 or 18. If a new version/release will not install in place with the installer, that's a BUG in and of itself. And a thank you for your suggestions, which I planned to try next. I'm filing away you comments for future problem resolution. I'll reset this to resolved/fixed from work in the am - I filed it from there & don't have the password for that id here
fixed for me
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
Reporter: This is not m17 or M18 but it's also not Mozilla 1.0. (and Mozilla 1.0 will also have a "few" bugs) We have a few bugs about this "installing over an older build" problem and this bugs will be fixed. And if you read the 0.9.5 release notes: "Install into a new empty directory. Installing on top of previously installed builds may cause problems." There will be a point where we don't mark bugs worksforme if they are fixed with a new profile but currently we do it. BTW: The nighly builds are test builds. You can crash on near every page with a nightly or you can loose all you mails or your bookmarks .... Thanks for your time, this bug report and that you are using mozilla. I'm happy that this works again for you !! Matthias verified after reporters comment
Status: RESOLVED → VERIFIED
Same problem on 2001101503 and 2001101603 Win32 installer builds (WindowsME). Reinstalling any of these builds does not help. Downgrading to 2001101103 saves the day. I believe this bug has something to do with multiple mail and news accounts (I have 3 each). Matti: I do not quite buy your argument in this case. It is a serious data loss which may sooner or later hit a milestone build. Then it needs at least to be relnoted. Therefore it is a valid dataloss bug. And think what happens if the milestone is the basis of next Netscape release. Losing the ability to use mail and news after upgrading to (say) Netscape 6.11 for users with multiple accounts would be a major problem for Netscape. Therefore nominating nsbeta1.
Severity: normal → major
Status: VERIFIED → UNCONFIRMED
Keywords: dataloss, nsbeta1, relnote
Resolution: FIXED → ---
OK. I did more research. Removing component.reg solved the problem. Therefore, I sent email to Hook (per comment of dmose on bug 93848) and mark the bug INVALID (also per bug 93848).
Status: NEW → RESOLVED
Last Resolved: 17 years ago → 17 years ago
Resolution: --- → INVALID
This is similar in symptoms but not identical to the blocker bug 105771.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.