Bug 136339 - spam score display in fancy headers does not seem to use configuration in home directory
Summary: spam score display in fancy headers does not seem to use configuration in hom...
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
Depends on:
Reported: 2006-10-26 16:04 UTC by Martin Steigerwald
Modified: 2015-04-12 10:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Martin Steigerwald 2006-10-26 16:04:05 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux


during integrating CRM114 with KMail (see bug #136261) I found that the SPAM score display does not seem to use the configuration in home directory. 

How to reproduce:

1) move /etc/kde3/kmail.antispamrc (or where it is in your distribution) 

2) test score display, it should not work... antispam wizard still works 

I found this as I had the kmail.antispamrc with the CRM114 entry in the ~/.kde/share/config and the original one from the distribution in /etc/kde3. KMail then showed scores for SpamAssassin and co, but not for CRM114. Once I copy the kmail.antispamrc to /etc/kde3 and restart KMail I get those CRM114 scores in the fancy headers display.

Comment 1 Laurent Montel 2015-04-12 10:11:41 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.
Comment 2 Martin Steigerwald 2015-04-12 10:52:59 UTC
Well as CRM114 filtering and spam score display is integrated since a long time and thus uses global configuration, I don´t know whether this bug still happens or not. I don´t use local spam filtering anymore until I summon up the courage to try to use it again (see bug #319226).