[Bug Report / MSFE v8.21 ] MailScanner.conf builder creates bad line

Discuss the ConfigServer MailScanner Front-End script
2 posts Page 1 of 1
Firewalls4Life
Junior Member
Posts: 57
Joined: 21 Nov 2011, 18:43


While tailing logs I noticed that I was getting an error message where MailScanner was complaining that it couldn't find the virus.scanning.rules file on the filesystem root.
Code: Select all
Dec  7 17:51:26 server MailScanner: MailScanner Email Processor version 5.0.2 starting...
Dec  7 17:51:26 server MailScanner: Reading configuration file /usr/mailscanner/etc/MailScanner.conf
Dec  7 17:51:26 server MailScanner: Reading configuration file /usr/mailscanner/etc/conf.d/README
Dec  7 17:51:26 server MailScanner: Cannot open ruleset file /virus.scanning.rules, No such file or directory

Obviously /virus.scanning.rules isn't the correct path, so I began searching the config files as to what was pointing to that file, and why it was looking in the filesystem root.

I found that the file at
Code: Select all
/usr/mailscanner/etc/MailScanner.conf
contained a configuration as seen here:
Code: Select all
#
# Removing/Logging dangerous or potentially offensive content
# -----------------------------------------------------------
#

# Do you want to scan the messages for potentially dangerous content?
# Setting this to "no" will disable all the content-based checks except
# Virus Scanning, Allow Partial Messages and Allow External Message Bodies.
# This can also be the filename of a ruleset.
Dangerous Content Scanning = %CRDIOERF77A1CVFFA6HLKZNDBJZBBY5ASGK2ISI0FVZKLUNDWC2-dir%/virus.scanning.rules
it should say:
Code: Select all
Dangerous Content Scanning = %rules-dir%/virus.scanning.rules
I believe when I edited via the MSFE GUI that it failed to generate that line properly.

I manually edited the
Code: Select all
/usr/mailscanner/etc/MailScanner.conf
file and changed it to say
Code: Select all
Dangerous Content Scanning = %rules-dir%/virus.scanning.rules
then I restarted MailScanner.

The logs now show as follows, with the error message no longer present. :)

Code: Select all
Dec  7 18:27:53 server MailScanner: MailScanner Email Processor version 5.0.2 starting...
Dec  7 18:27:54 server MailScanner: Reading configuration file /usr/mailscanner/etc/MailScanner.conf
Dec  7 18:27:54 server MailScanner: Reading configuration file /usr/mailscanner/etc/conf.d/README
Dec  7 18:27:54 server MailScanner: Read 868 hostnames from the phishing whitelist
Dec  7 18:27:54 server MailScanner: Read 5807 hostnames from the phishing blacklists
Dec  7 18:27:54 server MailScanner: Config: calling custom init function MailControlLogging
Dec  7 18:27:54 server MailScanner: Using SpamAssassin results cache
Dec  7 18:27:54 server MailScanner: Connected to SpamAssassin cache database
Dec  7 18:27:56 server MailScanner: Using locktype = posix
ForumAdmin
Moderator
Posts: 1400
Joined: 01 Oct 2008, 09:24


This will be fixed in the next release. Thank you for highlighting the issue.
2 posts Page 1 of 1