Ah. Because this is more of a "status: already downloaded" flag that
anything else. Nobody wants to receive a message more than once, and in
fact I think it would be extremely confusing if a message was viewed in
IMAP and then marked new again. I *believe* that removes the \Seen flag.
This would cause the message to be downloaded again by any POP clients.

I'm still a bit leery of using what is otherwise a "system level" status
flag for information about the message status wrt the user.

Perhaps Roel had a strong reason for doing it this way?

Aaron


On Fri, 27 Jun 2003, Jesse Norell wrote:

>
> Hello,
>
>   I the pop3 server exclusively uses the status flag for message
> status, and the imap server uses all the *_flag flags for it's status
> settings (I'm not very familiar with IMAP, but I know it's much more
> complex than pop3) ... and maybe the status flag too, or maybe not,
> I don't know.  A message is new/unread at status 0 - when a pop3
> client retrieves the message, it becomes status 1 - when they delete
> it, it becomes status 2.  dbmail-maintenance of course changes from
> 2->3 and also removes status 3.  I'm not sure how much the imap server
> keeps the status flag updated (it uses status 2 for deleted, I'm
> sure); there's some overlap in the functionality/meaning of both
> mechanisms, but at a cursory glance, I don't see an better way right
> offhand (a pop3 message can only have one status, but it looks like
> an imap message can probably have combinations of flags set/unset).
>
>
> > What's STATUS_SEEN for? I had thought that seen was an imap flag in the
> > messages table... is it being used in a different meaning here, or is that
> > an actual inconsistency / duplication in the design?
> ...
> > > #define STATUS_NEW     0
> > > #define STATUS_SEEN    1
> > > #define STATUS_DELETE  2
> > > #define STATUS_PURGE   3
> > > #define STATUS_UNUSED  4
> > > #define STATUS_INSERT  5
> > > #define STATUS_ERROR   6
>
>
> --
> Jesse Norell
> jesse (at) kci.net
>
>
> _______________________________________________
> Dbmail-dev mailing list
> [email protected]
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

Reply via email to