simon at simonandkate.net
Sun Apr 30 23:36:23 EDT 2017
Following on from my question on enabling squatter on my new install...
I have upgraded from Cyrus 2.3.7 on a CentOS 5 server to 2.4.17. on a
new CentOS 7 server. I've not yet migrated the users (only 6 x users).
They are both VMs on the same host, and at migration point I can
simply bring up the new server with the drive from the old Cyrus VM
that has the Cyrus partition on it, so new Cyrus will be able to 'see'
the mailboxes without having to do rsync or anything like that.
I've tested the new Cyrus server and it all appears to be functioning
- listening on correct ports / sockets, delivering mail etc.
So my questions:
1. Is 2.4.17 compatible with the mailboxes transferred from the old
Cyrus 2.3.7 server?
2. Assuming it is? Once the new Cyrus can see the mailboxes, will a
reconstruct be needed to have new Cyrus able to see the full mailbox
structure? If so with what flags to rebuild out all sub-mailboxes?
Will it retain 'seen' / replied flags and ACLs?
3. Do I need to do anything with the contents of /var/lib/imap/ on the
old server for retention on the new server?
4. Will I need to rebuild quotas once new Cyrus can see the mailboxes?
5. What is the best way to migrate sieve scripts? These are NOT on the
drive to be moved to the new server, so will need to be migrated
manually from /var/lib/imap/sieve etc... As a test I did a manual copy
to the new server of a sieve script, set permissions and soft links,
and it appears to work - is that the best way?
Thanks in anticipation of assistance :)
M: 0400 12 11 16
More information about the Info-cyrus