Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: bakedjake
Does anyone have a sendmail background that give me the "step-by-step" on this?
It's been a while since I've done any real perl coding, but I would suggest that it's possible that your host has isolated some system commands. You might want to check with them. CGI-to-Sendmail gateways have often been used as a source for spam-mail enthusiasts prompting some hosts to kill the ability to use such systems.
%ln -s /usr/bin/perl
This supposed to allow a .forward file to run perl programs. Does this seem correct?
That being said, you can just wrap the call to the perl interpreter somehow, so that the sendmail process doesn't notice it.
Make sure you have the line "#!/usr/bin/perl" (without the quote) as the very first line of your script and give the file execute permissions so that the sendmail process can run it. Then you can have the .forward file just call the script directly, without mentioning perl. Of course, if sendmail is smart, then it will catch this trick and balk anyway.
Alternatively, create a file emailcapture.sh, with the following contents:
exec /usr/bin/perl /home/virtual/talklist/home/httpd/cgi-bin/arplus/emailcapture.pl
(unwrap the second line if necessary) give it execute permissions, and then just call this file from .forward.
The net effect of either method should be identical to what you tried at first, unless the current sendmail versions have really sophisticated security checks built in.
Note that you *are* potentially opening security holes by running perl scripts from .forward, so you better make sure your script is next to trivial and you understand *completely* what it does.