Closed Bug 159700 Opened 23 years ago Closed 21 years ago

Bad SMTP hostname block creation of new POP account

Categories

(SeaMonkey :: MailNews: Account Configuration, defect)

x86
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: chris_carr, Assigned: racham)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 BuildID: 2002052918 I created an SMTP account in an ealier version of Mozilla, probably 0.9.8 but I'm afraid I'm not sure. I specified "hostname:port" for an SMTP server. I later upgraded to this build which automatically imported the old settings. When I tried to create a new POP account, it repeatedly blocked me with the message "Please enter a valid hostname." This confused me at first, since the only text entry box did in fact contain a valid hostname with a running POP server. Then I noticed text which read "Your existing SMTP server will be used." So I cancelled, deleted my SMTP server and created a new one, and tried to add the POP account again. This time it worked. Reproducible: Didn't try Steps to Reproduce: 1. Run an earlier version of Mozilla or Netscape. 2. Create a profile with an SMTP server. Specify the SMTP hostname in the form "hostname:port". 3. Run the installer for this build. 4. Add a new email account. 5. Go through the wizard to the point of adding a server. Specify POP (IMAP may have the same problem) and enter a valid hostname. 6. Observe that a dialog forces you to reenter a hostname and will block proceeding with the new account definition. Actual Results: I was forced to cancel the new account definition. Expected Results: I should have been permitted to create the new POP account and to correct the deficiency in the SMTP definition elsewhere. This bug appears closely related to bug #90263.
The problem is probably that you upgraded your Mozilla without wiping the old version's settings. Completely uninstalling the old version is mandatory, otherwise all sorts of problems occur. It could also be bug 108912. If this problem still occurs for you on with recent release/build, please reply. Otherwise, please resolve the bug.
I was not aware that complete uninstall of the prior version is mandatory. The installation did not require it, and indeed the application includes a utility for importing profile settings from the prior version. Perhaps the bug lies with the profile importer?
Reporter: Is this still a problem with a current Mozilla version?
no response-->resolving wfm
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.