I have KDE 4.10.2 running under OpenSuse 12.3. I have the Spamassassin filters installed in KMail and configured to send spam to a spam folder. I installed Spamassassin using Kmail’s wizard. Usually it works fine, but on a couple of occasions it started to send all my e-mail to the spam folder. If I deactivate the Spamassassin and spam handling filters, apply the changes, and then reactivate them, everything works fine again. I’ve looked at the emails and Spamassassin seems to be working correctly as the X-Spam-Flag is marked NO. Nonetheless the mail ends up in the spam folder so I’d suspect it is a Kmail issue. The problem has occurred a couple of times, but at rare intervals.
I haven’t seen this reported, so I’m wondering if it is something in my configuration files.
This is actually a bug, I have experienced the same behaviour, actually even worse. I had random “trashing” occurring to some mailing lists, then to others not. The trashing occurred also when the email address had its own dedicated filter. I noticed that the problem occurred with bogofilter, but apparently with you it is spamassassin. It would be nice to know if this started like with me the date around the 1st of April or near by. I think this cam in with the KDE-Pim update recently. Since then the orthographic corrector works with underlining again, since a long long time it was broken. Now filtering of spam seems broken. Do you also experience problems with other filters (like mail from mailing lists is not filtered at all or put into the wrong folder?
Kmail 2, relying on akonadi, is a total mess.
I have read in many forums and mailing lists that it is unstable and hardly usable.
Filtering is very broken.
This is really a pity because i have been using kmail since 2003 without many problems and it’s been really stable.
And now, with opensuse 12.2 and kmail2 i am living a nightmare to keep my mails and handle them almost correctly.
Filtering is broken, archiving is broken and storage seems to some extend broken. Also indexing of the messages, and it was a good idea to deactivate it by default now. What is difficult to understand is this:
a) due to the impracticability of the solution of akonadi as application base?
b) if it is practicable, is this lack of prioritisation?
c) lack of personal that makes it impossible to fix the existing errors?
d) a strategy to promote thunderbird?
e) lack of realism
f) ? what ever else
What is puzzling me, the errors all well known, the bugs reported but there is simply no fix, neither seems there be any interest for it. Another example of such “surprising abandon” was kopete. A very good program all of a sudden without reason dropped, quasi abandoned then, all of a sudden again continued. New features are announced everywhere, but none of the bugs are fixed. Maybe the program Kmail will have a dramatical change? So that the responsible devs do feel it would be a waste of time to fix bugs. Then they could communicate it.
But then, suddenly some things are fixed, but other functions in the very same moment regress. Really weird.
Filtering is broken, archiving is broken and storage seems to some extend broken. Also indexing of the messages, and it was a good idea to deactivate it by default now. What is difficult to understand is this:
I do have these problems with simple mailing list filtering as well. Once again it is seemingly random - sometimes it works, sometimes not. I too have used Kmail for a number of years and really don’t want to switch to something else.
Another symptom - when I reboot on occasion I’ll get an akonadi or Nepomuk related error message when Kmail comes up - last time I was told that I needed to install the Soprano backend and that Nepomuk was disabled because it was missing. Unfortunately, the backend was installed and Nepomuk was running so the message was seemingly bogus.
What is puzzling me that none of you guys seem to have posted a bug report or posted onto an existing bug report so to give the reports more strength and to point out that the problem is widespread.
What version of KDE are you running and what version of openSUSE when these errors take place?