--On Wednesday, September 01, 2004 11:40:40 -0400 Ken Murchison <[EMAIL PROTECTED]> wrote:



Cyrus isn't finding your SASL plugins, because no SASL mechs are listed
in the capability list.  Make sure you have SASL installed correctly.


SNIP


Hi Ken,

actually IMAP is authenticating against SASL.

I compiled sasl 2.1.9 like:
./configure --prefix=/usr/cyrus-sasl --sysconfdir=/etc --enable-login
--disable-checkapop --disable-krb4 --disable-gssapi
--with-openssl=/usr/local/ssl --with-saslauthd=/var/state/saslauthd
--with-ldap
And in sasldb/Makefile line 245
   changed     LOCAL_SASL_DB_BACKEND_STATIC :=
     to        LOCAL_SASL_DB_BACKEND_STATIC =

  since it was not "making"

I'm starting the daemeon like:
/usr/cyrus-sasl/sbin/saslauthd -a pam -O /etc/saslauthd

/etc/saslauthd:
MECHANISMS="pam"

--enable-login --disable-checkapop --disable-krb4 --disable-gssapi
--with-openssl=/usr/local/ssl --with-saslauthd=/var/state/saslauthd

I did exactly the same as with version 2.1.17 (old Server)

Can you give me any hint?

Try making a link fro /usr/lib/sasl2 to the directory which contains the mschanism plugins (libplain.so, libcrammd5.so, etc).


Many thanks, that works.

Although, I'm not sure why, because my linker (crle) shows /usr/cyrus-sasl/lib it in the search path.

Anyway

Cheers
 Gerald
---
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

Reply via email to