[Tickets #6972] Re: mailbox listing speed-up

bugs at horde.org bugs at horde.org
Thu Jun 26 21:59:44 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6972
------------------------------------------------------------------------------
  Ticket             | 6972
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | mailbox listing speed-up
  Queue              | IMP
  Version            | 4.2
  Type               | Enhancement
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2008-06-26 17:59) wrote:

> I have prefs set to display namespaces separately and use
> subscriptions. Now, if there is a shared folder from another user,
> the parent node saying "Other Users' Folders" is displayed (empty),
> even if I didn't subscribe to any of those other users' folders.

I thought this was a feature?  Or did we decide in the past that if a  
public/other namespace is empty, we would only show if subscriptions  
were off?  We do need to show this namespace somewhere, even if it is  
empty, if simply to allow the user to create subfolders in this  
namespace.

> Additionally, the user itself is clickable, though I'm not sure if
> this is an issue with the IMAP server or IMP, i.e. I have the
> hierarchy:
>
> Other User's Folders
>   username
>     foldername
>
> if the user "username" shared his folder "foldername". And both
> "username" and "foldername" appear as clickable, valid mailboxes.

Can you check the output from _getList() and see if  
"namespace.username.folder" is being returned from the IMAP server, or  
if both "namespace.username.folder" and "namespace.username" is being  
returned.  Obviously, if it is the former than IMP_Tree is buggy, and  
if it is the latter then the IMAP server is buggy.





More information about the bugs mailing list