cyrus-imapd howto

[Roger Grosswiler]

I updated from FC1 to FC2, it was no problem at all. So i assume:

- you authenticate via PAM to shadow (linux)-accounts
- you will use saslauthd for this.

I described once a short workaround for FC2-Test3 that worked well. So try out and let me know if this works. You find
this workaround here:

1)make sure, your saslauthd is correct configured: /etc/sysconfig/saslauthd should look somehow like this:

[roger at link sysconfig]$ more saslauthd
# To read about how postfix uses saslauthd read this:
# /usr/share/doc/postfix-*/README-Postfix-SASL-RedHat.txt
#
# To see a list of authentication mechanisms supported by saslauthd execute this command
# /usr/sbin/saslauthd -v
#
# Default to pam
MECH=pam
#MECH=shadow
[roger at link sysconfig]$

then, make sure your saslauthd is running, check with ps -ef | grep saslauthd: if this is what your seeing, restart
saslauthd with /sbin/service saslauthd restart. otherwise start it with /sbin/service saslauthd start

[roger at link sysconfig]$ ps -ef | grep saslauthd
root      2320     1  0 Jun04 ?        00:00:01 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root      2326  2320  0 Jun04 ?        00:00:02 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root      2332  2320  0 Jun04 ?        00:00:01 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root      2333  2320  0 Jun04 ?        00:00:01 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
root      2334  2320  0 Jun04 ?        00:00:01 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
roger    32104 32075  0 09:39 pts/23   00:00:00 grep saslauthd


in /etc, check your imapd.conf, that the following lines look somewhat like this:

sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN

restart your cyrus-imapd server. You can easily check with telnet localhost imap. Your cyrus-imapd should answer:

[roger at link etc]$ telnet localhost imap
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK link Cyrus IMAP4 v2.2.3-Red Hat 2.2.3-11 server ready

so, it's just your server responding, now have a look for the login. do:

a01 login username "password"

(btw. the "" where the password is in between are needed...)

thats what you should get back after you pressed enter...

a01 OK User logged in


voilà, if you are so far, you can connect and authenticate. finally, do a02 logout to terminate the session correctly
and try via a usual e-mail-client.

HTH, let us know if its working...
Roger