Re: 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 *`
[download]

--

Brother Frankus.

Comment on Re: Invoking Perl script from an email Download Code

Replies are listed 'Best First'.
Re: Re: Invoking Perl script from an email by stew (Scribe) on Aug 02, 2002 at 11:32 UTC
I've created a basic .procmailrc file similar to this `:0: * ^From.me ^Subject:.*(run\|file) { :0 c ! stew@my-server.com \| perl /path/to/my/file.pl }` [download] 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 :(	[reply] [d/l]
Re: Invoking Perl script from an email by Abigail-II (Bishop) on Aug 02, 2002 at 13:37 UTC
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	[reply]
Re: Re: Re: Invoking Perl script from an email by frankus (Priest) on Aug 02, 2002 at 12:52 UTC
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 beginners@perl.com ;) HTH -- Brother Frankus. ¤	[reply]