[Tickets #12720] Re: Mark sent-mail folders to show up in / hide from special folder container

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12720
------------------------------------------------------------------------------
  Ticket             | 12720
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Mark sent-mail folders to show up in / hide from
                     | special folder container
  Queue              | IMP
  Version            | Git master
  Type               | Enhancement
-State              | New
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-10-14 23:39) wrote:

>> Quite frankly, the number of people that have more than 2-3
>> identities is extremely small.  So adding an additional parameter
>> just for this few people is not a great idea.
>
> The people around me (e.g. in my GnuPG keyring) have 3 UIDs /  
> identities or more. So that point is not taken.

The fact that you know what a GnuPG keyring is means that you are in  
the 1% of users.

We have Horde/IMP installations that have *millions* of users.  These  
are "Gmail"  type users - they want a simple e-mail client.  Most of  
them only have 1 identity.  This would thus be adding a feature that  
would potentially negatively affect the 99% of users while only  
benefitting 1% of users.

That doesn't mean it can't be done.  But that means you have to think  
out the UI/UX before going forward so that those 99% of users AREN'T  
affected just to give advanced functionality for a few.

> Also frankly said, I could completely do without the special folder  
> container and just have all folders in one tree. The special folder  
> container takes up so much space (more than half of the sidebar with  
> all my sent-mail folders in it).

At the beginning of the project, we had several usability experts give  
us input on this.  Their overwhelming recommendation is that those  
special mailboxes are necessary for the 99%.  Most people only use a  
couple of mailboxes.  These mailboxes tend to be the special  
mailboxes.  Thus, those special mailboxes need to be in view and  
present at all times.

> The rest of the mailbox tree is buried under it.

For the record - I have something like 200 mailboxes.  And I have  
never thought there is inadequate space in the mailbox list.

> So, for me another option would be to have the special folder  
> container removed completely (including the INBOX) and have all  
> those folders re-intregated into the mailbox tree  (I have already  
> tested that). Though with a removal of the special folders  
> container, I would love to have custom icons for INBOX, sent-mail,  
> trash, templates, drafts.

We would consider a patch for this.  But it's going to take a bunch of  
work to abstract this.  Especially since the current code in  
javascript is designed with the special mailboxes section in mind and  
there is the Folder Actions menu that would need to be placed  
somewhere (quite honestly, it doesn't make much sense to put at the  
top of the list, above INBOX, so that's a question that needs to be  
addressed before anything is done).

The custom icon data is already abstracted and completely independent  
of the special mailbox location, so there's nothing to do there.

> Furthermore, I have other ,,important'' folders (mail filtered into  
> them by sieve) that I cannot add to the special folders container  
> (apart from using the config part in the backend, but that's not  
> user specific, but backend specific, so no option). However, this is  
> nothing that can be easily worked into the current special folder  
> implementation (IMHO).

This is exactly what the special_mboxes backends.php config option is  
for.  Granted, this is a config file only, as opposed to a  
user-editable thing.  But that is simply because nobody has taken the  
time to write the UI for it.  It neither interests me greatly, nor has  
anyone funded the work, so that's why it doesn't exist.