Hi there.

I'm running some servers for a small company and all employees are allowed to use whatever client they like. Most popular are Mozilla's TB, The Bat! and a webmail service that I provide.

Some of our mail accounts need access to shared folders. Courier-imap allows two different ways of doing this:

a) You can create mailboxes for things like "support@domain" and allow others to access this mailbox physically. This is awkward to maintain and keeps softlinks for each shared mail per subscribed user.

b) You can create those mailboxes and use "virtual shared folders", a way to specify courier-imap internal ACLs for mailboxes (UserA may read Mailbox B, C and write to D).

We used a) first, but because it's really nasty to maintain and because of some internal decisions I moved over to b). The trouble starts here:
courier-imap now puts all those virtual shared folders below #shared (#shared.support, #shared.marketing, whatever). According to the courier-imap developers this is both according to the IMAP RFC (# is for namespaces, if I got it right) and correct/won't change. Unfortunately some clients have problems to find this folders. Like The Bat!.
The courier-imap developer is a little bit grumpy and tends to say "if it doesn't work, your client is broken", but as far as I understand the issue an imap LIST only works for the specified (or global) namespace, so #shared folders don't turn up in a glob search.

Long story short: Do you understand the/my issue? Is the imap implementation in The Bat! lacking support here? Can it be fixed? Any timeline? Can I provide help/more info/limited access to a mailbox on a courier-imap server for a developer?

Thanks for reading all this mess,
Ben