Vexira Antivirus for Mail Servers version 2.5 released
Changes in product architecture and operation
Integrated daemons
Binaries of the earlier vasmtps, vasmtpd, ... daemons have been removed.
Now, vmbs can be started, by specifying special switches.
Changes:
vasmtpd --> vams start receiver
vasmtps --> vams start sender
vawatchdog --> vams start watchdog
vams --> vams start scanner
vashldstat --> vamsmon
New control command
Operations earlier executed by the vams command have been replaced by a new command: vamsctrl. Users can now use a new init script (vams) to start or stop the program.
Users can interrupt startup
The daemon will not be launched on startup, if the process launching it is stopped (e.g. when a user changes their mind and presses <CTRL>+<C> before the startup has been executed).
Improved startup process
When starting the product, daemons will not return until the whole init process has been completed successfully. In this way, users get precise and direct information on any startup problem.
Filter module related development
Fieldfilter: can filter any message header field
The module designed to filter e-mail headers can now filter any field in the header.
Fieldfilter: filtering for non-existent message header field
When checking the header, a new condition you can specify is the non-existence of a given field. This means that the specified action will be executed only if the header field is missing.
Languagefilter: display online statistics
The hit statistics of the languagefilter component have been made available on the general statistics panel. [statistics dashboard?, stats overview panel?]
Enhanced text filtering
You can now enable case sensitive text filtering. The product is able to evaluate extended regular expressions as well.
Run the filter module several times for the same message
Thanks to the new product architecture, a given filter module can be used several times in the same template. In this way, messages can be checked for different criteria.
Enhanced header field modification option
Header fields, which were modified or added in an earlier status of scanning, can be freely modified later, during the execution of filter modules.
New installation features
Easier custom installation
Whenever the setup prompts for a path during installation into a custom directory, it suggests a default path based on earlier changes.
Installation with user rights (Non-administrator installation)
The setup can now install the product at user level. In this case, the product will be installed and operated using the permissions of the user who initiated the installation.
New features related to black- and whitelists
The "whitelist-bypass" option available for any filter module
You can now disable any filter module when checking mail sent to whitelisted addresses.
Double check server addresses obtained from the "Received" line of message
headers
Going beyond RBL filtering, addresses of servers passing on an e-mail message obtained from the message header can now also be checked against the whitelist and blacklist specified in the configuration.
Changes in configuration file management
Add a file or directory to any part of the configuration file
Now you can issue an include command at any point of the configuration file. The syntax is "@<filename>". Specifying a directory is also supported. In this case, the configuration files corresponding to the specified file name/mask will be read.
Flexible template order
In the configuration file, templates don't need to be listed in the order of their origin any more.
New tokens
All header fields of a scanned message have become available as tokens.
New config file interpreter
The configuration file has got a new line interpreter, implementing several new features.
No more limits on the number of options
Limits on the number of rule, template, target, ... options that can be specified in the configuration file have been removed. Any number of options can be specified.
Custom tokens
Configuration has been made easier and more flexible: users can now specify their own tokens in the configuration file for later use.
Thursday, July 14, 2011 10:37 AM