Hello,This seems like a very strange behavior, because I’ve had this working before, and I can’t figure out the difference between what worked and what didn’t. So, I used to use a qmail-remote wrapper (i.e. the script I posted to the list a week ago or so) to do my DomainKey signing on my personal domain. Then I twiddled around (modified my logging patch) and ended up reinstalling qmail, which wiped out my wrapper. No problem, I posted it to the list, so I should be good to go, right? For some reason, now, when I try to replace qmail-remote with a script, sending mail just generates a terse “Unable to run qmail-remote” error message from qmail-send. The script uses full-paths only, so it’s not a path issue, and works fine when run by hand. The permissions are identical to the original qmail-remote binary: -rwx–x–x 1 root root 724 2007-04-12 18:31 qmail-remote* -rwx–x–x 1 root root 296K 2007-04-12 17:01 qmail-remote.orig* -rwx–x–x 1 root root 724 2007-04-12 18:29 qmail-remote.sh* It won't even do: #!/bin/sh exec /var/qmail/bin/qmail-remote "$@"Does anyone have any idea what possible reasons a wrapper script might have for refusing to run like this? Maybe I’m not thinking clearly, but I’m stumped. ~Kyle --The optimist thinks this is the best of all possible worlds. The pessimist fears it is true.
-- J. Robert Oppenheimer
|
