#631127 kmail: smtp auth fails (sasl(0) error)

Package:
kmail
Source:
kmail
Description:
full featured graphical email client
Submitter:
Benoit Panizzon
Date:
2011-10-17 20:30:06 UTC
Severity:
normal
#631127#5
Date:
2011-06-20 14:50:30 UTC
From:
To:
Since upgrading to kmail 4.4.11 SMTP-Auth is broken.

Sniffing the traffic between kmail and the server shows, kmail does not even try smtp auth even if the server supports it.

While sending emails a weird sasl error is displayed:

"an error occured during authentication: SASL(0): successfull result:"

I did try to install/reinstall the whole SASL Libraries, changed from mit to heimdal and back, reinstalled kmail, re-configured the smtp-server.
Tryed with another client (this worked, so it's not the server).

I have no clue what goes wrong, I suppose a bug.
#631127#10
Date:
2011-06-20 21:12:30 UTC
From:
To:
In the meantime a stigi update seems to have solved the issue....
Well, that's the only thing which changed in the meantime and now smtp auth
works again with kmail.
#631127#15
Date:
2011-06-22 21:47:09 UTC
From:
To:
I confirm this bug too. On my desktop Kmaiil cann't sent message even
by insecure SMTP. On my notebook installed the same version of Kmail
but without libsasl updates and all was fine. After libsasl updates
Kmail on notebook refuse to send messages and display simular error
message. I attached some information about subject packages:

kmail: 4:4.4.11.1+l10n-1 (current)
libsasl2-2: 2.1.24~rc1.dfsg1+cvs2011-05-23-4 (current)
libsasl2-2: 2.1.23.dfsg1-8 (working lib)

Best regards,
Nepochatov Staniclav
#631127#20
Date:
2011-06-26 17:39:53 UTC
From:
To:
Hello

sorry about the bug report. The problem was triggered by something else...

...a dhcp server not supplying the 'domain' option. If /etc/resolv.conf misses
a domainnamen, SASL doesn't work.
#631127#25
Date:
2011-06-27 20:12:51 UTC
From:
To:
Hi!

I'm having the same problem here that a recent update in Debian/testing
caused kmail mail sending to break with the mentioned weird error/non-error
message.

I disagree with the Benoit's solution though, for two reasons. Firstly, it
used to work without a domain. I'm using pdnsd, and there I don't even have
the option to enter a domain. I might even be on a machine I don't have any
admin privileges for. Last but not least, the error message simply blows.

There is also some discussion going on at
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/4cbca775e4e76da6
which is related to this bug and which suggests that a strigi update would
fix the problem, too.


Cheers!

Uli
#631127#30
Date:
2011-10-17 19:43:59 UTC
From:
To:
Hi!

I guess the "very strange KMail error" mentioned in [1] is actually
described in [2], right? In any case, I can also confirm that in
testing, current kmail (4:4.4.11.1+l10n-1) with libsasl
( 2.1.24~rc1.dfsg1+cvs2011) is still broken. I've tried version
2.1.25 from [3], too, but it doesn't fix those two bugs either.

What I'm still puzzled by is the issue with the domain in /etc/resolv.
What exactly do I have to do to get this to work again? Also, is that
a workaround for the libsasl2 bug or is it a bug in my /etc/resolf
that just happened to work with older libsasl versions?


Cheers!

Uli


[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636534
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631127
[3] ftp.de.debian.org:/debian/pool/main/c/cyrus-sasl2/libsasl2-2_2.1.25.dfsg1-2_powerpc.deb