SquirrelMail - Webmail for Nuts!

When saving, enter the following:

 __   __ _______  ZZZZZZ   _         _______ 
 \ \ / /(       )ZZ   ZZ  ( (    /| |__   __|
  \ V / | () () |ZZ       |  \  ( |    | |   
   | |  | || || |ZZ ZZZZZ |   \ | |    | |   
   |_|  | |(_)| |ZZ   ZZ  | (\ \) |    | |   
        | |   | |ZZ   ZZ  | | \   |    |_|   
        | )   ( | ZZZZZZ  | )  \  |          
        |/     \|         |/    )_)

Visit Preferences to set your user name

=== Set-up ===

* UW IMAP 2000
* !SquirrelMail (version unknown)

=== Problem ===

<code>
Unknown error: * CAPABILITY IMAP4 IMAP4REV1
</code>

''Error message was trimmed.''

=== Solution ===

Upgrade your !SquirrelMail installation.

----

=== Set-up ===

* Red Hat 8
* UW IMAP (version unknown)
* PHP 4.2.2
* !SquirrelMail 1.4.1

=== Problem ===

When showing the content of a folder as threads, the following error message might appear:

<code>
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
</code>

=== Work-around ===

Edit the {{<user>.pref}} file and turn threading off for that folder or globally turn it off in {{config.php}}

=== Solution ===

Upgrade to !SquirrelMail 1.4.2.

----

=== Set-up ===

* UW IMAP 2000
* !SquirrelMail 1.4.2.

=== Problem ===

Having two copies of the same mail in the same maildir causes an error message.

''The mails:''

''The error message:''

<code>
ERROR : Bad or malformed request.
</code>

=== Work-around ===

Disable server side threading and server sorting.

=== Solution ===

Fix the broken IMAP server.

Summary of change:
Add document to category:

Editing CompatibilityErrorWithUW