I just fixed #17212 and now, if a user has two imap accounts on the same server, but with differnent ports in 4.x, they will collide on disk. if a user has an account at nsmail-2.mcom.com:654 and nsmail-2.mcom.com, they would both get mapped to ~/.mozilla/<profile name>/ImapMail/nsmail-2.mcom.com on disk. an easy fix for this (and other collision problems) is to use the MakeUnique() method when creating directories on disk.

I thought you switched over to using createUniqueServer so that they got migrated over to "server1" "server2" etc?

nope, for migrated servers, we keep the 4.x name of the folder. (we just copy it over.) for new servers, we do the server<x> thing.

accepting.

moving to m16.

Triage to M17. Please add beta2 keyword if this must make beta2. Please let me know if this must be done by M16 feature freeze.

Mail Review recommends beta2 stopper. Adding nsbeta2 keyword.

Putting on [nsbeta2+][6/01] radar. This work must be done by 06/01 or we may pull this for PR2.

Due to slip in schedule, moving this bug from [6/01] to [Will be minus on 6/15] for fix deadline.

Cleaning up status whiteboard by marking beta2 minus (6/15 has passed) I'd be curious about how often this is problem. Note knowing much about this area, I'd suspect that this is more of an issue to a developer toying with multiple servers on a single machine (each on a different port). I've added the release note keyword.

It seems unclear to me whether this bug requires either of a "developer" or "user" release note. If anyone feels it does, can they please draft one and then nominate with the relnote-user or relnote-rtm strings in the Status Whiteboard. Thanks :-) Gerv

clearing milestone, m17 and m18 are meaningless now. these need to be triages along with the rest.

This is a major problem in 2 cases that I run into frequently: - Application proxy firewalls - SSH port forwarding My standard mail config has 3 different IMAP servers, all on different ports on localhost, using SSH port forwarding to get to the actual mail servers through various firewalls. The mozilla mail client is completely unuseable to me due to the server uniqueness key not including both the server name/addr and the port number. This bug is trivial, and has been open for a year and a half. Any chance that it might actually get fixed someday? I'd be happy to wade through the source code and fix it, if someone could point me in the right direction. I've never even looked at the mozilla source, and am not certain how much of it needs to be touched to resolve this issue.

the following comments are based on my experience w/ news server folder naming, but most of the comments apply to mail servers. could we try to make the folder names more unique? in 8.3 i have: host-new.com x5 host-new.org x2 i think mapping to first encountered hexips and storing a mapping would be preferable if i ran a server on localhost, it could be 7f000001.timeless.654 {%hex(ip).hostname.port} the likelyhood of such a name failing to be unique is very low support for ipv6 servers could be made by using 8 hex chars or the entire ipv6 address; although... cnews.corel.com and cnews.corel.ca would end up w/ nearly identical names [they're really the same server]

Mozilla 1.1b nightly build Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1b) Gecko/20020901 In fact, I have examed in one profile creating two different account in the same server--skating, mozilla automatically added a postfix for the latter mapping directory name-- such as skating-1. So I think this bug has been fixed , isn't it?

See also bug 41929, "can't have multiple accounts with same pop/imap server and username, even port is different".

sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.

as with bug 45777... ->WONTFIX since 4.x migation has been dropped on trunk. If one has an overwhelming need to see this fixed on branch, please attach a patch and reopen the bug. Also, evaluate whether the issue is a bug or an enhancement request and adjust severity accordingly. filter bugmail for "4.xmidrop" to delete these messages.