Version: 1.2.5 (using KDE 3.5.7 "release 10.1" , openSUSE )
Compiler: Target: x86_64-suse-linux
OS: Linux (x86_64) release 220.127.116.11-0.3-default
I recently upgraded to KDE 3.5.7 using the rpms for OpenSuse 10.2 (x86_64 version). I connect to an IMAP server. all messages now remain in the inbox and are not filtered into the proper folders. If I press Ctl-J on an individual message it is filtered to the proper folder. If I highlight a group of messages and press Ctl-J, only 1 message is moved. All other messages remain in the inbox, but have a line through them. To remove the line and use the inbox I need to move to another folder and then return to inbox.
Previously when the filters stopped working I would close Kontact and restart it and the filters would be fine. Nothing I have tried gets the filters working, other than pressing Ctl-J message by message.
Thsi began as soon as I upgrded to kde 3.5.7 using the rpms found on the OpenSuse buildservice
Update again. This bug has already been fixed in the OpenSuse packages.
Also see http://lists.kde.org/?t=117881133300002
I am sorry but there is no additional update for the openSuSE packages. I am getting the rpms from
The file is kdepim3-3.5.7-7.1-x86_64.rpm dated May 18, 2007. I even reinstalled that package. No difference. I checked the thread mentioned in Additional comment #2, but my problem is not that kmail leaves the messages in the inbox after filtering, but that it does not move the messages from inbox to the correct folder. My filters are from the IMAP inbox to other IMAP folders, with no messages in local folders.
Since other people don't have this problem it must be an openSuSE problem. i will ask there as well.
See my comment #3 above. I forgot to reopen the bug when I submitted that comment. Comment #1 indicates the bug has been fixed in the openSUSE packages. I have the packages dated 5-18-07, but the problem remains. If I am missing something I apologize.
You are not missing something, the bug fixed in the openSuse packages is another one.
The bug you have reported seems to be another case of bug 126182, which for some reason seems to happen more often in 1.9.7.
Therefore I'll close this as a duplicate.
*** This bug has been marked as a duplicate of 126182 ***