Bug 105861

Summary: kmail freezes while running ldap io slave
Product: [Applications] kmail Reporter: Heiko Nardmann <heiko.nardmann>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: kollix
Priority: NOR    
Version: 1.8   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Heiko Nardmann 2005-05-18 09:21:31 UTC
Version:           1.8 (using KDE 3.4.0 Level "b" , SUSE 9.3)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-20a-default

Situation:
our IT department has done a migration of the ldap server which is responsible for the global addressbook during the weekend. Yesterday I have also switched to SuSE 9.3 (from 8.2; new installation). This one comes with kmail 1.8 (3.4.0 "b" SuSE 9.3).

Now ... when I start kmail an ldap io slave is started which tried to contact the old ldap server configured for the addressbook. So this old ldap server was not reachable anymore. The ldap slave freezes kmail, i.e. getting mails from local /var/spool/mail does not progress but hangs at message 0.

After killing the ldap io slave download of mails is fine again. Also configuring the new ldap server for the addressbook lets the problem disappear.

So ... what I am missing ...

1) progress bar or progress dialog for ldap contacting is missing; there should be a visual feedback to the user here.

2) why does getting new mails not work if the ldap io slave is working? I don't see any dependencies here.
Comment 1 Martin Koller 2009-09-29 19:23:27 UTC
Do you still see this problem with KDE 4.3.1 ?
I also have an ldap server configured, which is not reachable from home, but I never had any problems with that.
Comment 2 Andrew Crouthamel 2018-09-04 18:21:35 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!