Bug 58872

Summary: read mail in subfolders refuses to stay read
Product: [Unmaintained] kmail Reporter: leon j. breedt <kde-bugs>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description leon j. breedt 2003-05-24 07:08:04 UTC 
Version:           1.5.2 (using KDE 3.1.2)
Installed from:    Gentoo
Compiler:          gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)
OS:          Linux (i686) release 2.5.69

i have kmail setup to use a maildir mbox for my receiving mail account, with a precommand of a script that runs fetchmail, eventually delivering into this mbox.

however, mail mysteriously gets back its unread status, even after i've re-read many times, shut down kmail, and started it up again.

i can read all the messages, stop kmail, start kmail again, and the messages i've just read will be marked unread again.

also, i can read all the messages in a folder with unread messages, switch to another folder, and when i switch back to the first folder, all the "new" messages are unread again.

however, after a longer period of time, it seems kmail finally gets the idea, and only the newest mail stays unread.
Comment 1 Ingo Klöcker 2003-05-25 23:30:58 UTC 
Subject: Re:  New: read mail in subfolders refuses to stay read

My guess is that the answer can be found in:

FAQ 6.4. Why did KMail regenerate the index of a folder?

KMail regenerates the index of a folder whenever the index appears to be 
out of date, i.e. whenever the contents of a folder is newer than the 
index. KMail does regenerate the index in this case in order to prevent 
the loss or corruption of messages. Unfortunately currently deleted 
messages might reappear and message flags (like important, etc.) might 
be lost when the index is regenerated.

An outdated index can have several causes. The two most important causes 
are: 

- Some other program modified the contents of the folder. If you want to 
use KMail together with procmail then please read this FAQ. If you want 
to use KMail together with another email client then please read this 
FAQ.

- If your mail directory (usually ~/Mail) is on a volume which is 
mounted via NFS and if the clock of the NFS server is ahead of the 
clock of your computer then the NFS server sometimes reports a wrong 
file date for the index file. In this case KMail assumes that the index 
is outdated although in reality it is not. To fix this problem you (or 
your system administrator) have to make sure that the clock of the NFS 
server and the clock of your computer are always in sync. One way to 
achieve this is the use of the ntp daemon.
Comment 2 leon j. breedt 2003-05-26 03:53:29 UTC 
the proposed solutions in both cases: 
 
(1) set up delivery to a seperate spool file (maildir in my case), from which KMail grabs 
the new mail 
 
(2) and use only maildirs for all mailboxes (the faq says this will solve all problems :) 
 
are both reflective of my current setup. the problem hasn't reoccurred since i've 
stopped using mutt for testing purposes, though, so there probably are still some 
interaction issues, even if using maildir mailboxes.
Comment 3 Stephan Kulow 2003-09-24 07:42:37 UTC 
*** This bug has been marked as a duplicate of 51448 ***
Comment 4 Claus Appelt 2004-01-08 21:32:10 UTC 
Unsynced Time between servers seems to be the problem. Had a wrong time on the client with Maildirs and Mailboxes lying on a Samba share...