Re: simple per-user content filter question

--=-fG4qduBs6EU6Eof+lxEw
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

this makes sense, and sounds simple enough as there are no "local" users
on this system.. but what is it that prevents something like
"content_filter_maps" or a feature along those lines?=20


On Mon, 2004-02-09 at 22:14 -0500, Victor.Duchovni@morganstanley.com
wrote:
> On Mon, 9 Feb 2004, steve j. kondik wrote:
>=20
> > I need the filter to trigger on the final destination address (which
> > would be found in virtual_mailbox_maps), rather than the "real" address=
..
> > using content_filter gets it right, and I had thought about just dealin=
g
> > with the sql lookups in amavisd-new to decide if it should just pass th=
e
> > message thru, but this adds _substantial_ overhead and i have to avoid
> > that.
> >
> > this seems like it should be simple, but every solution has been a dead
> > end so far. am i missing something here?
> >
>=20
> To do per-user content filtering, you need two instances of Postfix (two
> configuration directories each with main.cf, master.cf, separate queue,
> ...). The filter selection is made via a per-user transport table in the
> first instance, filtered mail is injected into the second instance for
> delivery (first instance is not an option, it would loop).
>=20
> Recipients not subjected to content filtering can be delivered directly
> from the first instance, but if you want to ensure that bounces are
> filtered also, you need to clear "mydestination" in the first instance,
> moving any local domains to relay_domains, and set "relayhost" in the
> first instance to point directly at the loopback injection port of the
> second instance.
>=20
> Postfix A ---> filter ---> Postfix B
> \ ^
> \------- relayhost ----/
>=20
>=20
> The transport map decides which user/domains are sent to the filter and w=
hich
> are sent directly to Postfix B.
>=20
> --=20
> Viktor.
--=20
steve j. kondik <shade@chemlab.org>

--=-fG4qduBs6EU6Eof+lxEw
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAKGFTMrBfzfMVwMcRAiA2AJ4vKjPHGRNtPVO0dwIkuK EEvovWRgCfUtxH
//yWUMoO90Wrlr6/st12sDk=
=QzNx
-----END PGP SIGNATURE-----

--=-fG4qduBs6EU6Eof+lxEw--