40 lines
1.8 KiB
Plaintext
40 lines
1.8 KiB
Plaintext
MBOX-Line: From guenther+imap at sendmail.com Wed Nov 18 13:02:53 2009
|
|
To: imap-protocol@u.washington.edu
|
|
From: Philip Guenther <guenther+imap@sendmail.com>
|
|
Date: Fri Jun 8 12:34:43 2018
|
|
Subject: [Imap-protocol] wildcards in other users' namespace
|
|
In-Reply-To: <alpine.OSX.2.00.0911181212090.244@hsinghsing.panda.com>
|
|
References: <2134052040.817.1258573414683.JavaMail.root@dogfood.zimbra.com>
|
|
<1258574152.3022.695.camel@timo-desktop>
|
|
<alpine.OSX.2.00.0911181212090.244@hsinghsing.panda.com>
|
|
Message-ID: <alpine.BSO.2.00.0911181248280.8115@vanye.sendmail.com>
|
|
|
|
On Wed, 18 Nov 2009, Mark Crispin wrote:
|
|
> Also, I can think of a case where "accessible" and "published" should be
|
|
> very different. The fact that something can be listed does not mean
|
|
> that it should be published.
|
|
...
|
|
> Should these mailboxes be published to the world due to the anyone
|
|
> rights, and thus show up in everybody's list of mailboxes? Or, as I
|
|
> contend, just to those who know to look in the mrc-class account?
|
|
|
|
Wasn't that the intent of the distinction between +l and +r? A mailbox
|
|
that is +r-l can be selected if you can enter its name. What you're
|
|
talking about here is some finer granularity within LIST/LSUB, where
|
|
'broader' operations such as
|
|
tag LIST "" *
|
|
require more than +l on some classes of mailboxes for them to be returned,
|
|
or maybe that 'narrower' operations such as
|
|
tag LIST "" /Users/mrc/%
|
|
require less than +l.
|
|
|
|
I guess the problem with +r-l is that it is dependent on client support
|
|
for directly entering mailbox names and that is apparently not something
|
|
someone can count on. In order to design a fix, what *can* be depended
|
|
on? The ability of a client to show that /Users/mrc exists at all and
|
|
peek into it with something like that last LIST above? More? Less?
|
|
|
|
|
|
Philip Guenther
|
|
|