- Previous message: Peter Hinse: "Re: Multiple instances of smtp and smtpd"
- Maybe in reply to: Marc G. Fournier: "mailbox_tranport_maps (or equivalent) ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: mouss (no email)
Date: Tue Nov 01 2005 - 15:31:20 EST
Marc G. Fournier a écrit :
> 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 ...
I guess you just tag and deliver (no block or quarantine ...)? if so,
there is no problem (a part from the perf issue) to let all traffic go
through the filter. just don't tag the subject (at least for users who
don't want to get that). recipients shouldn't care if their mail gets
the X-Spam- headers.
otherwise, here are some possibilities:
- switch to amavisd-new and use policy banks
- switch to maildrop/procmail (run spamc or spamassassin from there
depending on the user). you'll need to deliver or post the message after
it has been filtered, so this is not necessarily better than the
multi-instance way.
- A Viktor said, use multiple instances and transport_maps. just don't
declare the domain as local in the before-the-filter instance.
if you use address verification, make sure to set the transports for
verify to their "normal" values.
- use virtual aliases to redirect the unfiltered users to your lmtp, and
once the message is filtered, deliver it to the real user (for instance,
by using other virtual aliases in a 2d instance).
|
|
|