Migrate from 2.2.13 to 2.4.17 disasters

[Giuseppe Ravasio (LU)]

I think that the key difference between using imapsync and upgrading
cyrus is the amount of states that will be lost.
I almost sure that with imapsync you cannot recreate:

1. Subscribed folders
2. Seen states for shared folders (also for INBOX if imapsync isn't used
properly)
3. Shared seen states
4. Email flags (also for INBOX if imapsync isn't used properly)
5. Custom permissions

Therefore I think that imapsync is not the best choice for corporate
email servers or big installations.

Giuseppe

On 08/24/2015 01:44 PM, bshaw at vsvinc.com wrote:
>   Apologizes for the thread diversion here but I've been seeing a lot of
> discussion about using imapsync to migrate servers.  From what I have
> read in the documentation, you must have each user's password.  How is
> this possible in a business environment where you can't have (or
> shouldn't have) that information because of legal/privacy/ethical
> reasons?  Is there something I'm missing in the docs?
> 
> Brian
> 
> 
> *From:* Marcus Schopen <lists at localguru.de>
> *Sent:* Aug 24, 2015 3:54 AM
> *To:* mogens at fumlersoft.dk
> *Cc:* info-cyrus at lists.andrew.cmu.edu
> *Subject:* Re: Migrate from 2.2.13 to 2.4.17 disasters
> 
> Am Sonntag, den 23.08.2015, 20:36 +0200 schrieb Mogens Melander:
>> For a task like this, I would use imapsync, a well documented,
>> well supported and open source tool.
>> 
>> https://github.com/imapsync/imapsync
> 
> I've used imapsync to migrate an internal server from 2.1.18 to 2.4.17
> without any problems. Good tool.
> 
> Ciao!
> 
> 
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
> 
> 
> 
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>