Robust mbox to cyrus migrator?

[Dan Delaney]

On Sat, 23 Oct 2004, Andrew Morgan wrote:
> I think you are referring to the scripts I wrote (Oregon State University!
> Go Beavers!).  They were good enough to handle OSU's migration to Cyrus,
> One of the problems with any migration tools/script is that it is
> typically only written and used once.  :)

Sure. I figured I'd have to modify them for my setup. It was great
to have them to start with though. Thanks a lot for putting them out
there!


> 1. IMAP flags are not migrated (most notably SEEN).

Yeah, that's a shame. I wouldn't mind scripting that. Anyone have
any suggestions as to how to go about it? :-) I'm using UW-IMAP
right now, and migrating to Cyrus.


> 2. It does not handle unixhierarchysep: yes on the target system (easily
> fixed).

Hahaha. I found out that the hard way! :-) I went through and
changed all the periods to slashes and it worked fine. Might be good
to set a $sep variable at the beginning of the script and use it
throughout instead of the hard-coded period.


> If you have any suggestions for fixes, I'd be happy to update the scripts.

It would be nice to have all the paths defined in variables instead
of hard coded: $cyrusConfigPath, $cyrusDataPath, $inboxPath and so
on.

Cheers
-- Dan
__________________________________________________________________
 Daniel G. Delaney                          http://FluidMind.org/
__________________________________________________________________
Unix, MS-DOS and Windows NT (also known as
the Good, the Bad, and the Ugly)


---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html