upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Gavin Gray
We are planning towards upgrading our existing murder. The murder has four front ends, three backends and separate mupdate and lmtp servers. We want to move from version 2.2.12 to 2.3.14 so that we can make use of delayed expunge an possible replication. We have several thousand users

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Dave McMurtrie
Gavin Gray wrote: We are planning towards upgrading our existing murder. The murder has four front ends, three backends and separate mupdate and lmtp servers. We want to move from version 2.2.12 to 2.3.14 so that we can make use of delayed expunge an possible replication. We have

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Gavin Gray
Quoting Dave McMurtrie dav...@andrew.cmu.edu: 3. As part of our preparation for this work we have been experimenting with cyrus replication. The replication protocol seems pretty solid, however we have some concerns about how to make use of it in our upgrade. We are considering having a

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Dave McMurtrie
Gavin Gray wrote: Assuming we do do the migration first, how would you suggest we subsequently enable replication? Can we just start the sync_client doing rolling replication, or should we do an initial replication of all users by running sync_client manually with a list of users? We

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Michael Menge
Quoting Gavin Gray gavin.g...@ed.ac.uk: Assuming we do do the migration first, how would you suggest we subsequently enable replication? Can we just start the sync_client doing rolling replication, or should we do an initial replication of all users by running sync_client manually with a list

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Rudy Gevaert
Hi, Citeren Michael Menge michael.me...@zdv.uni-tuebingen.de: You need both rolling replication and one replication of all users. The rolling replication will only sync what has changed. So if a user recieves new mail, rolling replication will sync the mailbox, but not the sieve scripts or

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Brian Awood
On Thursday 16 July 2009 @ 05:21, Gavin Gray wrote: 2. We should end up then with our existing murder but with three backends running 2.3.14. We then plan to upgrade the other machines in the murder to 2.3.14 in the following order: frontends then lmtp and finally the mupdate server. Does

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Nic Bernstein
On 07/16/2009 09:55 AM, Brian Awood wrote: On Thursday 16 July 2009 @ 05:21, Gavin Gray wrote: replication is significantly slower than xfer, but it shouldn't affect the speed of xfer. We wrote some scripts to prevent xfer from getting too far ahead of replication. Since our replicas

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Brian Awood
On Thursday 16 July 2009 @ 09:53, Rudy Gevaert wrote: I wonder if it is possible to run sync to two different servers. Anyone? AFAIK, Not easily. We considered trying to do this when we moved from tape backup to disk based backup. We decided on an out of band process to replicate to our

Architectural mistake in cyrus ?

2009-07-16 Thread Denis BUCHER
Hello everyone, I already asked this question as an help request here some time ago, but noone was able to solve this bug in cyrus, and I think this issue should be addressed : 1] Problem : How to set quota for a user being in another domain than the main domain ?? 2] More precisely : How to

Re: upgrading a 2.2.12 murder to 2.3.14

2009-07-16 Thread Andrew Morgan
On Thu, 16 Jul 2009, Gavin Gray wrote: We are planning towards upgrading our existing murder. The murder has four front ends, three backends and separate mupdate and lmtp servers. We want to move from version 2.2.12 to 2.3.14 so that we can make use of delayed expunge an possible replication.

Re: Architectural mistake in cyrus ?

2009-07-16 Thread Andrew Morgan
On Thu, 16 Jul 2009, Denis BUCHER wrote: Hello everyone, I already asked this question as an help request here some time ago, but noone was able to solve this bug in cyrus, and I think this issue should be addressed : 1] Problem : How to set quota for a user being in another domain than

Re: Architectural mistake in cyrus ?

2009-07-16 Thread Denis BUCHER
Hello Andrew, Andrew Morgan a écrit : I already asked this question as an help request here some time ago, but noone was able to solve this bug in cyrus, and I think this issue should be addressed : 1] Problem : How to set quota for a user being in another domain than the main domain ??

replication

2009-07-16 Thread James M McNutt
We are running Cyrus IMAP v2.3.12p2 with replication. after a initial replication of all users. we turned on rolling replication. and then did another replication of all users. but when comparing some users not all is of the replication is complete. I have been running manual replication of all

Re: Architectural mistake in cyrus ?

2009-07-16 Thread Dan White
Denis BUCHER wrote: Hello Andrew, Andrew Morgan a écrit : I already asked this question as an help request here some time ago, but noone was able to solve this bug in cyrus, and I think this issue should be addressed : 1] Problem : How to set quota for a user being in another domain

Re: Architectural mistake in cyrus ?

2009-07-16 Thread Andrew Morgan
On Thu, 16 Jul 2009, Denis BUCHER wrote: servername: hostname.MY MAIN DOMAIN (replaced with real values) admins: cyrus cyrus@MY MAIN DOMAIN sasl_pwcheck_method: saslauthd sasl_mech_list: PLAIN virtdomains: on hashimapspool: true = I don't have any defaultdomain: but I already tried with

RE: Permissions question

2009-07-16 Thread Gary Smith
I know this is a thread from last year that I posted, but I'm still needing clarification as I can't find the answer in the documentation (or google searches for that matter). Unlike the last one, this is not autocreate. I am creating these accounts through perl using IMAP::Admin. When I