Toby-Spmassassin Advanced from MailScanner.conf

#
# Advanced SpamAssassin Settings
# ------------------------------
#
# If you are using Postfix you may well need to use some of the settings
# below, as the home directory for the "postfix" user cannot be written
# to by the "postfix" user.
# You may also need to use these if you have installed SpamAssassin
# somewhere other than the default location.
#

# SpamAssassin creates lots of temporary files as it works on messages.
# For speed, these should be created in a location mounted using tmpfs if
# you have it. MailScanner will attempt to mkdir it if necessary, so no
# special scripts are needed to set it up before running MailScanner.
# Note: If you move the "Incoming Work Dir" then you should move this too.
SpamAssassin Temporary Dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp

# The per-user files (bayes, auto-whitelist, user_prefs) are looked
# for here and in ~/.spamassassin/. Note the files are mutable.
# If this is unset then no extra places are searched for.
# If using Postfix, you probably want to set this as shown in the example
# line at the end of this comment, and do
#      mkdir /var/spool/MailScanner/spamassassin
#      chown postfix.postfix /var/spool/MailScanner/spamassassin
# NOTE: SpamAssassin is always called from MailScanner as the same user,
#       and that is the "Run As" user specified above. So you can only
#       have 1 set of "per-user" files, it's just that you might possibly
#       need to modify this location.
#       You should not normally need to set this at all.
#SpamAssassin User State Dir = /var/spool/MailScanner/spamassassin
SpamAssassin User State Dir =

# This setting is useful if SpamAssassin is installed in an unusual place,
# e.g. /opt/MailScanner. The install prefix is used to find some fallback
# directories if neither of the following two settings work.
# If this is set then it adds to the list of places that are searched;
# otherwise it has no effect.
#SpamAssassin Install Prefix = /opt/MailScanner
SpamAssassin Install Prefix =

# The site rules are searched for here.
# Normal location on most systems is /etc/mail/spamassassin.
SpamAssassin Site Rules Dir = /etc/mail/spamassassin

# The site-local rules are searched for here, and in prefix/etc/spamassassin,
# prefix/etc/mail/spamassassin, /usr/local/etc/spamassassin, /etc/spamassassin,
# /etc/mail/spamassassin, and maybe others.
# Be careful of setting this: it may mean the spamassassin.conf file
# is missed out, you will need to insert a soft-link with "ln -s" to link
# the file into mailscanner.cf in the new directory.
# If this is set then it replaces the list of places that are searched;
# otherwise it has no effect.
#SpamAssassin Local Rules Dir = /etc/MailScanner/mail/spamassassin
SpamAssassin Local Rules Dir =

# The rules created by the "sa-update" tool are searched for here.
# This directory contains the 3.001001/updates_spamassassin_org
# directory structure beneath it.
# Only un-comment this setting once you have proved that the sa-update
# cron job has run successfully and has created a directory structure under
# the spamassassin directory within this one and has put some *.cf files in
# there. Otherwise it will ignore all your current rules!
# The default location may be /var/opt on Solaris systems.
SpamAssassin Local State Dir = /var/lib/spamassassin

# The default rules are searched for here, and in prefix/share/spamassassin,
# /usr/local/share/spamassassin, /usr/share/spamassassin, and maybe others.
# If this is set then it adds to the list of places that are searched;
# otherwise it has no effect.
#SpamAssassin Default Rules Dir = /opt/MailScanner/share/spamassassin
SpamAssassin Default Rules Dir =

#
# Database SQL Configuration Settings
#
# This section allows you to over-ride any setting in this file or its
# related "include"d files with a setting or a ruleset in an SQL database.

# If you wish to read settings from a database or any other DBI-compatible
# data source, then this value should be set to the DBI data source name.
#
# This value is required for all of the database functions to work; if it
# is not supplied or is invalid, then all of the database functions will be
# disabled.  See the Perl DBI documentation for all available options.
#
# Example: DB DSN = DBI:DriverName:database=DataBaseName;host=Hostname;port=Port
DB DSN =

# Optional username to use to connect to the data source defined by DB DSN.
DB Username =

# Optional password to use to connect to the data source defined by DB DSN.
DB Password =

# This should be a valid SQL statement that returns a single row of data from
# your data source in integer format. This value is periodically checked every
# 15 minutes and if it is numerically greater than the previously retrieved
# value then the MailScanner child will exit and reload its configuration.
#
# This setting is required for all database functions to work; if it is not
# defined or the SQL is invalid then all database functions will be disabled.
#
# Example:  SELECT value FROM config WHERE option='confserialnumber'
SQL Serial Number =

# This should be a valid SQL statement that takes two placeholder arguments
# and returns a single row and column of data.  The first placeholder will
# contain the 'external' variable representation of the MailScanner setting
# being looked-up and the second placeholder will contain the hostname of the
# host that is requesting the data.
#
# This setting is required for all database functions to work; if it is not
# defined or the SQL is invalid then all database functions will be disabled.
#
# Exmaple: SQL Quick Peek = SELECT value FROM config WHERE external = ? AND host = ?
SQL Quick Peek =

# This should be a valid SQL statement that has a single placeholder argument
# and must return two columns and one row per configuration setting.
# The placeholder will contain the hostname of the host requsting the data.
# The first column must return the 'internal' representation of the setting
# and the second column must return the value that should be assigned.
# If the value contains 'foobar.customi[zs]e' then the value is presumed to
# be a database ruleset and will cause the defined 'SQL Ruleset' statement to
# be run and will use 'foobar' as the ruleset name to retrieve the ruleset.
#
# This setting is required for all database functions to work; if it is not
# defined or the SQL is invalid then all database functions will be disabled.
#
# Exmaple: SQL Config = SELECT option, value FROM config WHERE host=?
SQL Config =

# This should be a valid SQL statement that has a single placeholder argument
# and must return two columns and one or more rows.  The first column must be
# a numeric starting at 1 and in ascending order and the second column should
# be the rule string.  The placeholder will contain the ruleset name.
#
# Example: SQL Ruleset = SELECT num, rule FROM ruleset WHERE rulesetname=? ORDER BY num ASC
SQL Ruleset =

# This should be a valid SQL statement that returns a single column and one
# or more rows.  Each row that is returned is pushed into an array and joined
# into a string separated by newlines and then passed into the SpamAssassin API
# using the {post_config_text} attribute. See the SpamAssassin API for details.
# The returned rows should be valid SpamAssassin configuration settings that
# will be processed by SpamAssassin after it has read all of normal configuration.
# Any errors will therefore be reported by SpamAssassin and will show up by
# running 'MailScanner --lint' or 'MailScanner --debug-sa'.
#
# Example:  SQL SpamAssassin Config = SELECT text FROM sa_config
SQL SpamAssassin Config =

# If enabled; this will log lots of debugging output to STDERR and to syslog
# to help pinpoint any errors in the returned database values and will show
# exactly what is being processed as the data is being loaded.
SQL Debug = no