Seiji T wrote: > Paul, > > Here is the report on the downgrade but before that ... > > On 9/2/05, Paul J Stevens <[EMAIL PROTECTED]> wrote: > >>Dbmail at present isn't very good at sending unilateral server data. If >>clientA deletes messages from a mailbox which clientB also has selected, >>dbmail should sent a notification to clientB. Currently this doesn't happen. > > > Is this planned to be fixed?
That is not on the timeline for 2.2. 2.2 is mainly aimed at imap fetch/search performance which required a complete removal of the home-grown mime-parser, addition of separate header tables, and a complete restructuring of the message handing code for both insertion and retrieval. All that is pretty much done by now, and I'm mostly working on testing different clients to flush out imap bugs, cleaning up the codebase as a whole, and speeding up fetch/search. Redesigning the basic server design will be one of the major goals for 2.4. And a redesign of the server is what is required to handle this kind of situation. >>>BTW, will it be a problem if I go from 2.1.2 -> 2.0.6 -> 2.1.x ? >> >>Nope. You just need to run dbmail-util -ay after upgrading from 2.0 to >>2.1 so all the header tables get filled. > > > I've recently downgraded from 2.1.2 to 2.0.7 and it seems that the > MIME decode problem seem to have went away. (I've found out that > dbmail 2.1.* has not only a S/MIME problem but with other MIME emails > also.) 2.1.2 still contained a lot of the old mime-parser. I'm putting the finishing touches on the code before releasing 2.1.3. That will be the first release based purely on gmime. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
