mozilla mail startup requests password for non-existent pop3 server



MailNews Core
Networking: POP
15 years ago
9 years ago


(Reporter: warren, Assigned: Navin Gupta)


Windows 98

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312

I had to upgrade to 1.3 after 1.0.2 had self-destructed at 3 this morning. After
struggling many hours to get the old profile accepted, it finally recognizes the
old emails and bookmarks. But it pops up a box asking for password to
non-existent mangled account name. It has TWO '@' signs in the non-existent
server name.

Reproducible: Always

Steps to Reproduce:
1. start mozilla
2. There it is

Actual Results:  
mail starts up then immediately a popup request for password

Expected Results:  
just start up and password manager already has the accountname & passwords for
the existing 2 pop3 servers.

The profile was restored by cutting and pasting the old profile into the
'default profile' then renamed to 'My Profile'.
Do you see a problem in "prefs.js" that could explain this ?
Are tha mail-path correct in this profile ?

Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.