6.0.0-beta1
7/4/25

[#11140] Mails 'Search (Entire Message)' does not work with IMAP under Windows
Summary Mails 'Search (Entire Message)' does not work with IMAP under Windows
Queue IMP
Queue Version 5.0.19
Type Bug
State Duplicate
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester almikhailov (at) parallels (dot) com
Created 04/10/2012 (4833 days ago)
Due
Updated 06/29/2012 (4753 days ago)
Assigned 06/18/2012 (4764 days ago)
Resolved 06/19/2012 (4763 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/29/2012 12:03:53 AM maiko (at) physics (dot) umanitoba (dot) ca Comment #13 Reply to this comment
Hi Michael,

I sent you and Jan an email earlier today detailing what I actually found, and
asking that you close this report. The problem is that my IMAP server is not
able to handle 'UTF-8 CHARSET'  as currently configured.

It's quite obvious actually. This is not a bug, but a *misconfiguration* on my
part, and my lack of understanding on the relatively new UTF-8 and all 
the issues and grief it has (and continues) to cause. Yes, I know it's 
been 5+
years since it appeared - I'm just a bit behind on the topic - now I know :)
Maybe your version of IMP is too old?
The final version of 4.0.6 was June, 2011. For some reason I thought it was
pretty recent, and for reasons I don't immediately recall, I was a bit 
hesitant to
go the 5.0 route, so I picked what I thought was the latest version.

Anyways, problem is *solved* for now as detailed in the email I sent you both.

Sorry if this wasted anyone's time.

As far as I'm concerned, the issue is closed. Thanks.

Maiko

06/28/2012 10:12:14 PM Michael Slusarz Comment #12 Reply to this comment

[Show Quoted Text - 9 lines]
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?
06/28/2012 02:02:40 PM maiko (at) physics (dot) umanitoba (dot) ca Comment #11
New Attachment: imaplog[1] Download
Reply to this comment

Upgrading Horde_Imap_Client did not fix this - do you want me to 
submit a NEW ticket ?

MORE DETAILS BELOW

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"]

Log attached, I assume the search is detailed where you see LSUB.

I'm going to try and debug this as well, I need to get it fixed.

Maiko

06/27/2012 08:53:03 PM maiko (at) physics (dot) umanitoba (dot) ca Comment #10 Reply to this comment

Last post - sorry to clutter up the ticket system, but I think I 
figured this out ...

1. check for upgrades by running this :

       perl list-upgrades

    which gives me :

       [root@drop ~]# pear list-upgrades
       pear.horde.org Available Upgrades (stable):
       ===========================================
       Channel        Package             Local           Remote          Size
       ...            ...                 ...             ...             ...
       pear.horde.org Horde_Imap_Client   1.5.1 (stable)  1.5.4 (stable)  136kB
       ...            ...                 ...             ...             ...

2. I can then upgrade the package in question by running this :

        pear upgrade -a -B horde/Horde_Imap_Client

Hopefully that's all there is to it.

Maiko

06/27/2012 06:12:03 PM maiko (at) physics (dot) umanitoba (dot) ca Comment #9 Reply to this comment

I don't want to screw this up. Can anyone give me the proper
command line on how I should do this. This is for HORDE 4.0.6
groupware email edition. Thanks muchly.
Updating a PEAR package within a major release (e.g. 
Horde_Imap_Client 1.x) will not break anything.
06/20/2012 08:24:50 PM Michael Slusarz Comment #8 Reply to this comment
Updating a PEAR package within a major release (e.g. Horde_Imap_Client 
1.x) will not break anything.
06/19/2012 08:33:15 PM maiko (at) physics (dot) umanitoba (dot) ca Comment #7 Reply to this comment

I see the fix is in the '/usr/share/pear' libs.

I am currently running :  Horde Groupware Webmail Edition, version 4.0.6

Question : can I safely update the pear side and not break what is now 
a production system ?

Lots of changes have been made to all of this stuff since I got 4.0.6 :(

Maiko

06/19/2012 08:05:35 PM Michael Slusarz Comment #6
State ⇒ Duplicate
Reply to this comment
Duplicate of Ticket  #11117.
06/18/2012 07:48:52 AM Jan Schneider Comment #5
Assigned to Michael Slusarz
State ⇒ Assigned
Reply to this comment
I removed the log per user request. I will mail it directly to you, Michael.
06/18/2012 07:48:07 AM Jan Schneider Deleted Original Message
 
06/18/2012 03:38:48 AM maiko (at) physics (dot) umanitoba (dot) ca Comment #4 Reply to this comment
Sorry, this is linux (SL 6.2), not Windows, and I am using :
Horde Groupware Webmail Edition (from a few months ago)


06/18/2012 03:35:44 AM maiko (at) physics (dot) umanitoba (dot) ca Comment #3
New Attachment: imaplog
Reply to this comment
Here is a complete IMAP log for you guys
I'm getting the 'Mailbox listing failed: IMAP error reported by server.' error
displayed to me when trying to SEARCH my inbox folder for 'From' field.
Consistently does this. When trying to find the error code in Exception
it would come up as UNSPECIFIED (if that helps any).
Wonder if this is related to UTF-8 ? Anyways, I'll leave it with you folks.
Thanks (getting very nice reviews from my users as far as fonts and layout)
Maiko

04/27/2012 09:13:09 AM Jan Schneider State ⇒ No Feedback
 
04/12/2012 09:56:42 AM Jan Schneider Comment #2
Priority ⇒ 2. Medium
State ⇒ Feedback
Reply to this comment
To further debug this issue, we need details of the IMP -> IMAP/POP 
communication.

To enable debugging, see instructions contained in 
imp/config/backends.php (the 'debug' config parameter).

Debugging should not be enabled on a production server,   Attach/post 
only the portion of the log that directly deals with the problem 
reported (it may be simplest to clear the log file and then perform 
the event that causes the error).
04/10/2012 08:44:39 AM almikhailov (at) parallels (dot) com Comment #1
Priority ⇒ 3. High
State ⇒ Unconfirmed
New Attachment: search.JPG Download
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Due ⇒ 04/10/2012
Summary ⇒ Mails 'Search (Entire Message)' does not work with IMAP under Windows
Type ⇒ Bug
Reply to this comment
PROBLEM DESCRIPTION

Platform: Windows 2008 R2, MailEnable 6.0, IMAP protocol is used.

Mails 'Search (Entire Message)' filter does not work, see screeenshot.
Error in horde.log:
==================
2012-04-10T15:30:12+07:00 ERR: HORDE [imp] IMAP error reported by 
server. [pid 5112 on line 351 of 
"C:\inetpub\vhosts\webmail\horde\imp\lib\Imap.php"]
==================

Saved Queries