MBOX-Line: From markrcrispin at panda.com  Thu Jan 29 15:04:28 2009
To: imap-protocol@u.washington.edu
From: Mark Crispin <markrcrispin@panda.com>
Date: Fri Jun  8 12:34:42 2018
Subject: [Imap-protocol] Re: SEARCH OR question
In-Reply-To: <4982284E.1000102@sun.com>
References: <4981FBC7.9040509@sun.com>
	<alpine.OSX.2.00.0901291151270.283@hsinghsing.panda.com>
	<4982284E.1000102@sun.com>
Message-ID: <alpine.OSX.2.00.0901291453310.283@hsinghsing.panda.com>

On Thu, 29 Jan 2009, Bill Shannon wrote:
> Yes, based on the trace from the customer, it's:
> * OK Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 (myServer.org) ready.

Bummer.

> Perhaps the bug is due to the particular terms or keys the customer is using.
> He's used the same terms with success on other servers, so the problem seems
> to be specific to Exchange.

Sadly, newer versions of Exchange are worse, and aren't the only offenders 
among broken IMAP server implementations.

The overall direction of the market seems to be not to use these 
fancy-schmancy features that "standard clients" (read: Outlook) doesn't 
use.  It gets quite depressing receiving bug reports for your client that 
feature the phrase "Outlook doesn't have this problem".

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

