Re: [SM-USERS] Suse 9.2 and squirrelmail

[p d. t. <pdo...@an...>]

Please do not respond off-list.  If "other user of SL 9.x report the the 
same problem", then don't you want this thread available for them to 
view like you viewed theirs?

> Am Mittwoch, 5. Januar 2005 00:22 schrieben Sie:
> 
>>>after the last Update for cyrus on my suse 9.2 Box I tried up to 10x to
>>>get a login on squirrelmail
>>>
>>>most I get an Error message in my logfile like this:
>>>
>>>aslauthd[28193]: DEBUG: auth_pam: pam_authenticate failed: Authentication
>>>failure
>>>saslauthd[28193]: do_auth         : auth failure: [user=xxxx]
>>>[service=imap] [realm=] [mech=pam] [reason=PAM auth error]
>>>imap[28365]: badlogin: localhost [127.0.0.1] plaintext may SASL(-13):
>>>authentication failure: checkpass failed
>>
>>1) this has NOTHING to do with SM.  you need to ask the cyrus folks
> 
> why you think that? egroupware also works fine

Because SM does *NOT* connect to the auth daemon itself.  It merely logs 
in to IMAP.  IMAP is responsible for contacting whatever auth server you 
are running.

>>2) if you want good help, you need to include more info like all
>>saslauth related config files and startup options and the version of
>>sasl that you ended up with
> 
> saslauthd -v
> saslauthd 2.1.19
> authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap
> what you also need?

SM settings, saslauth startup options, info about how your IMAP server 
uses sasl (assuming you are using Cyrus IMAP?  don't make us guess), 
logs from PAM, which is where the actual problem is happening.

Have you read this?:

http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines

Again, you will probably get better help asking somewhere more relevant.