On 29 Aug 2006, at 11:39, Ken Murchison wrote:
The main reason things changed is sypport for shared mailboxes. I
can't elaborate now because I'm driving.
Can you say more about this? I'd like to fix this code and resubmit
it. The current implementation causes sync_client to bail out,
particularly during xfer.
On a related note, what was the problem with accepting the Cambridge
patches for delayed folder deletion? I'm interested in working on
getting that or similar code accepted. Now that we have delayed
expunge for messages, we continue to run tape backups only for the
case where users inadvertently delete folders.
:wes
-----Original Message-----
From: "Wesley Craig" <wes@xxxxxxxxx>
To: "David Carter" <dpc22@xxxxxxxxx>
Cc: "Bron Gondwana" <brong@xxxxxxxxxxx>; "Ken Murchison"
<murch@xxxxxxxxxxxxxx>; "Info Cyrus" <info-cyrus@xxxxxxxxxxxxxxxxxxxx>
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://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
