Black list on header value?
james at gray.net.au
Mon Sep 13 12:40:51 IST 2010
On 13/09/2010, at 8:52 PM, Hugo van der Kooij wrote:
> On Mon, 13 Sep 2010 19:14:04 +1000, James Gray <james at gray.net.au> wrote:
>> Hi All,
>> I've done a bit of digging through the archives and didn't find
>> so I'll ask anyway - but first some background. I have an upstream
>> provider who uses SpamAssassin and I can't enable/disable it on a
>> or domain basis - it's all or nothing. Given this limitation, is there
>> way I can use a black list rule to prevent MailScanner rescanning
>> already flagged as spam by the upstream?? Specifically, I want to
>> blacklist on the "X-Spam-Flag: YES" header.
> I know you can use checks like this in postfix. But my normal blacklisting
> entries use a REJECT policy there and you definity don't want to REJECT
> them as it will result in a a spam bouncer.
Thanks Hugo. As you allude to, I want to avoid an MTA-level reject for exactly the reason you specify. I can see a custom function in my future. If I wrote it, would anyone else be interested??
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3826 bytes
Desc: not available
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20100913/39f8fa78/smime.bin
More information about the MailScanner