I started with trying to go with the one recipient approach but then after considering the performance impacts of everything that's running in the filter, we decived just to rewrite the filter to handle multiple domains. It's a good time to review all of that code anyway.
So we are approach it as a bug that needs to be fixed on our side... Which is probably the best approach for the long run.
From: owner-postfix-users@... on behalf of Victor Duchovni
Sent: Sat 3/1/2008 7:49 PM
To: Gary W. Smith
Subject: Re: filter per domain not working
Reading the code more closely, it appears that content filters don't
behave the way I thought. There is no practical difference between
"filter:dummy" and "filter". When the nexthop is absent, it is set
to $myhostname. So either way all recipients are routed to a single
destination. You can either take all the recipients together or one at
a time by setting the transport destination recipient limit to 1.
Sorry about that. This is unlikely to change I think, too many people
probably use just "filter" and get decent performance because all the
recipients *are* sent together. If this were to be made possible it
would need to be controlled by a boolean parameter that defaults to
the current behaviour.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.