The main reason things changed is sypport for shared mailboxes. I can't
elaborate now because I'm driving.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
-----Original Message-----
From: "Wesley Craig" <[EMAIL PROTECTED]>
To: "David Carter" <[EMAIL PROTECTED]>
Cc: "Bron Gondwana" <[EMAIL PROTECTED]>; "Ken Murchison" <[EMAIL PROTECTED]>;
"Info Cyrus" <info-cyrus@lists.andrew.cmu.edu>
Sent: 8/29/06 11:05 AM
Subject: Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in
one run
On 29 Aug 2006, at 04:35, David Carter wrote:
> My original code (which we are still running: I'm not in any hurry
> to upgrade to 2.3) sorts mailbox actions by user. If a single
> mailbox action associated with a user fails the rest are discarded
> and a USER event is generated. If the USER event fails it locks the
> given user out of the mboxlist and tries again. This is close to
> what you describe above.
Why is 2.3 different? I'm fairly sure that these issues:
4) xfer onto a replicating backend causes sync_client to exit
8) renaming users causes sync_client to exit
would be solved with the algorithm you're using (or the one Bron
outlined).
:wes
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
