On Thu, Sep 10, 2015 at 07:01:59PM +0200, Francis Brosnan Blázquez wrote:
> > This is how Postfix content filters work:
> >
> > postfix1 -> filter -> postfix2
> >
> > The filter takes precedence in postfix1;
>
> Just to clarify we are talking about the same thing, "filter" is not a
> "content filter" taking the mail from postfix and re-injecting it into
> postfix, but valvula reporting "FILTER transp2:", as described at [1],
> using delegation protocol ([2]),
If your policy service says "FILTER ..." it is setting a content_filter
that preempts transport table routing for *all* recipients.
> I'm confused about this statement because it is not what's happening
> right now and I have shown an example that demonstrates it :-?
Yes, you're confused. No, you don't have a counter-example.
> But if I make valvula to report "FILTER transp2:", then postfix2, in the
> diagram "postfix1 -> filter -> postfix2" completely ignores
> transport_maps:
Exactly as it should, it is up to "transp2" to re-inject the mail
back into Postfix (bypassing the policy service with its FILTER
replies).
--
Viktor.
