-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 wouldn't it be better to release CVS current as 1.1rc1, and let us test it. this way we don't run into the silly things that happened to 1.0 :)
- -ben "Unix is user friendly, Its just picky about its friends." On Tue, 4 Feb 2003, Roel Rozendaal - IC&S wrote: > Hi all, > > from our point of view, dbmail 1.1 is needed as soon as possible since > the 1.0 release does not compile straight away and suffers from severe > pop-bugs. These problems seem to be solved now; we are planning to > release the current CVS as dbmail 1.1 next thursday. I would ask you > all for patches are available but have not yet been included in cvs. > Some key points from the top of my head: > > * automake > anyone has some working automake/autoconf patches for current CVS? > * separate authentication (LDAP) > has this been tested? is it ready for release? are patches available > to include auth_connect() calls? is it possible to disable the separte > authentication (such a waste to connect twice to the same database)? > * QUOTA imap extension > has testing been performed? does it work correcly with the internal > dbmail quotum system? does it consider > removed-but-not-yet-purged-in-maintenance messages (i.e. messages with > status < 2 should not count for the mailboxsize)? i will remove the > QUOTA keyword from the CAPABILITY string in case of any doubt.. > > i know, these are a lot of questions and probably i could find some > answers myself but we are real busy now :-( (but then again, life can't > always be as fun as dbmail coding - sometimes you just have to make > money :p) > > > > Met vriendelijke groet, > > > Roel Rozendaal > > > _________________________ > R.A. Rozendaal > ICT Manager > IC&S > T: +31 30 2322878 > F: +31 30 2322305 > www.ic-s.nl > > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+P+xcflzKmtpiQEMRAg9DAJwIIj7C3+zArDfYGxeEnzLGTOAv2QCgiM0R Ggbujn4m5l6fV6hVLs+qJgg= =gv3o -----END PGP SIGNATURE-----
