[Tickets #12937] The 'utf8' parameter usage in the sieve backend doesn't work as described.

noreply at bugs.horde.org noreply at bugs.horde.org
Sat Jan 25 16:17:35 UTC 2014


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

Ticket URL: http://bugs.horde.org/ticket/12937
------------------------------------------------------------------------------
  Ticket             | 12937
  Created By         | nordmark at mech.kth.se
  Summary            | The 'utf8' parameter usage in the sieve backend doesn't
                     | work as described.
  Queue              | Ingo
  Version            | 3.1.3
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


nordmark at mech.kth.se (2014-01-25 16:17) wrote:

The 'utf8' parameter, as described in the backends.php, should enable  
the UTF-8 encoding for folder names. The code that uses the parameter  
is found in lib/Script/Sieve/Action/Fileinto.php, and looks like

if (!empty($vars['utf8'])) {
    $this->_vars['folder'] =  
Horde_String::convertCharset($this->_vars['folder'], 'UTF7-IMAP',  
'UTF-8');
}

However, it seems that the folder name is already coded as UTF-8 when  
this code is reached, with the result that each non-ACSII character is  
turned into a sequence like '??'.

On the other hand, if the 'utf8' parameter is false or not defined,  
UTF-8 characters in mailboxes work fine.'

Thus, both the description and the code seems to come from a time when  
folder names were stored encoded as IMAP-UTF-7. Unless this can still  
be true, the parameter should be removed and the examples in  
backends.php should be updated.

Thanks
Arne Nordmark





More information about the bugs mailing list