<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=Big5" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Nalin Dahyabhai wrote: <blockquote cite="mid20070321125034.GE17225@redhat.com" type="cite"> <pre wrap="">On Wed, Mar 21, 2007 at 12:04:06AM +0800, <a class="moz-txt-link-abbreviated" href="mailto:edwardspl@ita.org.mo">edwardspl@ita.org.mo</a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> [edward@svr1 ~]$ rpm -qa | grep "cyrus" cyrus-sasl-ldap-2.1.22-4 cyrus-sasl-plain-2.1.22-4 cyrus-sasl-devel-2.1.22-4 cyrus-sasl-ntlm-2.1.22-4 cyrus-sasl-2.1.22-4 cyrus-sasl-md5-2.1.22-4 cyrus-sasl-lib-2.1.22-4 cyrus-sasl-sql-2.1.22-4 cyrus-sasl-gssapi-2.1.22-4 [edward@svr1 ~]$ Still the problem ( password fail )... </pre> </blockquote> <pre wrap=""> If your clients are attempting to use either the DIGEST-MD5 or CRAM-MD5 mechanisms, then the bad news is that the plugins can't use the hashed passwords in /etc/passwd or /etc/shadow to authenticate users because they need the plaintext passwords to work properly. If they're using those mechanisms, then you'll need to set those up using 'saslpasswd2'. But then, depending on the client software, they may well be using the PLAIN or LOGIN mechanisms, in which case you'll want to follow Brian's advice and double-check on the SELinux policy. HTH, Nalin </pre> </blockquote> Hello, I just found out that I forgot to enable the saslauth service... So, now it is good for work now ! Actually, thank for your help ! Edward. </body> </html>