On Sun, 2003-06-01 at 19:48, Jack Coates wrote: > On Sun, 2003-06-01 at 10:17, Luca Olivetti wrote: > > En/na Jack Coates ha escrit: > > > hey, > > > > > > just upgraded my server from 9.0 to 9.1, went fairly smoothly but my > > > Postfix SASL setup is now busted. Since I need SMTP AUTH to work, this > > > is a problem :-) > > > > If you're using the sasldb, sasl v1 (i.e libsasl7) packages are broken > > in 9.1, since they're compiled with gdbm as the backend instead of > > berkeley db. The problem originates from the fact that they combined in > > the same srpm both sasl v1 and sasl v2. Since sasl v1 isn't developed > > anymore it doesn't support the latest version of berkeley db, while sasl > > v2 does. In the combined package you can buildrequire libdb3.3-devel or > > libdb4.0-devel but not both, so the old library version is linked with > > gdbm instead. I have experimental packages with separate srpm for sasl > > v1 and sasl v2 (each linked with the "correct" database library) but the > > maintaner didn't accept them because he says they don't compile in cooker. > > I suppose you can grab the current srpm, replace the "Buildrequires: > > libdb4.0-devel" with "Buildrequires: libdb3.3-devel" and tweak configure > > options for sasl v1 (remove the --with-gdbm or something similar). > > > > Bye > > thanks for the tip -- this makes sense, so I did as you suggested and > got the Mandrake 9.1 srpm, -ivh'ed it, edited the spec and changed > buildrequire from libdb4.0-devel to libdb3.3-devel, and installed all > the relevant -devel packages. I then had to remove all gdbm related > lines completely, including the patch lines, in order to make it compile > cleanly. Once that was done I gave it a for i in `rpm -qa|grep sasl`;do > rpm -e $i --nodeps;done and then installed all the freshly made RPMS, > ensuring that mine were installing rather than the stock 9.1 RPMs by > replacing the stock ones with these in my hard disk source. > > I've then restarted Postfix and gotten no change in behavior :-( > > So, unless there's an error up there I'm back to the Postfix config. > Anything obviously wrong here? ... > I'm running out of ideas, and I need to get it working soon. Help, > please :-)
More info -- read enough and used testsaslauthd enough to decide sasl is basically working... I've now found an actual live and relevant error message! When I try to send an authenticated message, Postfix complains that whatever pwcheck method I specified in /usr/lib/sasl/smtpd.conf is unrecognized: Jun 1 22:12:57 felix postfix/smtpd[5896]: warning: SASL authentication problem: unrecognized plaintext verifier saslauthd Jun 1 22:17:09 felix postfix/smtpd[5958]: warning: SASL authentication problem: unrecognized plaintext verifier pwcheck One exception, pwcheck_method of pam gets no error message at all -- no mail, either, even if I... [insert filthy unprintables here] It just started working when I switched to pwcheck_method: pam. By just started working, I mean 250-AUTH LOGIN DIGEST-MD5 PLAIN CRAM-MD5 250-AUTH=LOGIN DIGEST-MD5 PLAIN CRAM-MD5 now you're probably wondering what these two things have to do with one another... I know I am. -- Jack Coates Monkeynoodle: A Scientific Venture... http://www.monkeynoodle.org/resume.html
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
