At 15:44 2001-04-06 -0500, Kip Turk wrote:
# the poplock removal stuff
:0:
* ^TO_(_dot_)*root(_at_)wcc\(_dot_)net
* From:(_dot_)*ums(_at_)wcc\(_dot_)net
* Subject:.*superduperscripttoremovepoplocks
{
:0bc
/root/scripts/diepopper
:0
| /root/scripts/diepopper
}
/dev/null
First, that /dev/null is bogus -- the delivery for the preceeding
conditions is found within the braces.
Next, you really should enable verbose logging and take a look at the log file.
Third, you have no indication here that you do anything to ERASE the file
-- the contents will be APPENDED. Want to know why you have five copies of
the test rule in that file? Because you've run the mail through five times.
I've tried the second portion without the "c", but it had no effect.
Second portion? You mean where the diepopper script is executed?
See 'man procmailrc', then replace the content within the braces with the
following:
# erases the content of the script file (we could just use rm)
:0Wi
|type /dev/null > /root/scripts/diepopper
# places the body of the message into the file
:0bc
/root/scripts/diepopper
# sets the execute mode, and then executes the script.
:0ai
|(chmod +x /root/scripts/diepopper;/root/scripts/diepopper)
See the URL in my .sig for info about debugging procmail scripts.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail