> >
> >
> > It is relatively easy.
> > You can create a touter which calls a "custom" transport.
> >
> > The router could look like this:
> > mypipe_router:
> > domains = internal.domain.tld
>
> What shall I list in the domains field to handle only outgoing email?
> Or I shall check To/From/Cc etc headers to judge what kind of email it
> is, incoming or outgoing?
It depends on what you really need. You can have also the result of an
acl as your condition, it was just an example.
>
> > driver = accept
> > require_files = /home/example/mycommand
> > local_part_suffix_optional
> > transport = newspipe
>
>
> It should be 'mypipe', as named below (i.e. the custom transport I
> create to handle that)?
>
Yes, I forgot to change that in the example. I just copied a part of a
config I am running. So the transport is not newspipe, but mypipe.
> Also, where shall I place this custom router in order not to ruin the
> normal message handling after it has been processed?
>
You can place it near the top as long as your condition (here:
domains=internal.domain.tls) is sufficiently restrictive for what you
want to achieve.
