Hi,
> 1. Why are you doing this? What do you hope to achieve?
It all started with the intention to migrate Cyrus from one server to
another. Old server is an Ubuntu with Cyrus 2.5~dev2015021301, the new
one is a CentOS with Cyrus 2.5.8. For the data migration I just rsynced
/var/lib/imap and /var
A couple of things.
1. Why are you doing this? What do you hope to achieve?
2. Possibly kolab's Cyrus configuration stores files in other paths (tmpfs,
data dirs) which are Berkeley dbs and don't expect their environment to be
trashed under them.
On Thu, 29 Sep 2016, at 23:47, Tobias Brunner v
Hi,
I've discovered an odd behaviour which I don't understand: After a
completely fresh Kolab 16 install on CentOS 7
(cyrus-imapd-2.5.9.27-5.1.el7.kolab_wf.x86_64) everything looks fine. I
can create mailboxes, stop/start Cyrus, all works as it should do. The
contents of /var/lib/imap looks like t
