[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-mailutils] Re: Wrong flag definition in maildir code?
From: |
Sergey Poznyakoff |
Subject: |
Re: [bug-mailutils] Re: Wrong flag definition in maildir code? |
Date: |
Thu, 03 Mar 2011 22:55:23 +0200 |
Kamil Jońca <address@hidden> ha escrit:
> Sergey Poznyakoff <address@hidden> writes:
>
> > Kamil Jońca <address@hidden> ha escrit:
> >
> >> Maybe I should ask different question: What is difference between
> >> #define MU_ATTRIBUTE_SEEN 0x10
> >> #define MU_ATTRIBUTE_READ 0x20
> >
> > MU_ATTRIBUTE_SEEN means that the user has already seen this message
> > *in the message list*, e.g. in the 'h' output in mailx, or as a result
> > of LIST command in POP3, etc. In other words, it means that the user
> > is aware of the existence of this message, but does not imply he has
> > ever attempted to read it.
>
> So, MU_ATTRIBUTE_READ corresponds to \Seen flag in IMAP protocol
Right.
> and (AFAIR,IMO etc) "S" maildir suffix.
MU_ATTRIBUTE_READ means the user has read the message, i.e. he has
accessed its headers and/or body in some way. The 'S' suffix, according
to [1], means "the user has viewed this message, though perhaps he
didn't read all the way through it". This looks pretty much the same
thing, indeed.
> MU_ATTRIBUTE_SEEN - has no equivalent suffix in maildir,
It looks so.
> and in IMAP
In IMAP, the absense of MU_ATTRIBUTE_SEEN is equivalent to \Recent, and
vice-versa: the absense of \Recent flag means MU_ATTRIBUTE_SEEN is
set.
Regards,
Sergey
[1] http://cr.yp.to/proto/maildir.html