MBOX-Line: From tss at iki.fi  Mon Nov 28 12:09:07 2005
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
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.0511281140040.562@pangtzu.panda.com>
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>
	<Pine.OSX.4.64.0511281140040.562@pangtzu.panda.com>
Message-ID: <1133208547.3403.49.camel@hurina>

On Mon, 2005-11-28 at 11:41 -0800, Mark Crispin wrote:
> 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?

Sure, as long as the per-user capabilities actually get picked up by
clients.

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

Yes, accept the new capabilities in [CAPABILITY ..] if server sends
them.

I'd like to have only STARTTLS and AUTH= capabilities before user has
logged in, and the rest only after login. Unfortunately most clients
just ignore all the other capabilities than the one they requested
before logging in. But even just being able to add/remove capabilities
based on per-user settings with some commonly used clients would be
nice..

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20051128/d6454923/attachment.sig>
