Quoting Ferdinand Goldmann <[EMAIL PROTECTED]>: > > > On Fri, 4 Jan 2002, Lawrence Greenfield wrote: > > > try: > > > > ln -s /usr/local/lib/sasl /usr/lib/sasl > > > > libsasl looks in /usr/lib/sasl for the plugins but installs them into > > /usr/local/lib/sasl. > > Yes, I know, I already did this after SASL installation: > # ls -l /usr/lib/sasl > lrwxrwxrwx 1 root system 19 Oct 23 12:46 /usr/lib/sasl -> > /usr/local/lib/sasl > # ls /usr/local/lib/sasl > libanonymous.a libcrammd5.a libdigestmd5.a > libplain.a > libanonymous.la libcrammd5.la libdigestmd5.la > libplain.la > libanonymous.so.1 libcrammd5.so.1 libdigestmd5.so.0 > libplain.so.1 > libanonymous.so.1.0.15 libcrammd5.so.1.0.15 libdigestmd5.so.0.0.17 > libplain.so.1.0.14 > > I still have no idea, why my plugins are not detected, or why SASL does not > anounce anything when connecting to imapd or popd. Still, everyone can log > in > fine to their POP3/IMAP accounts, I guess because I am running a pwcheck > daemon.
The reason that your users can login to IMAP and POP3 is probably because they are not using the AUTHENTICATE or AUTH commands (ie, SASL) respectively. IMAP and POP3 each have their own built-in plaintext commands (LOGIN and USER/PASS). Ken -- 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
