[Tickets #10447] Re: New trash folder gets created in the shared namespace

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10447
------------------------------------------------------------------------------
  Ticket             | 10447
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | New trash folder gets created in the shared namespace
  Queue              | IMP
  Version            | 5.0.10
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-08-22 17:51) wrote:

*Sigh*... this issue again.  Unfortunately your proposed solution is  
wrong because it breaks servers that use sane values for namespaces.

Obviously, namespaces can be whatever they want to be per the RFC  
definition.  But in practice, using anything other than the empty  
namespace for personal mailboxes is a terrible, terrible idea.  See,  
e.g.,  
http://mailman2.u.washington.edu/pipermail/imap-protocol/2007-August/000652.html

The issue comes with user input.  If I want to specifically*create a  
mailbox in a shared mailbox, I should be able to pass in the full  
mailbox name (including namespace).  Everything else should be  
interpreted as a mailbox being created in the default namespace.

The problem with using something other than the empty namespace as the  
personal namespace (or, more accurately, using the empty namespace for  
something OTHER than the default personal namespace) is that it is no  
longer possible to correctly auto-determine namespaces from user  
input.  E.g. Trash - you are making an assumption that they want to  
create INBOX.Trash.  However, an equally valid assumption is that they  
want to create a mailbox in a shared mailbox named Trash.  Therein  
lies the problem.

IIRC, the "solution" we previously came up with is essentially that we  
ALWAYS assume that user input is in the personal namespace only.  In  
other words, we prevent creation of mailboxes outside of the personal  
namespace.  However, this is a terrible compromise IMHO (although it  
might be necessary given the "broken" IMAP servers, e.g. Courier,  
Cyrus, that use terrible defaults for namespaces).