pgoetz at mail.utexas.edu
Mon May 1 09:39:22 EDT 2017
I'm not 100% sure about how cyrus gets installed on CentOS, but can
attempt to answer some of these:
On 04/30/2017 10:36 PM, Simon Wilson wrote:
> 1. Is 2.4.17 compatible with the mailboxes transferred from the old
> Cyrus 2.3.7 server?
I upgraded from 2.2 to 2.4 in place and don't recall having any problems.
> 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?
Not sure about ACL's, but the "seen" information is stored in
/var/lib/imap (/var/imap on Arch) in the user directory.
> 3. Do I need to do anything with the contents of /var/lib/imap/ on the
> old server for retention on the new server?
I'm assuming here that /var/lib/imap is where the mailboxes.db file is
stored. You absolutely must migrate this folder to the new server, or
cyrus won't know about any mailboxes.
> 4. Will I need to rebuild quotas once new Cyrus can see the mailboxes?
Quota information is similarly stored in /var/lib/imap
Last server migration, I had success following this recipe.
1. Install cyrus, cyrus SASL on new server and copy over
/etc/cyrus/imapd.conf and /etc/cyrus/cyrus.conf as well
as any SASL configuration and SSL certs. If you're
upgrading, be mindful of cyrus configuration changes which
need to be made to the /etc/cyrus configuration files.
2. Stop cyrus on the old server
3. Copy user mailboxes from old server to new one
4. Copy the following contents of the configdirectory, usually
/var/imap or /var/lib/imap or /var/lib/cyrus from the old
server to the new one:
(The rest of the content is generated automatically.)
5. Depending on how you have cyrus set up, you might also need to copy
/var/spool/cyrus (/var/spool/imap on Arch)
6. Start the cyrus master on the new server. Everything should
More information about the Info-cyrus