MBOX-Line: From brong at fastmail.fm  Sun Oct 23 01:04:49 2011
To: imap-protocol@u.washington.edu
From: Bron Gondwana <brong@fastmail.fm>
Date: Fri Jun  8 12:34:46 2018
Subject: [Imap-protocol] Apple's iCloud server non-compliant!
In-Reply-To: <CABa8R6sVubHKcdV0o_6YRSLOvgUS5MZ+rjOMGNYjNUTcR7bhYg@mail.gmail.com>
References: <alpine.OSX.2.00.1110221212460.29979@hsinghsing.panda.com>
	<727DCD4D-BA76-4EBA-A582-B0A6853F07BB@iki.fi>
	<20111022200153.GA3907@brong.net>
	<CABa8R6sVubHKcdV0o_6YRSLOvgUS5MZ+rjOMGNYjNUTcR7bhYg@mail.gmail.com>
Message-ID: <20111023080449.GA10954@brong.net>

On Sat, Oct 22, 2011 at 01:56:55PM -0700, Brandon Long wrote:
> I think we have only one deliberate break from the spec, and that's that we
> don't do substring searches.

I believe your envelopes are bogus too, and we had another issue which I
should see if I can dig up...

Oh, yeah:

======================
The bug is with gmail.

http://tools.ietf.org/html/rfc3501#section-4.3.1

  8-bit textual and binary mail is supported through the use of a
  [MIME-IMB] content transfer encoding.  IMAP4rev1 implementations MAY
  transmit 8-bit or multi-octet characters in literals, but SHOULD do
  so only when the [CHARSET] is identified.

Basically, they can transfer that as utf-8, but only if they send it as
a literal.  Just quoting the string is bogus.
======================

You send 8bit stuff inside quotes.

> I know there are other issues, like we sometimes don't get the size quite
> right (comes of storing the message with just LF line endings and having to
> convert to CRLF), but mostly we tend to bend the spec but not break them...
> matching the IMAP mailbox model with the gmail one is tough.

Yeah, that's a bit messy.  Any particular reason, other than saving a
few bytes?

> I tried running Timo's tests against gmail, but its pretty hard to debug
> failures, and the set of tests isn't quite wide or separable.  Its somewhere
> on the todo list to work that again.

Improving the tests would be nice too.  We have our own thing, cassandane,
which does a whole test harness for running multiple Cyrus instances and
testing things like replication and our "murder" clustering thing too.

> I would say that our biggest issue with IMAP is that the amount of resources
> required for some of the commands is really high, which is hard to optimize
> for or to fairly share resources.

body search is the real killer for us, everything else is pretty lightweight.

Bron.

