On Thu, 18 May 2006, Peter Ip wrote:
Thanks for the suggestion. I had already thought about that. But we're
planning to convert tens of thousands of mailboxes and we're trying to reduce
the amount of time we're down. It seems to me that mailutil.c should be able
to do exactly what your perl script does, and should do it much faster.
Peter
Would you like a copy of the code?
We did the conversion at quite times, over several days without shutting
down the service, although we have two orders of magnitude less users to
worry about then you.
My script checks for running imapd processes and will not coverts a
user's mbox file if they have an imapd process running.
There is the problem of people leaving their mail client connected for
days, but a publicised quick stop and start of the service could help with
that.
If you are using the feature to automatically move messages from the spool
file to an inbox (mbox or INBOX) in their home directory, then the
following should be possible.
Rename and then convert their mbox to an INBOX file
They will still be able to access new mail in the spool file while you
convert to an mbx INBOX.
The next time their imap client connects after the converted INBOX file
has been placed in their home directory, they will be able to access their
old and new messages
I didn't have to try that particular trick
All the best
Richard Westlake
School of Crystallography, Birkbeck College, Malet Street, London WC1E 7HX
Tel: 020-7631-6859
----------------------------------------------------------------------
Truth endures but spelling changes -- Anon.
----------------------------------------------------------------------
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
