SQLWhitelist for content.scanning.rules

Steve Freegard steve.freegard at fsl.com
Fri Nov 14 11:19:43 GMT 2008

Kit Wong wrote:
> Sorry about this, I do have it configured as you described. What I am
> trying to do is use the whitelist created within MailWatch. This is
> accessed via &SQLWhitelist in the MailScanner.conf.
> The whitelist works fine when its used where its supposed to be, ie 
> Is Definitely not spam = &SQLWhitelist
> But when I use to at 
> Scan Messages = &SQLWhitelist 
> It doesn't scan any messages.

Well thinking about it the reason is obvious:

Value		Is Definitely Not Spam		Scan Messages
yes		Whitelisted			Message is scanned
no		Not whitelisted			Message is not scanned

The logic for the options is inverted - so if you want to use 
SQLWhiteList for Scan Messages instead you will have to invert the 
return codes.

In SQLWhitelist - change all occurrences of 'return 1' to 'return 0' and 
all occurrences of 'return 0' to 'return 1' and it will work correctly.

> Just wondering if it is possible to not scan messages in the whitelist
> rather than scanning them but never marking them as spam. (since
> whitelist still gets scanned for viruses and filenames etc).

Personally - I think that's a really bad idea; it lets your users 
side-step any rules that you have in-place for their/your own safety.


More information about the MailScanner mailing list