From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <89979aff9defd6e858273a8897ffb970@plan9.bell-labs.com>
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] imap4d bugs(?)
Date: Sun, 17 Nov 2002 12:30:16 -0500
Topicbox-Message-UUID: 22433cf8-eacb-11e9-9e20-41e7f4b1d025

We've changed to upper case responses, but just in case anyone cares what
the imap4 standard really says, this comes from the BNF description of
the protocol commands and responses in rfc2060:

   Except as noted otherwise, all alphabetic characters are case-
   insensitive.  The use of upper or lower case characters to define
   token strings is for editorial clarity only.  Implementations MUST
   accept these strings in a case-insensitive fashion.

Of course, they're all defined in upper case so I suspect that's what
many clients expect.  Also, ms lookout responds with upper case and that's
what most most clients are probably trained against.