+++ This bug was initially created as a clone of Bug #186264 +++ I find bug #186264 still present in KDE 4.3.2. I submitted the information repeated below to that bug, but I've received no response and the bug has not been re-opened. Assuming this could be because the devs don't look at old closed bugs, I'm opening a new one. I've not found a report of this bug since the ones closed by the commit that fixed #186264 etc, and there's no indication in the 4.3.3 changelog that it might have been fixed there, so I'm not sure if it's worth downloading and compiling 4.3.3 (or the 4.3 branch) myself to see if it's gone. I still see this bug on KMail 4.3.2 (KDE 4.3.2) with on current Debian "unstable" (package kmail version 4:4.3.2-1) against an IMAP account. Attachment #38457 [details] includes the portions of my kmailrc which relate to filters. I've got 30 emails in my Inbox that match the "arocket" filter, some of which have been there for over 2 days. I've got hundreds of emails that will match my spam filter, if it's ever run on them, but wading through this, or selecting all my emails and running the filter manually is getting to be a *real* pain. Especially as the manual filter seems to sometimes stop and not finish processing emails as well. Turning on the filter log reveals nothing particularly interesting, except for the fact that it seems to run a heck of a lot less frequently than I get incoming emails. Currently (as of 13:48) the last time it ran was 10:20, and it's only run against 5 new emails today, despite me having received well over 50. Please help; this makes KMail almost totally unusable at the moment. If there's anything I can do, let me know.
Filterin incoming IMAP mails works for me. Perhaps you can try with a fresh kmail configuration?
What, we're being reduced to "Your computer's playing up? Try rebooting and see if that helps."? Come on! Free software is *better* than that. My filters (among other parts of my config) took me quite a while to build up, and I don't want to throw them away and spend hours re-entering them, on the off chance that this *might* help and allow *me* alone to bypass this bug, while leaving it in the code for others to potentially trip over. Running the filters by hand every couple of days is preferable to that mindless drudgery. Plus I can think of many things I'd find much more interesting and rewarding, like spend hours installing debug symbols, running kmail through a debugger, and seeing where that leads me. Only I've no idea where to start putting breakpoints. I'd be happy to send you my entire kmailrc by private email if you think that might help. And probably any other config files that might be of use. FWIW, this is still occuring on KMail 1.12.4 - KDE 4.3.4, from the latest Debian unstable packages (mostly 4:4.3.4-1)
Updating summary to reflect that this still occurs on 4.3.4
You can save your kmailrc somewhere, delete the one in the config folder and check whether the problem still occurs with the fresh one. You can always can copy your existing configuration back.
Hmmm....it's kind of working. I removed my kmailrc, restarted kmail, entered details (I now have duplicate identities - the new one I was asked to enter, and the old ones. WTF?) recreated the arocket filter, noticed I'd lost all the UI/theme/toolbar customisations I'd spent ages building up and getting comfortable with ... and went to work. Checking my account externally while I was at work, arocket mail was piling up in my inbox without being filtered by kmail running on my home PC. When I got home in the evening, no new mails had been caught by the arocket filter, but none were showing up in my inbox either. Switching to the arocket folder showed no changes, but switching back to the inbox caused it to suddenly realise I had new mail, and it filtered the arocket emails as appropriate. Will see if this happens again, and report back. I can't keep this up for more than another day or so without switching back to my old kmailrc. As my spam filters aren't currently running (they're set up on the old kmailrc) I now have 957 emails in my inbox, 98% of which are spam.
Ah, I forgot that "interval mail checking" needs manually setting on the account. (Why is this not set by default? It's an IMAP account - it's *supposed* to be a live view of data on the server. When IDLE support is written, will that be turned off by default?) That done, I'm getting email, and the filter appears to be running by itself. I guess that means there's something in my original kmailrc which is causing the problem. So, what now? How do we figure out which bit is wrong so a) I can remove it and restore the rest of my old kmailrc, and b) some KDE hacker can fix the problem with kmail's behaviour when it comes across such a config?
Well, you can always post your kmailrc and see whether it helps. But look at the amount of kmail bugs and you see, that there is just a very small chance that it gets fixed. But if you can find out what is the great difference between your old kmailrc and the working one, that results in the unwanted behaviour - a developer can probably quickly use your work to fix the problem. That's the thing about free software. Currently I can even not exclude the possibility of wanted behaviour because of the configurations in the kmailrc.
"Well, you can always post your kmailrc and see whether it helps." Hmmm....I already posted the parts that related to filters. I'm not sure what else might be useful, but I'm a bit too concerned about my privacy to just post the whole thing to a public website. "But if you can find out what is the great difference between your old kmailrc and the working one," The diff is over 7800 lines long, and I have no idea what I might be looking for. "I can even not exclude the possibility of wanted behaviour because of the configurations in the kmailrc." Any clues as to what configurations might affect the setting to automatically filter mail? *sigh*. I'll have a play and see if I can figure something out. Thanks for the help so far.
Well, you can check in the extended configuration vor each of your filters whether it is really applied to mails going into your inbox.
"Well, you can check in the extended configuration vor each of your filters whether it is really applied to mails going into your inbox." I did. I'll do it again. But does Attachment #38457 [details], which I linked to in my initial report of this bug, not tell you that info?
I didn't even look at your attachment because it wouldn't help. I'm just trying to help you to find out what's wrong and to hunt down the possible bug until a developer has a chance of getting it fixed. Please understand that this is no commercial support center. There are 3000 bugs open for kmail - the more you can find out the more likely a developer can fix the problem.
After installing KDE 4.4.4, I noticed that a few (5-6) of the low-traffic ones started working again. I had a look at my kmailrc to see if there was any difference between those filters and the ones which were not working, and the vast majority of my filters had "apply-on=manual-filtering" only. Sure enough, checking them via the GUI, most filters were not set to be applied to incoming messages. After I turned this on, they all started working again. I have no idea what was going on here. As can be seen from the filter definitions I posted in attachment #38457 [details] to bug #186264, they were definitely set to be applied to incoming messages at the time. And I've not changed anything since. And the filters that started working with 4.4.4 definitely weren't in 4.3.4. But, like I said, it's working now. I also appear to be the only person who ever saw this, so closing as worksforme. *shrug*