Francois Sauterey 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 [EMAIL PROTECTED]"
> 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 [EMAIL PROTECTED]"
> driver = pipe
> command = "/usr/lib/sympa/bin/queue [EMAIL PROTECTED]"
> user = sympa
> group = sympa
> return_output
>
> The autogenerated config file is good, exim restarted bat no transport was
> found...
>
> Any solution ?
Not Debian here, (Ecartis, BSD )but the only difference that stands out is:
Where you have ..'pipe_transport =...' we have just plain 'transport = ...'
Bill
--
## List details at http://www.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/
