[Tickets #11140] Re: Mails 'Search (Entire Message)' does not work with IMAP under Windows

bugs at horde.org bugs at horde.org
Thu Jun 28 22:12:14 UTC 2012


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

Ticket URL: http://bugs.horde.org/ticket/11140
------------------------------------------------------------------------------
  Ticket             | 11140
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Mails 'Search (Entire Message)' does not work with IMAP
                     | under Windows
  Queue              | IMP
  Version            | 5.0.19
  Type               | Bug
  State              | Duplicate
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-06-28 16:12) wrote:

> Still getting the following error on client display, when Search a  
> mail folder :
>
>    Mailbox listing failed: IMAP error reported by server.
>
> The /var/log/messages is showing the following :
>
>    Jun 28 08:48:00 drop HORDE: [imp] IMAP error reported by server.
>       [pid 32362 on line 345 of "/var/www/html/horde/imp/lib/Imap.php"]

I cannot reproduce.  You are getting this error from the IMAP server:

C: 5 UID SEARCH CHARSET UTF-8 FROM maiko
S: 5 NO UTF-8 character set is not supported.

But with the latest version of IMP (5.0.22), this is impossible due to  
the code in IMP_Imap#_search().  At least once a session, we  
explicitly check whether UTF-8 is supported via a test query (the  
validSearchCharset() call on line 488 of IMP_Imap).   Sure enough, I  
see this on a server that doesn't support UTF-8:

C: 8 SEARCH CHARSET UTF-8 BODY a 1
S: 8 NO UTF-8 character set is not supported.

...and later, my actual search query:

C: 3 UID SEARCH FROM test
S: * SEARCH
S: 3 OK SEARCH done.

which doesn't use UTF-8 and instead directly uses US-ASCII.

Not sure what is wrong on your system.  Maybe your version of IMP is too old?





More information about the bugs mailing list