[9fans] imap4d bugs(?)

[9fans] imap4d bugs(?)

[presotto]

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.

Re: [9fans] imap4d bugs(?)

[Lyndon Nerenberg]

presotto@plan9.bell-labs.com writes:
>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.

I'm surprised this is just coming up now. This was rarely, if ever, and
issue at any of the IMAP4 interop events, and I know for a fact there
were servers there doing mixed-case responses (and clients for that
matter). If people are running into clients that get this wrong, I would
appreciate it if you could tell me the name and version of the client
so that the appropriate bug reports can be filed.

--lyndon

Re: [9fans] imap4d bugs(?)

[Skip Tavakkolian]

> Also, ms lookout responds with upper case and that's
> what most most clients are probably trained against.

Was it a Freudian slip, or did you mean to call it that? That
would be the perfect name for it, maybe just add an exclamation
mark to the end of it ☺