SquirrelMail - Webmail for Nuts!

When saving, enter the following:

 ####    ##   ##   TTTTTT   _   _          
  #  #   ##   ##   TT      ( ) ( )         
  #   #  ##   ##   TT      | |_| | ##  ##  
  #   #   #####    TTTT    |  _  | ## ##   
  #   #    ###     TT      | | | | ####    
  #  #     ###     TT      (_) (_) ####    
 ####      ###     TT              ## ##   
                                   ##  ##

Visit Preferences to set your user name

''Unknown error: * CAPABILITY IMAP4 IMAP4REV1''

(Error message was trimmed)

If you get this error with UW IMAP 2000, you need to upgrade your !SquirrelMail installation. This was fixed several versions ago (and there's some new security and features since your version).

It happened because we didn't properly parse the login string.  UW 2000 was the first server that we have seen that added extra lines of information when logging in, even though it was in the RFC properly.  It's all better now.

----

I have uw-IMAP  on Red Hat 8 with PHP version 4.2.2 and !SquirrelMail 1.4.1, when I turn on server-threading I intermittently get the following error in my message list for my INBOX (or any other folder where i've turned threading on);

ERROR : Bad or malformed request.
Query: FETCH (FLAGS UID RFC822.SIZE BODY.PEEK[HEADER.FIELDS (Date To Cc
>From Subject X-Priority Content-Type)])
Server responded: Bogus sequence in UID FETCH

Once I get this error it's there solidly until I edit my {{.conf}} file and turn threading off for that folder or globally turn it off at {{conf.pl}}. It's annoying because I have to be in a shell session and I don't have shell access from work, the reason I turned to !SquirrelMail in the first place... and i'm left with unreadable INBOX until I get home.

I don't have a solution, other than to not turn threading on. It's annoying as I like threading view. I set up the IMAP server type as 'uw', I'm not sure if it's made any difference; also I've added extra memory to {{php.ini}}, again I will have to test to see what condition turns the mailbox threading bad.

scot.

----

There is a solution. Uprade to the latest !SquirrelMail 1.4.2 CVS STABLE snapshot. This was fixed shortly after the release of 1.4.1

Marc Groot Koerkamp.

----

RE: ERROR : Bad or malformed request.

I had the same error as above with my current install of 1.4.2. Not sure what started it but I had to disable server side threading and server sort through {{conf.pl}}. Looks like Ill up to 1.4.3 now and check it out.

UPDATE: 
It looks like there are two copies of the same mail.
One marked read (1095382455.M891602P68906V00020D0CI000CA6B7.mail.host.com,S=7953:2,S)
and one marked unread (1095382455.M891602P68906V00020D0CI000CA6B7.mail.host.com,S=7953:2,). 
When both of these files are present in  a Maildir UW/!SquirrelMail dies and gives the FETCH error.

/Donavan

Summary of change:
Add document to category:

Editing CompatibilityErrorWithUW