On Mon, Sep 24, 2007 08:56:13 AM -0700, Bart Schaefer
(barton(_dot_)schaefer(_at_)gmail(_dot_)com) wrote:
Er, no. Or rather, not if he's running procmail from a script
rather than as part of MTA local delivery. Procmail has nothing to
do with generating the bounce message -- the MTA does that, upon
receiving the 77 exit code from procmail. So if there's no MTA
involved, there's no bounce.
Of course this means the same procmailrc can't be used at delivery
time and at script time, but that doesn't appear to be what's wanted
here.
Exactly. This one I'm building with your help is a procmailrc that
will be used only from within a bash script launched from cron. This
is why I am trying to avoid any variant that makes procmail create
other copies of the messages: if procmail returns one of the exit
codes that my script recognizes, the script itself moves the messages
where I want (this also happens if I choose without realizing it 77 or
some other "reserved" exitcode, since it the script that catches it,
nobody else).
If the exitcode is not one of those I hardcode in the script, nothing
happens. And eventually, all the messages (=files) older than one week
or month will be simply moved with mv (not procmail) to some
"hey-figure-out-why-these-weren't-processed" mailbox
Marco
--
Your own civil rights and the quality of your life heavily depend on how
software is used *around* you: http://digifreedom.net/node/84
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail