Bug 147159 - POP3 ioslave dies everytime when using CRAM-MD5
Summary: POP3 ioslave dies everytime when using CRAM-MD5
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Unmaintained
Component: pop3 (show other bugs)
Version: 1.9.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-06-24 11:10 UTC by Kurt Marschall
Modified: 2009-08-22 14:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Marschall 2007-06-24 11:10:10 UTC 
Version:            (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

After the last update of kde 3.5.7 (kdepim3-3.5.7-21.1) the above error message appears any time I check my mails via the pop3 or pop3s protocol.

I don't want to downgrade kdepim3 and future versions shall be without this bug...
Comment 1 Thomas McGuire 2007-06-24 13:04:54 UTC 
There is most likely something wrong with your installation, probably something was messed up when upgrading.
POP3 works fine for me (GMX as well).
You did restart after upgrading, right?
Did you update the kdebase and kdelibs packages as well?
Comment 2 Kurt Marschall 2007-06-24 16:51:37 UTC 
@Thomas McGuire
I updated everything on kde. I used YastOnlineUpdate.

What I just did: I created a new user and configured kontact from scratch... Still the same error...
Comment 3 Thomas McGuire 2007-06-24 17:14:58 UTC 
What kind of encryption and authentication method do you use?
Does changing them solve the problem?
Comment 4 Kurt Marschall 2007-06-24 21:19:51 UTC 
Thanks, I used to use CRAM-MD5 as the authentication method...
I have changed it to APOP and it seems to work now
Since you use gmx.net as well: Are you having the same problem? Could you check that on your machine?

Many thanks!
Comment 5 Thomas McGuire 2007-06-25 13:37:00 UTC 
CRAM-MD5 works fine for me.
Comment 6 FiNeX 2009-04-05 00:38:51 UTC 
@Kurt: After two years, are you still having this issue using more recent KDE version?
Comment 7 Martin Koller 2009-08-22 14:45:05 UTC 
no response; let's close it.
If that still occurs with KDE 4.3, please reopen