[kdepim-users] Kmail stops delivering mail after a period of time

Roy J. Tellason rtellason at verizon.net
Fri Jan 25 01:16:47 GMT 2008

On Thursday 24 January 2008 17:21, Ingo Klöcker wrote:
> On Thursday 24 January 2008, r bartlett wrote:
> > I'm having this problem on FC8 (Qt: 3.3.8, KDE: 3.5.8-19.fc8 Fedora,
> > KMail: 1.9.6) but had it on a different computer in FC5 too.
> > Everything's fine, no problems, but at some point -- sometimes hours,
> > usually more like days -- Kmail just stops delivering my email.  It
> > _checks_ for it.  But it just doesn't appear in the inbox.  Usually I
> > get curious that so-and-so hasn't replied yet and then start to get
> > suspicious...and sure enough, if I kill Kmail, wait for the processes
> > to die, then restart it -- Poof!  The 5 or 6 or 10 or 80 messages
> > that collected appear in the Inbox.
> >
> > Does anyone else have this issue?  One additional wrinkle is that it
> > does not seem to be _all_ my different accounts.  Just a few.  For
> > example, my Comcast inbox mail appears fine, but my such-and-such
> > mail stops.  On my other computer, I noticed that there were tons (20
> > or so) slave sockets for kmail that were running and even after
> > killing it, usually one was sticky and would remain unless I manually
> > killed the process.
> >
> > On this computer though, FC8, there were no processes left seconds
> > after I closed Kmail.  (Actually, I'm using Kontact, so I close
> > Kontact, not Kmail).
> A long time ago a similar problem (email stopped arriving via POP3 when
> KMail ran for a longer time) was reported. My guess is that some error
> condition in the communication with the server leaves KMail in a state
> where it thinks it is still checking the account and therefore no new
> checks are initiated. AFAIK we were not able to track down and fix this
> problem. So the only workaround for people experiencing this problem is
> to restart KMail (resp. Kontact) every once in a while.

I've noticed this behavior here,  as well,  where my status line will indicate 
that it's in the middle of checking for new mail,  and just sit there.  For 
what eventually turns into a rather interminably long time.  I don't recall 
now whether I had to restart things or whether I was able to simply stop the 
attempt and get it to try again,  though I'm leaning toward the latter in my 

There are occasional other issues with some software on this box,  I'm not 
sure exactly _which_ software,  that apparently has memory leaks somewhere.  
I run into it showing up as ever-increasing use of swap,  until I shut down 
KDE and restart it,  at which point I can have exactly the same mix of 
applications running with _no_ swap being used.  Typically I'll have firefox 
and kmail and perhaps kmix and noatun or similar running,  on the first three 
desktops here,  and maybe something else on the fourth -- at times it's been 
a pdf viewer,  right now it's konqueror.  I notice that if I shut things down 
when I'm not using them this delays the swap issue considerably,  though 
inevitably at some point it'll come back.

I've had linux boxes running for many months at a time,  usually only 
interrupted by either me running into power problems or me doing some sort of 
hardware change or upgrade.  Yet this doesn't seem to be too feasible for KDE 
and the mix of applications I'm running here. Do the developers/testers not 
leave their machines on?

Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin
KDE PIM users mailing list
kdepim-users at kde.org

More information about the kdepim-users mailing list