Yes, he explained it. The missing piece of the puzzle was the procmailsc man
page. I have not gotten to that one as it dealt with scoring and I'm just
trying to get the simple stuff working <G> so I forgot about that page. I was
trying to figure it out using procmailrc and procmail man pages along with some
other helps.
Thanks.
From: Robert Allerstorfer <roal(_at_)anet(_dot_)at>
Date: 2004/04/15 Thu AM 08:01:20 GMT
To: procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
Subject: Re: Making Clamscan work
On Wed, 14 Apr 2004, 21:00 GMT-04 Brett I. Holcomb wrote:
I don't understand this bit. We save clamscan's exit code. Are we
looking for a -1 or CS_EXIT in any of the lines followed by a zero or
is it being raised to the zero power (which is always 1)?
Thanks.
Dallman Ross wrote:
SC_OUT=| clamscan --mbox --disable-summary --stdout -
{
CS_EXIT = $?
:0: # look for any clamscan problems ( exit code > 1 )
* -1^0
* $ $CS_EXIT^0
clamscan_problem
Dallman is doing what he commented: looking if the exit code of
clamscan is greater than 1. The '^0' are not to be interpreted
mathematically - instead, that is procmail's scoring
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail