On Tue, 30 Apr 2002 11:39:38 -0400 (EDT) Rob Siemborski <[EMAIL PROTECTED]> wrote:
RS> On Tue, 30 Apr 2002, Eric S. Johansson wrote: RS> RS> > I understand that. What I can't figure out as how to get imapd to stop RS> > insisting on cram-md5 from the local database RS> RS> use the "mech_list" option (sasl_mech_list in imapd.conf), or just delete RS> the plugins from your /usr/lib/sasl2 directory that you don't want. yup it did. I used: sasl_mech_list: plain RS> > the fact I'm getting the unknown password verifier tells me that I I RS> > have either a misspelling, I am missing a sasl2 authentication RS> > library, or I didn't compile imapd correctly. RS> RS> saslauthd is a separate binary. you need to configure sasl RS> --with-saslauthd to compile it (and enable the password verifier internal RS> within the library). I did configure sasl with ---with-sslauthd (as well as a bunch of other stuff[1]) but I'm not sure what you mean by enabling the password verifier internal within the library. [1] I configured sasl with: ./configure --prefix=/usr/local/sasl --disable-krb4 --without-gssapi -with-auth=unix --with-pwcheck --with-saslauthd I run saslauthd as: /usr/local/sasl/sbin/saslauthd -a PAM but what I'm seeing in the log looks like imapd doesn't even know that saslauthd is there. just how does imap and saslauthd communicate? Is there a way I can check to make sure saslauthd is functioning correctly? By the way, I do appreciate all the help you and others have been giving me. ---eric
