35 lines
1.5 KiB
Plaintext
35 lines
1.5 KiB
Plaintext
MBOX-Line: From daboo at isamet.com Mon Nov 28 10:51:03 2005
|
|
To: imap-protocol@u.washington.edu
|
|
From: Cyrus Daboo <daboo@isamet.com>
|
|
Date: Fri Jun 8 12:34:36 2018
|
|
Subject: [Imap-protocol] Re: IMAP capability for maximum APPEND message size?
|
|
In-Reply-To: <Pine.OSX.4.64.0511281018540.562@pangtzu.panda.com>
|
|
References: <Pine.OSX.4.64.0511231556030.533@pangtzu.panda.com>
|
|
<1132831193.14231.285.camel@localhost.localdomain>
|
|
<Pine.OSX.4.64.0511240618280.533@pangtzu.panda.com>
|
|
<1132853918.6797.13.camel@hurina>
|
|
<Pine.OSX.4.64.0511281018540.562@pangtzu.panda.com>
|
|
Message-ID: <8E4E069D3416C28B7F5E166C@ninevah.local>
|
|
|
|
Hi Mark,
|
|
|
|
--On November 28, 2005 10:40:04 AM -0800 Mark Crispin
|
|
<mrc@cac.washington.edu> wrote:
|
|
|
|
> If a server establishes a limit for this reason, the client should have a
|
|
> way of knowing about this limit. Right now, the client would just get an
|
|
> error message and not know the reason.
|
|
|
|
Well this begs for better error reporting as much as anything else. The
|
|
MAXAPPEND capability does not guarantee that a client can append up to that
|
|
amount without error, all it guarantees is that an attempt to store more
|
|
than that will fail. i.e. a client still has to cope with APPEND failures
|
|
even with MAXAPPEND. (e.g. the temp store in your example might be shared
|
|
by multiple server sessions so if several people are trying to upload at
|
|
the same time the maximum available may be some fraction of the temp store
|
|
space, so a transient 'come back later' error may be appropriate).
|
|
|
|
--
|
|
Cyrus Daboo
|
|
|