|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: selective filtering question
From: Alex van den Bogaerdt (alex
ergens.op.het.net)
Date: Wed May 21 2003 - 10:02:48 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 21, 2003 at 08:49:27AM +1000, Colin Campbell wrote:
> > Currently when a mail is sent to user1
domain and user3
domain, the
> > filter is used for both users (because the mail is sent through it,
> > with both recipients in it). I need to split the mail into at least
> > two separate deliveries.
>
> I think you can probably do it with two instances of postfix. You have one that
> accepts all mail. Use a transport map to send clients to be filtered to the
> second instance. That instance can happily filter everything it receives.
I'm afraid that's going to happen then. Bummer. I think I've seen
some mail describing a more elegant setup but I cannot find it anymore.
Thanks for answering.
> My needs are more complex than yours unfortunately.
Isn't it just an extra layer of what I need to do?
You have multiple decision points (one list per client)
where I just have one.
> I need the ability to filter on
> o client - with the ability to apply exceptions, eg
> if (mail from client-x) {
> if (recipient == "Y") {
> don't filter
> }
> else {
> filter
> }
For each (special) client, "filter" to a next instance. In
that instance do not filter but use a transport map to the
next instance which may or may not filter. You'll be using
FILTER as a means of early transport decision. The second
instance uses a real transport table on a per user basis,
instance 3a filters, instance 3b does not.
> o sender - maybe, given that these are so easily forged
Indeed. You may want to skip that, unless of course you
know you can trust the client.
> o recipient - multi-recipient mails should only be filtered for those recipients
> who want it.
This is just the case for all other clients. Don't filter
here, just transport to the second layer and make a transport
decision on a per user basis.
> In the past I have suggested qmgr and got blasted for it.
Yup, that seems to be quite normal here. Often completely
unnecessary and also often due to hasty reading by the
blasting party.
Alex
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]