- Lots of fixes for mmap_disable = yes. It finally seems to be working pretty well.
- POP3 idle timeouts changed to 10min
I just wrote a simple stress test tool for IMAP and I've had one for POP3 for some months. The IMAP stress test was very helpful in finding out the bugs I fixed today. If anyone wants to try them, they're in: http://dovecot.org/tools/
Timo Sirainen wrote:
- Lots of fixes for mmap_disable = yes. It finally seems to be working pretty well.
- POP3 idle timeouts changed to 10min
Still no happiness on the dovecot-auth front with secure login (running SuSE Linux Enterprise 9.0, FWIW):
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x08053e6a in mech_cram_md5_auth_continue (auth_request=0x8095d78,
data=0x80780b0 "testing@example.com 11d39375ef6a105f19cea2442eaaa09c",
data_size=52, callback=0x8075134
Plaintext login works fine (so it probably isn't anything in the configuration file or user database setup).
I'm very motivated to get this fixed, since I am in the final stages of setting up a new mail server and would like to use Dovecot 1.0 instead of 0.99.something. This machine is not in production use, so I can offer full support for debugging this problem (up to and including giving you a local access for testing).
Please let me know if there is anything at all I can do to assist in fixing this problem...
John
-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747
On 5.12.2004, at 13:31, John Peacock wrote:
Timo Sirainen wrote:
- Lots of fixes for mmap_disable = yes. It finally seems to be working pretty well.
- POP3 idle timeouts changed to 10min
Still no happiness on the dovecot-auth front with secure login (running SuSE Linux Enterprise 9.0, FWIW):
Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () #1 0x08053e6a in mech_cram_md5_auth_continue (auth_request=0x8095d78, data=0x80780b0 "testing@example.com 11d39375ef6a105f19cea2442eaaa09c", data_size=52, callback=0x8075134
) at mech-cram-md5.c:145
This happens because you are using a passdb that doesn't work with anything else than plaintext (pam, passwd, shadow, etc.). Dovecot was actually supposed to be checking this and failing at startup but looks like I had broken the check at some point and instead it now just crashes.
Timo Sirainen wrote:
This happens because you are using a passdb that doesn't work with anything else than plaintext (pam, passwd, shadow, etc.). Dovecot was actually supposed to be checking this and failing at startup but looks like I had broken the check at some point and instead it now just crashes.
That makes complete sense, now that you mention it. If I want to use a non-plaintext login, I'll have to use the SSL layer then (which I'll start testing now that I know this).
Thanks
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
Timo Sirainen wrote:
This happens because you are using a passdb that doesn't work with anything else than plaintext (pam, passwd, shadow, etc.). Dovecot was actually supposed to be checking this and failing at startup but looks like I had broken the check at some point and instead it now just crashes.
Actually, now that you mention this, it _is_ possible to enable vpopmail to work with cram-md5, but only if you are running vpopmail with pw_clear_passwd set (which is what they recommend for larger sites). I'll take a look at the code and see about implementing that...
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
I still got the following when trying to move a message from one folder to another with TB 1.0rc. I can't move the message and my log are full of this error: Dec 5 17:40:38 aster dovecot: child 22746 (imap) killed with signal 11
Please tell if you need any more details.
Regards,
Nico Aime la vérité, mais pardonne à l'erreur. -+- Voltaire -+-
On 5.12.2004, at 19:04, Nicolas STRANSKY wrote:
I still got the following when trying to move a message from one folder to another with TB 1.0rc. I can't move the message and my log are full of this error: Dec 5 17:40:38 aster dovecot: child 22746 (imap) killed with signal 11
Is the source folder in IMAP server or local? I couldn't reproduce it easily, so gdb backtrace would be useful. http://dovecot.org/bugreport.html
Le 12/05/2004 06:35 PM, Timo Sirainen a écrit :
On 5.12.2004, at 19:04, Nicolas STRANSKY wrote:
I still got the following when trying to move a message from one folder to another with TB 1.0rc. I can't move the message and my log are full of this error: Dec 5 17:40:38 aster dovecot: child 22746 (imap) killed with signal 11
Is the source folder in IMAP server or local? I couldn't reproduce it easily, so gdb backtrace would be useful. http://dovecot.org/bugreport.html
The source folder is on IMAP server: I'm trying to move a message from one folder to another, in the same IMAP tree. I'll manage to get a backtrace.
-- Nico Ma femme et moi, nous nous entendons parfaitement : je n'essaie pas de diriger sa vie et je n'essaie pas de diriger la mienne
participants (3)
-
John Peacock
-
Nicolas STRANSKY
-
Timo Sirainen