Am Mo, den 15.11.2004 schrieb Krzysztof Krupa um 14:03: > : smtpd_sasl_authenticate:sasl_method CRAM-MD5 > : smtpd_sasl_authenticate:encoded challenge: > <[EMAIL PROTECTED]> > : > unknown[192.168.200.2]:334 > PDQwNDQxNjczOS4xMDAwMjE3MUBtYWlsLnJvem5vc2NpLmludC5wbD4= > : < > unknown[192.168.200.2]:a3J6eXMgZGFkYzJiMjExN2RkZWJjNTMyMWYxYzFjOWMwYzFhZmI= > : smtpd_sasl_authenticate:decoded response: krzys > dadc2b2117ddebc5321f1c1c9c0c1afb > : warning:unknown[192.168.200.2]: SASL CRAM-MD5 authentication failed > : > unknown[192.168.200.2]:535 Error: authentication failed > : watchdog_pat: 0x8062160 > : smtp_get: EOF > : lost connection after AUTH from unknown[192.168.200.2] > : disconnect from unknown[192.168.200.2] > : master_notify: status 1 > : connection closed > : watchdog_stop: 0x8062160 > : watchdog_start: 0x8062160 > > koniec LOG'a mail.log > > w sasldb2 mam logujacego sie usera, w shadow tez. > Nie moze sie zalogowac a ja juz nie mam pomyslow. > Ma ktos jakas rade?
ja mialem cos podobnego przy przesiadce na najnowsza wersje sasl w sarge - sasl bez pam chce haselka w plaintext. Moze to wlasnie to? Pozdrowienia Wojtek