[Tickets #9842] Re: Search does not work

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9842
------------------------------------------------------------------------------
  Ticket             | 9842
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Search does not work
  Queue              | IMP
  Version            | 5.0
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Jan Schneider, Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-04-13 05:35) wrote:

> Working w/ charset:
> ----------------------------------
> . SEARCH CHARSET UTF-8 RETURN (ALL COUNT) FROM horde
> * ESEARCH (TAG ".") ALL

This is flat-out wrong.  Pursuant to RFC 4466 [2.6.1], the order of  
the arguments goes as follows:

    Arguments:  OPTIONAL result specifier
                OPTIONAL [CHARSET] specification
                searching criteria (one or more)

> So it appears the order of the CHARSET option.  Not sure if a cyrus  
> specific workaround is needed or if this how its supposed to be.   
> Every mention of charset in this paper shows it at the beginning:  
> http://www.faqs.org/rfcs/rfc5182.html

That's because RFC 5182 is not using the optional result specifier argument.

Sure enough, this is a Cyrus bug:
http://bugzilla.cyrusimap.org/bugzilla3/show_bug.cgi?id=3435