Marc Dirix wrote: > because all the "good" effort is pointed to creating a new stable 2.2. > > Probably the bugfix was done after the last stable 2.0.10 release. > > As paul said, please try 2.1.6 it has many new features, as wel as many > old features reimplemented better.
Well actually, iirc this particular fix was done pretty early on, possibly even before 2.1.0. But even then, the changes compared to branch_2_0 were massive! The main reason for branch_2_0 was to allow me to merge my first big fix of the imap code, and it was that re-organisation of the imap code that allowed me to fix this particular problem in the first place. Fixing problems like the 'recent' bug in the 2.0 codebase is a painful affair at best, and best done properly; ergo 2.1. Bugfixes for 2.0 are only done if it concerns critical bugs, or regressions. In this case it's neither. This problem has always existed in dbmail up until 2.0.10. If it didnt arise in imp-3/dbmail-1 it is because imp3 didn't see it, not because dbmail-1 properly cleared the recent flag. Jacques, I will gladly fix any problem you might encounter while rolling out 2.1.6 or svn-trunk. But fixing this in 2.0 is not an option. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
