root@??? said:
> Okay this is what i'm trying to do. I have built a 'pipe' transport in
> Exim that calls a perl script as a command. In the perl script there
> is come code that manipulates the mail file directly and then opens a
> socket to one of two availabe remote machines running a Visual Basic
> Socket Server.
You don't get the mail data in a pipe transport as a file - it comes in
on stdin.
> However, calling the script from Exim seems to shut down all IO. The
> logs are not logged and the socket fails to TX to the Server. After
> reading the docs on Exim i found that Exim opens it's own socket to
> the script! Am i reading this correctly? If so is it possible to stop
> Exim 'sucking' all the IO from the script back to itself via this
> pipe.
Is the script ever being run - standard mistake is not setting
user/group permissions on the exim director/transport. Check your exim
logs for hints.
What user should exim run this script as?
Have you checked that that user id can run the script (permissions), or
that the script works when run from that user id (other permissions).
Does your script expect things to be set in the environment - like the
path?
Does you script run as /path/to/script as opposed to "perl
/path/to/script"?
Does perl -cw script give you any output?
Does your script work with taint checks on? [unlikely to be the
problem]
after all that... is there any useful debugging information or should I
continue guessing :-)
Nigel.
--
[ - Opinions expressed are personal and may not be shared by VData - ]
[ Nigel Metheringham Nigel.Metheringham@??? ]
[ Phone: +44 1423 850000 Fax +44 1423 858866 ]
