from logs.
Well, enable VERBOSE logging, and the specific recipes will stand out. As
the flag in question ('i') is really only suitable for filter and
deliver-to-program recipes. My guess is that you're using it on a delivery
to mailbox.
[snip]
None of what you provided shows a *RECIPE* -- the stuff with flags,
conditions, and action. The error explicitly cites "flag", so you should
be looking for flag lines...
---
Sean B. Straw / Professional Software Engineering
---------------------------------------------------------------------------
Everyone,
Thanks a bunch!
Your deductions were so correct. Here was the offending rule
# Check for a virus in this packet and if found them dump it
VIRUS=`/usr/local/bin/clamscan -v --mbox --disable-summary --stdout -`
:0 Di
* VIRUS ?? FOUND
{
:0
{ SUBJ_=`formail -c -xSubject: \
| sed -e 's/^[ ]*//g' -e 's/[ ]*$//g'` }
:0
{ DATETIME_=`date "+%Y%m%d %k%M%S"` }
:0
{ VIRUS_SHORT=`basename "${VIRUS}"` }
:0 fhwi
| formail -I"Subject: ${VIRUS_SHORT} ${DATETIME_} ${SUBJ_}"
:0 fhwi
| formail -A"X-SMILE_Virus: Virus ${VIRUS_SHORT}"
:0:
/log/e.viral.txt
}
When I removed all of the 'i' suffixes it worked without the notation in the
logs.
I'm afraid I am still in the 'see monkey do monkey' stage with procmail so
thanks for
your help.
Greg Ennis
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail