MBOX-Line: From mrc at CAC.Washington.EDU  Mon Nov 28 11:41:22 2005
To: imap-protocol@u.washington.edu
From: Mark Crispin <mrc@CAC.Washington.EDU>
Date: Fri Jun  8 12:34:36 2018
Subject: [Imap-protocol] Re: IMAP capability for maximum APPEND message
	size?
In-Reply-To: <000d01c5f452$541ab820$6301a8c0@xms.co.za>
References: <Pine.OSX.4.64.0511231556030.533@pangtzu.panda.com><438B4AB4.2020102@sun.com>
	<FD53C5ED7A77BE8EADAC9A88@ninevah.local><Pine.OSX.4.64.0511281048490.562@pangtzu.panda.com>
	<000d01c5f452$541ab820$6301a8c0@xms.co.za>
Message-ID: <Pine.OSX.4.64.0511281140040.562@pangtzu.panda.com>

On Mon, 28 Nov 2005, Timo Sirainen wrote:
> If it's going into capabilities, it should at least be a per-user limit,
> so clients would have to be able to parse the capability reply in
> LOGIN/AUTHENTICATE command's OK message.

Isn't per-user or systemwide a server implementation issue, as long as it 
shows up in capabilities?

> I don't think they're currently
> required to do that, and most probably don't do it. Actually I'd rather
> like to see that change regardless of MAXAPPEND..

Do what?  Parse capabilities in LOGIN/AUTHENTICATE?

I agree that clients should do that, or at least issue a new CAPABILITY 
command after authenticating.

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

