Closed Bug 16075 Opened 20 years ago Closed 20 years ago
IAccount Manager::Create Incoming Server doesn't set server type
Create a new incoming server with CreateIncomingServer( "imap", &myServer); Create an account with nsIAccountManager::CreateAccount() Call account->SetIncomingServer( myServer); The data saved into prefs.js after this executes does not include the type for the newly created server - the name, hostname, and userName are present but mail.server.serverX.type is missing. This wreaks havoc later on and causes the new account and server to be non- functional and to crash portions of the UI.
Status: NEW → ASSIGNED
Priority: P3 → P1
Target Milestone: M11
Woah! This explains a couple wierd bugs...this is great! I've got the fix ready in my tree, just need a review.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
fix checked in.
To test this should I create a new account and check the preferences to verify that the "type" entry is correct?
Alec, just want to make sure couple of things before I mark this bug as Verified. 1. Where is the method 'SetIncomingServer'? 2. I have used 'CreateIncomingServer(...)' to create a new account. And the type shows up in prefs.js file. Is this enough to verify this bug or should I use 'SetIncomingServer()' method?
oh, in C++, attributes get changed into Get/Set methods so the "incomingServer" attribute becomes GetIncomingServer and SetIncomingServer So anyway, "incomingServer" is ok. What we need to verify is that when I say createIncomingServer(type), that the server.type value is actually set to the type given.
thanks for the help, BTW :)
Changing QA Contact. Verified by testing all three types (pop, imap, nntp).
You need to log in before you can comment on or make changes to this bug.