All it means is that if you receive an unsolicited CAPABILITY command, you need to update your cache.
I would think that you should be making your CAPABILITY decisions close to the point of use - in other words, you'd make the decision to use MULTIAPPEND or APPEND at the time you were copying messages to the server, and not when you connected to the server. Caveat: I am not a client author, I am not fully conversant with the issues for clients :) Larry Osterman -----Original Message----- From: Grant Baillie [mailto:[EMAIL PROTECTED]] Sent: Friday, March 29, 2002 10:22 AM To: Mark Crispin Cc: [EMAIL PROTECTED] Subject: Re: Changing CAPABILITY after LOGIN? On Thursday, Mar 28, 2002, at 20:06 US/Pacific, Mark Crispin wrote: > On Thu, 28 Mar 2002, Grant Baillie wrote: >> I recently ran across an IMAP server which advertises several extra >> capabilities after you've successfully issued a LOGIN. > > The short answer to your question is that the world has changed. > > The slightly longer answer is that the introduction of TLS and a better > understanding of SASL necessitated a change to the "capabilities don't > change" policy. > > Consequently, clients can not assume that capabilities won't change. Well, I understand that they need to change sometimes. But leaving open the option of their changing any time, without notice, seems wrong. Otherwise, how can clients be sure that it's OK to cache them? In principle (if not in practice), they'd have to issue CAPABILITY before issuing any extension command, for example. ________________________________________ Grant Baillie Mac OS X Mail - Apple Computer, Inc. ________________________________________
