Closed
Bug 141965
Opened 22 years ago
Closed 21 years ago
Does not register as Windows Default Mail Client
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 207974
People
(Reporter: arnova, Assigned: mscott)
References
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 Even though I selected "Use Mozilla mail as default mail application", it doesn't register itself to Windows as being the default mail client. Windows still thinks that Netscape 4.x is the default mail client (as nothing no changes were performed by Mozilla). Reproducible: Always Steps to Reproduce: 1. Goto Preferences 2. Select Mail & Newsgroups 3. Select "Use as default mail client" Actual Results: Other web related applications still don't think Mozilla mail is the default mail client. Expected Results: Those applications should have known that Mozilla is the OS default mail client.
Comment 1•22 years ago
|
||
I have seen a similar problem with making Mozilla the default mail client for OS X. I expect that the implementation is totally different between the two operating systems, but thought I'd mention it here anyway.
The problem can be reproduced in the following way: 1) First install netscape 4.x and let it register itself as the default mail client 2) Next install Mozilla 3) After the installation the registry key [HKEY_CLASSES_ROOT\mailto\shell\open\command] still has the string value of "C:\Program Files\Netscape\netscape.exe -m "%1"" 4) Then try to go to Mozilla Preferences, Mail & Newsgroups, and enable "Use Mozilla as the default mail application. 5) Back to the registry => still has the Netscape.exe value 6) Now when I manually edit the registry and change the value to @="E:\\Program Files\\Mozilla.org\\Mozilla\\mozilla.exe -mail \"%1\"" its fixed. I still think that mozilla forgets to write the root registry as well is this shows obviously.
Comment 4•22 years ago
|
||
I confirm having exactly the same problem !!
*** Bug 144769 has been marked as a duplicate of this bug. ***
*** Bug 178266 has been marked as a duplicate of this bug. ***
*** Bug 124724 has been marked as a duplicate of this bug. ***
*** Bug 144456 has been marked as a duplicate of this bug. ***
*** Bug 145901 has been marked as a duplicate of this bug. ***
Comment 10•22 years ago
|
||
*** Bug 146233 has been marked as a duplicate of this bug. ***
Comment 11•22 years ago
|
||
*** Bug 172984 has been marked as a duplicate of this bug. ***
Comment 12•22 years ago
|
||
Confirming on Windows XP.
QA Contact: trix → stephend
Comment 13•22 years ago
|
||
This has been broken for a long time, and at least should be ASSIGNED, even go as far to say it . The preference is always checked. Even if you uncheck it, exit preferences, and reopen them, it has reverted back to checked. I can't find the pref in prefs.js. Does anyone know what it should be? Copying sspitzer because this looks like it may be related to bug #144828
Comment 14•22 years ago
|
||
*** Bug 192250 has been marked as a duplicate of this bug. ***
Comment 15•22 years ago
|
||
*** Bug 192886 has been marked as a duplicate of this bug. ***
Comment 16•21 years ago
|
||
The issue that started this bug off is still true. I missed this bug during a recent sweep of related issues; see my comments in Bug 77846. This is closely related to Bug 96717, but I don't think identical -- 96717 doesn't seem to be asking for the mailto: to be assigned when Mozilla becomes the default, it's asking for a mailto: checkbox on Preferences|Advanced|System. The symptom in comment 13 is not the same as the issue that opened this bug. Mozilla's checkbox is set based on the default value of HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail and it is *not* stored in prefs.js Clearing the 'Default mailer' checkbox is an odd case, because it doesn't say which of the available clients should be made the system default. Again, see my comments in Bug 77846. This is not part of Bug 144828, either.
Comment 17•21 years ago
|
||
One additional issue: this bug should depend on getting Bug 198547 fixed.
Comment 18•21 years ago
|
||
Cc'ing Minotaur developers.
Comment 19•21 years ago
|
||
*** Bug 208430 has been marked as a duplicate of this bug. ***
Comment 20•21 years ago
|
||
Note that the duplicate has a patch in progress which appears to require some assistance; a single faulty line of code has been found. Move your votes! *** This bug has been marked as a duplicate of 207974 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Verified dup
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•