ArticlesArticles Most Popular ArticlesMost Popular Articles
RSS Feeds
DrillDown Icon Table of Contents
DrillDown Icon 2019 Official Holidays & Support Schedule
DrillDown Icon IMPORTANT: End of Life of SHA1 on Windows Server 2003
DrillDown Icon IMPORTANT: Supported Operating Systems
DrillDown Icon PLEASE READ: Our Update Server IPs Have Changed
DrillDown Icon Support
DrillDown Icon modusGate for Microsoft Azure
DrillDown Icon modusCloud
DrillDown Icon Alleviating Spam – Best Practices
DrillDown Icon directQuarantine Technical Information
DrillDown Icon modusMail & modusGate Technical Information
DrillDown Icon Documentation & Release Information
DrillDown Icon Known Issues (non-release related)
DrillDown Icon Configuration Information
DrillDown Icon modusGate & modusMail
DrillDown Icon modusGate Only
DrillDown Icon modusMail Only
DrillDown Icon SQL Server Information
DrillDown Icon How-To: Enable Full Text Indexing for SQL Server Express
DrillDown Icon Known Issue: SQL Server Express Setup Problems on Windows 2000 Server
DrillDown Icon Info: Extended Database Format for ModusMail
DrillDown Icon How-To: Configure the SieveStore Database in SQL Server
DrillDown Icon How-To: Use SQL Server Instead of the Built-in MDB Database for Quarantine storage
DrillDown Icon How-to: Prevent Quarantine-Related Problems
DrillDown Icon How-To: Configure SQL TCP stack
DrillDown Icon How-To: Move SQL database from one server to another
DrillDown Icon MySQL Information
DrillDown Icon Security
DrillDown Icon Sieve
DrillDown Icon Spam and False-Positives
DrillDown Icon Statistics and Monitoring Section
DrillDown Icon Web Components
DrillDown Icon Troubleshooting
DrillDown Icon Hardware & OS System Requirements
DrillDown Icon Tools
DrillDown Icon Other Product Technical Information
DrillDown Icon Professional Services
DrillDown Icon Newsletters
  Email This ArticlePrint PreviewPrint Current Article/Category and All Sub-Articles/Categories
 
How-To: Configure the SieveStore Database in SQL Server

 

Product: All

Version & Build: 4.4.568 and below

 

Summary

This document explains how to use a SQL database instead of Access for SieveStore data.  The SieveStore database contains your custom sieve filters and any Whitelist/Blacklist entries.

 

Install Microsoft SQL Server

When installing Microsoft SQL server, specify that SQL authentication will be used (not Windows authentication).  Make sure to note the username and password you choose as you will need them later.  For example, the default user proposed by Microsoft is SA.

 

 

Configuring the Database on a Microsoft SQL Server

 

Creating the SieveStore DB


This Database will contain all custom rules, the Trusted Senders List and the Blocked Senders List:

  • Open the Microsoft SQL Enterprise Manager
  • Expand the tree in the left pane and open Databases
  • Right-click on Databases and select New Database
  • Name the database (e.g. SieveStore) and click on OK
  • Open the Query Analyzer (Menu Tools>Query Analyzer)
  • Select the newly created database (e.g. SieveStore)
  • Execute the scripts found in ...\Vircom\Modus<Mail or Gate>\DBStructures to create the tables (ScriptArchive, ScriptStatistic, ScriptDomainUser and SieveCatalog)
  • It is OK if an error occurs that some tables cannot be removed
  • Close the Query Analyzer and Microsoft SQL Enterprise Manager
  • Check that the  ScriptArchive, ScriptStatistic, ScriptDomainUser and SieveCatalog tables were correctly created in the SieveStore database

  

Importing Your Current Sieve Scripts, Trusted Senders List and Blocked Senders List:

 

  • In MS SQL Enterprise Manager, click on Databases
  • From the menu bar, click on Action > All Tasks > Import Data

o        The DTS Import/Export Wizard should appear  - click on Next

  • At Data Source, use the pull-down menu and select Microsoft Access
  • At File Name, browse for SieveStore.mdb, located in ...Vircom\Modus<Mail or Gate>\SieveData and click on Next
  • At Destination, use the pull-down menu to select a destination as your SQL server

o        The destination will be preset as your SQL server

  • Select Use SQL Server Authentication and click on Next
  • In the Specify Table or Query panel, select Copy table(s) and view(s) from the source database and click on Next
  • In the Select Source Tables and Views, select Select All and click on Next
  • Click on Next twice and Finish to complete the operation
  • The 4 tables should have been exported successfully

 


Configuring the SieveStore DB on the Modus Server

 

  • On your server, go to Administrative Tools > Data Sources (ODBC)
  • Click on System DSN
  • Click on Add
  • Select the driver for which you want to set up a data source (most likely SQL Server)
  • Click on Finish
    • Enter the name of the data source, its description and specify to which SQL Server you want to connect (likely the name of the SQL Server)
  • Click on Next and continue configuring your new DSN
  • Use SQL Authentication and the account created when installing SQL Server
    • Set the database as the default database (i.e. SieveStore)
  • Click on Finish
  • Ensure that the configuration is correct and click on Test Data Source to test the data source
  • If everything is OK, the message TESTS COMPLETED SUCCESSFULLY will appear - your data source is now properly created
  • Open the Modus Console and go to Spam – Properties – Sieve Database
  • Enter the name of the newly created System DSN, its user name and password
  • Click on Apply



 

NOTE:  If you were using another database for the Sieve DB before creating one in SQL Server and perform a spam update, there is a chance that you may get an error stating that there are no new updates.  This indicates that the the database is not being updated.
 
To resolve this issue, proceed with the following:
  • Open the Registry Editor
  • Go to HKEY_LOCAL_MACHINE\System\Modusadm\Parameters
  • Delete the SieveUpdateLUSN and SieveUpdateLUD keys
  • Exit the Registry Editor and perform another spam update

 

Modified 7/23/2007
Keywords: sievestore database sieve database SQL
Article ID: 1562