squirrelmail search broken?

C

CentOS5

Verified User
Joined
Jan 26, 2006
Messages
57
Updated SquirrelMail to latest from custombuild and now the serach is broken within squirrelmail, anyone else having this problem?

ERROR: Bad or malformed request.
Query: FETCH (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance Priority Content-Type)])
Server responded: Error in IMAP command UID FETCH: Invalid arguments.
Click to expand...

Previous versions worked fine

Looks like a know issue with squirrelmail and they say that it will be fixed in the next update, anyways url below if you want to read, and a patch fix.

http://old.nabble.com/Search-error-td25193347.html
 
Last edited:
Error in IMAP command UID FETCH: Invalid arguments.

Its not passing the right amount of arguments. Edit the squirrelmail source code, update squirrelmail, or ask on dovecot website.
 
I've got a user account with the same problem.
ERROR: Bad or malformed request.
Query: FETCH (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance Priority Content-Type)])
Server responded: Error in IMAP command UID FETCH: Invalid arguments.
Click to expand...
This user has a very large mailbox (~2.8 with lots of saved messages (with organized folders, not all in the inbox) so I'm not sure if that's an issue. Running under the "stock" DirectAdmin version of squirrelmail, 1.4.0 RC2. So the bug is definitely not fixed. Any ideas on how to eliminate this?
 
As a follow up I've tested this on smaller mailbox size users and the same problem exists. In checking the Squirrelmail listmail archives this is a known problem. Consider the following response from one of the developers. apparently there is a new version, 1.4.20-svn rather than RC2. Note the emphasis is mine, not the developer's. Is there any chance to get this patched or the newer version substituted?

From: Tomas Kuliavas <tokul <at> users.sourceforge.net>
Subject: Re: Search option broken in SquirrelMail 1.4.20-RC2
Newsgroups: gmane.mail.squirrelmail.user
Date: 2010-02-01 08:36:13 GMT (2 days, 10 hours and 6 minutes ago)

2010.02.01 10:15 Abdul Khader rašė:
> Hi,
> I added .htaccess file and now I am seeing the search page but when I do
> search, I get the following error.
>
> *ERROR: Could not complete request.*
> Query: FETCH (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS
> (Date To Cc From Subject X-Priority Importance Priority Content-Type)])
> Reason Given: Error in IMAP command received by server.

Which SquirrelMail version gives this error? Please note that I've already
said that 1.4.20-rc2 has known issues in search. Please don't say that you
have problem with search, if you are using 1.4.20-rc2 and not 1.4.19 or
1.4.20-svn. If you insist on using 1.4.20-rc2, you WILL have problems in
search and filters.

What kind of search you are doing? Do you search in one folder or all of
them? Do you search for some basic ascii text or for some 8bit string in
some local language? Do you have one word or more words separated with
spaces in your search criteria?

--
Tomas

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Click to expand...
 
But those are the current versions. Guess you will just have to wait till they release fixes.
 
Nope, neither are the current release version. RC2 was a developmental release. The bug found in RC2 has been fixed in the SVN release, but both are considered development releases. The last non-beta "release" version is 1.4.19 which apparently also does not have the bug. So if we're going to be running a test version, we need to update to the latest test version as pointed out by one of the developers.
 
Last edited:
Bumping this. Can we get the fixed version? This problem has been noted by the developers and it is noted that the version currently included in DA is a buggy release candidate. Can we either downgrade to the current release version (1.4.19), or "upgrade" to the latest fixed version (1.4.20-svn)? Either way, but for right now we're left in limbo.
 
You must log in or register to reply here.
Back
Top