example database structure for rules and configs

[Lance Haig]

Thanks Steve 

Steve Freegard <steve.freegard at fsl.com> wrote:

>On 08/10/10 14:10, Lance Haig wrote:
>> Hi Steve,
>>
>> does this apply to rules as well?
>>
>>
>
>Rules are a bit different.
>
>You need a database table 'rulesets' in the following format:
>
>name
>num
>rule
>
>In MailScanner.conf you need to set:
>
>SQL Ruleset = SELECT num, rule FROM rulesets WHERE name=? ORDER BY num ASC
>
>Then for any option in the 'config' table you want to use a database 
>ruleset for you set the value to 'name.customize' (e.g. foo.customize). 
>  This will cause the functions to lookup the ruleset using the name 'foo'.
>
>Note that the number ordering is critical; you want to make sure that 
>you don't have any duplicates for a given rule (read: use a unique key) 
>and that you order them properly.
>
>Regards,
>Steve.
>-- 
>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! 
>
>--
>This message was scanned by Better Hosted and is believed to be clean.
>Click here to report this message as spam. 
>http://mx1.betterhosted.com/cgi-bin/learn-msg.cgi?id=1552A9F9D6.A2735
>
>

--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com