This is my first time posting a problem to the list, I've searched the archives but
couldn't find anything of help on this error.

I've been running SQ from the early 1.2.x days and never received this error until I
upgraded to 1.4, so I'm thinking something's changed in the IMAP libraries maybe? When
installing SQ 1.4.0, I made no other modifications to anything else on the system.

Certain, few, users (over 600 in total) are receiving this error after logging in:
ERROR : Bad or malformed request.
Query: FETCH 231,232,233 (FLAGS BODY.PEEK[HEADER.FIELDS (RECEIVED)])
Server responded: Unrecognized UID subcommand

I've tried turning off "Enable UID support" from the config but then it yeilds this 
error:
ERROR : Bad or malformed request.
Query: FETCH 2,3,4 (FLAGS BODY.PEEK[HEADER.FIELDS (RECEIVED)])
Server responded: Null command

It's very strange that only some would get this error. I've checked their mailboxes on
the Cyrus DB and the /var/spool/imap/users directory -- rebuilt, re-SQUATed, reindexed,
everything I could think of but nothing changes for these users. If their mailbox
contains no messages, they log in just fine; if they've got even one message, this 
error
comes up after logging in.

I don't mind sticking with 1.2.11 because it works but I'd rather use 1.4.0 because 
it's
the latest and that's where development is now. Alot of the plugins dropped support
before 1.4.x

Any help would be greatly appreciated,
Andre

Server configuration:
Apache 1.3.27
PHP 4.1.2
Cyrus 2.1.13
SASL 2.1.13 with MySQL authentication
Sendmail 8.11.6




-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives:  http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

Reply via email to