[
https://issues.apache.org/jira/browse/JAMES-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917930#action_12917930
]
Eric Charles commented on JAMES-1052:
-------------------------------------
Thinking more on this, we could extend the scope and define a way to "copy"
mailrepository (2.3) and mailstore (3.0) to mailstore (3.0).
This could be used to migrate 2.3-to-3.0, 3.0-to-3.0 in case of mailstore
change (db change, db to jcr,...), and even backup reasons (simply copy the
existing mailstore to a second mailstore)
On impl, this could be done via two addition commands on remote manager:
- copyMailRepository from=beanName to=beanName
- copyMailStore from=beanName to=beanName
The beanName should be added by the administrator in the spring-beans.xml
Same for the User and Domain stuff.
With Mail/User/Domain, we cover all needed data.
WDYT ?
> Provide a tool to migrate 2.3 mail-repositories to 3.0 mailbox-stores
> ---------------------------------------------------------------------
>
> Key: JAMES-1052
> URL: https://issues.apache.org/jira/browse/JAMES-1052
> Project: JAMES Server
> Issue Type: New Feature
> Affects Versions: 3.0-M1
> Reporter: Eric Charles
> Assignee: Eric Charles
> Fix For: 3.0-M1
>
>
> A migration tool must be provided to ease the 2.3 mail store pumping into the
> new 3.0 maiblox store.
> This should be implemented against MailRepository and Mailbox/MessageManager
> and not against low-level API (File, JDBC,...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
