On 28/10/09 00:47 -0700, Maria McKinley wrote: >ella:/var/log# testsaslauthd -u "test" -p "xxx" -s smtp >0: OK "Success." >ella:/var/log# testsaslauthd -u "test" -p "xxx" -s imaps >0: NO "authentication failed" >ella:/var/log# testsaslauthd -u "test" -p "xxx" -s imap >0: OK "Success." Can you provide sanitized copies of the following?: Your saslauthd startup options (e.g. /etc/default/saslauthd) Your saslauthd.conf if it exists your PAM configuration for smtp, imaps and imap if appropriate >TLS seems to work just fine for smtp: > >Oct 28 00:13:21 ella postfix/smtpd[5794]: initializing the server-side >TLS engine >Oct 28 00:13:21 ella postfix/smtpd[5794]: connect from >c-76-28-239-89.hsd1.wa.comcast.net[76.28.239.89] >Oct 28 00:13:21 ella postfix/smtpd[5794]: setting up TLS connection from >c-76-28-239-89.hsd1.wa.comcast.net[76.28.239.89] >... > >But I get tls errors regarding imaps: > >Oct 26 06:36:35 ella cyrus/imaps[18356]: Fatal error: >tls_start_servertls() failed Permissions problem? Can your cyrus user read the TLS files you've specified in imapd.conf? If not, please include sanitised copies of your imapd.conf and cyrus.conf. >I'm not entirely sure how big of a deal this is, since we use ssl over >imaps to check mail, but it does seem to be causing a problem with >filters/sieve. When someone attempts to change filters using >squirrelmail, the connection times out, and the logs fill with imaps tls >errors. > >Oct 28 00:37:45 ella cyrus/sieve[7080]: starttls: TLSv1 with cipher >AES256-SHA (256/256 bits new) no authentication >Oct 28 00:37:48 ella cyrus/imaps[7082]: imaps TLS negotiation failed: >[10.208.108.93] >Oct 28 00:37:48 ella cyrus/imaps[7082]: Fatal error: >tls_start_servertls() failed What does your sieve entry look like in cyrus.conf? What's your squirrelmail sieve (avelsieve?) configuration look like? -- Dan White ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
