I've managed to get cyrus to work as a running imap server, but it's only good in plaintext right now. I'm a little concerned with this log message: PAM-warn: function=[pam_sm_authenticate] service=[imap] terminal=[<unknown>] user=[tallison] ruser=[<unknown>] rhost=[<unknown>] I guess I should be trying to find out what options I have for cyrus-imap authentication but the documentation doesn't go beyond, "You can use A, B, C, D, or E..." Well, thanks for the glossy brochure version but I'm still stuck on plaintext authentications... But I don't see anything that will let me create CRAM or DIGEST MD5 password files and reference them by cyrus. (BTW, which one is better, CRAM or DIGEST?) help?
Am Mittwoch, 22. Oktober 2003 02:18 schrieb Tom Allison:
I've managed to get cyrus to work as a running imap server, but it's only good in plaintext right now.
I'm a little concerned with this log message: PAM-warn: function=[pam_sm_authenticate] service=[imap] terminal=[<unknown>] user=[tallison] ruser=[<unknown>] rhost=[<unknown>]
In Suse, the default-configuration for Cyrus-IMAP is to use saslauthd, and saslauthd uses PAM.
I guess I should be trying to find out what options I have for cyrus-imap authentication but the documentation doesn't go beyond, "You can use A, B, C, D, or E..." Well, thanks for the glossy brochure version but I'm still stuck on plaintext authentications...
But I don't see anything that will let me create CRAM or DIGEST MD5 password files and reference them by cyrus.
saslauthd is bound to Plaintext-Mechs. If you want to use CRAM-MD5 or DIGEST-MD5 you have to configure sasldb.
(BTW, which one is better, CRAM or DIGEST?)
There is no really diffrence. Both are shared-secret-mechs. In my mind comes, that Mutt has problems with one of them. But at the moment i don't know which one it was. -- Andreas
participants (2)
-
Andreas Winkelmann
-
Tom Allison