Re: Problems with latest imap stuff

[Simon Josefsson <jas@pdc.kth.se>]

Lyndon Nerenberg <lyndon@esys.ca> writes:

> In this case, if all you want to do is differentiate between RFC1730 and 
> RFC2060 capable servers, use the CAPABILITY command and switch based on the 
> IMAP4 and IMAP4REV1 responses.

No, I wanted to differentiate between a working server and a broken
one. :-)

> As for broken servers, yell at the server vendor. Don't promote
> broken software by special casing in the client. Instead, make the
> client robust in the face of unexpected behaviour.

Yup. In this case, I think nnimap handles the situation the best way
it can (always trusting the server data), so we should just forward
the problem to the server vendor.

On the other hand, I think adding code to a client to detect a buggy
server and tell the user something about the situation would be
nice. Perhaps one could separate this into a tool that collect the
server bugs that we've encountered and run some checks against a
server. This could be useful, it could do a much better work than a
client would anyway.

/s