At 5:09 PM -0700 2005/06/20, Christopher Smith wrote:
>
http://mailsync.sourceforge.net/
>
>I've used mailsync for a number of migrations. It's a very smooth way to
>manage the problem.
Thanks for the pointer; I've listed it for my users.
Building it on Mac OS X seems nontrivial. The instructions
don't mention Mac OS X, and it requires c-client (which requires a
make argument, Mac OS X/Darwin not listed; FreeBSD failed when I
tried it). The c-client (UW IMAPd) instructions require openssl in
/usr/local/bin, and I don't feel like installing another openssl or
dropping the required symlinks.
I'm going to punt to users to handle in their mail clients. I
could probably get this going myself, but don't want to have to go
through the whole password changing dance on old & new servers for
each user to migrate them, and I'm not going to talk my users through
building this, or running it on the new (Tiger) server.
Chris
PS-I thought this would be generally easy in normal IMAP clients.
Eudora & Entourage just can't do it. Mail.app can do it, but you have
to cache all the old mailboxes locally first, or it creates empty
mailboxes on the old server. Thunderbird complains (twice per
mailbox? I never let it run far enough to find out) for one of my
servers, so that's a no-go. Disappointing.
--
Chris Pepper: <
http://www.reppep.com/~pepper/>
Rockefeller University: <
http://www.rockefeller.edu/>