I've been having this problem since kde-3.4.0 and I thought it might be fixed by upgrading to kde-3.4.1, but I'm still having the problem. I can receive email but I can't send any. Right now I'm using Thunderbird for my email purposes, but was just wondering why I can't send email with Kontact, when I could using previous versions of KDE. This is the error message I'm currently getting when I try to send any mail:
sending mail using KontactSending failed:
Authorization 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:
Verizon
I've googled but haven't found anything. I got to check out the bug report next.
Just curious what's going on.
I'm using Slackware 10.1.
Thanks for any info.
tom

The error posted sounds like you are attempting to use an encryption protocol (SASL), but that the smtp server you put down does not support it. Go back to your kontact configuration, find where you enter the smtp server's address, and make sure the authentication protocol is appropriate. I believe there is an option to "Check what the Server supports" somewhere there. Try that and make sure there are no errors. The options I described may be in the Security tab. (Currently, do not have access to kontact so I cannot tell you the exact steps).

I too am having trouble sending. I try to telnet the SMTP server with a port # either 25 or 587 and the Telnet just hangs. I can receive finely.

My settings are exactly as per my host's advice. The same settingas seed to work fine in MS Windows- I won't go there........

Long Day, I need sleep and will continue on this when I return from exercising tomorrow.

If I have any progress, I'll post it.

Salman

This sounds like a problem that I had on SuSE 9.2 when I manually upgraded to KDE 3.4. I think the problem in that case was that the pcakages for KDE were broken. I ended up reverting back to KDE 3.2 til SuSE 9.3 came out with fixed RPMs.

Try updating your kde-pim package and see if that makes any difference.

Cheers,

Cleidh Mor