mailing list archives

meli community discussions

⚠️ if something does not work as intended when interracting with the mailing lists,
reach out Github mirror Gitea repo @epilys:matrix.org

E-mail headers
From: Mark Crispin <mrc@Washington.EDU>
To: imap-protocol@u.washington.edu
Date: Fri, 08 Jun 2018 12:34:41 -0000
Message-ID: alpine.OSX.1.00.0801311803590.10877@pangtzu.panda.com permalink / raw / eml / mbox
In-Reply-To: 08Jan31.180102pst."58696"@synergy1.parc.xerox.com
References: fc.00802cf1026ac56600802cf1026ac566.26adfec@cciu.orgalpine.OSX.1.00.0801302244470.10877@pangtzu.panda.comfc.00802cf1026ae3b200802cf1026ac566.26b3de0@cciu.orgalpine.OSX.1.00.0801311231290.10877@pangtzu.panda.com08Jan31.180102pst."58696"@synergy1.parc.xerox.com
On Thu, 31 Jan 2008, Bill Janssen wrote:
> I'm curious about how the client knows if the server supports
> keywords.  Supposedly, it's by receiving a PERMANENTFLAGS response
> code containing \*, in response to some action, say SELECT of a
> mailbox.

Correct.

> So, if I just send [PERMANENTFLAGS] without a specific list
> of message flags, which means that "all flags can be changed
> permanently"

I don't know how you concluded that, but that is incorrect.  If you send 
PERMANENTFLAGS with an empty list, then there are no permanent flags and 
no keywords.

> , should the client assume keywords are supported?  Or is
> it only when \* is explicitly sent in the list of flags?

Given what I just said, do you agree that this question is moot?

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