On Fri, May 6, 2016 at 12:20 PM, Wietse Venema <wie...@porcupine.org> wrote:
> Mike Schleif: > > Postfix: 2.10.1 > > > > Content filter according to: > > http://www.postfix.org/FILTER_README.html#simple_filter > > > > Where in the overall process does this content filtering take place? > > > > Does this happen prior to querying the aliases and virtual tables? > > With the simple filter example the virtual aliases expansion is > both before and after the filter. How can it be "both before and after?" > > Where is this documented? > > virtual alias expansion is done in the cleanup daemon (described in > ADDRESS_REWRITING_README.html). > > It is configurable with receive_override_options which is documented > under Advanced content filter :-( > > I suppose that the simple filter is meant to be simple, if you want > sophistication, the smtp-based approach is better. > This postfix server has been running the "simple filter" successfully all year. This company has hundreds of email domains, only two of which are in $mydestination. This filter rewrites some headers for users in $mydestination domains. This is the way they want it. Currently, we are not using virtual_alias_domains. The number of domains is very large and changes frequently. Even without virtual_alias_domains, mail addressed to virtual_domains in the filter database are getting processed correctly. The problem I'm trying to solve involves the "loop" generated when mail is received for _unknown-us...@virtual-example.com. If this filter is executed prior to querying the virtual table, then I need onlyl list postmas...@virtual-example.com & its ilk in virtual, and "@ virtual-example.com nore...@mydestination.com" which will be discarded via transport: "nore...@mydestination.com discard:" That seems like it will work; but, I remain confused about the sequence. What am I missing? ~ Mike > Wietse >
