OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: mailbox_tranport_maps (or equivalent) ...

From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Tue Nov 01 2005 - 13:47:23 CST


On Tue, Nov 01, 2005 at 03:38:17PM -0400, Marc G. Fournier wrote:

> we use spamassassin with the spamcheck.py that *used* to come bundled with
> it, that acts as an lmtpproxy between postfix->lmtp ... I just wish to be
> able to switch that off per recipient, and have it go straight through to
> lmtp, if the recipient doesn't want it to go through ...
>

Two Postfix instances with transport_maps routing some to the real LMTP
and some to the content filter. In the Post-filter instance users are
always routed to the real LMTP. In other words, instead transport_maps
instead of content_filter. I do cotent filtering, but I no longer use the
content_filter mechanism except via FILTER header checks downstream of the
real content filter proxies, to route tagged messages to a quarantine.

--
        Viktor.

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:
<mailto:majordomopostfix.org?body=unsubscribe%20postfix-users>

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.