Hello, Athentication via PLAIN requires that one of several backend methods are available to do the actual authentication. In the SASL readme.html doc it lists sasldb, pwcheck daemon, or the saslauthd daemon. I believe you may also write a method of your own. We use the saslauthd daemon for several reasons. 1. We have over thirty thousand IMAP accounts. Maintaining a sasldb would be an administrative nightmare. 2. See reason number one to not use pwcheck daemon. 3. We have a kerberos infrastructure already in place to support AFS. All I need to do is create an account for someone on the server and they can authenticate to it with their userid and passwd that they already know (provided I name the account properly) and provided I use the kerberos4 mechanism for saslauthd.
Regards, Earl Shannon -- Systems Programmer, Computing Services, Information Technology NC State University. http://www4.ncsu.edu/~ershanno tsg wrote: > > Hi all! > Moving to the new Cyrus IMAP(v 2.1.1)/SASL(v 2.1.0) I got a problem: > I can't get plain text authentification - even sasllib comlilled with > --enable-plain --enable loging. In the mean time DIGEST-MD5 and CRAM-MD5 work > well. So KMail, wich support CRAM-MD5 well works with my new installation and > Mozilla mail and Outlook which support only plain password doesn't. I tryed > both sasl_pwcheck_method: sasldb and saslauthd but nothing help. > My previous installation IMAP v 2.0.16 and SASL v 1.5.27 was perfect and I > had no problem. > Could please anybody tell me what I made wrong? > Best regards and thenks in advance > Sergios
