Hi Stefano-
MOVEMAILS worked very well for me. For anyone else using this command, I
would recommend to use this in a sandbox env then backup the db. When
moving to production, you can restore this backup. Set the appropriate
config settings and you should be up and running.
Thank you very much!!
tony
Stefano Bagnara wrote:
Hi Tony,
I just added a MOVEMAILS command to the current trunk RemoteManager.
https://issues.apache.org/jira/browse/JAMES-704
Being current trunk storage and config.xml compatible with 2.3.0 you
may want to try to use that commands to convert your mails from one
storage to another.
MOVEMAILS file://var/mail/username dbfile://maildb/inbox/username
Should work.
Please note that MOVEMAILS move messages between SPOOL repositories:
if there are no concurrent processes it will work even with MAIL
repositories, but I strongly suggest you to do this in a sandbox and
not on a live instance of james (also because we are talking of
unstable/unrelease/untested code).
So backup your db and everything else if you want to try this solution!
Cuevas Tony wrote:
First, I want to congratulate everyone that worked on the latest
release, 2.3. I'm in the process of migrating and so far so good.
Does anyone have any scripts to migrate existing file based mail
messages/repository (I know there are 2 files per message) into a db
based repository?
Or, if anyone can tell me the structure of these files so that I can
either write a script or program to do so then that would work as well.
Thanks in advance,
/tc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
