521627 - 2.0rc1: e-mail account creation skips account type selection

Status: VERIFIED DUPLICATE of bug 521861

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Thomas Peters]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091007 SeaMonkey/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091007 SeaMonkey/2.0

On mozilla.support.seamonkey I was told to file a bug report about this:

When I try to create an e-mail account with SeaMonkey 2.0rc1 (Edit -> Mail & News Account Settings -> Add Account), it skips the step where it asks for the server type (IMAP, POP3, News). Instead, it only asks for my name and e-mail address and then for the name of the *news server*. So it seems it only accepts the creation of new news server accounts for whatever reason.

Don't know if this could be in any way related to bug 521424.


Reproducible: Always

Steps to Reproduce:
1. Create e-mail account

Actual Results:  
2. SeaMonkey asks for name and e-mail address
3. SeaMonkey asks for news server address


Expected Results:  
2. SeaMonkey asks for server type
3. SeaMonkey asks for name and e-mail address
4. SeaMonkey asks for server address

Comment 1

[Philip Chee]

Bug 521573 is fixed. You might try todays nightly to see if this also fixes your problem.

Comment 2

[:Hb]

This error occurred when the account vs. id vs. server relationship is mismatched in prefs.js. Using a new profile solves this problem, so NORMAL severity. 

If todays nightly fixes the problem needs to be tested against the old prefs.js

It is bad that Seamonkey does not check the consistency of the account vs. id vs. server relationship. At least a warning to the error console is needed.

Comment 3

[Philip Chee]

So is this a profile migrated from a 1.1 profile?

Comment 4

[Thomas Peters]

Yes, I migrated from 1.1.something.

Comment 5

[Thomas Peters]

Same problem with the current nightly build.

Comment 6

[:Hb]

I precautionary set blocking‑seamonkey2.0 ? because of a profile destroying migration issue.

Did you add or remove any mail or news accounts after migrating from 1.1.x?

Is the old prefs.js file preserved in the old 1.1.x profile directory? If yes, could you please anonymise both the old and new file and upload it here?

Does a new profile solves this error for your installation too?

Comment 7

[Thomas Peters]

I think I definitely added a news account after migrating to 2.0 but I'm not sure about the e-mail accounts.

Unfortunately, I do not have the old 1.1.x data anymore.

With a new profile the problem is solved.

Comment 8

[:Hb]

The faulty behaviour in the Account Wizard is similar to bug 521861 where a workaround is shown.

Comment 9

[Jens Hatlak (:InvisibleSmiley)]

Marking duplicate since the other bug has more details, analysis and workaround.

Note: This surely won't block 2.0 this late (blocking means "if this were the last blocking bug we'd hold a release for it" and we're already in RC phase) but if you like you may request wanted-seamonkey2.0 on the other bug.

Comment 10

[Thomas Peters]

Setting mail.server.serverX.valid to true solved the problem. Thanks!