MBOX-Line: From tss at iki.fi  Wed Mar 27 13:47:21 2013
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:50 2018
Subject: [Imap-protocol] Working around the evils of LITERAL+
In-Reply-To: <CABa8R6vHmnOsKMsCfNZJoj_GHO=4EAKn_jNY2WvRLrJRKsYOJw@mail.gmail.com>
References: <CABa8R6s3rK5JkXBtV7RWbav9T2GBCg+pw-aWd9=5Szv3ocDS_g@mail.gmail.com>
	<DA4AB101-1D7E-466C-8DA1-6234EB098FF8@iki.fi>
	<CABa8R6v5dApFF6Quwzrb0=XethrwCU0EQT6t3XtLVK6VRoYhmA@mail.gmail.com>
	<B2E07E1B-80E9-4FFB-8518-B4CDC344639E@isode.com>
	<20130327140405.Horde.xVBCOb0icPn4imuUgPQweQ2@bigworm.curecanti.org>
	<CABa8R6vHmnOsKMsCfNZJoj_GHO=4EAKn_jNY2WvRLrJRKsYOJw@mail.gmail.com>
Message-ID: <32457081-EE35-4B27-892D-A059757A1B77@iki.fi>

On 27.3.2013, at 22.33, Brandon Long <blong@google.com> wrote:

> a append inbox {60000000}
> a BAD [ALERT] Message too large. http://support.google.com/mail/bin/answer.py?answer=8770

NO, not BAD. Client didn't do anything syntactically wrong.

> Which goes to that other issue between the updated responses codes not being backward compatible with ALERT... which I guess I can just ignore since most clients ignore ALERT anyways.

* NO [ALERT] Message too large. http://...
a NO [MAXSIZE 123456] Too large.

Or vice versa.


