[Bug 121969] Automatic filtering in kmail marks messages as read

MartinG <[email protected]>
Newsgroups gmane.comp.kde.devel.kmail
Message-ID <[email protected]>
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=121969         




------- Additional Comments From gronslet gmail com  2007-04-19 15:39 -------
This problem seems to be solved in kdepim-3.5.6-6.fc6. After upgrading, KMail crashed severly and wiped my local dimap cache (this happened when I pressed Ctrl-J to filter the last collapsed thread of messages in my inbox).

I backed up some stuff, and restarted KMail, had to re-enter all my IMAP folder subscriptions, and update all my filters (they pointed to non-existing folders with some numbers in them), but now - new messages are no longer automatically marked as read upon filtering :)

There is one peculiarity though - after a message has been automatically filtered into a subfolder, I can (correctly) see a bold number next to the folder increase by one, e.g. showing "(1)", but then KMail "synchronize" the folder or something, and the new message disappears from the subfolder (the bold number also disappears), and then it comes back again (and so does the bold number). The new thing with KMail 3.5.6-6.fc6 is that it is still marked as new (as it should be). The scenario described here all happens within seconds depending on the connection speed.

Another thing to notice, is that my folder structure in KMail has changed: in kdepim-3.5.6-6.fc6 all subfolders are directly under my "inbox" (which is nice)
In the previous versions I have had a folder "mail" as the parent of all my subscribed subfolders. Also, I seem to recall that I had a file in my homedir on the IMAP server holding a list of all subscribed folders. I had some issues with folders starting with "~/" or not in that list. (that file is gone now, and I have forgot the name. But "grep name_of_subscribed_folder .*" should find it if you have it I think)

Maybe this was the root to all the problems in the first place?

Anyway, just wanted you to know the great news :)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.