Bug 103050 - IMAP connection to host keeps breaking
Summary: IMAP connection to host keeps breaking
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-02 07:47 UTC by Kurt Bennater
Modified: 2009-02-08 15:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Bennater 2005-04-02 07:47:42 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

KMail displays error messages "Connection to host ... is broken" every few minutes.

The host is a UW IMAP server, other users using Thunderbird don't seem to have problems with this server. The server's log files indicate that KMail first connects in "authenticate" mode, but after a few minutes tries to connect via the "login" mode, which (probably since it is still logged in from the "authenticate" mode) causes the server to kill both connections.

I played around with all possible combinations of SSL and TLS, and "clear text" and "login" settings, but the error messages keep appearing.
Comment 1 Carsten Burghardt 2005-04-03 18:16:06 UTC
On Saturday 02 April 2005 07:47, Kurt Bennater wrote:
> KMail displays error messages "Connection to host ... is broken" every few
> minutes.


As I can not reproduce this with uw imap server it would be good if you could 
compile kmail and the imap kioslave (kdepim/kioslaves/imap4) with 
--enable-debug=full and get a debug output from the console.
Comment 2 Kurt Bennater 2005-04-10 18:00:46 UTC
O.k., sorry for the delay, here it is:

kmail: processNextCheck, remaining 1
kmail: for host hostname1.edu current connections=0 and limit is 0
kmail: connection limit reached: false
kmail: processing next mail check for account1
kmail: processNewMail false,status=1
kmail: check mail started - connections for host hostname1.edu now is 1
kmail: processNextCheck, remaining 0
kmail: account account1 finished check
kmail: connections to server hostname1.edu now 0
kmail: processNextCheck, remaining 1
kmail: for host hostname2.de current connections=0 and limit is 0
kmail: connection limit reached: false
kmail: processing next mail check for account2
kmail: processNewMail false,status=2
kmail: KMFolderImap::checkValidity of: /INBOX/
kmail: CheckValidity - waiting for connection
kmail: check mail started - connections for host hostname2.de now is 1
kmail: [void
KMail::ImapAccountBase::slotSchedulerSlaveConnected(KIO::Slave*)]
kmail: KMFolderImap::checkValidity of: /INBOX/
kmail: [void
KMail::ImapAccountBase::slotSchedulerSlaveConnected(KIO::Slave*)]
kmail: KMFolderImap::slotCheckValidityResult of: INBOX
kmail: processNextCheck, remaining 0
kmail: account account2 finished check
kmail: connections to server hostname2.de now 0

"account2" is the one causing problems; although the security settings for both 
accounts are the same, KMail obviously treats them differently. The error message "Connection to host hostname2.de is broken" is displayed often during checks of account1 (!), There is no new debug information shown during this error message. As I said, my information concerning the "authenticate" and "login" modes is taken from the server's log files.
Comment 3 mchugh19@yahoo.com 2005-04-10 20:45:55 UTC
I have nothing to add except this is a problem for me as well. I get around it by clicking on a local directory or returning back to the into to kmail screen. That seems to stop the constant polling of the imap server.
Comment 4 Tristan Hoffmann 2008-03-10 17:32:13 UTC
Does someone still see this problem in a more recent KMail version?
Comment 5 Kurt Bennater 2008-03-11 20:43:20 UTC
I don't have this account on the UW imap server any more, so I can't check that.
Comment 6 Tristan Hoffmann 2009-02-08 15:04:43 UTC
Since there's no activity on this bug since 2005 I close it for now.

If somebody still has a problem with this in a recent KMail version, please just reopen this bug, thanks.