Ruleset problem/question

[Soeren Gerlach]

Hi,

referencing to the ruleset example I set up a simple rule for MailScanner to 
use different files for the "Deleted Bad Filename Message" parameter. It 
looke like so in my config file:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Deleted Bad Filename Message Report = 
/opt/MailScanner/etc/rules/deleted_bad_filename_message_report.rules
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

There, some rules are defined for several domains:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
To: *@all-about-shift.com 
/opt/MailScanner/etc/rules/messages/deleted_bad_filename_message_report.all-about-shift.com.txt
To: *@all-about-shift.de 
/opt/MailScanner/etc/reports/de/deleted.filename.message.txt
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 


The file for the first domain exists and is a customized version of the 
general version used as default in MailScanner. But when starting 
MailScanner, it reports the following error via Syslog:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Syntax error in line 1 of ruleset file 
/opt/MailScanner/etc/rules/deleted_bad_filename_message_report.rules for 
keyword deletedfilenamemessage
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

What am I missing? It looks quite perfect to me (at least....) ,-))

Two questions regarding this problem: How does M. distinguish in the config 
file between a rulefile and the final text file to use for this (and other 
parameters) as both versions take a file in the config file itself.
The second question accompanies the "M. in mem" thread which goes on for 
some days: Will all the referenced text files be read upon start so they 
are in mem while a M.process is running? If yes, does this also apply for 
customn rules as shown above?


Best regards,
Soeren Gerlach