164245 - Windows hangs during initial/first use/configuration of mail.

Status: VERIFIED DUPLICATE of bug 140995

(MailNews Core :: Import, defect)

Description

[Robert Bradbury]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721

Mozilla is installed on a Windows 2K machine in test mode.  Default browser is
Netscape 4.77 and IE 5.5 are also on the machine.  Email information for
browsers is not configured (if I don't give the browsers email information its
impossible for it to be lifted by actors behind the scenes) [normally I do all
my email using Pine on a Linux box to avoid possible viruses].

Clicking ona mailto: URL in Mozilla brings up a mail configuration window.  It
wants to know the name one wants to be identified as (e.g. "Robert Bradbury") --
though this is not filled in by Mozilla and a reply address (e.g.
[e-mail] that it has presumably extracted from some
configuration information).  Once that window is displayed all other windows
are non-functional.  Attempts to switch between windows with the mouse do not
work.  One can only switch between windows with ALT-ESC.  Even then the windows
are unresponsive.  The only solution to the problem is to use CTRL-ALT-DEL to
bring up the Task Manager and then terminate the Mozilla process.

Reproducible: Always

Steps to Reproduce:
1. Install Mozilla on a machine where Netscape is not configured to use Email
(may not be "required" -- a virgin Mozilla install may be sufficient).
2. Attempt to use mailto:XXX URL on said machine
3. Should bring up window requesting you configure mail
4. All other windows on the machine should now be "hung".

Actual Results:  
After terminating the Mozilla process, it could be restarted and function normally.

Expected Results:  
Mozilla should not *demand* that users provide UserID/return address information.
Instead it should allow users to cancel that window and enter messages (perhaps
postponing them after they are entered).  Only when they attempt to send a
message that is incomplete, should an error be generated.

To get out of this bug, one must force a termination of the Mozilla process. 
That causes a loss of information with respect to ones work in other Mozilla
processes.

Comment 1

[Daniel Wang]

dupe of bug 140995?

Comment 2

[Daniel Wang]

Reporter (Robert Bradbury), does the problem persist in newer build? If not,
please resolve this bug as duplicate of bug 140995

Comment 3

[Asa Dotzler [:asa]]

*** This bug has been marked as a duplicate of 140995 ***