On Dec 24, 2003, at 12:40 PM, Dan Egli wrote:
> Michael Johnson wrote:
>
> | On Dec 24, 2003, at 12:21 PM, Dan Egli wrote:
> |
> |> Michael Johnson wrote:
> |>
> |> | system_aliases:
> |> | driver = redirect
> |> | allow_fail
> |> | allow_defer
> |> | data = ${lookup{$local_part}lsearch{/etc/aliases}}
> |> | user = smmsp
> |> | file_transport = address_file
> |> | pipe_transport = address_pipe
> |> |
> |> not enough info. Show us your /etc/aliases file. We need to see how
> your
> |> file says to handle mailman@???.
> |>
> | D'oh! I meant to include that. The appropriate line is:
> |
> | mailman: "|/usr/local/mailman/mail/mailman post mailman"
>
> then the pipe transport is correct. The | is a pipe. Does mailman
> provide any logs you can read? What do your exim logs show when
> attempting to deliver?
2003-12-24 08:00:09 HQEHG9-0001MI-BO ** mailman@smudette
<mailman-bounces@smudette> R=mailman_router T=mailman_transport: Child
process of mailman_transport transport returned 127 (could mean unable
to exec or command does not exist) from command:
/usr/local/mailman/mail/wrapper
I'm thinking this means I have a permission/user/group problem as in I
haven't chosen the correct group to run the pipe under. Does that
sound correct?
> the file_transport is not comming into play because the transport
> method
> used is determined by the final destination. Since thie final
> destination is a program with the | character in front of it, that
> tells
> exim to use the pipe_transport.
>
> It might also help if we saw your address_pipe transport.
I didn't alter this from the way it was done in the installation:
address_pipe:
driver = pipe
return_output
-Michael
