Bug 78290 - kmail 3.4beta1 : kioslave smtp Authorization not supported
|
Bug#:
78290
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: kde@gentoo.org
|
Reported By: tdi@pozman.pl
|
|
Component: KDE
|
|
|
URL:
|
|
Summary: kmail 3.4beta1 : kioslave smtp Authorization not supported
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-01-16 16:10 0000
|
on kde 3.4beta1 kmail cannot send mail : Authentication support is not compiled
into kio_smtp.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Expected Results:
it should send mail
Please try emerging "kdebase-kioslaves" with the USE flag "sasl" enabled. If it
works we should probably make this dep as a default as probably the auth code
now works only with cyrus-sasl support compiled.
kio_imap4 also misses sasl authentication. As this kio slave is included in
kdepim (and the corresponding split ebuild) this should also have the USE flag
"sasl".
I was sure it was already added. Probably it was misses in some berlios svn
updates. thanks for finding this out. (I'll commit this chenged this evening if
none do this before).
ok it solves the problem. But there is a problem with cyrus-ssl ill post it as
new bug
*** Bug 78389 has been marked as a duplicate of this bug. ***
kdeteam: are you ok to remove the "sasl" USE flag and make "cyrus-sasl" as a
fixed depency? as it looks that without it the pop3 and imap authentication
won't work.
You have my vote at least, Simone. I just can imagine the irritated
user/developer crying "You killed an option, you killed an option, ...". ;)
Done in kdebase-kioslaves (also fixed a deps on kde-base/kdesktop that didn't
used the "deprange" script) and in kdepim-kioslaves.
Forced cyrus-sasl in kdebase and kdepim, too.
Sorry, I forgot to also update them.
A version bump on kdebase-kioslaves would be helpful to resolve this bug.
Simply installing cyrus-sasl does not fix the problem, as the kioslaves need to
be recompiled.
*** Bug 162583 has been marked as a duplicate of this bug. ***