dovecot - Apr 2012 - imapc / namespace question

Hi,

I've got two questions regarding imapc and namespaces:

1) Is there a way of stating, that I only want part of the hierarchy on
the end of an imapc connection to be available here? My "problem":

On the other end the layout is:

INBOX.Shared.{some,nice,folders}

If I mirror this into my dovecot hierarchy with prefix "Gemeinsam" I
get
the following folder structure:

Gemeinsam.INBOX.Shared.{some,nice,folders}

But I want to ignore the two top-most parts of the hierarchy, i.e. I
want it to look:

Gemeinsam.{some,nice,folders}

Is this possible? I tried with 'location=imapc:INBOX.Shared.' but this
did not change anything.

2) "Private" namespaces only make sense, if location contains
something
user-specific like "%u" or "~". Is this correct?
If yes: Is there some other way to make something like an imapc
connection only appear for one user, if there is nothing in the location
or imapc_user to denote the user it belongs to and hence I cannot use
"private"?
The only way I see currently is to use "shared" and set up ACLs to
forbid all users except one to access the namespace (which gets slightly
ugly as I have to use global ACLs, as -- I think -- there is no way to
store ACLs for an imapc storage).

Thanks,
Ren?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20120413/0817d55d/attachment-0004.bin>

On 13.4.2012, at 23.41, Ren? Neumann wrote:
> I've got two questions regarding imapc and namespaces:
> 
> 1) Is there a way of stating, that I only want part of the hierarchy on
> the end of an imapc connection to be available here? My
"problem":
hg has now imapc_list_prefix.
> 2) "Private" namespaces only make sense, if location contains
something
> user-specific like "%u" or "~". Is this correct?
> If yes: Is there some other way to make something like an imapc
> connection only appear for one user, if there is nothing in the location
> or imapc_user to denote the user it belongs to and hence I cannot use
> "private"?
> The only way I see currently is to use "shared" and set up ACLs
to
> forbid all users except one to access the namespace (which gets slightly
> ugly as I have to use global ACLs, as -- I think -- there is no way to
> store ACLs for an imapc storage).
Well, it's not necessarily a problem to use a private namespace for anything
you want. If you set it hidden=yes (probably should do anyway) then IMAP clients
won't even know that you've set it as private. Internally the main
difference between private and public namespaces is the default ACLs.