More problems than just ALL_TRusted

[Richard Edge]

Doh! How did I miss that one. I am not sure how that changed from & to $
since I had pasted that value in when first setting it up installing
MailWatch. I have found a clue though. It appears to have changed during
a previous upgade, I founf a MailScanner.conf.old from a MailScanner
upgrade I did on Jan 27. From that file (MailScanner.old) it is correct:

-----------------------
#Is Definitely Not Spam = &SQLWhiteList

# Spam Blacklist:
# Make this point to a ruleset, and anything in that ruleset whose value
# is "yes" will *always* be marked as spam.
# This value can be over-ridden by the "Is Definitely Not Spam" setting.
# This can also be the filename of a ruleset.
Is Definitely Spam = no
#Is Definitely Spam = &SQLBlacklist 
-----------------------

I guess it occurred during an upgrade_MailScanner_conf and I missed it
when checking the new conf file before mv'ing to the new one. Thanks for
catching that. I guess this just emphasizes the need to verify changes
before committing them.

Richard Edge
Senior Systems Administrator | Technology Services
Trinity Western University | t: 604.513.2089
f: 604.513.2038 | e: edge <at> twu.ca| www.twu.ca/technology 

 

-----Original Message-----
From: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Glenn
Steen
Sent: Monday, February 06, 2006 2:02 PM
To: MailScanner discussion
Subject: Re: More problems than just ALL_TRusted

On 06/02/06, Richard Edge <Edge at twu.ca> wrote:
> I have looked at the following:
>
> > Syntax error in line 1480, value "" for spamblacklist is not one of 
> > allowed values "yes","no" at 
> > /usr/lib/MailScanner/MailScanner/Config.pm
> > line 2360
>
> My line 1480 is 'Is Definitely Spam = $SQLBlacklist' and is the same 
> as my mx20 config.

IIRC, SQLBlacklist is a subroutine/function call and should be spelled
with an "&", not a "$"... IOW: Is Definitely Spam = &SQLBlacklist

> > Syntax error in line 1473, value "" for spamwhitelist is not one of 
> > allowed values "yes","no" at 
> > /usr/lib/MailScanner/MailScanner/Config.pm
> > line 2360
>
> My line 1473 shows 'Is Definitely Not Spam = $SQLWhitelist' which is 
> exactly what the same line on my config file on mx20.twu.ca and is 
> supposed be set to this for MailWatch.

Same error as for the blacklist call above.

> > Possible syntax error on line 26 of
> > /etc/MailScanner/filename.rules.conf
> > at /usr/lib/MailScanner/MailScanner/Config.pm line 1274 Remember to 
> > separate fields with tab characters! at 
> > /usr/lib/MailScanner/MailScanner/Config.pm line 1276 Read 702
>
> My line 26 in /etc/MailScanner/filename.rules.conf shows 
> '/etc/MailScanner/filename.rules.conf' which was not added by me, but 
> is a part of your base file setup. The only changes I made in this 
> file was to comment out the winmail, .bmp,.ico, .ani, .cur, and .hlp 
> deny lines a couple of versions ago.

Don't know about this one... Perhaps the wrong type of comment chars?

> I don't know where the 'warning: score set for non-existent rule' 
> lines are coming from since I do not recognize any of these rules. 
> They are not scores I have set anywhere.

Better heads than mine will likely help with this one... Could they be
"leftover" rules from a previous SA? Or some "plugin" not being loaded
correctly?

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!