Kmail sasl issue

Question

When trying to send an email, I get
Failed to transport message. An error occurred during authentication: SASL(-4): no mechanism available: No worthy mechs found
and the other person just receives a blank email or no email. I have installed libsasl, gsasl, cyrus-sasl-sql, cyrus-sasl-ldap, cyrus-sasl-gssapi, and cyrus-sasl

Answer 1

Hope this helps someone in the future...
I was able to successfully bind to RedHat Directory Server using a cert off a PKCS11 token today. I found 2 problems and fixing one or the other would probably take care of it.
I turned on debugging output and was following the SSL handshake between the server and my application. I noticed for PKCS11 keystore it only showed 1 cert in the chain but for PKCS12 keystore it showed the full chain of 3 certificates. Later in the handshake the server gives the client a list of trusted CA's which on my server was the top-most root. Because the PKCS12 token was able to chain the user cert back up to that root it knew to present the user certificate to the server and could connect successfully. The PKCS11 token was missing the intermediate CA and so effectively didn't realize that the one cert on the card was usable and never offered it to the CA. Some of this was getting masked by the fact that we had "allow client authentication" instead of "require client authentication" on the ldap server. Before it was only "working" because when we did a PKCS11 login it fell back to just plain old SSL and because of the way I had the ACI's set up on the server (very open) we thought it was still working fine.
So in short....I fixed the issue by adding the intermediate CA as an explicitly trusted CA on the server.
Good luck.