Hi, > > > > internet -> front-end Postfix instance -> filter -> back-end > > > Postfix > > > > > instance > > > > > > > > > > The front-end Postfix instance uses transport_maps to select a > suitable > > > > > filter. > > > > > > > > > > example.com: smtp:<filter-for-example-com> > > > > > example.org: smtp:<filter-for-example-ord> > > > > > > > > > > Each filter then delivers to the back-end Postfix. > > > > > > > > This implies one IP per domain as well, correct? > > > > > > No. One front-end instance can receive mail for N domains, and they > > > can share (MX) IP addresses. > > > > > > You can have multiple front ends, again that is not required for > > > per-domain filters to work. > > > > I'm starting to understand and really appreciate your help. Can I ask you > > to provide me with an example of what you mean? Are you referring to > what's > > That is shown above, expressed in terms of transport maps and > customized content filters in-between general-purpose Postfix > instances. > > header/body checks don't generalize beyond narrow use cases. >
I'm trying really hard, but I just don't understand what you mean. I set up multi-instance with Viktor's help some time ago, where each instance essentially processes mail for a somewhat related group of domains. Adding transport maps to the front-end instance would be different than what I remember doing with Viktor. I don't have any content filters set up in the front-end postfix. How do I connect the front-end postfix with the filters? I think this is something I can implement, but I need more of a description of how it should work, please.
_______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
