MBOX-Line: From mrc+imap at panda.com  Tue Feb 22 21:33:57 2011
To: imap-protocol@u.washington.edu
From: Mark Crispin <mrc+imap@panda.com>
Date: Fri Jun  8 12:34:45 2018
Subject: [Imap-protocol] detecting new messages
In-Reply-To: <2CA53ECF4094AB4D8BDC7C60A75B1C02110C0FBAB0@hawaii.shoretel.com>
References: <2CA53ECF4094AB4D8BDC7C60A75B1C02110BEAFC52@hawaii.shoretel.com>
	<5398C04A-99D8-47E5-ABB8-AE10B168F3C4@iki.fi>
	<alpine.OSX.2.00.1102171137330.782@hsinghsing.panda.com>
	<2CA53ECF4094AB4D8BDC7C60A75B1C02110C0FBAB0@hawaii.shoretel.com>
Message-ID: <alpine.OSX.2.00.1102222106050.791@hsinghsing.panda.com>

On Tue, 22 Feb 2011, Darren Croke wrote:
> Thanks for all the answers to my question. An interesting side
> note--Microsoft Exchange 2007 rejects * as an invalid message set...

Sadly, this is not at all surprising.

The IMAP-savvy Microsoft employees (you can look at the archives of this
mailing list) were pulled off Exchange years ago.  Their replacements are
unimaginably inferior kids.  The results speak for themselves.

Microsoft has no intention of fixing their broken implementation of IMAP.
They have said so, repeatedly.

You face an unpleasant choice: either you comply with IMAP, or you comply
with Microsoft.

If you comply with IMAP, you have to read the specification, and possibly
use an ABNF syntax parser to follow IMAP's at times overly-subtle syntax
rules.

If you comply with Microsoft, it's easy; just implement the small subset
of IMAP that Outlook uses.  If you have a server, send any old nonsense
for the rest of IMAP.  If anyone complains about your client, say "it
works fine with Exchange, therefore it's a bug in your server."  If anyone
complains about your server, just say "it works fine with Outlook,
therefore it's a bug in your client."

-- 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.

