User manual

the Folder name field. On the other hand, if using the SQL server for a central
whitelist, the variable [DBCatalog] will be replaced with the fixed name
’Whitelist’. You can use the [DBCatalog] variable to use a database
connection for multiple databases within a MS SQL Server. Please note that
the databases need to be created exactly under that name. Otherwise any
connection attempts will fail!
e. Data Source=LOCALHOST\SQLEXPRESS; mandatory parameter for a
locally installed MS SQL Server 2005 Express. In this case, enter the ’Data
Source=’ parameter manually an set the Avira AntiVir Exchange variable
Server as required. The [Server] variable will be replaced with the server’s
NetBios name at runtime. If working with sub-domains in more complex
environments, you can also use the Avira AntiVir Exchange variable Server
(network), in which case the [ServerFQDN] variable is set and the server’s
FQDN (Fully Qualified Domain Name) is read. If the SQL server is used for
central whitelists, enter the name of the central SQL server manually.
Attention: Exception: In case of a central SQL server, e.g. to be used for central
whitelists, the two Avira AntiVir Exchange variables Server and Server (network)
cannot be used in the ADO string. Enter the name of the SQL server manually, i.e.
DataSource=Name_of_server;
5. In the Database user field enter the name of the SQL user who is allowed to
access the database (shown as User in the figure). In the following field, enter the
corresponding Password. The values entered here can be retrieved and inserted in
the ADO string through the variables [ADOUser] and [ADOPwd].
6. Use the Command timeout field to set the number of seconds after which the
database connection is aborted if no data is returned from the database. For large
databases, it is recommended to begin with a value around 60 seconds.
Setting up Central Whitelists
In a multi-server environment, each server creates its own user whitelists. Thus, without
server synchronization, each user is provided with a separate whitelist for each of the
servers, which all need to be maintained individually. In order to manage these whitelists
centrally and simplify administration, you can set up a Microsoft SQL server instead of
the standard local database based on the Microsoft Jet Engine. This Microsoft SQL
server will write the information for all Avira AntiVir Exchange servers involved to a
central SQL database.
To configure central whitelists, a database connection between the SQL server and the
Avira AntiVir Exchange server has to be configured first. Then, additional settings are
required within Avira AntiVir Exchange in order for Avira AntiVir Exchange to be able to
retrieve entries from the whitelist database.
The configuration of the database connection depends on the server environment.
1. Depending on the operating environment, proceed as described in the
corresponding scenarios under "Configuration of the Database Connection".
2. Under Data Source= enter the central SQL server.
Note: Please note that in the database connection ADO string, the [DBCatalog]
variable for the whitelist database is replaced with the fixed database name
’Whitelist’.
3. Under Avira AntiVir Exchange Servers - Properties in the field Select database
connection for whitelist entries select the SQL server.
This field provides a selection of all data sources specified under Database
connections.
4. Open the Wall job Advanced spam filtering - Actions - Definite criteria - No
Spam and enable the option E-mails from User Whitelist entries.
Avira AntiVir Exchange 7
49