wasm-demo/demo/ermis-f/imap-protocol/cur/1600095077.22820.mbox:2,S

33 lines
1.3 KiB
Plaintext

MBOX-Line: From arnt at gulbrandsen.priv.no Tue Nov 10 02:51:15 2009
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri Jun 8 12:34:43 2018
Subject: [Imap-protocol] "k" right in IMAP ACLs
In-Reply-To: <4AF93685.1050801@isode.com>
References: <alpine.OSX.2.00.0911092020290.72789@hsinghsing.panda.com>
<2EEFAD8A-EA31-43FE-932D-ADFA5148786E@iki.fi>
<4AF93685.1050801@isode.com>
Message-ID: <vz6RLt7axrkW0mogHa2J9A.md5@lochnagar.gulbrandsen.priv.no>
Alexey Melnikov writes:
> Timo Sirainen wrote:
>> On Nov 9, 2009, at 11:47 PM, Mark Crispin wrote:
>>> What do clients that implement IMAP ACL expect from the "k" right?
>> I'm not aware of any other clients than Mulberry that really supports
>> ACLs. I don't know what it expects.
> There are several clients supporting read-only ACLs, e.g. Thunderbird.
My impression (just from reading server logs) is that read-only is far
from unheard. One of the webmail thingies is the only I can recall that
does read-write.
Makes sense, too: It's easy to send a MYRIGHTS command and use the
result to enable/disable e.g. a "create mailbox" button or menu entry,
and much harder to write an edit dialog.
Now that I think about it, if a client does that, it may never run into
the corner case that started the thread.
Arnt