Version: 1.1 Beta 2 (using KDE 3.3.92 (beta2) Level "a" , SUSE 9.2 UNSUPPORTED) Compiler: gcc version 3.3.4 (pre 3.3.5 20040809) OS: Linux (x86_64) release 2.6.8-24.11-smp After upgrading to KDE3.3.4beta 2 and then trying to send an email, I get the following message: Sending failed: Authorisation failed, An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found authentication not supported The message will stay in the 'outbox' folder until you either fix the problem (e.g. a broken address) or remove the message from the 'outbox' folder. The following transport protocol was used: If I go to Settings > Configure Kmail > sending > modify > security > Check what servers supports, it returns with Encryption = TLS, Authentication = Plain. I am trying to connect to a T-Online sever. I have kdepim3-3.3.92_2005020809-0.1.x86_64.rpm installed. Down grading to KDE 3.3.4 resolves the issue again.
You probably need to install the cyrus-sasl package and its authentication mechanisms. Please re-open if that doesn't solve the problem. *** This bug has been marked as a duplicate of 97139 ***
You need to put /usr/lib/sasl2 (or similar) in your "OpenSSL path" in Konqueror's crypto config. After doing that, and restarting KMail / Kontact, sending worked for me, again. IMHO KMail / Konq should auto detect these libraries somehow.
*** Bug 101712 has been marked as a duplicate of this bug. ***
*** Bug 101721 has been marked as a duplicate of this bug. ***
*** Bug 101737 has been marked as a duplicate of this bug. ***
*** Bug 101969 has been marked as a duplicate of this bug. ***
*** Bug 101977 has been marked as a duplicate of this bug. ***
Please give an other error out if no sasl support is installed. This error box is ver unusable for an "only user".
*** Bug 101703 has been marked as a duplicate of this bug. ***
*** Bug 102428 has been marked as a duplicate of this bug. ***
*** Bug 103828 has been marked as a duplicate of this bug. ***
*** Bug 107588 has been marked as a duplicate of this bug. ***
*** Bug 146267 has been marked as a duplicate of this bug. ***