Closed Bug 142601 Opened 24 years ago Closed 24 years ago

Mail no longer saves account settings

Categories

(MailNews Core :: Backend, defect)

Other
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: hcharles, Assigned: mscott)

Details

I started getting the "Create new email" account panel with RC1 and also 1.0.0+ *every* time I run mozilla. Settings/Account info is apparently not being saved on exit, or somehow thinks its a new browser vers running.
QA Contact: gayatri → nbaca
WFM, current linux CVS. Is it possible that your prefs.js has a syntax error somewhere? (There's a bug on it not being read in properly then, and the mail account info is in prefs.js) prefs.js shouldn't be manually edited - it's better to create a user.js if you want to tune various settings. user.js overrule settings in prefs.js if "conflicting".
Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.0+) Gecko/20020506 / WinME here. I have seen the exact same. When I set the server settings to look for mail every 2 minutes, download automatically and leave the settings on the server, then click OK, messages are downloaded from the server no matter what. Upon returning to the settings, Mozilla Mail hasn't retained my settings.
Just for fun I moved my current settings in $HOME/.mozilla to $HOME/.mozsav and let mozilla recreate a new default profile, etc. 1. My prefs.js was in fact corrupt (short file) in the failing version. I *might* have run out of disk space at one point (highly likely) while quitting mozilla. 2. I had hand editied the prefs.js previously to support the "open unrequested windows" flag (version .97+ i belive) now that option is in the prefs panel. I attribute this to a corrupt .prefs.js file. Starting and stopping mozilla repeatedly works correctly with a good prefs.js file.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Verified Worksforme per reporters results.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.