What is SpamAssassinBundled and how to...

Article updated on 22 January, 2008

What is SpamAssassinBundled and how to enable it as an anti-spam filtering system in AXIGEN

1. Besides a SpamAssassin connector which is available in all previous versions, AXIGEN 5.x delivers a built-in SpamAssassinBundled filter that can be used as an anti-spam filtering system.
Controlling the scanner can be done via the provided axigenfilters initscript. The specific location of this initscript for your OS platform can be located in the README file that is included in the downloaded AXIGEN package.

For example on Linux platforms this location may be:

/etc/init.d/axigenfilters
Usage: /etc/init.d/axigenfilters { start | stop | restart | force-reload | status | quiet-status }

Please note that this inistcript also controls the operations on other filters provided by AXIGEN such as:
AxigenDK Verifier
AxigenDK Signer
AxiMilter

2. This section presents details about the built-in SpamAssassinBundled filter if it is needed to adapt the default configuration details and rules as to match your existing requirements.

In order to verify the version and available options of the Bundled SpamAssassin Daemon currently provided with your AXIGEN package, you can access this data by issuing: ${spamd} -V or --help. Please note that ${spamd} must be replaced with the path to the Bundled SpamAssassin Daemon specific for your OS, as found in the provided README file.

As an example on Linux:
/opt/axigen/bin/spamd -V
The supported options and attributes that can be enabled for this scanner can be obtained via the following command:
/opt/axigen/bin/spamd --help

If it's needed to modify the existing behavior or enable some specific requirements, the arguments that can be passed to the spamd daemon can be specified in the axigenfilters initscript under the DAEMON_OPTIONS_spamd variable. For other configuration data and rules files for the bundled SpamAssassin package you can also verify the specific locations under the README file that comes with your AXIGEN Mail Server package.

Note that if you decide to modify the socket address of this filter, you will need to define the new filter address in the AXIGEN configuration file, axigen.cfg under the AV:SpamAssassinBundled socket filter section.

3. After starting the SpamAssassinBundled filter via the axigenfilters initscript, you should verify that the filter is properly running and binds to the defined address with the use of the netstat command.

If  the default configuration of the filter is used, the output should reveal something along the lines:
tcp    0    0 127.0.0.1:1987      0.0.0.0:*         LISTEN      1933/spamd -d
The filter will by default bind to the loopback address on TCP port 1987

4. Activating the filter can be done via the WebAdmin interface, from the Security & Filtering context -> AntiVirus and AntiSpam -> Supported Applications. If the status of the SpamAssassinBundled filter is currently Could not connect, you should restart the filter detection process by selecting the corresponding option found at the bottom of this section.
An Available status on the filter indicates that AXIGEN has detected the specified filter, and you can choose to activate it by selecting the Enable button.

Releases: Mail Server 5.0.X
OS: Linux, FreeBSD, OpenBSD, NetBSD, Solaris
Distros: RPM based distros, RPM based distros with gcc4, Slackware, Debian, Ubuntu, Gentoo, FreeBSD 5.4, NetBSD 3.0, OpenBSD 3.8, OpenBSD 3.9, Solaris 10 x86, FreeBSD 6.1, Mandriva Linux, DEB based distros with gcc4, Yellow Dog, Solaris 10 SPARC