[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 69418] filters don't work anymore as in 3.1.4
From:       Martin Koller <m.koller () surfeu ! at>
Date:       2004-01-01 14:03:49
Message-ID: 20040101140349.11135.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=69418     




------- Additional Comments From m.koller@surfeu.at  2004-01-01 15:03 -------
Subject: Re:  filters don't work anymore as in 3.1.4

On Thursday 01 January 2004 14:28, Andreas Gungl wrote:
> This looks like a bug which has been considered to be fixed.
>
> ############### (commited 22.12.2003)
> CVS commit by kloecker:
>
> Fix bug 69860 (output of pipe through sometimes not used). This also fixes
> ad hoc filters. Based on patch by Andreas Gungl. Reviewed by Don.
> ###############
>
> I need some more information to debug that problem. First I need to know
> what change triggered the rule to use spamoracle. Was it "size >= 0" or
> "Match all ...". Second I would like to know how the message looks like
> after spamoracle was applied. Can you create a small shell script
> (one-liner: spamoracle mark | tee ~/filter result ) and use that in the
> Pipe Through action.

OK, I think we've got it:
The filter on incoming message does pass spamoracle without modification - 
that is due to the fact, that spamoracle does not recognize the input as a 
mail I think.
I checked why, and have seen that the incoming message does not have the very 
first line

- From dermalptch1zx@rogers.com Thu Jan  1 14:45:45 2004

The input to spamoracle starts with the

Return-Path: <dermalptch1zx@rogers.com>

Header.

When I save the received mail as plain text, I see this first "From" line, and 
when I feed this by hand through spamoracle, it then does get the X-Spam 
header!!

The second issue regarding the ">=0" match:
I changed it back to match "any", and it still works (matches).
I double checked and changed also back to ">0", which does _not_ match.

So this seems to be a second bug.

- --
Best regards/Schöne Grüße

Martin
registered as user #332716 with the Linux Counter, http://counter.li.org

       Some operating systems are called 'user friendly',
             Linux however is 'expert friendly'.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/9ChOHmdPoI37D4YRAonEAJ4jlSCwkLoYa6J6m/7zUB0wPyWB3gCgwHel
8cquGGRhUckhJVEclHM0YPk=
=VBqo
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]