Alec Flett Reporter
	Description • 25 years ago

In the 4.x world, we described IMAP servers as "hostname:port" in the prefs, so
you could have a port like:
"imap.server.myserver:1234.username" = "alecf"

When this gets migrated over to 5.0, this (currently) becomes:

"mail.servers.server4.hostname" = "myserver:1234"

With the recent URI parsing cleanup, hostnames in this format get confused
because FindServer() is looking for "myserver"


This means that any place we depend on FindServer(), we fail.

This should be migrated over to preferences like:
"mail.servers.server4.hostname" = "myserver"
"mail.servers.server4.port" = "1234"

You'll have to add a new "port" attribute to nsIMsgIncomingServer as well.
(the signed-ness is the same as the one in nsIURI/nsIURL)

	(not reading, please use seth@sspitzer.org instead) Assignee
	Comment 1 • 25 years ago

accepting.

marking m11 and all.

	laurel
	Comment 2 • 25 years ago

I'm not sure what symptoms are caused by this IMAP port issue, but I tried a
non-secure irregular port news server with migration and there is a blank folder
pane afterwards (and lasts throughout relaunch(es)).  I logged bug #17222 for
the news port migration problem.

	hamerly
	Comment 3 • 25 years ago

For most users, the port number is fixed...this is not believed to be dogfood.

	(not reading, please use seth@sspitzer.org instead) Assignee
	Comment 4 • 25 years ago

fixed.

	laurel
	Comment 5 • 25 years ago

mail.server.server1.port is now set upon migration of IMAP servers with
irregular port numbers.

OK using 1999-11-01-08m11 commercial build on linux 6.0
OK using 1999-11-02-10m11 commerical build on NT 4.0
migration currently broken for mac (ref bug #16305)

	laurel
	Comment 6 • 25 years ago

Can't verify on Mac using the edit server name trick (mail server name field
won't allow a colon":" for appending port), so will assume it's okay on mac.

port pref migrated fine for news server, so will assume it would do so for mail.

Marking verified.