[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 82259] Expire mail does not really deletes mails
From:       David Faure <faure () kde ! org>
Date:       2004-07-05 13:07:57
Message-ID: 20040705130757.5675.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=82259      




------- Additional Comments From faure kde org  2004-07-05 15:07 -------
FolderStorage::getMsg() has that code which checks if the message and the msgbase
have the same subject, and if not, disables compaction [for ever, since there's no \
way to reenable it after that].

We discussed this as part of #82259/#37898.

I finally found how to very simply reproduce the problem, with maildir (much simpler
than with mbox, but the problem applies to both).

I simply deleted the file holding a mail using "rm" in a terminal, while kmail was \
running. Then when some code tried to access a message in that folder, the check \
                triggered.
kmail: Could not open file r+ \
/home/test/.kde/share/apps/kmail/dimap/.535027005.directory/.INBOX.directory/Notes/cur/1089031079.5468.iBPdD:2,S
                
kmail: ERROR: ############ Error: \
/home/test/.kde/share/apps/kmail/dimap/.535027005.directory/.INBOX.directory/Notes \
Index file is inconsistent with folder file. This should never happen. (I have a \
messagebox there now, that's how I noticed it).

I know that users aren't probably supposed to delete random files from the command \
line, but doesn't this also happen to people using multiple mail clients?

Can't we just throw away the index when this happens? In this case it's
clearly outdated, we should just throw it away and recreate it. Certainly
no reason to disable compaction for ever, nor for showing "No Subject / Unknown / \
Unknown" :)


[prev in list] [next in list] [prev in thread] [next in thread]