You may be up a creek, or there may be a way to snaggle past the little
annoyances. You are certainly in a case where you don't have a shell, so
don't have stdin/stdout/stderr available normally. However, I suspect that
stdin/stdout have been remapped, since that is how most web page things
work, last I looked. (He says, knowing virtually nothing about writing web
page handling.)
A little quick digging in the Win SDK looking at script hosting seems to
imply that if you use cscript.exe to start one script from inside another
script, you can also get to at least stdin/stdout for the called process.
You may be able to get to stderr that way also. Or redirect stderr to a
file, which is I think what you wanted to do in the first place. This might
imply firing off a new script from your script and piping the email message
to the new script's stdin, and then grabbing the response. I found a
vbscript example of doing that sort of thing, but I don't know about
PerlScript; I suppose it should be generally possible to do the same thing.
I can't see anything that says that SA running in a perl script handler
shouldn't be able to have a stderr. However, if you are running directly as
a web server client you may not be abel to get to stderr. So if you can get
your web page server to fob off a new process to do the SA and pipe the
message in and out, you might get what you want.
Loren
