6.0.0-beta1
7/17/25

[#11675] IMP search broken in large mailbox
Summary IMP search broken in large mailbox
Queue IMP
Queue Version Git develop
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester jemartins (at) fis (dot) unb (dot) br
Created 11/08/2012 (4634 days ago)
Due
Updated 11/12/2012 (4630 days ago)
Assigned 11/09/2012 (4633 days ago)
Resolved 11/12/2012 (4630 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
11/12/2012 07:40:07 PM Michael Slusarz State ⇒ Not A Bug
 
11/12/2012 01:38:09 PM jemartins (at) fis (dot) unb (dot) br Comment #10 Reply to this comment
What I am asking for is a way to reliably reproduce.  I can't 
provide much more feedback since I have no idea where to being 
looking since I don't see this behavior.  Thus, it will require you 
to track down to a certain area of the code to help out.  Or to 
figure out ways to NOT trigger this error - that is potentially also 
useful information.
I can't reproduce that behaviour also now. Searching are working well. 
Maybe there was problem in mbox when I noticed this problem.
Thank you.
11/11/2012 01:04:17 PM jemartins (at) fis (dot) unb (dot) br Comment #9 Reply to this comment
What I am asking for is a way to reliably reproduce.  I can't 
provide much more feedback since I have no idea where to being 
looking since I don't see this behavior.  Thus, it will require you 
to track down to a certain area of the code to help out.  Or to 
figure out ways to NOT trigger this error - that is potentially also 
useful information.
I have one more site where I can debug. I am not familiar with PHP. 
What I need do?
11/11/2012 03:09:21 AM Michael Slusarz Comment #8 Reply to this comment
OK, Michael. I trust in your job. May be this is a specific problem 
with WU-IMAP or misconfiguration system. So, it's my fault.
What I am asking for is a way to reliably reproduce.  I can't provide 
much more feedback since I have no idea where to being looking since I 
don't see this behavior.  Thus, it will require you to track down to a 
certain area of the code to help out.  Or to figure out ways to NOT 
trigger this error - that is potentially also useful information.
11/11/2012 01:21:57 AM jemartins (at) fis (dot) unb (dot) br Comment #7 Reply to this comment
I am searching for word "palomitas" using body search criteria in
Enviados/Sent folder. I don't have this problem if the small folder.
And I don't have this problem at all.  Even searching on a mailbox 
with 100,000 messages.
OK, Michael. I trust in your job. May be this is a specific problem 
with WU-IMAP or misconfiguration system. So, it's my fault.
11/11/2012 12:41:13 AM Michael Slusarz Comment #6 Reply to this comment
I am searching for word "palomitas" using body search criteria in 
Enviados/Sent folder. I don't have this problem if the small folder.
And I don't have this problem at all.  Even searching on a mailbox 
with 100,000 messages.
11/10/2012 01:14:52 AM jemartins (at) fis (dot) unb (dot) br Comment #5 Reply to this comment
I am searching for word "palomitas" using body search criteria in 
Enviados/Sent folder. I don't have this problem if the small folder.
11/10/2012 12:01:57 AM Michael Slusarz Comment #4 Reply to this comment
OK. See imaplog in attach.
This is a valid IMAP command it is choking on:

C: 4 UID SORT (ARRIVAL) UTF-8 BODY ""
S: * OK [PARSE] Unexpected characters at end of parameters: : 8bit

It is perfectly fine to search for an empty string.  It may not make 
much sense (more on that in a second), but it shouldn't break.  You 
are pretty much out of luck if your IMAP server is broken in this 
manner since we can't really work around it.

As for the blank search term: I can't reproduce that.  What exactly 
are you searching for?  (Make sure your search doesn't have any 
accented characters).
11/09/2012 11:48:30 PM jemartins (at) fis (dot) unb (dot) br Comment #3
New Attachment: imaplog Download
Reply to this comment
OK. See imaplog in attach.
11/09/2012 10:39:18 PM Michael Slusarz Comment #2
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).
11/08/2012 11:27:27 PM jemartins (at) fis (dot) unb (dot) br Comment #1
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Due ⇒ 11/08/2012
Summary ⇒ IMP search broken in large mailbox
Type ⇒ Bug
Priority ⇒ 1. Low
Reply to this comment
If we try search (advanced or not) using body criteria in large folder 
(for example: sent with over 8500 messages) the system broken with 
this message: "Error when communicating with the server" and in log we 
can see:

2012-11-08T21:20:00-02:00 ERR: HORDE-5.0 [imp] The mail server was 
unable to parse the contents of the mail message. Unexpected 
characters at end of parameters: : 8bit [pid 14176 on line 382 of 
"/home/httpd/html/horde-5.0/imp/lib/Imap.php"]

Saved Queries