Black list on header value?

Steve Freegard steve.freegard at fsl.com
Tue Sep 14 13:01:43 IST 2010


On 14/09/10 12:42, Hugo van der Kooij wrote:
>
> On Tue, 14 Sep 2010 09:35:07 +0200, Glenn Steen<glenn.steen at gmail.com>
> wrote:
>> IIRC you do use Postfix, and then the Received ->  HOLD thing puts a
>> limit on what you can do... Hugo posted a nice alternative to it,
>> rather longish while back, but unfortunately I don't think you can
>> utilize that to the effect needed... So it looks like you need do
>> something clever in MS. I'm just into my second cup of java, so ...
>> Bright ideas will follow the third or fourth:-):-)
>> Or Hugo will jump in and tell us that you can use his alternative
>> method;-)... Or Jules will write it for you:D
>
> If you just want to make sure they end up in the quarantine area and are
> never passed on just give them a big bonus.
>
> In "spam.assassin.prefs.conf" you could add:
>
> header          BUUSSPAM        X-Spam-Flag =~ /YES/
> describe        BUUSSPAM        Detected Big Ugly Upstream Scanner SPAM
> score           BUUSSPAM        100.0
>

That won't work as SpamAssassin removes X-Spam-* headers in PerMsgStatus.pm:

$self->{msg}->delete_header('X-Spam-.*');

The only way to do this is via a CustomFunction if you want MailScanner 
involved.

Regards,
Steve.


More information about the MailScanner mailing list