I'm currently fighting with a mbox migration (I'm not the only one, considering the threads on the subject) on 5.0.20.
I'm using the Python mbox2imap script but I'm having several issues with it.
This is the one I'm using : http://people.cs.uchicago.edu/~brend...ipts/mbox2imap
First of all, the imported messages are shown with the import date/time in the ZWC, not the message date.
Fixing it is quite easy but needs to re-import each message: you just have to use the "Thunderbird hack", ie add "/tb" at the end of the username.
Then, I have a first issue when dealing with recursive import. The script fails with a Python error (and I don't code Python at all). I fixed this by removing ".group(1)" at the end of line 285.
But the worst issue, still in recursive import, is the way the folders are created on the ZCS server.
mbox2imap creates the folders tree based on the mbox files folders (on the hardrive) and, as it's using IMAP, it uses dot in order to separate the levels.
Example, on the hardrive, I have several folders and files (each file is a mbox file):
mbox2imap creates, on the ZCS server, these folders using IMAP:
The dot is supposed to be the IMAP separator between folder and sub-folder but this doesn't work (at all): in the ZWC, instead of getting the same tree than on the harddisk, I'm getting all the folders at the same level with the dots in their name...
Does anyone know why the dot is not working properly as separator in IMAP?