What am I missing, Em4i1 from filePro

[Fairlight]

You'll never BELIEVE what Robert T. Repko (R Squared Consultants) said here...:
> For several years I have been running a script that generates a file 
> from filePro and then email (using lightmail) it to the client.  This 
> has work great but now I need to change the procedure and mail from 
> within my filepro processing table.  I say to myself 'no problem, use 
> the system command to send the email'.  Well, after about a week of 
> beating my head against a wall I give up and am asking for another 
> set of eyes to see if they can spot what I am doing wrong.  
[snip]
> I'm stumped, can anyone think of a reason why it would not email from the
> system command.

I wish you'd come to me sooner, Robert.  I hate the fact you ended up
frustrated after a week.  Check your email, and you'll see I have supplied
what I believe is the problem, as well as several solutions we can
approach.

For the record, there is an issue with IndigoStar's perl2exe, of which
only -one- version was ever released for SCO, which was discovered only
about 2-3 years after I released LightMail for all supported platforms.
In essence, it doesn't like SUID, and it typically core dumps under
such conditions.  Perl2exe is the program that I used to make a Perl
program into a standalone executable back then, just so we're clear.  The
problem isn't actually with LightMail proper, it's with the executable
bootstrapper, although that's a fine distinction some might not grasp.

The solution(s) range through:

1) Use PFSYSEDUID=OFF if that's an option.

2) I can supply a SUID-friendly source version, but one needs perl
   installed and needs to install two modules for LightMail to run.

3) I can try a different approach with PAR and see if that works.  I find
   PAR to be a better packager with more stable results, these days.

Bests,

mark->
-- 
"Moral cowardice will surely be written as the cause on the death
certificate of what used to be Western Civilization." --James P. Hogan