[Tickets #10093] Re: Cannot create folder name with ampersand

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10093
------------------------------------------------------------------------------
  Ticket             | 10093
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Cannot create folder name with ampersand
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-05-17 23:07) wrote:

> This test whether a string is already encoded doesn't work.  
> Ampersands are used for other escapings than escaping the ampersand  
> itself too. I can't access the folder "Quarantäne" anymore, for  
> example, because it translates to "Quarant&AOQ-ne".

Then all of Horde_Imap_Client is broken.  Because we allow UTF-8 input  
for all mailbox parameters, which are all internally converted to  
UTF7-IMAP, so all of Horde_Imap_Client is unusable with mailboxes with  
ampersands according to its API.

The best solution is to ALWAYS require UTF-8 mailbox names.  But this  
is going to require a complete rewrite of much of IMP, since we mostly  
use UTF7-IMAP to internally represent mailbox names (although we  
interchangably use the two in several locations).

Which means that IMP 5.1 needs to be released (and soon).  This is a  
major issue to me since it completely prevents entire mailboxes from  
being accessed.

This is EXACTLY why RFC 3501 tells you not to use ampersands in  
mailbox names.  Just because it is technically feasible does not mean  
that we should allow it.