A stupid but simple way to handle this might be to always set
recent_flag=0 in every query that updates the messages table.
The logic is that if the user is setting any flags on a message,
they've seen the message. I'm inclined to say that turning off recent
just because you have listed the mailbox, as some servers will do,
is more overhead than needed, although more technically correct.

So, db_set_msgflag, db_set_msgflag_range, db_movemsg, db_copymsg
should all set recent_flag=0 (pretty much anything with 'UPDATE messages')

Aaron


On Thu, 10 Apr 2003, Mark Smulders wrote:

> >From the IMAP4rev1 RFC (rfc 2060):
>
>         \Recent     Message is "recently" arrived in this mailbox.  This
>                     session is the first session to have been notified
>                     about this message; subsequent sessions will not see
>                     \Recent set for this message.  This flag can not be
>                     altered by the client.
>
>                     If it is not possible to determine whether or not
>                     this session is the first session to be notified
>                     about a message, then that message SHOULD be
>                     considered recent.
>
>                     If multiple connections have the same mailbox
>                     selected simultaneously, it is undefined which of
>                     these connections will see newly-arrives messages
>                     with \Recent set and which will see it without
>                     \Recent set.
>
>
> > -----Oorspronkelijk bericht-----
> > Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Chris Nolan
> > Verzonden: donderdag 10 april 2003 12:03
> > Aan: dbmail@dbmail.org
> > Onderwerp: Re: [Dbmail] Two DBMail bugs?
> >
> >
> > On the point of \Recent, what does the \Recent flag actually do?
> >
> > Interestingly, we use SquirrelMail at this DBMail site and it has
> > precisely no problem seeing new messages (as far as I can tell - in the
> > case that happened today, SquirrelMail correctly saw all messages when
> > Outlook Express didn't.)
> >
> > Chris
> >
> > Aaron Stone wrote:
> >
> > >On the topic of point 1, I reported a few weeks ago but got no response...
> > >that I see *every message* since I upgraded to 1.1 as \Recent. It looks
> > >like the only way to have a message not be \Recent is to flag is from my
> > >application. I don't think this is correct; all other IMAP servers I know
> > >of automatically handle removing \Recent if the message is \Seen or \Read.
> > >
> > >On point 2, I have heard rumors that this is being fixed?
> > >
> > >Aaron
> > >
> > >
> > >On Thu, 10 Apr 2003, Chris Nolan wrote:
> > >
> > >
> > >
> > >>Hi all,
> > >>
> > >>Since rolling out DBMail, I've noticed two possible bugs. These bugs may
> > >>simply be limited to when Outlook Express is used as the client, but
> > >>I've noticed similar behaviour to point 1 in Mozilla Mail 1.3
> > >>
> > >>1. Often, the mail client (OE or Mozilla Mail) will report that new mail
> > >>is in one's Inbox. However, the messages will not be pulled down,
> > >>regardless of what is tried (synchronising messages and/or headers,
> > >>restarting the client, clearing the local message cache, restarting
> > >>dbmail-imapd, changing status flags, restarting the mail client etc).
> > >>2. In OE, many messages have their Sender name surrounded by double
> > >>quotes (inverted commas to any other Australians who went through
> > >>primary school in the mid-late eighties). This is mostly cosmetic, but
> > >>it does break sorting on the client side, making the finding of messages
> > >>just a bit more difficult.
> > >>
> > >>If anyone wants to point me to the appropriate sections in the source
> > >>tree, I'll have a go at fixing these myself (They drill C into us real
> > >>good at uni!). Of course, I'll submit patches if successful.
> > >>
> > >>Chris
> > >>http://www.itoperations.com.au/dbmail.html
> > >>
> > >>_______________________________________________
> > >>Dbmail mailing list
> > >>Dbmail@dbmail.org
> > >>https://mailman.fastxs.nl/mailman/listinfo/dbmail
> > >>
> > >>
> > >>
> > >
> > >_______________________________________________
> > >Dbmail mailing list
> > >Dbmail@dbmail.org
> > >https://mailman.fastxs.nl/mailman/listinfo/dbmail
> > >
> > >
> >
> >
> > _______________________________________________
> > Dbmail mailing list
> > Dbmail@dbmail.org
> > https://mailman.fastxs.nl/mailman/listinfo/dbmail
> _______________________________________________
> Dbmail mailing list
> Dbmail@dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>

Reply via email to