|
cyrus denies login and reports "no mechanism available" in logs
Pardon me if this is an easy fix. Mail is the one thing in linux (from a server stand point) that has me more frustrated than ever.
I have Cyrus 2.2.3 and Postfix 2.1.1 installed. The current problem I have is actually with Cyrus and authentication.
My setup requires virtual domains, but I don't want to authenticate to system users - I'm going for simplicity. So, after googling around, I decided the 'sasldb' was the route to go. In my imapd.conf, I changed 'sasl_pwcheck_method' from 'saslauthd' to 'sasldb'. This doesn't work: the log (/var/log/messages) indicates that there is "no mechanism available" and the login fails.
I can get the authentication to work if I set 'sasl_pwcheck_method' to 'saslauthd' which uses pam by default, and set pam to authenticate imap via unix/console logins. That, however, won't work for our setup. I can't have console users for every email account.
I have a 'sasldb2' file in the /etc directory. I can use the 'saslpasswd2' command to add users. I can also use the 'sasldblistusers2' command, and the users show up properly. Unfortunately, cyrus isn't looking at this file. I even tried setting 'sasl_pw_check_method' to 'sasldb2' but same results as before: "no mechanism available."
I did try sending logins through saslauthd, and set pam to use pam_mysql. Well, that doesn't work because this distro doesn't include pam_mysql, and I don't dare mess too much with pam... I really don't want to mess the system up!
If I type 'saslauthd -v' I get: "authentication mechanisms: getpwent kerberos5 pam rimap shadow". I don't know what getpwent is, but I know what the others are, and I don't think they would work for what I'm doing. I have a few domains (a total of 4) I host mail for, and I only have 20 or so workstations, so I'm not looking for a highly scalable enterprise setup.
Any suggestions?
|