If postfix 2.0.12-2mdk built with sasl2, that is the way it should be. Eventually all apps should be built against sasl2, and sasl1 phased-out.do you know why postfix in cooker still uses sasl v1?because ldap uses sasl v1 and postfix is bind to ldap and it is not good to use sasl v1 libs and sasl v2 libs in one application.
anyway i just took the sources for sasl v1 and rebuild saslauthd for sasl1 (changing the socket path) and it works like charm with postfix.
regards,
L.
Argh :(. Should I revert 2.0.12-2mdk change then? (pardon my lack of knowledge in postfix field..)
I would be happy to take a look at the postfix package, but am not running a cooker environment. I'm mostly 9.1 based, with a few cooker additions, and others that haven't made it in the cooker yet (Openldap 2.1.20 & db41 that Oden & Buchan have been working on).
There was a question about (current) openldap requiring db41:
From the openldap admin guide...
Berkeley DB <http://www.sleepycat.com/> is available from Sleepycat Software <http://www.sleepycat.com/>'s download page http://www.sleepycat.com/download.html. There are several versions available. At the time of this writing, the latest release, version 4.1, is recommended. This package is required if you wish to use the BDB database backend.
OpenLDAP's /slapd/(8) LDBM backend supports a variety of data base managers including Berkeley DB <http://www.sleepycat.com/> and GDBM <http://www.gnu.org/software/gdbm/>. GDBM <http://www.gnu.org/software/gdbm/> is available from FSF <http://www.fsf.org/>'s download site ftp://ftp.gnu.org/pub/gnu/gdbm/.
Thanks,
S
