[Tickets #10726] Re: Exchange 2003 IMAP error: Specified character set not supported.

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10726
------------------------------------------------------------------------------
  Ticket             | 10726
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Exchange 2003  IMAP error: Specified character set not
                     | supported.
  Queue              | IMP
  Version            | 5.0.14
  Type               | Bug
-State              | Feedback
+State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-11-09 15:17) wrote:

Issue is that Exchange 2003 does not appear to support UTF-8 in SEARCH  
queries (which is kind of ridiculous in this day and age...)  RFC 3501  
only requires compliant servers to handle US-ASCII.

Although, in your situation, we are just searching by flags, so there  
is no reason to even add CHARSET information.  So I've made this change.

> Things are getting funnier. I accidentally changed sort order in  
> DIMP interface from subject to thread and suddenly the mails where  
> listed as expected. Further tests showed that they only get listed  
> when sorted by thread. Any clue?

This is completely expected.  The THREAD extension REQUIRES the server  
to handle UTF-8 queries (which begs the question: the server can  
obviously handle UTF-8, so why does it now allow UTF-8 support in the  
default SEARCH command?)

This is probably a good idea to complete sanity checking in the search  
query when a bad charset is used.  The only option is to downconvert  
to us-ascii.