MBOX-Line: From mrc+uw at Panda.COM  Wed Nov 18 11:00:25 2009
To: imap-protocol@u.washington.edu
From: Mark Crispin <mrc+uw@Panda.COM>
Date: Fri Jun  8 12:34:43 2018
Subject: [Imap-protocol] wildcards in other users' namespace
In-Reply-To: <1258570418.3022.660.camel@timo-desktop>
References: <alpine.OSX.2.00.0911181030030.244@hsinghsing.panda.com>
	<1258570418.3022.660.camel@timo-desktop>
Message-ID: <alpine.OSX.2.00.0911181056290.244@hsinghsing.panda.com>

On Wed, 18 Nov 2009, Timo Sirainen wrote:
>> For example, given a server which exports
>>  	(("" "/")) (("/Users/" "/")) (("/Public" "/"))
>> what servers permit a client to do:
>>  	tag LIST "" /Users/*
> Dovecot, if configured to do so. And of course not all users, only those
> that have mailboxes with +l permission to LISTing user.

Does Dovecot configure this by default?  Why or why not?

Does Dovecot scan the entire private user tree looking for +l mailboxes, 
or does it have a reverse cache of accessible names?  Or does it have a 
global ACL database?

>> To follow-up on my previous question, what clients besides Thunderbird
>> attempt to do such a command?
> If that didn't work, I think shared namespaces would be almost unusable
> in most IMAP clients. Clients don't support accessing mailboxes that
> they can't LIST (or LSUB, but subscribing would again require LIST to
> show them).

Please note that I am talking about access to other users' mailboxes and 
not to shared mailboxes.  Of course,
 	tag LIST "" /Public/*
should work in the above example.

What I am trying to determine is the use case for
 	tag LIST "" /Users/*

Is it really true that clients must be able to download a complete tree of 
all possible names in order to be able to access a name?

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

