Ski Kacoroski <[email protected]> writes: > Hi, > > At $work we purchased a new mail server (Scalix) and need to migrate > from our old mail server (CommunigatePro). We have 2500 accounts with > the largest account about 4.2GB/53000 messages. Our problem is that in > testing several of the imap migration programs available (mailutil, > imapsync, MoveIMAPMail) we are looking at roughly 30 days to complete > the migration which just is not going to work. One idea we have for > doing this in a weekend is to have 30 processes running in parallel, but > I am wondering what other people do to migrate to a new mail server in a > large organization.
Huh. well, a long time ago I did a migration from qpopper to imap on a large mailstore (uh, maybe 25% of yours, but this was a long time ago, so you should have more ram/faster disk than I did) Our problem was that we wanted the UIDL values to be the same (all our customers were on pop3, and most of them had set 'leave mail on server') - well the qpopper uidls were in unix mbox format with at UIDL: header and courier uses the filename as the UIDL. well, some of the qpopper uidls had funny characters, like / in them. What I ended up doing was writing a small patch to courier-impap's pop3d so that if the filename stared with 0x, it would assume that was hex for the ascii value of the uidl, otherwise it would treat it normally. that and a perl script to hack the unix mbox files to maildir files (and change the filenames appropriately) did the trick... I think actual downtime for the conversion was less than an hour. So yeah, I'd suggest figuring out the format the mail is stored in and copying it on the file level. (of course, with propritary tools, sometimes this can be difficult. you are paying them lots of money, right? ask them for help.) _______________________________________________ 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/
