Portal Home > Knowledgebase > SMCP > Building DSPAM for use with cPanel and SMCP
Building DSPAM for use with cPanel and SMCP
The best way to install DSPAM for use with SMCP is to install it as an RPM even though it can be installed from the distribution TAR file. The DSPAM distribution file can be downloaded here. The latest version is 3.10.2. We recommend installation as an RPM for easier installation and distribution across multiple servers. Keep in mind when using either method to build DSPAM that SMCP requires the DSPAM binaries in specific locations for proper operation.
Building DSPAM with RPM
To build DSPAM with RPM do the following:
- Download the DSPAM source RPM from the Fedora Project site. The latest version of the DSPAM source RPM can be downloaded at here. The Fedora Project source is only required for a few of the additional files that are part of the Fedora RPM package such as the logrotate configuration file and the start up script to start DSPAM in daemon mode.
- Download the spec file we provide to build DSPAM for use on a cPanel server. The spec file can be downloaded here. The spec file is just a modified version of the spec file provided by the Fedora Project in their DSPAM source RPM.
- Download DSPAM from Source Forge. The latest version is 3.10.2 and it can be downloaded here. This isn't really required since the DSPAM source archive file is included in the Fedora Project DSPAM source RPM.
- Install the Fedora Project DSPAM source RPM on the build server.
- Copy the dspam.spec file that we have provided to the "SPECS" directory of your RPM build directory to replace the Fedora Project RPM spec file.
- Run the "rpmbuild" command to build the DSPAM RPM. If you are not familiar with how to build RPM packages you can check the RPM documentation at www.rpm.org.
- The DSPAM RPM packages will be in the appropriate architecture directory in "/usr/src/redhat/RPMS". The DSPAM packages that need to be installed for a working installation of DSPAM are the following:
- After installing the DSPAM RPMs you do not need to create the database for DSPAM to use because the dspam-mysql RPM will create the DSPAM database and the dspam database user..
Building DSPAM from the source distribution file
This method can be used to build and install DSPAM but it is not recommended.
Additional information on building DSPAM from the source distribution is available at the DSPAM site or the README file included in the source distribution. The main thing to remember when building DSPAM for installation via this method is to use the parameters for the configure script that are listed in this section.
- Download DSPAM from Source Forge. The latest version is 3.10.2 and it can be downloaded here.
- Extract the DSPAM archive file and go into the directory that was created when the file was extracted.
- Enter the following command from the command line:
./configure ---enable-daemon --enable-domain-scale --enable-long-usernames --enable-syslog
--disable-large-scale --enable-clamav --disable-homedir --enable-virtual-users --enable-preferences-extension
--enable-debug --with-mysql-includes='/usr/include/mysql' --with-dspam-home='/var/lib/dspam'
- Run the "make" command to build and then install DPSAM.
- Create a database for DSPAM in MySQL named "dspam" and use the MySQL schema files provided with the DSPAM source to create the tables. The files to use are mysql_objects-4.1.sql and virtual_users.sql.
- Create the "dspam" user in MySQL and grant it all priveledges to the "dspam" database.
Locations where SMCP expects various DSPAM files to be located
SMCP looks for the DSPAM binaries, data and configuration files in specific locations in the file system. If the DSPAM files are not in those locations SMCP will not work properly. The locations where SMCP expects to find the DSPAM files are the following:
- The binaries need to located in either "/usr/bin" or "/usr/local/bin".
- The data directory where the quarantine boxes are located needs to be in "/var/dspam"
- The configuration file needs to be in "/etc" or "/usr/local/etc":
Add to Favourites Print this Article
SMCP FAQ (Views: 6663)
SMCP Features (Views: 1772)