Re: Migrate cyrus 2.3.8 to 2.4.17

2014-10-08 Thread jayesh shinde

Hi Giuseppe ,

I want to learn few points from your migration scenario.

Few days back I migrated my  32 bit cyrus-imapd-2.3.7-12.el5_7.2   to 64 
bit cyrus-imapd-2.4.17-6.el6.x86_64 server
I faced the below problems , how you are handling the below points on 64 
bit server  in your case ?


1) How do you  maintained the seen-unseen mail flags.
2) I came across duplicate email download issue in email client .
   When IP of 32bit server shifted to 64 bit server , then for those 
client who have setup POP3 account with leave copy on server in email 
clients for them emails got download again.


On 64 bit server there was no changes in  /etc/hosts and DNS A records 
and /etc/resolve.conf , it was exactly same as 32 bit.


Request you to please share your comments / suggestion which need to 
take care for above issues.


Regards
Jayesh Shinde


On 10/06/2014 08:27 PM, Giuseppe Ravasio wrote:

Hi,
I'm planning and testing the migration of a IMAP mail server based on
cyrus 2.3.8 with about 3TB of mailstore, 300 users and a lot of shared
folders (with shared flags (group permission with +w)).

The old server is a 32bit one and the new one is 64bit virutual machine.
as now I've succesfully used this procedure:
- Rsync of all mailstores /var/lib/imap and /var/lib/sieve
- rm -v /var/lib/imap/db/* /var/lib/imap/db.backup1/* \
/var/lib/imap/db.backup2/* /var/lib/imap/deliver.db \
/var/lib/imap/tls_sessions.db /var/lib/imap/mailboxes.db
- ctl_mboxlist -u  /tmp/mboxlist.txt
- ctl_cyrusdb -r
- tls_prune
- ctl_cyrusdb -c

- cyr_expire -E 3

The last command took about 24 hours to complete and if understand right
It converted cyrus mailbox DBs from v9 to v12.

I wonder if the first cyr_expire could run even with the service started
and if it should be better to run a reconstruct on all the mailboxes in
place of this cyr_expire.

Last but not least, do you think that sieve filters should be recompiled?

Any other hints?

Thanks
Giuseppe

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

Re: Migrate cyrus 2.3.8 to 2.4.17

2014-10-08 Thread Giuseppe Ravasio
On 10/08/2014 11:10 AM, jayesh shinde wrote:
 Hi Giuseppe ,

 I want to learn few points from your migration scenario.

 Few days back I migrated my  32 bit cyrus-imapd-2.3.7-12.el5_7.2   to 64
 bit cyrus-imapd-2.4.17-6.el6.x86_64 server
 I faced the below problems , how you are handling the below points on 64
 bit server  in your case ?

 1) How do you  maintained the seen-unseen mail flags.

In my test case I hadn't any problems with seen and other flags.
I to be told that both source and destination are using skiplist as seen 
database format.

 2) I came across duplicate email download issue in email client .
 When IP of 32bit server shifted to 64 bit server , then for those
 client who have setup POP3 account with leave copy on server in email
 clients for them emails got download again.
 On 64 bit server there was no changes in  /etc/hosts and DNS A records
 and /etc/resolve.conf , it was exactly same as 32 bit.

To be honest this server is an IMAP only service, so I haven't tested 
the POP3 cases.
Anyway I think that this problem is related with the first one, because 
if a message is downloaded via POP3 the server sould set the seen flag 
on it.
I did a public cyrus server migration months ago from 2.2.x to 2.4.17 
and I don't recall to have had thoose kind of problems (and I'm sure 
that there where 30/50 users using POP3 with copy on server).

Did you rsync the /var/lib/imap/user/ from the old server?

Bye
Giuseppe


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