Script question

[Lt. Commander]

> -------------------------------------------------------
> Bingo! You got it. Works fine.
>
> Funny tho, I have used that little sh shell intro for years to lead into
> various scripts. This is the first time it didn't work as I had it.
>
> Oh, well... now it's fixed and that's all that counts.
>
> Once again many thanks for the help!!
>
> --Jason
>
>
> --
-------------------------------------------------------------

I received some excellent help on straightening out my scripts, but here;s the reason I need the script and it's maddening that I should even need it if procmail could get it right or my recipes worked. Spamass is doing a fine job of IDing spam, however I've tried all of the recipes to catch emails above the threshold of 6 to no avail on way too many spams. Below follows an example:

 First, spamass reports:
X-Spam-Flag YES
X-Spam-Status YES, hits=77.60 required=6.00

This rules are not catching them though and get on through:
## spam
:0:
* ^X-Spam-Status: YES
$SPAM

## spam rule
:0:
* ^X-Spam-Status:(.*\<)?YES
$SPAM

## New spam rule
:0:
* ^.*(shortcircuit=spam)
$SPAM

## Test #2 Catch spam tagged by sa-milter
:0:
* ^(X-Spam-Status: Yes)|(X-Spam-Flag: YES)
$SPAM

I don't know what's wrong but certainly need a better set of rules I guess instead of the patch script to snag IPs the "high spams" produce.

Anyone with any ideas?

Thanks,
/Jason