Re: [Exim] ignoring pipes in .forward files

Mark T. Valites <valites@???> wrote:
> When I cut over my existing email system from sendmail to exim, I
> left the forward files created for users in place, as is. Instead of
> relying on the call to a vacation program from a pipe in a .forward
> file, I now call vacation when a .vacation.msg file exists.
>
> A typical forward file currently looks like:
>
> \<user>, "|/usr/bin/vacation <user>"

<snip>

> The .forward file is created through a SquirrelMail plugin. I realise
> could quickly rewrite the plugin to not put a forward in place to
> solve the problem, but I was hoping there's a way to ignore pipes in
> forward files so I wouldn't have to edit all the forward files
> currently in place. (And additionally if for some crazy reason my
> site ever decided to revert back from exim, it would be one less
> thing to worry about.)

You could perhaps configure the router to allow pipes but set the
pipe_transport option to point to a transport that does something other than
run the pipe - perhaps an appendfile transport with file = /dev/null?

Entirely untested.

Peter