RE: shared mailbox permanent flags?

[Pete Maclean]

Argh!  I have always had a serious misunderstanding about this then.  It 
seemed to me that the very fact that there is a response explicitly listing 
FLAGS applicable to the mailbox meant that a server was not required to 
support all of them.  Well, I stand corrected.  Thank you for the 
clarification, Mark.

Pete Maclean
At 05:54 PM 8/18/2004, Mark Crispin wrote:
On Wed, 18 Aug 2004, Pete Maclean wrote:
I think that either what you say is not quite correct or I am not 
understanding it right.  RFC 3501 gives an example of a FLAGS response 
that does not include all the system/built-in flags:
Example:    S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
\Recent is not included in the untagged FLAG response because it can not 
be used with STORE.  It is, however, mandatory to implement.

Note that difference between the "flag" and "flag-fetch" rules in the 
Formal Syntax.

In this case, \Recent is missing.  As I read the spec, if you do not 
include a particular system flag in this response, it means that you do 
not support it for the mailbox.
Nope.  Refer to section 7.2.6:
      [...] The flag parenthesized list identifies the flags (at a
      minimum, the system-defined flags) that are applicable for this
      mailbox.
Incidentally, some versions of my server do not support \Recent at all.
A server may choose never to return a lit \Recent flag, but it must 
otherwise implement it (e.g. the RECENT argument to SEARCH and STATUS).

-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.