Re: Is user lock-out required for backend xfers?

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

 



On 12 Mar 2009, at 13:03, Dave McMurtrie wrote:
> You should not need to do anything to prevent client access to a  
> mailbox
> when it's being moved and there should never be any resulting
> corruption.  Cyrus locks the mailbox while it's being moved.

And any result different from the above should be considered a bug :)

> I will mention, however, that some clients get confused if they're
> connected while a mailbox is being moved and I've never actually  
> figured
> out why.  The confusion is usually a matter of a user's mailbox  
> suddenly
> appearing to be empty which is resolved by having them restart their
> mail client.  The most extreme confusion I've seen so far was with  
> some
> version of Outlook where the user actually had to delete and recreate
> their account configuration to convince Outlook that the mailbox  
> was not
> empty.

I'm pretty sure this is because neither the frontends nor the clients  
are able to intelligently handle the kinds of transient errors that  
are returned.  Frontend improvements might be possible.  Client  
improvements are Sisyphean.

: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

[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