Closed
Bug 13833
Opened 25 years ago
Closed 25 years ago
Adding accounts with same host name can cause problems
Categories
(MailNews Core :: Networking, defect, P3)
MailNews Core
Networking
Tracking
(Not tracked)
VERIFIED
FIXED
M11
People
(Reporter: esther, Assigned: sspitzer)
Details
Using 19990914 build on win98, Using the New Account Wizard, if I add multiple
accounts with the same server (ie. 3qatest07 using nsmail-2, qatest03 using
nsmail-2, and qatest04 using nsmail-2) the account location of the multiple POP
accounts will be the same.
1. Migrate an IMAP account from 4.x (one that has several accounts you can
assigned to the same server. I used accounts 3qatest07 as my IMAP account using
server nsmail-2 and migrated it first. Then I added POP accounts qatest03 and
qatest04 using the server nsmail-2 too)
2. Launch this account and select Tasks Messenger
3. Select New Account Wizard from the Edit Menu and add the second account.
(ie qatest03)Close and reopen Seamonkey. Repeat step 2
4. Select New Account Wizard from the Edit Menu and add the third account(ie
qatest04). Close Seamonkey.
Result: In the case above, if you look at the prefs.js file, you will see the
same directory location for both pop accounts:
user_pref("mail.server.server4.directory",
"D:\\Users50\\3qatest07\\Mail\\nsmail-2");
Expected: Each POP account should have a different directory structure so
messages don't get mixed up.
Note: Seth saw this and said he has a fix for it.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Target Milestone: M11
Assignee | ||
Comment 1•25 years ago
|
||
marking m11.
fixed.
here's how it works:
any pop, imap or news servers that get migrated (with -installer) will retain
the directory names they had in 4.x
examples:
user_pref("mail.server.server1.directory",
"/home/seth/.mozilla/seth/ImapMail/tintin");
user_pref("mail.server.server2.directory",
"/home/seth/.mozilla/seth/ImapMail/nsmail-2");
user_pref("mail.server.server3.directory",
"/home/seth/.mozilla/seth/ImapMail/sspitzer");
user_pref("mail.server.server4.directory",
"/home/seth/.mozilla/seth/Mail/server4");
user_pref("mail.server.server5.directory",
"/home/seth/.mozilla/seth/News/host-news");
user_pref("mail.server.server6.directory",
"/home/seth/.mozilla/seth/News/host-news.mozilla.org");
user_pref("mail.server.server7.directory",
"/home/seth/.mozilla/seth/News/host-terpsichore.mcom.com");
user_pref("mail.server.server8.directory",
"/home/seth/.mozilla/seth/News/host-zia.mcom.com");
user_pref("mail.server.server9.directory",
"/home/seth/.mozilla/seth/News/host-news.mcom.com");
"Local Mail" and any new accounts you create with the account wizard will have
directories that match the server key.
examples:
user_pref("mail.server.server10.directory",
"/home/seth/.mozilla/seth/ImapMail/server10");
user_pref("mail.server.server11.directory",
"/home/seth/.mozilla/seth/Mail/server11");
user_pref("mail.server.server12.directory",
"/home/seth/.mozilla/seth/News/server12");
because the server key is unique, we avoid collisions on disk, and now you can
have more than one mail account of the same type (pop, imap) on the same server!
there is one problem, but it is an edge case.
example:
int 4.x, the user had a 4.x pop account on a server named "server1"
they run -installer
then they add additional pop accounts (using the wizard) on "server1"
this would cause a collision on disk.
I'm logging a bug about it, but for now, we aren't going to fix this.
its very unlikely and I've got bigger fish to fry.
OK using 1999-11-09-11m11 commercial build NT 4.0: added multiple IMAP or POP
accounts to same server get unique directory allocations using the server
number.
OK using 1999-11-09-11m11 commercial build linux 6.0: OK multiple IMAP and POP
accounts on same server.
OK using 1999-11-09-16m11 commercial build mac OS 8.5.1: OK multiple IMAP and
POP accounts on same server.
Did not test for the edge case seth mentions.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•