Bug 51448 - messages become unread again
Summary: messages become unread again
Status: RESOLVED DUPLICATE of bug 43931
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 47562 52676 58872 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-12-02 23:32 UTC by Werner Kratz
Modified: 2007-09-14 12:17 UTC (History)
2 users (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 Werner Kratz 2002-12-02 23:32:34 UTC
Version:            (using KDE KDE 3.0.4)
Installed from:    SuSE RPMs
Compiler:          gcc (GCC) 3.2 
OS:          Linux

I have created some new folders- the messages in this folders become "unread" again. First after having set the messages by means of "mark all as read" (or whatever equivalent the english version uses - I use the german localization), all messages are marked as read. After changing the folder (eg. clicking onto another folder), the messages turn to the "unread" state again. This happens as well when I close kmail, and reopen it again.
Amazingly this situation occurs only on certain accounts on a computer. Write permission is not an issue in this case, I have already checked this.
Comment 1 Werner Kratz 2002-12-02 23:43:15 UTC
Moving a message into the inbox and back into the folder solves the problem 
for the specific message. 
Comment 2 Ingo Klöcker 2002-12-03 09:29:36 UTC
Which "Ordnertyp" have the affected folders? mbox or maildir? Is your home directory (or your 
mail directory) located on an NFS mounted volume? If yes, then please check if the clock of the 
NFS server and the clock of your computer are in sync. 
Comment 3 Werner Kratz 2002-12-04 23:52:20 UTC
Format is maildir. The directory is not located on an NFS directory (or any 
other type of network filesystem). 
Comment 4 Thomas Gr 2002-12-12 19:19:06 UTC
I got the same problem here. The system is SuSE 8.1 with KMail 1.4.3
The mail folder is mounted with samba.
Comment 5 Ingo Klöcker 2002-12-12 21:30:36 UTC
Subject: Re:  messages become unread again

On Thursday 12 December 2002 19:19, Thomas Gr
Comment 6 Ingo Klöcker 2002-12-12 21:30:36 UTC
Subject: Re:  messages become unread again

On Wednesday 04 December 2002 23:52, Werner Kratz wrote:
> Format is maildir. The directory is not located on an NFS
> directory (or any other type of network filesystem).

Is probably another program (procmail or another mail client) writing to 
~/Mail?

Comment 7 Thomas Gr 2002-12-15 10:28:41 UTC
The problem here is solved. It went away after I syncronized the clocks of the
client and the server. Whenever I mark e-mails as read now, they stay marked.
Obviously, Kmail reacts quite nervous to desyncronized clocks. 
By the way: SuSE 8.1 installs xntpd by default, doesn't start it. The ntp-doc
package is not installed by default, you have to install it explicitly,
otherwise there will be no docs at all for ntp. The man page will only refer you
to the doc package.

Many thanks to Ingo for the help.

Thomas
 
Comment 8 Alan Prescott 2003-03-04 18:27:36 UTC
I've had this same problem and yes my mail folder is via nfs - the clocks are only out by 4min, will sync 
and check later. If this is the case this info needs to be in the kmail documentation/FAQ. 
Comment 9 Rickard Nordstr 2003-05-08 14:57:30 UTC
I have had the same problem with Kmail 1.5.1 using a mail directory located on a nfs 
mounted volume. I syncronized the clocks and now everything works just fine.  
Comment 10 Stephan Kulow 2003-09-23 16:42:12 UTC
*** Bug 47562 has been marked as a duplicate of this bug. ***
Comment 11 Stephan Kulow 2003-09-24 07:42:40 UTC
*** Bug 58872 has been marked as a duplicate of this bug. ***
Comment 12 Stephan Kulow 2003-09-24 07:43:21 UTC
*** Bug 52676 has been marked as a duplicate of this bug. ***
Comment 13 Stephan Kulow 2003-09-27 21:41:02 UTC
the symptom isn't exactly the same, but the problem is the same: index out of sync 

*** This bug has been marked as a duplicate of 43931 ***