On Tue, 2003-07-15 at 21:49, Tim Showalter wrote:
> Larry Osterman wrote:
>
> > The server respond with:
> > S: * 1 FLAGS (\Seen)
> > S: 1 OK Fetch completed
>
> > As opposed to failing the STORE.
>
> Cyrus will fail the store. This has always been its behavior (as far as
> I can remember). M
Larry Osterman wrote:
The server respond with:
S: * 1 FLAGS (\Seen)
S: 1 OK Fetch completed
As opposed to failing the STORE.
Cyrus will fail the store. This has always been its behavior (as far as
I can remember). Mirapoint's server behaves the same way, and we do
have OE users. (I'm not one
r, so I'm not sure
which client it was that depended on the behavior.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
> Behalf Of Timo Sirainen
> Sent: Tuesday, July 15, 2003 3:14 AM
> To: [EMAIL PROTECTED]
> Subject: RE: EXAMINE, SELECT,
On Tue, 2003-07-15 at 01:34, Larry Osterman wrote:
> There are clients out there (I believe
> PINE is one of them, I know that Outlook Express is another) that
> require flags updates on read-only mailboxes, and if you carefully read
> the spec's language on READ-ONLY and FLAGS, it's clear that the
On Mon, 14 Jul 2003, Tim Showalter wrote:
> > As a result of the above, "FETCH seq (FLAGS BODY[] FLAGS)" is equivalent
> > to "FETCH seq BODY[]".
> This ought to be the case, but it isn't, because it doesn't consolidate
> and it doesn't notify. The FETCH response, in fact, is of the form
> "FLAGS
Mark Crispin wrote:
(2) "FETCH [seq] (FLAGS BODY[] FLAGS)" returns a FETCH response with the
obvious three items in that order. The first FLAGS is (). The
second flags is (\Seen).
This is alright, provided that \Seen is in fact a session-only flag.
It isn't, and the modification is permenan
On Mon, 14 Jul 2003, Tim Showalter wrote:
> (1) The \Seen flag was changed by "FETCH [seq] (FLAGS BODY[]
> INTERNALDATE)" while the mailbox was being EXAMINEd. \Seen is not
> advertised in PERMANENTFLAGS in EXAMINE, but the change appears
> permanent.
>From RFC 3501, 6.3.2:
The
#3 is clearly bogus.
I'd actually argue that #2 is the correct behavior. When the first
FLAGS response is generated, the message isn't yet \Seen. When the
FETCH is executed, the message is marked as being \Seen, and an untagged
FLAGS response is queued. I can't explain why they don't generate a
