Closed Bug 286604 Opened 20 years ago Closed 20 years ago

Mozilla doesn't save default email setting

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Other
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 279627

People

(Reporter: allltaken, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050217 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050217 This is either a main mail bug or a preferences bug, not sure how categorize it. Each time I start Mozilla mail, it asks if it should be the default email client. I click "yes" and may or may not check the box about asking again, and it never saves the settings. In "preferences" I can set Mozilla to be the default mail client, click "OK", open the preferences immediately and find the setting not saved. In "about:config", I can't find any line for setting Mozilla mail to be the default email client. In Win98SE registry settings, I didn't find any line that seemed to be used to set a default email client. I assume that's where system mail settings should be listed, such as for "mailto" links and the eml filetype. Reproducible: Always Steps to Reproduce: 1. Start Mozilla mail. 2. Click yes in the box asking if Mozilla should be the default mail client. 3. Open preferences, note that Mozilla mail is not marked as the default mail client, and mark the box indicating Mozilla is to be the default mail client. 4. Exit Mozilla (all windows). 5. Restart Mozilla mail Actual Results: Mozilla's dialog box asking to be the default mail client opens again. Expected Results: Mozilla should have saved the settings from the previous session in the preferences and any other appropriate locations (system data, Windows registry). This problem didn't exist with 1.7.3 and perhaps 1.7.5, but I saw it in an earlier 1.8 version. I've been running Spybot 1.3 which monitors registry changes, and uninstalled it to see if the mail setting would be saved with Spybot not installed. It wasn't, so that is not the problem.
fixed two days ago *** This bug has been marked as a duplicate of 279627 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.