example database structure for rules and configs
lhaig at haigmail.com
Sat Oct 9 12:30:24 IST 2010
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:
>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.
>MailScanner mailing list
>mailscanner at lists.mailscanner.info
>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.
This message was scanned by Better Hosted and is believed to be clean.
More information about the MailScanner