Bug 99632 - sasl authentication error no mechanisms found
Summary: sasl authentication error no mechanisms found
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: smtp (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Marc Mutz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-17 20:01 UTC by Valerie
Modified: 2005-05-04 16:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Valerie 2005-02-17 20:01:48 UTC
Version:            (using KDE KDE 3.3.92)
Installed from:    Compiled From Sources
Compiler:          gcc3.2 
OS:                Linux

This bug showed up once I upgraded from Kmail 1.7 (installed from unstable debian binary) to Kmail 1.7.92 (kde 3.4 beta2 compiled)
I cannot send any mails using the SMTP protocol. The error goes something like this
'Sending 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."
console output
"kio (KIOJob): error 46 An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found
kio (KIOJob): Job::kill this=0x83c1cc0 KIO::TransferJob m_progressId=0 quietly=true
kmail: [virtual void KMSender::cleanup()]"
I checked out existing bugs, which gave me a doubt regarding the SASL authentication modules I was using. Turns out I have all the latest ones installed. Also, I can send mails using Thunderbird with the same account specifications without a hitch. So I believe it has to be Kmail. 

The settings have not been changed from the older version, so am not sure if there is some option I need to turn off. The SMTP connection in question was to Gmail and I made sure it the authentication was as per what was supported by the server (TLS encryption and Plain Authentication).

Can I add more data that helps?
Comment 1 Marc Mutz 2005-02-18 00:58:44 UTC
On Thursday 17 February 2005 20:01, Valerie wrote:
> Can I add more data that helps?

Yes. Downgrade only the smtp kioslave (kio_smtp is the binary) to the one from 
kdebase-3.3, and try again.

This way, we'll see wether the kio slave is the culprit or whether it's KMail.

Thanks,
Marc

Comment 2 Valerie 2005-02-18 19:35:50 UTC
Its the kio_slave. I downgraded only the kio_smtp.so and kio_smtp.la files from the 3.3 version and mails go out fine now. No problems at all. Just to make sure I replaced them again with the version that was not working and it only confirmed that something is wrong in the kio slave itself.

Regards 
Valerie
P.s Thanks for the downgrade tip.. now I dont need to go to Thunderbird to send mails any more.
Comment 3 Johannes Orth 2005-03-02 14:08:39 UTC
I can confirm this bug. I have exactly the same problem, downgrading the smtp kio slave solves the problem for me too.
Comment 4 Valerie 2005-03-10 07:08:40 UTC
this bug still shows up in 3.4 RC1.. :(
Comment 5 Rolf Eike Beer 2005-03-13 23:16:06 UTC
Duplicate of #97139. Install cyrus-sasl-{plain,digestmd5,crammd5} and it works again.
Comment 6 Valerie 2005-03-14 20:00:11 UTC
Oh right.. I was looking at libsasl2 which was the newest version. 
To put matters right- for debian you require the libsasl2-modules package greater that 2.1.19 or the latest cyrus-sasl packages from ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/

It works for me.. so am closing the bug.
Comment 7 Marco Ferretti 2005-05-04 14:40:08 UTC
Sorry, I seem to have the same problem  (kde 3.4) upgrading to vesion 1.8 on mandrake/mandrivia . Since I am not a guru, would you mind explaining (step by step) how you solved it ? I looked for the sasl2 module and the system reports it's installed, but if I ls /usr/lib/sasl2 I have nothing in there ...


TIA 


Marco 

Comment 8 Marco Ferretti 2005-05-04 16:04:35 UTC
Ok, I have solved re-installing libsasl-plugin-plain . It looks like urpmi configuration procedure for my update was correctly uninstalling the old version but not installing the new one .