Version: (using KDE KDE 3.4.0) Installed from: Unspecified Linux While going through anti-spam wizard, window for choosing target folder for unsure isn't active/accessible. At least with bogofilter and gmx.
Well, if you can tell me how to determine messages classified by SpamAssassin as "unsure", then I'll certainly willing to implement that functionality. It's just that I don't know how to find out that a message got classified as unsure with the mentioned two tools. That's why the wizard intentionally doesn't allow to select a folder.
Didn't it work properly in betas? I'm not that familiar with bogofilter, but I guess -o parameter is used for setting cut-off parameter. Filter actions would just file the messages with, let's say, 0.40-0.90 spamicity statistic to unsure or whatever folder. I'd look deeper into that, but I'm somewhat busy right now. Here's some quicky googled reference, I guess it's not outdated in any means: http://david.jamesnet.ca/kde/kmail_bogofilter.html
Am Dienstag, 1. März 2005 11:48 schrieb Xukasz Fibinger: > Didn't it work properly in betas? I'm not that familiar with bogofilter, No, there has been no change in the handling for Bogofilter for a long time. SpamBayes was the tool because of which we introduced the unsure handling. And it has been added only for that tool so far. > but I guess -o parameter is used for setting cut-off parameter. Filter > actions would just file the messages with, let's say, 0.40-0.90 spamicity > statistic to unsure or whatever folder. Sounds reasonable. Here is a patch for kmail.antispamrc which should give you the expected behavior: --- kmail.antispamrc.orig 2005-03-01 13:36:49.402527962 +0100 +++ kmail.antispamrc 2005-03-01 13:37:54.997238537 +0100 @@ -31,16 +31,16 @@ Executable=bogofilter -V URL=http://bogofilter.sourceforge.net PipeFilterName=Bogofilter Check -PipeCmdDetect=bogofilter -p -e -u +PipeCmdDetect=bogofilter -p -e -u -o 0.90,0.40 ExecCmdSpam=bogofilter -N -s ExecCmdHam=bogofilter -S -n DetectionHeader=X-Bogosity DetectionPattern=(yes)|(spam\b) -DetectionPattern2= +DetectionPattern2=unsure DetectionOnly=0 UseRegExp=1 SupportsBayes=1 -SupportsUnsure=0 +SupportsUnsure=1 ScoreName=Bogofilter ScoreHeader=X-Bogosity ScoreType=Decimal Please note that the support of different versions for a tool might be a difficult task. See the DetectionPattern above, it makes sure that older and newer Bogofilter versions work. I'm not sure about the options mentioned in the URL you've provided. So it would be really cool if somebody could provide a statement telling this and that is needed to make KMail work fine with Bogofilter and who would take care for regressions due to version changes. OTOH I've planned to change the spam tool detection system used in KMail in the next release, so that KMail has more flexibility to prepare the filters depending on the version of the found tools. Regards, Andreas
Just wanted to add that given solution works flawlessly for me and I think it should make its way into 3.4.1.