Philip Kizer <[email protected]> writes: > > A big thing to consider is whether you will be planning on one big > light-switch cut-over keeping the service name the same to refer to > the server regardless which server application you're running or > whether you have the option of doing a transition mechanism by which > you could set up something like one of: > > new server on new/temporary name to allow users to check it out and > move their own mail with a change of names (and where incoming mail is > delivered) "later", or > > new server into production with the old one available for access to > the older mail allowing them to move their own e-mail in some way > > just using a different name for the new server > > With any of those, you might consider something like making a web- > enabled way of invoking Scalix's recommended imapsync to assist the > users with moving their e-mail. Using an imapsync mechanism, since it > just does the fetch and imap put, can be done at any time since the > imap server will be maintaining the proper mailbox structure and > conflicts really are not a concern.
Ooh. well, if you can't bother the users, I know with pop3 I've used redirect proxies that allow the user to connect, type there username, and then the proxy redirects all further traffic to the server that username is on. Heck, you could use this to capture the password for the move, too. Unfortunately, the only pop3 proxy I have worked with was an in-house thing. so I don't know if such a thing exists for IMAP. it doesn't seem like a hugely difficult thing to write. _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
