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)

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. Incidentally, some versions of my server do not support \Recent at all.

Pete Maclean

At 05:09 PM 8/18/2004, Larry Osterman wrote:
You MUST support ALL the built-in flags on every mailbox.  You might not
be able to persist those flag settings, but you MUST support them on a
per-session basis.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of petite_abeille
Sent: Wednesday, August 18, 2004 2:00 PM
To: [EMAIL PROTECTED]
Subject: Re: shared mailbox permanent flags?

Hi Timo,

On Aug 18, 2004, at 22:37, Timo Sirainen wrote:

> FLAGS list shouldn't be empty. It should contain at least the system
> flags.

Ok. So FLAGS should always returns \Answered \Deleted \Draft \Flagged
\Recent and \Seen? Even if they are not applicable for such  mailbox?

>> But this doesn't seem to help :/
>
> Yep. I doubt there's a way to make it work many (if any) clients.

Sigh :/

PA.



Reply via email to