On Tue, 2003-11-04 at 12:28, Jeffrey Stedfast wrote: > delete actions are saved until the very end. this way if you have > filters which would copy the message elsewhere, it doesn't get copied > with the delete flag.
> so... this would not be a bug. I can understand deferring the delete, but 2 things still puzzle me. First, last action on this filter is "Stop Processing"; why would late filter fire on the message. Second, why does it work properly then when I right-click on the message and say 'apply filters'. Seems like such inconsistent behavior should be a bug. John > Jeff > > On Tue, 2003-11-04 at 13:23, [EMAIL PROTECTED] wrote: > > I think this may relate to problematic behaviour that I have found. > > > > I am running Evo 1.4.5 and in a desire to read less information, I have > > been trying to use filters on subjects to delete message threads that I am > > not interested in. If these messages are from a mailing list where there > > is already a filter to move to another mailbox, the delete filter is not > > run regardless of how I order the filters in the list. > > > > Thanks, > > Lloyd > > > > > > > I have bogofilter in place which puts my spam into a separate folder, > > > but I also have put a simple shell filter in place to separate out all > > > of these bogus MS security/virus emails that come in on my accounts and > > > them as they arrive. > > > > > > The filter is just a shell and looks like this: > > > > > > cat |egrep -i "^content-"| egrep -i -e '\.exe' -e '\.pif"' -e '\.com' -e > > > '\.bat' 2>&1 >> /dev/null > > > exit $? > > > > > > The exit code of the second egrep is the exit status of the shell. > > > (There's probably a nicer regexp that would eliminate the need for two > > > egreps, but this is at the quick & dirty stage right now.) > > > > > > My evolution filter verifies that the email has an attachment and if so, > > > runs the shell command on it. If the return is 0, it deletes the > > > message. Here is the rule. > > > > > > <rule grouping="all" source="incoming"> > > > <title>VIRUS</title> > > > <partset> > > > <part name="attachments"> > > > <value name="match-type" type="option" value="exist"/> > > > </part> > > > <part name="pipe"> > > > <value name="command" type="command"> > > > <command>/home/jrh/bin/viruscheck</command> > > > </value> > > > <value name="retval-type" type="option" value="is"/> > > > <value name="retval" type="integer" integer="0"/> > > > </part> > > > </partset> > > > <actionset> > > > <part name="delete"/> > > > <part name="stop"/> > > > </actionset> > > > </rule> > > > > > > The odd thing is that this rule is much earlier in the stack than my > > > bogofilter rule. When email is checked, these emails end up in my spam > > > folder (per bogofilter.) > > > > > > If I then select and right-click on these 'infected' emails and apply > > > filters, this filter fires and the email is deleted. > > > > > > Why would it work manually, but not when the email is being received. > > > > > > Thanks > > > John > > > > > > -- > > > John Harlow <[EMAIL PROTECTED]> > > > > > > _______________________________________________ > > > evolution maillist - [EMAIL PROTECTED] > > > http://lists.ximian.com/mailman/listinfo/evolution > > > > > > > > _______________________________________________ > > evolution maillist - [EMAIL PROTECTED] > > http://lists.ximian.com/mailman/listinfo/evolution -- John Harlow <[EMAIL PROTECTED]> _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
