Daniel Lorch wrote:
<> > Because after a piece of mail is delivered, procmail is finished and
<> >stops, maybe? That's like asking why when you turn your reading lamp off it
<> >doesn't shine any longer...
<>
<> Ah sorry. this was a simplified example of a recipe in a more
<> complex scenario.
[ ... ]
<> VERBOSE=ON
<> LOGFILE=a.log
<>
<> EXITCODE=99
<>
<> :0fw
<> | /usr/local/bin/spamassassin
<>
<> EXITCODE=99
<>
<> :0W
<> |/usr/bin/filepipe /usr/local/bin/vdeliver >&2
<>
<> EXITCODE=99
<>
<> HOST
[ ... ]
<> That's what confuses me. Until procmail reaches "HOST" it
<> doesn't know that vdeliver will be the final, delivering
<> recipe and should be assigning the value to EXITCODE, no?
The first person's response, which you didn't attribute, is still the
correct answer. The pipe into filepipe/vdeliver is the delivering
recipe. Once that's completed succesfully, procmail dusts it's hands
and goes away.
The +reason+ it is a delivering recipe and the pipe to spamassassin
isn't is because of the "f" flag on the spama recipe. Check the
procmailrc man page.
Reto
--
R A Lichtensteiger rali(_at_)tifosi(_dot_)com
"Remember the KL10 is an oversexed mutant with these strange bulging
growths oozing out of random body parts, all of which have to be
duplicated no matter how bizarre." - Ken Harrenstien to its-lovers
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail