http://dovecot.org/test/ Sorry :) The last fix I made a few minutes before test54 release didn't turn out to be exactly correct. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20041130/daf0de9d/attachment-0001.bin>
:-) maybe now people understand, why i don't like to "test" test releases on a productiopn server.... ;-) Regards G?tz Timo Sirainen wrote:> http://dovecot.org/test/ > > Sorry :) The last fix I made a few minutes before test54 release didn't > turn out to be exactly correct.-- G?tz Reinicke IT Koordinator - IT OfficeNet Tel. +49 (0) 7141 - 969 420 Fax +49 (0) 7141 - 969 55 420 goetz.reinicke at filmakademie.de Filmakademie Baden-W?rttemberg Mathildenstr. 20 71638 Ludwigsburg www.filmakademie.de
Timo Sirainen wrote:> http://dovecot.org/test/ > > Sorry :) The last fix I made a few minutes before test54 release didn't > turn out to be exactly correct.Still doesn't fix the SIG11 problem with logging in using secure methods (plaintext login works fine). How can I get dovecot-auth to dump a core so I can backtrace this? Clearly dovecot-auth can be run standalone, but I don't see documentation for testing it outside of running it within dovecot itself... John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748