Hi, I'm facing the task of migrating two cyrus 2.0 servers over to a single one, and I'd like to be sure I'm doing things TheRightWay (tm). The first task is simply moving the mailboxes over. I could always just create their mailboxes and resubmit older email, but I'd rather not.
>From what I understand it'd a no-no to simply copy the mailboxes into place. Would creating them with a cyradm script and then (while the server is down) populating the /var/spool/imap and /var/imap trees, and running the reconstruct script be a bad idea? Also, we'd like to move over from sasldb to using cleartext passwords in a MySQL table. There are plenty of reasons for this, first of all it eases integration with other systems, allows easier creation of administrative tools etc. This raises two questions: a) How to extract the passwords? In order to use CRAM-MD5 you've got to have cleartext passwords on the server, so I'm assuming the sasldb (v1 btw) contains either the passwords or a password equivalent. Is there a RightWay (tm) to extract these? b) In order to keep using CRAM-MD5 and friends, do I understand things correctly that we need to use sasldb alongside of the plaintext authentication system? If so, then I understand we can use sasl_auto_transition to set the passwords in sasldb, but will this be able to update the sasldb system when the user changes a cleartext password? Also, will the user need to log in using a cleartext password, or can he log in with CRAM-MD5 or APOP etc the first time if the authentication backend (in this case MySQL) can proide the cleartext password? Also, because sasl so far have been my only worry with Cyrus, it's very tempting to jump to 2.1 to gain the advantage of cyrus-saslv2. How stable is it? Should I keep my hands off at all costs? Any feedback appreciated! Terje
