Hi,

Is anybody else seen this?: new messages arrive with \Seen flag set.

On a Solaris 9, uw imap-2006 server, I have in ~/INBOX/.mixstatus
registers like this:

:00000c7e:00000000:0012:450f14da:
:00000c7f:00000000:0011:450f1148:

I changed manually the flags on the first message to \Deleted and not
\Seen, just to see if flags are being updated, but new messages arrive
with the flags shown on the last message, which has \Seen set (the last
one in 0011) and is wrong.

A snoop dump may be interesting (first message arrival, before I
changed flags):
=========================
Server -> Client IMAP R port=1292 * 3198 EXISTS\r\n* 10

0: 2a20 3331 3938 2045 5849 5354 530d 0a2a * 3198
EXISTS..*
16: 2031 3020 5245 4345 4e54 0d0a 2a20 4f4b 10 RECENT..*
OK
32: 2054 696d 656f 7574 2069 6e20 3330 206d Timeout in 30
m
48: 696e 7574 6573 0d0a inutes..

Client -> Server IMAP C port=1292 DONE\r\n

0: 444f 4e45 0d0a DONE..

Server -> Client IMAP R port=1292 qoah OK IDLE complet

0: 716f 6168 204f 4b20 4944 4c45 2063 6f6d qoah OK IDLE
com
16: 706c 6574 6564 0d0a pleted..

Client -> Server IMAP C port=1292 twi4 UID FETCH 3198:

0: 7477 6934 2055 4944 2046 4554 4348 2033 twi4 UID FETCH
3
16: 3139 383a 2a20 2855 4944 2046 4c41 4753 198:* (UID
FLAGS
32: 2052 4643 3832 322e 5349 5a45 2042 4f44 RFC822.SIZE
BOD
48: 592e 5045 454b 5b48 4541 4445 525d 2049 Y.PEEK[HEADER]
I
64: 4e54 4552 4e41 4c44 4154 4529 0d0a NTERNALDATE)..

Server -> Client IMAP R port=1292 * 3198 FETCH (UID 31

0: 2a20 3331 3938 2046 4554 4348 2028 5549 * 3198 FETCH
(UI
16: 4420 3331 3938 2046 4c41 4753 2028 5c52 D 3198 FLAGS
(\R
32: 6563 656e 7420 5c53 6565 6e29 2052 4643 ecent \Seen)
RFC
48: 3832 322e 5349 5a45 2031 3532 3120 424f 822.SIZE 1521
BO
64: 4459 5b48 4541 4445 525d 207b 3134 3839 DY[HEADER]
{1489
=========================
--
René Berber

On Mon, 18 Sep 2006, Rene Berber wrote:
> Is anybody else seen this?: new messages arrive with \Seen flag set.

You're the first person to report this.

> I changed manually the flags on the first message to \Deleted and not
> \Seen, just to see if flags are being updated, but new messages arrive
> with the flags shown on the last message, which has \Seen set (the last
> one in 0011) and is wrong.

How are messages delivered? Do you use tmail/dmail?

If messages are delivered to the spool file in traditional UNIX format,
and then moved into the mix mailbox, the latest imap-2006a development
tarball may fix the problem.

-- Mark --

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

Mark Crispin wrote:

> On Mon, 18 Sep 2006, Rene Berber wrote:
> > Is anybody else seen this?: new messages arrive with \Seen flag set.
>
> You're the first person to report this.
>
> > I changed manually the flags on the first message to \Deleted and not
> > \Seen, just to see if flags are being updated, but new messages arrive
> > with the flags shown on the last message, which has \Seen set (the last
> > one in 0011) and is wrong.
>
> How are messages delivered? Do you use tmail/dmail?

No dmail/tmail, just sendmail to the spool and imapd to the user's
mailbox.

> If messages are delivered to the spool file in traditional UNIX format,
> and then moved into the mix mailbox, the latest imap-2006a development
> tarball may fix the problem.

OK, I will try that next.

Thanks.
--
René Berber

Mark Crispin wrote:
[snip]
> If messages are delivered to the spool file in traditional UNIX format,
> and then moved into the mix mailbox, the latest imap-2006a development
> tarball may fix the problem.

Yes, it fixes the problem, thanks.

A note: There's something odd with 2006a and command noop:

a007 noop
* 3219 EXISTS
* 3 RECENT
a007 OK Invalid flag: Ș
a008 noop
a008 OK NOOP completed
a009 noop
* 3220 EXISTS
* 4 RECENT
a009 OK Invalid flag: Ș)
a010 noop
a010 OK NOOP completed
a011 fetch 3220 (flags)
* 3220 FETCH (FLAGS (\Recent))
a011 OK FETCH completed

That last message was just sent, so there is no \Seen flag set anymore.
But on some of the NOOP responses there is that "Invalid flag:
<garbage>", at first I tought I had hit a key by accident and the
garbage was just the ESC-] or whatever, but it repeats every other NOOP
with slightly different garbage, seems like an uninitialized variable
to me.

Regards.
--
René Berber

On Mon, 18 Sep 2006, Ren$Bi(B Berber wrote:
> But on some of the NOOP responses there is that "Invalid flag:
> <garbage>"

Please try the latest imap-2006a development snapshot. This should
resolve that issue.

I do not recommend production operation with messages being copied from
the spool file. Although the mix driver will do copying from the spool
file, it does not try to do it efficiently. If you use mix, you should
install tmail as described in the tmail man page (or use dmail from
procmail).

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

Mark Crispin wrote:

> On Mon, 18 Sep 2006, René Berber wrote:
> > But on some of the NOOP responses there is that "Invalid flag:
> > <garbage>"
>
> Please try the latest imap-2006a development snapshot. This should
> resolve that issue.

OK, thanks.

> I do not recommend production operation with messages being copied from
> the spool file. Although the mix driver will do copying from the spool
> file, it does not try to do it efficiently. If you use mix, you should
> install tmail as described in the tmail man page (or use dmail from
> procmail).

I'll look into this. Thanks for the recommendation.
--
René Berber