MBOX-Line: From tjs at psaux.com  Sun Dec 31 10:46:57 2017
To: imap-protocol@u.washington.edu
From: Tim Showalter <tjs@psaux.com>
Date: Fri Jun  8 12:34:55 2018
Subject: [Imap-protocol] Deleting selected mailbox
In-Reply-To: <CAPacwgxtf2soqi0yKrvR0r35dCHw5uq2E5zx=xqjxr9=JzEvXQ@mail.gmail.com>
References: <CAPacwgy_nVaePkawv3r2SVOM3yADyRjaX-=mfY_djevPSaV-Zw@mail.gmail.com>
	<vIPNOWMw3/S8yusfY1XTWtxFzSHnlx6wF6r6znWNDV0=.sha-256@antelope.email>
	<CAPacwgxtf2soqi0yKrvR0r35dCHw5uq2E5zx=xqjxr9=JzEvXQ@mail.gmail.com>
Message-ID: <CAByav=gR8a4vLVuQntxx476HdE4itGuVLYroNYgTjSve0-AuFw@mail.gmail.com>

On Sat, Dec 30, 2017 at 12:16 PM, Andris Reinman <andris.reinman@gmail.com>
wrote:

> Thanks, that's something I was assuming as well. The only problem I could
> think of would be clients that keep multiple connections for the same user
> account open. One connection tries to delete a mailbox, gets BYE and
> disconnects. The other one sees that DELETE was not properly answered and
> thus assumes that the mailbox is still there. Though I'd guess that clients
> that are able to keep multiple connections open are smart enough to not
> delete mailboxes that are currently selected.
>

Clients can't make this assumption. There is no reason to believe that only
one type of clients are accessing a mailbox, and the other type clients
have no responsibility (or ability) to "play nice".

I believe RFC 2180 discusses this in some detail. The document is pretty
old now, but was a topic of some discussion a few years back. I think that
it's very difficult to be really "smart" in any of these scenarios, and
probably the best practice is to keep it simple. I have seen a lot of
interesting interpretations from clients, but this one seems like the one
most likely to cause least confusion.

Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20171231/7dcffdb4/attachment.html>
