Description of problem: After an upgrade from sendmail-8.12.10-1 to sendmail-8.12.11-3.3 the sasl2 support isn't any longer available - so why?! In my eyes, something simply went wrong, but please look yourself: --- snipp --- # rpm -qpl sendmail-8.12.10-1.i386.rpm | grep sasl /usr/lib/sasl2/Sendmail.conf # # rpm -qpl sendmail-8.12.11-3.3.i386.rpm | grep sasl /usr/lib/sasl/Sendmail.conf # --- snapp --- Version-Release number of selected component (if applicable): sendmail-8.12.11-3.3 How reproducible & Steps to Reproduce: Everytime; upgrade from sendmail-8.12.10-1 to sendmail-8.12.11-3.3 and find the missing sasl2 support... Actual results: Well, in the spec file of sendmail-8.12.11-3.3 I found: --- snipp --- %define with_sasl2 no --- snapp --- Expected results: To support sasl2 again, as it was case in 8.12.10-1, do --- snipp --- %define with_sasl2 yes --- snapp --- and rebuild it - which solved it for me personally, but I still can't really do that at a supported RHEL3 at our customers...
The reason for the change was that sendmail also used LDAP. In RHEL3, libldap uses sasl version 1, so sendmail ended up with both versions of the library loaded at run-time (you can verify this by running "ldd" against the sendmail binary). Because both version 1 and 2 of the sasl library provide symbols with the same names but which are binary-incompatible, there's no guarantee that that combination could ever work reliably (i.e., without causing sendmail to crash, which would actually be the most likely outcome), so the change had to be made.
Nice...but I still hope, that this isn't the final answer for my issue. Because I really can't tell that reason to my colleagues and our customers, because they want to use saslauthd/sasl2. And offering them my personal (for me) working hack, isn't a supported solution for RHEL3 productive systems...
I am sorry, but this is the final answer. Please use sasl1 instead.
*** This bug has been marked as a duplicate of 124086 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.