MBOX-Line: From roma at stalker.com  Thu Mar  6 17:26:29 2008
To: imap-protocol@u.washington.edu
From: Roman Prokhorov <roma@stalker.com>
Date: Fri Jun  8 12:34:41 2018
Subject: [Imap-protocol] LSUB with the %
Message-ID: <47D099C5.9040805@stalker.com>

Hello,

Quoting RFC 3501:
>       A special situation occurs when using LSUB with the % wildcard.
>       Consider what happens if "foo/bar" (with a hierarchy delimiter of
>       "/") is subscribed but "foo" is not.  A "%" wildcard to LSUB must
>       return foo, not foo/bar, in the LSUB response, and it MUST be
>       flagged with the \Noselect attribute.

Could someone please explain why this exception is needed?



E.g. if I'm subscribed to "User/somedropbox", why would I need to 
discover that I'm also subscribed to "Users" if I'm not? Assuming that 
'LSUB *' will return only User/somedropbox - any client can get confused.

If some client uses a sequence of 'LSUB %', then 'LSUB found/%', etc for 
reading the tree of subscriptions - this is a problem of the client, and 
it should not be transferred to all servers and clients.

If I have lookup right on 'one/two' mailbox but no lookup right on 'one' 
- does it mean that the same "special situation" should occur for LIST 
command which on 'LIST "~someuser" "%"' should show me 'one' (despite of 
the fact that I don't have lookup right for it) if a 'one/two' mailbox 
exist which for I do have lookup right?

-- 
Roman

