Marc Williams wrote:
On Mon, 2004-09-06 at 20:50, Marc Williams wrote:
On Mon, 2004-09-06 at 19:12, Alexander Dalloz wrote:
Am Di, den 07.09.2004 schrieb Marc Williams um 1:45: What is your /etc/imapd.conf content. Which AUTH MECHs do you use?
Thanks for responding Alexander. I look forward to your posts in the FC lists.
The entirety of my imapd.conf is as follows: [EMAIL PROTECTED] etc]# cat imapd.conf configdirectory: /var/lib/imap partition-default: /var/spool/imap admins: cyrus sievedir: /var/lib/imap/sieve sendmail: /usr/sbin/sendmail #hashimapspool: true sasl_pwcheck_method: saslauthd sasl_mech_list: pam tls_cert_file: /usr/share/ssl/certs/cyrus-imapd.pem tls_key_file: /usr/share/ssl/certs/cyrus-imapd.pem
It's *almost* stock. As I recall, I changed "PLAIN" to "pam" and commented hashimapspool. The mech listed in /etc/sysconfig/saslauthd is "shadow" which shouldn't matter, I believe, since the sasl_mech_list in imapd.conf would override.
Here I go again, responding to my own post. I hate when that happens.
I changed out my imapd.conf so that sasl_mech_list now says "plain" and guess what? It now works. Which I guess sort of answers the question except it's a little disconcerting to know that imapd will handle pam but timsieved won't. Especially since I figured "plain" wouldn't be very good security. Maybe I'll just leave it at "plain" and throw the whole thing behind SSL.
You seem confused between SASL mechanisms and plaintext verification methods. You should read this page from the Wiki:
http://acs-wiki.andrew.cmu.edu/twiki/bin/view/Cyrus/CyrusSaslComponents
-- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
