On Mon, 14 Feb 2005 07:04:01 +0100, Alexander Dalloz <ad+lists@xxxxxxxxx> wrote: >Am Mo, den 14.02.2005 schrieb Steven Stern um 6:51: > >> I know what the error is -- "no secret" in the file /etc/sasldb2 >> >> I just don' t know how to fix it. There are hundreds of hits on Google, but >> no solutions... people just seem to give up. > >> Steve > >No, certainly they don't give up. > >The original log message was: > >Feb 13 19:38:23 ciscy sendmail[28257]: j1E1cJo7028257: AUTH failure >(CRAM-MD5): user not found (-20) SASL(-13): user not found: no secret in >database > >So add a user to the sasldb2 using saslpasswd2 and be sure you use the >correct realm to authenticate then! If you do not pass a realm with the >saslpasswd2 command, then your hostname is used as realm. Your login >name is then > >user@hostname > >If you leave away the realm, then of course the user will not be found. > Part 2: I entered testuser1@xxxxxxxxxxxxx as the login address for Thunderbird and it worked! Thanks. When I try to authenticate as a different user Do I have to have an entry in sasldb2 for every user? Is there any way to get it to use pam and shadow? If not, is there an easy way to synch the system password with the sasl password? saslauthd is supposed to be using "shadow" to look up passwords: It runs as: /usr/sbin/saslauthd -m /var/run/saslauthd -a shadow -- Steve