This may be a little tricky to describe, so please bear with me ... (or, if you don't care for bears, you could just duck ... )

Revise the "Rules" area as follows:

1. First, we'll put headings on the existing boxes for each rule. From left to right, we'll call them "Where", "When", and "What". So, "The 'From' field" is "Where", "contains" is "When", and "spammersall.com" is "What".

2. Next, on the right, we'll add a drop down labeled "Next", with the values (blank), "and", "or", and "unless". This tells how we want to combine the preceeding rule with the next one.

3. Also, on the left we'll add a checkbox labeled "Drop". When checked this allows us to remove any rule, not just the last one.

So an example might look like this ([_] indicates a checkbox):

We could complicate things further by adding the following values to the "Next" options: "and (", "or (", "unless (", ") and", ") or", ") unless", ")" ...

Or, maybe something like this:

Code:

Drop   (   Where...........  When............  What...........   )   Next [__]  [_]  The 'From' field  contains          spammersall.com  [_]  and [__]  [_]  The 'From' field  does not contain  abuse            [_]  (blank)

... but that may be going just a bit too far, eh?

_________________
Lightly scrambled, over-easy and stuffed with all sorts of goodies.

I forgot to mention ...

Yes, this would require an expanded format for the filters file, because of the extra ANDs and ORs, in which case it would be nice if someone would write a small utility to convert "old format" filters to the "new format", but that shouldn't be all that difficult since it's really just a matter of propagating the existing condition as many times as needed.

Or, the "new filters" be given a different file name - say "nufilter" perhaps - which would allow MW to still process both formats.