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: Marc G. Fournier (scrappyhub.org)
Date: Tue Nov 01 2005 - 13:38:17 CST


On Tue, 1 Nov 2005, mouss wrote:

> Marc G. Fournier a écrit :
>
>>
>> I've been playing alot with moving config files into an SQL database over
>> the past little while, since it gives me a very clean way to manipulate
>> configuration files from a web interface ...
>>
>> The one thing I'd like to be able to do, that I can't seem to figure out
>> the proper way of, is having per-recipient "mailbox_transports" ... right
>> now, for instance, anti-spam tagging is set "server wide", while I'd like
>> to be able to do it "per recipient" ...
>
> how do you intend to do per-recipient spam filtering?

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 ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappyhub.org Yahoo!: yscrappy ICQ: 7615664