TopPost:
Sorry for this stupid question below -- only reason (and not an excuse) was
that I was a 3-day old "baby procmailer" and without regexp skills.
However, re-reading a bunch of docs, I now understand the use of ORing
which solved this issue.
I really find Procmail v3.22 (my first install) very, very helpful and when
combined with Sendmail & SpamAssassin, is a powerful set of tools for
controlling....
Thanks to the list....
Date: Fri, 04 Jul 2003 21:53:13 -0500
To: Procmail
From: "Jack L. Stone" <jacks(_at_)sage-american(_dot_)com>
Subject: Trapping SPAM - More
Thanks to this list, I have my global procmailrc file recipes pretty-well
trapping the tagged spam via SpamAssassin. For the spam, I'm using two
separate conditions, when it dawned on me that they could be combined by
testing for the first condition and then looking for the second. I depend
on the first condition for 99% of the spam diverted to the $SPAM folder.
Here is how the recipes look now:
<snip of variables>
PATH=/bin/csh
MAILDIR=${HOME}/mail
DEFAULT=/var/mail/${LOGNAME}
SPAM=/path/to/spam-mail
# All mail tagged as spam (eg. with a score higher than the set threshold)
# is moved to "spam". NOTE: Remove Lock colon if /dev/null is used.
:0:
* ^X-Spam-Status: Yes
$SPAM
## Use this to catch any missed above for ? reason
:0:
* ^Subject:[ ]\[SPAM Content]
$SPAM
My question is how can I do this:
condition 1: Test to see if X-Spam-Status is Yes or No
- if Yes, then send to $SPAM
- if No, then test for condition 2
condition 2: Test for Subject:[ ]\[SPAM Content]
- if match found, send to $SPAM
- if no match, send to DEFAULT
Thanks for any additional help....
Best regards,
Jack L. Stone,
Administrator
Sage American
http://www.sage-american.com
jacks(_at_)sage-american(_dot_)com
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail