Bug 101969 - Sending Mail to gmx not possible after upgrade to 1.8
Summary: Sending Mail to gmx not possible after upgrade to 1.8
Status: RESOLVED DUPLICATE of bug 99911
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.8
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-20 10:58 UTC by Axel Braun
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2005-03-20 10:58:32 UTC 
Version:           1.8 (using KDE 3.4.0 Level "a" , unofficial build of SUSE )
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.147-default

Upgraded to KDE 3.4 and KMail 1.8. Since this point in time I'm not able anymore to send mails using auth-smtp (mail.gmx.net). Removing encryption (TLS) does also not help. Error message: 
Authentifizierung fehlgeschlagen, An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found wird nicht unterstützt
Comment 1 S. Burmeister 2005-03-20 11:18:59 UTC 
Please install the remaining sasl packages using the packagemanager of your choice, or compile them if you wish.

To the kmail devels: As this kind of "bug" has been reported so many times, maybe one should put a piece of information in the notification that this error might be due to some sasl packages not being installed.

Is there some way to force rpm-packagers to set dependencies with sasl?
Comment 2 Axel Braun 2005-03-20 11:52:53 UTC 
Sven, thanks for your hint. The package cyrus-sasl was already installed and it worked with KMail 1.7, so there was no obvious reason why it should not work now. Anyway, after installing cyrus-sasl-* the problem was fixed, Thanks!
Comment 3 Thiago Macieira 2005-03-20 16:55:06 UTC 
We cannot force the packagers to do anything. It's up to them.


*** This bug has been marked as a duplicate of 99911 ***