It's been a problem for TWIG for forever. I was never quite sure why all messages were \Recent, figured it was a 1.2 bug and just turned off the Recent Messages status in TWIG. I am glad that it's been identified and will be resolved in 2.1, though!
Let's not block 2.0 on this. If it can be fixed cleanly in a point release, well, that's what point releases are for ;-) Aaron Paul J Stevens <[EMAIL PROTECTED]> said: > Why? > > Even though it does break rfc compliance, nobody noticed this until you > reported it. It's not like this will > break functionality. No major clients have trouble with the recent flag being > set on all messages, they simply > ignore it and follow their own cache. Do you have any experiences to the > contrary? > > Bug 97 will be fixed in the 2.1 codebase. Fixing it is not trivial by far, > the best way to do it still has to > be decided upon. So it's a no-go for 2.0. > > > Alessandro Magnolo wrote: >> On Tue, 12 Oct 2004 17:04:30 +0200, Ilja Booij <[EMAIL PROTECTED]> wrote: >> >>>There isn't a specific date yet... But: >>> >>>What bugs in the bugtracker are showstoppers? >> >> >> IMHO, bug #97 should be resolved before releasing 2.0. >> _______________________________________________ >> Dbmail-dev mailing list >> [email protected] >> http://twister.fastxs.net/mailman/listinfo/dbmail-dev >> > > > -- > ________________________________________________________________ > Paul Stevens mailto:[EMAIL PROTECTED] > NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] > The Netherlands________________________________http://www.nfg.nl > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > --
