Re: [Imap-protocol] Deleting selected mailbox

--===============2761692019085609626==
Content-Type: multipart/alternative; boundary="94eb2c1c072a57281d0561a74a46"

--94eb2c1c072a57281d0561a74a46
Content-Type: text/plain; charset="UTF-8"

On Sat, Dec 30, 2017 at 12:16 PM, Andris Reinman <[email protected]>
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

--94eb2c1c072a57281d0561a74a46
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Dec 30, 2017 at 12:16 PM, Andris Reinman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:[email protected]" target=3D"_blank">andris.reinman@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r">Thanks, that&#39;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 t=
hus assumes that the mailbox is still there. Though I&#39;d guess that clie=
nts that are able to keep multiple connections open are smart enough to not=
 delete mailboxes that are currently selected.</div></blockquote><div><br><=
/div><div>Clients can&#39;t make this assumption. There is no reason to bel=
ieve that only one type of clients are accessing a mailbox, and the other t=
ype clients have no responsibility (or ability) to &quot;play nice&quot;.</=
div><div><br></div><div>I believe RFC 2180 discusses this in some detail. T=
he document is pretty old now, but was a topic of some discussion a few yea=
rs back. I think that it&#39;s very difficult to be really &quot;smart&quot=
; in any of these scenarios, and probably the best practice is to keep it s=
imple. I have seen a lot of interesting interpretations from clients, but t=
his one seems like the one most likely to cause least confusion.</div><div>=
<br></div><div>Tim</div><div><br></div></div></div></div>

--94eb2c1c072a57281d0561a74a46--

--===============2761692019085609626==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Imap-protocol mailing list
[email protected]
http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
--===============2761692019085609626==--