[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:       Andreas Gungl <a.gungl () gmx ! de>
Date:       2004-01-01 13:28:11
Message-ID: 20040101132811.676.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 a.gungl@gmx.de  2004-01-01 14:28 -------
Subject: Re:  filters don't work anymore as in 3.1.4

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.

On Donnerstag, 1. Januar 2004 13:47, Martin Koller wrote:
> On Wednesday 31 December 2003 22:15, Andreas Gungl wrote:
> > ------- Additional Comments From a.gungl@gmx.de  2003-12-31 22:15
> > ------- Martin, in your (second, extended) log I've found:
> >
> > kmail: ####### KMFilterMgr::process: going to be apply filter rule
> > Match any of the following: "<size>" <greater> "0"
> > kmail:
> >
> > Can you countercheck with:
> > - Match ALL of the following
> > - "<size>" <greaterOrEqual> "0" (I mean size >= 0, don't know the exact
> > phrase in the moment.)
> >
> > If that doesn't shed some light on the problem, then it's getting
> > really difficult. I think, we'll have to add more debug output. At
> > least the rule is used and somehow it's not considered to match the
> > message. I hope, we can solve the issue before 3.2 is tagged.
>
> First of all - A happy new year!
>
> I changed now the rule to >=0, I have still the same problem but some
> changes also:
>
> The interesting sections are:
>
> kmail: ####### KMFilterMgr::process: going to be apply filter rule Match
> all of the following:
> "<size>" <greater-or-equal> "0"
> kmail:
> kmail: ####### KMFilterMgr::process: filter rule did match
> kmail: ####### KMFilter::process: going to apply action remove header
> "X-Spam" kmail: ####### KMFilter::process: going to apply action pipe
> through "spamoracle mark"
> kmail: ####### KMFilterMgr::process: going to be apply filter rule Match
> all of the following:
> "X-Spam" <contains> "yes"
> "Subject" <contains-not> "[Bug"
> kmail:
> kmail: ####### KMFilterMgr::process: going to be apply filter rule Match
> all of the following:
> "
>
> Interesting here is, that on incoming mail the filter gets now applied,
> but it seems that kmail did not recognize the added X-Spam header
> afterwards (in the rule after this one).
>
> But more important, it seems that what comes out of spamoracle with that
> filter is NOT the mail which is then stored in kmail, because if I look
> at the mail-source (pressing "V"), I don't find the X-Spam header!
> So maybe that is the source of the whole problem.
>
> Was there a change in the handling of receiving mails from 3.1.4 to 3.2,
> so that the received mail is somehow only temporary and only this one is
> modified by spamorcale ?
>
> Now look what happend when I pressed CTRL-J:
>
> ...
> kmail:
> kmail: ####### KMFilterMgr::process: going to be apply filter rule Match
> all of the following:
> "<size>" <greater-or-equal> "0"
> kmail:
> kmail: ####### KMFilterMgr::process: filter rule did match
> kmail: ####### KMFilter::process: going to apply action remove header
> "X-Spam" kmail: ####### KMFilter::process: going to apply action pipe
> through "spamoracle mark"
> kmail: ####### KMFilterMgr::process: going to be apply filter rule Match
> all of the following:
> "X-Spam" <contains> "yes"
> "Subject" <contains-not> "[Bug"
> kmail:
> kmail: ####### KMFilterMgr::process: filter rule did match
> kmail: ####### KMFilter::process: going to apply action remove header
> "X-Spam" kmail: ####### KMFilter::process: going to apply action file
> into folder "JUNK-mail"
> kmail: ####### KMFilter::process: going to apply action mark as "U"
> k
>
> So it seems by applying the filters manually, the mail is then really
> modified and therefore also used by the next filter.
>
> I attach the full log.
>
>
> Created an attachment (id=3912)
 --> (http://bugs.kde.org/attachment.cgi?id=3912&action=view)
>  --> (http://bugs.kde.org/attachment.cgi?id=3912&action=view)
> kmail.log.goe0.gz
[prev in list] [next in list] [prev in thread] [next in thread]