Bug 101703 - detection of mail server authentication method fails to detect login
Summary: detection of mail server authentication method fails to detect login
Status: RESOLVED DUPLICATE of bug 99911
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-17 16:40 UTC by murray
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 murray 2005-03-17 16:40:48 UTC 
Version:           1.1 (as reported by kontact) (using KDE 3.4.0 Level "a" , SUSE 9.2 UNSUPPORTED)
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809)
OS:                Linux (i686) release 2.6.8-24.11-default

When I try to detect authentication methods to smtpauth.earthlink.net it reports PLAIN and TLS when I press "check what server supports" Trying to use these settings fails with "An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found authentication not supported"

If I manually select LOGIN and TLS things work fine. This looks like a regression to me as the autodetection used to work in previous KDE versions.

Thanks,
murray smigel
Comment 1 Ingo Klöcker 2005-03-21 00:01:12 UTC 
Note the following:
  // LOGIN doesn't offer anything over PLAIN, requires more server
  // roundtrips and is not an official SASL mechanism, but a MS-ism,
  // so only enable it if PLAIN isn't available:

I guess your problem will go away when you install cyrus-sasl and cyrus-sasl-plain. Additionally, you should install cyrus-sasl-digestmd5, cyrus-sasl-crammd5 and probably also the other cyrus-sasl-* packages.
Comment 2 murray 2005-03-21 00:38:37 UTC 
On Sunday 20 March 2005 18:01, Ingo Klöcker wrote:
[bugs.kde.org quoted mail]
**
Thanks, that did the trick. Perhaps a more informative error message might be 
possible? I certainly would not have thought to look under cyrus*.rpm!

Thanks for your help,
murray
Comment 3 Till Adam 2005-03-21 07:48:26 UTC 

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