Re: Replication of delayed deletes/expunges

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 19 October 2011 17:38, Bron Gondwana <brong@xxxxxxxxxxx> wrote:
> On Wed, Oct 19, 2011 at 04:58:35PM +0100, Guy wrote:
>> I've just started playing around with Cyrus replication and I've got a
>> set up with chained replication working nicely. I haven't tested
>> delayed expunges yet, but delayed deletes don't appear to work on the
>> replicas. The master server does a delayed delete and I can see the
>> renamed mailbox in the list of mailboxes, but on the slaves the
>> mailbox is simply deleted.
>>
>> I'm running imapd 2.4.12. Below are the configs for the main master
>> and slave. Am I missing something extra needed for the delayed deletes
>> to propagate as delayed?
>
> It should sync-log the delayed folder and then rename on the replica
> as well.  As far as the replica is concerned, it was just a:
>
> RENAME user.foo.sub DELETED.user.foo.sub.$TIMESTAMP

After some experimentation I've found that sub mailboxes behave as
expected but if the top-level mailbox is delayed deleted on the master
it is immediately deleted on the replica.

I've tried enabling the "allowusermoves" on the master and replica to
allow the account to be renamed but this has not worked.

Is this the expected behaviour for the top-level mailbox or is there a
way around this?

Thanks
Guy


-- 
Don't just do something...sit there!
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/



[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux