Bug 277744

Summary:	spam filtering is broken
Product:	[Applications] kmail2	Reporter:	Anders Lund <anderslund>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ilya.hegai, montel, quazgar
Priority:	NOR
Version:	2.1.1
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:

Description Anders Lund 2011-07-14 08:54:27 UTC

Version:           2.1.1
OS:                Linux

I use spam filtering set up using the built in wizard and bogofilter. This produces two filters, one running bogofilter which adds a header to the mail, and one that uses the provided header to move spam mails into a folder. The second filter is very often either not run, or at least mails are not correctly moved. This problem was also discussed at forum.kde.org. 

Reproducible: Didn't try

Steps to Reproduce:
use kmail2 with spam filtering

Actual Results:  
broken spam filtering

Expected Results:  
working spam filtering

OS: Linux (i686) release 2.6.39-ARCH
Compiler: gcc

Comment 1 Anders Lund 2011-07-15 16:53:53 UTC

Filtering manually (hitting ctrl + j), the "spam handling" filter is not run either, or at least the message is not correctly moved to trash, though the bogofilter sets the expected header (X-Bogosity: Spam, tests=bogofilter, spamicity=1.000000, version=1.2.2).

Comment 2 Laurent Montel 2011-07-17 08:19:32 UTC

How I can test a spam ?:)

Comment 3 Laurent Montel 2011-07-17 08:22:32 UTC

There was a pb with header before, now it's fixed in 4.6/4.7/master.
Could you retest it ?

Comment 4 Anders Lund 2011-07-17 17:42:33 UTC

I can test when a updated archlinux package is released.

Comment 5 Ilya Hegai 2011-08-10 11:05:40 UTC

problem still presents in kmail 4.7.0

Comment 6 Tobias Koenig 2011-09-17 21:21:56 UTC

Hej,

this has been fixed today in master.

Ciao,
Tobias

Comment 7 quazgar 2012-01-21 19:14:45 UTC

(In reply to comment #6)
> this has been fixed today in master.

Hello, into which release did/will get the master go into?

4.7.3 shows the same effects, probably caused by the filter program piping not having effects on the content that was parsed by later filters (Are they using the old, cached email?).

Cheers,
Daniel