35 lines
1.4 KiB
Plaintext
35 lines
1.4 KiB
Plaintext
MBOX-Line: From davew at hireahit.com Tue Jan 26 00:44:22 2016
|
|
To: imap-protocol@u.washington.edu
|
|
From: Dave Warren <davew@hireahit.com>
|
|
Date: Fri Jun 8 12:34:55 2018
|
|
Subject: [Imap-protocol] Selected mailbox deleted by another client
|
|
In-Reply-To: <1453765295.487330.502398698.1C26076F@webmail.messagingengine.com>
|
|
References: <20160125231528.GA21616@mew>
|
|
<1453765295.487330.502398698.1C26076F@webmail.messagingengine.com>
|
|
Message-ID: <56A731E6.60104@hireahit.com>
|
|
|
|
On 2016-01-25 15:41, Bron Gondwana wrote:
|
|
> Another possible thing (and what Cyrus IMAP used to do for a little while
|
|
> in the 2.4 series when I added long-lived index locks) is to say
|
|
> "NO Mailbox is locked" to the session which tries to delete an open
|
|
> mailbox. This was bad because the situation actually occurs quite often
|
|
> in practice that someone's phone or desktop is sitting there with a mailbox
|
|
> open for hours or days just NOOPing away.
|
|
|
|
From a user perspective, this is probably the least desired
|
|
possibility, although it certainly would avoid any further complications :)
|
|
|
|
Another possibility would be to block any further attempt to SELECT, or
|
|
add messages into the mailbox and queue the delete for the next time the
|
|
lock is released. I know of one server that does this in certain
|
|
circumstances, and it seems minimally harmful from a end-user and client
|
|
perspective.
|
|
|
|
--
|
|
Dave Warren
|
|
http://www.hireahit.com/
|
|
http://ca.linkedin.com/in/davejwarren
|
|
|
|
|
|
|