In my case I don't really care when it runs just that it runs in response to an error in the perlscript.
I guess that just isn't possible. although I cannot use "save" if I had a bootstrapping perlscript that called my other perlscript I could use mail::audit to save the messages to a mailbox when the perlscripts exit status indicated error. On 3/24/08, Phil Pennock <[EMAIL PROTECTED]> wrote: > > On 2008-03-24 at 14:19 -0500, Robert Nicholson wrote: > > From reading the documentation it doesn't look like it's possible to > access > > the return code of the pipe in order to conditionally take some action. > > Correct. In particular, "filter.txt" supplied with Exim notes: > > ----------------------------8< cut here >8------------------------------ > Remember that, as was explained earlier, the pipe command is not run at > the > time the filter file is interpreted. The filter just defines what > deliveries > are required for one particular addressee of a message. The deliveries > themselves happen later, once Exim has decided everything that needs to be > done > for the message. > > A consequence of this is that you cannot inspect the return code from the > pipe > command from within the filter. Nevertheless, the code returned by the > command > is important, because Exim uses it to decide whether the delivery has > succeeded > or failed. > ----------------------------8< cut here >8------------------------------ > > -Phil > -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
