MBOX-Line: From arnt at gulbrandsen.priv.no  Mon Jul 23 12:56:14 2007
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri Jun  8 12:34:40 2018
Subject: [Imap-protocol] Unordered FETCH replies
In-Reply-To: <alpine.WNT.0.999.0707230922120.3360@Shimo-Tomobiki.Panda.COM>
References: <1185164783.25618.157.camel@hurina>
	<SiUoOH/TOnCUwgNjSV1qDA.md5@libertango.oryx.com>
	<alpine.WNT.0.999.0707230922120.3360@Shimo-Tomobiki.Panda.COM>
Message-ID: <lKl3BX9eFTipzhOXC1HvGQ.md5@libertango.oryx.com>

Mark Crispin writes:
> On Mon, 23 Jul 2007, Arnt Gulbrandsen wrote:
>> Yes, and no breakage. Clients break on many things they should handle 
>> (try sending lowercase OK/NO/BAD ;) but that one seems fine.
>
> Which clients break on that?

I don't remember. Some bug tracking system may remember, but I've left 
the relevant company and no longer have access to that information.

> They and their vendors should be publicly humiliated.

It went like this:

A fool made OK/NO/BAD lowercase sometimes and got it released. One day 
later the first breaking client showed up. The fool saw that it was an 
open source client (mutt, as it happens), and submitted a very simple 
patch, and the patch was accepted at once. Over the next week, n more 
clients showed up.

I wish uw, cyrus or courier would send lowercase IMAP keywords to flush 
these bugs out.

Signed,
a fool

