On Thu, Sep 30, 2010 at 12:48:19PM +0200, Christian R??ner wrote:
> I have a problem that the smtpd_proxy_filter option has higher priority
> than a FILTER setting in an access table:
No, it does not. Rather, these are completely separate mechanisms, and
there is no reason to expect post-queue FILTER directives to influence
the pre-queue proxy, or conversely instantiation of a pre-queue filter
to influence post-queue FILTER directives.
> Sep 30 12:33:04 mx0 postfix/smtpd[5250]: warning: access table
> cidr:/etc/postfix/maps/client_access.cidr: with smtpd_proxy_filter
> specified, action FILTER is unavailable
It is not possible for the SMTP server that is in-front of the pre-queue
filter to add "FILTER" records to the Postfix queue-file, as no queue-file
is generated. The message is sent via SMTP to the pre-queue proxy, there
are is no "FILTER" verb in SMTP.
The FILTER directive can only be set by the SMTP server that is *behind*
the pre-queue proxy. The front-end SMTP server can add headers, which
you could use downstream to (carefully avoding allowing outside parties
specify the FILTER transport or nexthop) selectively trigger a FILTER
in the SMTP server that is back-end SMTP server.
--
Viktor.
