> > Yes, but starting with Glib 2.14: > http://library.gnome.org/devel/glib/stable/ix09.html > > Aaron > Thanks. INSTALL file needs to be updated with this as it indicates 2.8.
> > On Fri, Nov 14, 2008, Larry Low <[EMAIL PROTECTED]> said: > > > Is 'g_string_append_vprintf' supposed to be in Glib2? Using 2.12 but > it does not seem to be in there on CentOS 5. > > > > Oddly I was also having problems with libzdb as the PostgreSQL check > of PQprepare was segfaulting. I just bypassed the check so that I > could get it compiled. Need to look into it more. > > > >> Larry Low wrote: > >> > Do you consider the database schema pretty much set in stone? > >> > >> Pretty much, sure. No plans to change them on this end. > >> > >> > I'm considering beginning testing in my lab and looking forward to > >> testing if the expunging has been improved. > >> > >> O yeah! The imap code has been extensively stress-tested by both > >> myself, > >> and Jon using the dovecot imaptest tool on ubuntu/hardy and freebsd > on > >> both i386 and amd64. Imaptest does explicitly test for correct > expunge > >> response, among many other things. > >> > >> Dbmail-2.2 doesn't come close to imap compliance here, but the 2.3 > code > >> produces very few warnings or errors, and then *only* under very > high > >> concurrencies, like accessing one single account from around 100 > highly > >> active clients at the same time. > >> > >> If you find *any* imap problem, *please* let us know. dbmail-imapd > must > >> be fast, scalable and correct! > > > > Will do. Testing is limited to very few clients but the client in > question will generate any alarms if it gets in trouble. > > > >> > >> That said, some known issues deserve consideration. The pop3, lmtpd > and > >> managesieve daemons have had far less extensive live testing than > the > >> imapd. Though they were changed less drastically - still being > single > >> threaded - some regressions in the event codepath may still remain > >> hidden in the code. Valgrind sessions will probably unveil some > >> critters. > >> > >> So, for now, I would advise running dbmail daemons using > daemontools, > >> runit, or inittab, or some other keep-alive monitor. Some > unconfirmed > >> segfaults have been reported in lmtpd. > >> > >> -- > >> ________________________________________________________________ > >> Paul Stevens paul at nfg.nl > >> NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 > >> The Netherlands________________________________http://www.nfg.nl > >> _______________________________________________ > >> Dbmail-dev mailing list > >> Dbmail-dev@dbmail.org > >> http://twister.fastxs.net/mailman/listinfo/dbmail-dev > > _______________________________________________ > > Dbmail-dev mailing list > > Dbmail-dev@dbmail.org > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > > > > -- > > > > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
