Re: Not executing the piped script?

Hi there, I already tried all the ways of specifying the path to the

script, including $HOME/scriptname, but it makes no difference.

Basically my test script just opens and writes to a text file, which has

universal read / write / execute permissions for now.  But it doesn't do

it (but does work from the command line)!  Doesn't touch the text file in

any way.  Procmail.log tells me:


procmail: Executing "/home/inbound/inbound.pl"


But no other information.  Is there anything about general configuration

that could cause this / permissions to directories, or anything?  I'm sure

I had this working before but when I've come to it recently, it seems to

have stopped.


Cheers


Kirk.




On Sat, 22 Jun 2002, Timothy J. Luoma wrote:


> On Fri, 21 Jun 2002, Kirk Bowe wrote:

>

> > Hi there, what are the reasons why procmail would say that it is executing

> > a piped perl script, but doesn't actually do it?  This is the recipe:

> >

> > :0

> > * ^TO_inbound\-\/.*

> > | ~/inbound.pl

>

> Common 'gotcha'

>

> man procmailrc | fgrep '~'

>

> 	Procmail does not support the expansion of `~'.

>

> Try $HOME/inbound.pl

>

> TjL

>

>

>


_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail