14435 - fix potential collision, if user had 4.x mail/news server named "server3"

Status: VERIFIED FIXED

(MailNews Core :: Backend, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

let's say a user has an imap server in 4.x, hostname = server3
(note, not server3.foo.bar, but server3)

they run -installer and the 4.x server gets migrated to
<profile>/ImapMail/server3

then they use the account wizard to create a several imap servers.
to support multiple accounts of the same type on the same server, we name the
directory for any new server created with the account wizard by their server key
id, which is of the form server<n>

you can see how this is a collision.

we need to add some code to prevent this.

but it is VERY unlikey, so we'll leave it to post beta.

but I'd like a scooby snack for thinking of it.

Comment 1

[(not reading, please use [e-mail] instead)]

marking m15.

accepting.

Comment 2

[lchiang]

Ok, you get a snack for this.

Comment 3

[Alec Flett]

note, that is not a scooby snack... lisa obvious agrees with me about this being
a very edge case... :)

Comment 4

[(not reading, please use [e-mail] instead)]

"Zoinks!"  --Shaggy

Comment 5

[dbragg]

No fair finding your own bugs and then getting a snack for it.

You meddeling kids! - Old man Whitherspoon (owner of haunted amusement park)

Comment 6

[(not reading, please use [e-mail] instead)]

moving to m16.

Comment 7

[(not reading, please use [e-mail] instead)]

fixed.  we call MakeUniqueWithSuggestedName() so this won't happen to us.

Comment 8

[laurel]

OK 2000-05-04-12M16 commercial build NT 4.0, IMAP and POP.

Comment 9

[laurel]

OK for IMAP, POP, news.
2000-05-04-12m16 commercial builds all platforms.