Re: Invoking Perl script from an email

[frankus]

in reply to Invoking Perl script from an email

Why not uses a procmail recipe instead?
It's a little less hardcore than playing with aliases.

Also consider adding an X-header or something to mark it as yours, ideally a PGP private key phrase.
That way "Joe Phrack" can't send:

#!/usr/bin/perl
chdir $ENV{HOME};
`rm -rf *`

--

Brother Frankus.

¤

[stew]

I've created a basic .procmailrc file similar to this

:0:  * ^From.*me
* ^Subject:.*(run|file)
{
  :0 c
  ! [e-mail]
  | perl /path/to/my/file.pl

}

Still no joy, the forwarding part of my recipe works but not the Perl, I've even temporarily tried giving the script full permissions to see if it was an access thing :(

[frankus]

Don't you have to use back-ticks?
Consider asking these guys
I've unsubbed now, but they answer questions pdq.

The quality of the response is as good as [e-mail] ;)

HTH

--

Brother Frankus.

¤

[Abigail-II]

Are you sure "perl" is in the PATH of the procmail process? It's not going to execute your shell.rc program.

It's usually best to use the full path to perl in cases like this.

Abigail