Problem with Shared Mailbox - Cyrus Aggregation - Backend - 2.4.1

[Bron Gondwana]

On Tue, Oct 19, 2010 at 01:14:12AM -0200, Lucas Zinato Carraro wrote:
> My configuration
> 
> User Inbox         - Backend cyrus 2.4.1
> +SharedFolderA - Backend cyrus 2.4.1
> +SharedFolderB - Backend cyrus 2.3.16
> 
> Client used  Mozilla Thunderbird 3.1.4
> 
> In File Subscribe i can see all Folders ( INBOX, SharedFolderA, SharedFolderB )
> When i click in subscribe, i dont have any problem or erroneus message
> 
> I see " shared folder"  in my HOME server normal,  but folders in
> another server ( SharedFolderB )
> appears in Grey Italic.
> 
> Reference:
> 
> http://kb.mozillazine.org/Grey_italic_folders
> 
> "" A IMAP folder will be displayed in grey italics if the folder has a
> \Noselect flag. Normally this means
>  the folder can contain child folders, but not messages. [1] This is a
> IMAP protocol flag, not one of
>  the folder flags that can be set using the Folder Flag extension. """"
> 
> If i uncheck the option "Show only subscribed folder" in Config >>
> Account >> Server >> Advanced.
> I can work normal with all mailboxes...
> 
> This is the correct behavior in Cyrus 2.4.1 ?
> 
> In Cyrus 2.3.16 i dont have to set this option, i can subscribe normal in
> remote mailboxes servers.
> 
> With Cyrus 2.4.0 i see the folders to subscribe, but the folders are
> not avaiable i dont see
> any folder, in Cyrus 2.4.1 i see this folders, but  in grey italic.

Ok - what's the version on your frontend?  If that's running 2.4.1
(and restarted) then it should be filtering out the \Noselect flag
if (and only if) the mailbox exists in murder.

All your "LSUB" response is coming from the Inbox server - and it
has \Noselect for all the folders that aren't on that same server.
The frontend the passes this to pipe_lsub (in imap_proxy.c) which
filters the \Noselect flag off.

There was a bug in 2.4.0 (and presumably earlier, I didn't touch
that code before) where it wasn't removing \Noselect, despite a
comment to the effect that it should be.  Upgrade your frontend
to 2.4.1 and that will be fixed.

Bron.