Francois Sauterey <fs@???> wrote:
> Well, it's a well knowned problem about "pipe_transport unset in..." error,
> but I can't find a pertinent answer ;~{
> I use the exim4 debian sarge package, in a splited configuration style,
> and I'm trying to configure it with the sympa mailling ist.
> I've a router/450_exim4-config_sympa with:
> sympa_aliases:
> debug_print = "R: sympa_aliases for $local_part@$domain"
> driver = redirect
> allow_fail
> allow_defer
> data = ${lookup{$domain-$local_part}lsearch{/etc/mail/sympa.aliases}}
> pipe_transport = sympa_pipe
> and a transport/40_exim4-config_sympa_pipe with:
> sympa_pipe:
> debug_print = "T: sympa_pipe for $local_part@$domain"
> driver = pipe
> command = "/usr/lib/sympa/bin/queue $local_part@$domain"
> user = sympa
> group = sympa
> return_output
[...]
The pipe_transport of of the redirect router specifies how to handle
items in /etc/mail/sympa.aliases that look like this:
"|/some/command ready,steady,go"
http://www.exim.org/exim-html-4.62/doc/html/spec_html/ch22.html#SECTspecitredli
i.e. the *aliasfile* specifies the command.
OTOH if you want a router that uses one predefined command with
different args you probably should use an accept router. -
http://www.exim.org/howto/mailman21.html#roconf should give you the
right idea.
cu andreas
--
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken. (c) Jasper Ffforde
