Hi
I'm reposting this as I'm completely flummoxed.
I'm getting lines like this in the logs:
2004-05-19 14:40:24 1BQRJ0-0002g2-Js =>
|/root/bin/exim4_postgres_insert.pl $h_date $message_id $h_X-Filter-ID
$recipients $h_subject $message_size $h_from $h_to $h_cc <system-filter>
T=system_pipe_transport
but nothing is hitting the script. I'm trying to collect the parameters
in @ARGV and there is nothing there!
Also, why does the name of the command have to appear in both the
transport definition and the system filter file pipe line?
Thanks for any eludication.
Rory
On 13/05/04, Nigel Wade (nmw@???) wrote:
> Rory Campbell-Lange wrote:
> >I'm having trouble understanding how the system filter pipe command
> >works. I use pipes in other filter and also pipe transports -- I can't
> >work out how to make this work though! (No example in the docs that I
> >could find).
> >
> ># main
> >system_filter = /etc/exim4/sysfilter
> >system_filter_user = 8
> >system_filter_group = 8
> >system_filter_pipe_transport = system_pipe_transport
> >
> ># transport
> >system_pipe_transport:
> > driver = pipe
> > command = /root/bin/exim4_postgres_insert.pl
> > ignore_status
> > return_fail_output = false
> > return_output = false
> >
> ># filter file pipe line
> >pipe "<cmd> arg1 arg2"
>
> The system_filter_pipe_transport defines which transport is to be used when
> a pipe command appears in the system filter. The command to be used is
> specified in the system filter e.g.
>
> unseen noerror pipe "/etc/exim/sophos_update"
>
> in the system_filter will pipe the message to the command
> "/etc/exim/sophos_update" in the system_filter_pipe_transport.
--
Rory Campbell-Lange
<rory@???>
<
www.campbell-lange.net>