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 |
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 :)
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
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?
New Attachment: imaplog[1]
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
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
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.
Horde_Imap_Client 1.x) will not break anything.
1.x) will not break anything.
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
State ⇒ Duplicate
#11117.Assigned to Michael Slusarz
State ⇒ Assigned
Horde Groupware Webmail Edition (from a few months ago)
New Attachment: imaplog
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
Priority ⇒ 2. Medium
State ⇒ Feedback
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).
Priority ⇒ 3. High
State ⇒ Unconfirmed
New Attachment: search.JPG
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Due ⇒ 04/10/2012
Summary ⇒ Mails 'Search (Entire Message)' does not work with IMAP under Windows
Type ⇒ Bug
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"]
==================