Bug 215091 - Kmail (Kontact) occasionally stops receiving mail for no apparent reason
Summary: Kmail (Kontact) occasionally stops receiving mail for no apparent reason
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 6
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-10 21:32 UTC by Mike Cohler
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: kdepim-3.5.7-3.fc7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-18 08:28:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mike Cohler 2006-11-10 21:32:39 UTC
Description of problem: kmail running from Kontact within KDE occasionally stops
receiving mail from pop server.


Version-Release number of selected component (if applicable):kdepim-3.5.5-0.1.fc6


How reproducible: Keeps happening but about every few days


Steps to Reproduce:
1. Start Kontact and put kmail in main window
2. Leave mail fetching every couple of minutes from remote pop server
3. Usually runs OK but periodically stops receiving new mail - and clicking
"Check Mail In" no longer updates the incoming mail.
4. If Kontact is closed and restarted then the system updates normally for a few
days until it stops as above again.
  
Actual results: No new mail comes in after some period


Expected results:Mail should continue to be fetched from pop server


Additional info: On a different machine in a different location fetching mail in
the same way but running fully updated FC5 instead of FC6 also shows the same
symptoms. Both systems fully up to date with yum.  This has been happening for
some months despite updates to KDE. There are no error messages in
/var/log/messages or anywhere else that I can find.

Comment 1 Mike Cohler 2007-09-18 08:27:43 UTC
This problem has not appeared at all with F7 so I am closing this bug as
resolved in the current system.


Note You need to log in before you can comment on or make changes to this bug.