Rob,
1) There was no way of specifying system maximums. Eg. drop anything with
a spam score higher then 30, or quarentine all virus emails. The user
could always override the maximums.
If you are talking about SQL lookups for per-recipient settings,
you must already have some SQL
RHutton wrote:
It has been a long time since I have worked with Amavis, but there
used to be some pretty severe limitations on applying per recipient
policies (eg. one recipient dropping, while another recipient quarantines,
while another tags and passes) if the email was passed
] Multiple recipient question with postfix
RHutton wrote:
It has been a long time since I have worked with Amavis, but
there
used to be some pretty severe limitations on applying per recipient
policies (eg. one recipient dropping, while another recipient
quarantines,
while another
it,
then all recipients would get it because amavis did not modify the
envelope.
Thanks,
Rob
Rob Hutton
DataScan Technologies
Gary V [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
12/28/2005 01:16 PM
To
amavis-user@lists.sourceforge.net
cc
Subject
Re: [AMaViS-user] Multiple recipient question
RHutton wrote:
The problem used to be twofold.
1) There was no way of specifying system maximums. Eg. drop anything with
a spam score higher then 30, or quarentine all virus emails. The user
could always override the maximums.
Well, the first match wins, so someone's setting will be
It has been a long time since I have worked with Amavis, but there
used to be some pretty severe limitations on applying per recipient
policies (eg. one recipient dropping, while another recipient quarantines,
while another tags and passes) if the email was passed directly from
postfix
