Populating the QMS System

From GWAVA4

There are three ways to populate the QMS system - via the Quarantine service in GWAVAMAN, via the Global Quarantine options in GWAVAMAN, and via manual import.

Quarantine Service

This is covered in detail in Events and Services.

In brief, when a message triggers an event, such as a text filter, GWAVA can be configured (using the web interface in GWAVAMAN) to Quarantine the message. The MIME message, along with an XML routing envelope containing metadata, is then dropped in the QMS import queue and imported by the QMS.

Global Quarantine

For diagnostic or compliance reasons, it may be desirable to automatically quarantine all messages that pass through the GWAVA scanner engine, regardless of scan results. Another reason is to build detailed custom reports.

Of course, the original message is NOT blocked unless an event with a block service attached is processed.

This can be enabled in the GWAVAMAN web interface. Select the server object, then Manage Scanners, then the scanner object, and then Message services. Finally, click on Global Quarantine.

• Store all message envelopes in the quarantine - this will store the database information, but not the actual message. The message will be displayed in the QMS Message List, and can be searched for using the Search Form, but the actual message contents cannot be displayed, and the message cannot be released or forwarded. However, this option takes a lot less disk space.
• Store all messages and message envelopes in the quarantine - Stores both the database information and the actual message. All messages will be available in the QMS Message List, and all functions such as release and forward will function normally.

Note: It doesn't actually makes sense to select both options.

Note: Don't forget to click Save Changes after changing the configuration.

Note: Messages will not be included in digest reports unless blocked by the appropriate event.

Manual Import

In normal operations this is never done. However it is possible to manually import information into the QMS. One scenario might be disaster recovery, where the items under the <GWAVARoot>/services/qms/data/storage subdirectory are intact but the databases are not.

Unless you've changed the configuration setting (Configuring General Server Options), the import queue for QMS is located at <GWAVARoot>/services/qms/in_queue.

Two files, each with the same filename, but different extensions are expected. The MSG file is an RFC 822 MIME message in its entirety, including text and attachments. The MSR file is an XML formatted message containing metadata such as the routing envelope, the source of the message, date of the message, etc. It's probably easiest to look at some regenerated files under the <GWAVARoot>/services/qms/data/storage directory to understand the format of this file.

After the importing process, the message files are moved from the in_queue to the storage subdirectory, partitioned by year, month, day, etc. The main data database (qms_data.db) will now contain the imported information used for searching and display in the web interface.