50 lines
2.0 KiB
Plaintext
50 lines
2.0 KiB
Plaintext
MBOX-Line: From slusarz at curecanti.org Wed Mar 27 14:07:03 2013
|
|
To: imap-protocol@u.washington.edu
|
|
From: Michael M Slusarz <slusarz@curecanti.org>
|
|
Date: Fri Jun 8 12:34:50 2018
|
|
Subject: [Imap-protocol] Working around the evils of LITERAL+
|
|
In-Reply-To: <32457081-EE35-4B27-892D-A059757A1B77@iki.fi>
|
|
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>
|
|
<32457081-EE35-4B27-892D-A059757A1B77@iki.fi>
|
|
Message-ID: <20130327150703.Horde.pQwnqjTHsljVrQcznTh2Rw6@bigworm.curecanti.org>
|
|
|
|
Quoting Timo Sirainen <tss@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.
|
|
|
|
Isn't MAXSIZE a METADATA specific response? (Maybe you were just using
|
|
as a placeholder example...)
|
|
|
|
Also... I believe this has come up before but ALERTs aren't useful for
|
|
providing directed feedback about an action. Alerts only need to be
|
|
displayed to the user - but there is no requirement how/when this
|
|
would happen. In the above example, there is no indication that the
|
|
ALERT is somehow tied to the actual APPEND action. So when a client
|
|
eventually displays the alert to the user, it could be completely out
|
|
of context to the activity of sending a message and might confuse the
|
|
heck out of the end user.
|
|
|
|
michael
|
|
|
|
|