After banging my head against the wall all night, I found what looks like a
bug in 2.0.12. If you misspell 'partition-default' as 'partition-defualt',
imapd segfaults when trying to connect. I've tracked it to config_init() in
imap/config.c and probably fatal() in imapd.c, but my limited linux
debugging knowledge stopped me from making any more progress. Can anyone
reproduce this?


Unfortunately, I still cannot login to the imap server. Can someone offer me
some advice? On connecting, I see:
[cyrus@jedi jimh]$ imtest -m plain localhost
C: C01 CAPABILITY
S: * OK jedi Cyrus IMAP4 v2.0.12 server ready
S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID
NO_ATOMIC_RENAME UNSELECT MULTIAPPEND SORT THREAD=ORDEREDSUBJECT
THREAD=REFERENCES IDLE
S: C01 OK Completed
Please enter your password:
C: A01 AUTHENTICATE PLAIN
S: A01 NO no mechanism available
Authentication failed. generic failure
Security strength factor: 0
. logout
* BYE LOGOUT received
. OK Completed
Connection closed.


auth.log shows no record of my login attempt and imapd.log shows imapd
starting and exiting normally. I obviously don't have any authentication
mechanisms listed, where have I gone wrong? User cyrus is in the sasl
database (PLAIN, DIGEST, and CRAM are listed for the user when I run
sasldblistusers as the user cyrus). My sasl_pwcheck_method is sasldb, but it
also fails if I try passwd or PAM with a LOGIN mechanism specified for
imtest.

I've compiled cyrus with new compiles and installs of Berkeley DB 3.2.9 and
sasl 1.5.24 (not to mention two earlier versions of each). I'm using <gasp>
RedHat 7.0... I'd like to stick with it to avoid a reinstall, but if I have
to install a different dist, I'm willing.

Reply via email to