Bug 138457

Summary: could not connect to host localhost
Product: [Unmaintained] kmail Reporter: Al Eggen <aeggen>
Component: pop3Assignee: kdepim bugs <pim-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: martin
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Al Eggen 2006-12-06 16:22:22 UTC 
Version:            (using KDE KDE 3.5.2)
Installed from:    Mandriva RPMs
OS:                Linux

Now whenever I click check mail in I get the 'could not connect' message.  This started just recently.  Sometimes when opening kmail I get a message that it's already running on host xxxx. That host will be in the kmail lock file, so I delete the lock file and everything seems to work (The same thing sometimes happens with oowriter).  This time I did that and ever since have been getting the 'could not connect' message whenever I try to download my email (pop3 on charter.net).  I still can compose and send email from the account.  The lock file reads: app=kmail; host=pc71-80-125-92.willi.ct.charter.com; pid=5904; program name=KMail.  The host and pid are not always the same.
Thanks, Al
Comment 1 Martin Koller 2009-07-31 17:47:02 UTC 
I don't fully understand this bug report in regards what the reporter really did and when.
If this is still a problem with kmail/KDE4, please explain in more detail, otherwise please close this bug.
Comment 2 Christophe Marin 2009-07-31 17:51:06 UTC 
needsinfo/fixed is not a valid combo.
Comment 3 Andrew Crouthamel 2018-09-04 18:23:52 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!