mailscanner whitelist (SQLWhitelist)

Steve Freegard steve.freegard at
Tue May 5 18:50:25 IST 2009

Ken A wrote:
> Steve Freegard wrote:
>> Ken A wrote:
>>> Miguel Angel Nieto wrote:
>>>> Hi,
>>>> I have the whitelists configured with MailWatch:
>>>> Is Definitely Not Spam = &SQLWhitelist
>>>> Mailscanner reads the whitelist:
>>>> May  5 13:57:16 eksmtp01 MailScanner[26158]: Whitelist refresh time
>>>> reached May  5 13:57:16 eksmtp01 MailScanner[26158]: Starting up SQL
>>>> Whitelist May  5 13:57:16 eksmtp01 MailScanner[26158]: Read 89
>>>> whitelist entries
>>>> But Mailscanner scans the message with Spamassassin, and It shouldn't
>>>> happen.
>>>> What i'm doing wrong?
>>> Nothing. That is normal behavior. Whitelisting does not exclude a
>>> message from SA scanning. It doesn't apply the MailScanner SA rules to
>>> the message, so even if it scores above your 'high' threshold, it will
>>> not be spam tagged or quarantined or whatever.
>>> If you want to exclude a message from scanning, you need to use the "Use
>>> SpamAssassin" instead, or even "Spam Checks". Read the config file.
>> That's not quite correct.
>> Set 'Always Include SpamAssassin Report = No' and MailScanner will not
>> run SA for messages that are whitelisted.
>> Regards,
>> Steve.
> Ah, that's a simpler to change, no ruleset required. Maybe I need to
> read the config file again. It's been a couple years.  :-)
> Thanks for correcting me.

No problem; it's actually not clear in the docs in MailScanner.conf what
effect this option can have - it's from bitter experience and reading
the code that I know about this behaviour.

I always disable this option on sites that are struggling with load
issues as it almost always helps.


More information about the MailScanner mailing list