Installation of DSPAM

Gotchas

Never use the default MySQL table type (myisam) for DSPAM, otherwise, whenever the MySQL daemon is killed or the machine is rebooted unexpectedly, the database will become corrupt and it will take a lot of time to repair. Always use the innodb table type. Just issue something like "alter table TABLE-NAME type=innodb" after creating the DSPAM tables.

In addition, the purge.sql script may prevent DSPAM from updating the DB while it is running. Strangely in that case DSPAM will not write any header into the mail but the processing is considered successfully. To prevent such cases, try setting the innodb_lock_wait_timeout to a larger value (default is 50 seconds) in /etc/mysql/my.cnf. You may run purge.sql manually to see how long it takes and then decide the value to use.

Integration with MTA

The most transparent way to your users to run DSPAM is to integrate it with the MTA. This can be tricky so make sure first that your MTA is setup properly and working. Often there is more than one possible way, so choose the one that works best for you. On a single user installation it might be better to call DSPAM from your mail delivery agent (see below).

Integration with MDA

Calling DSPAM from your MDA (e.g. Procmail or Maildrop) is the easiest way of integration. Choose this on a single user setup or a small scale installation with only local, knowledgeable users.

Integrating with MUA

Moving to DSPAM

Tips for moving to DSPAM from other Anti-Spam solutions

STEP BY STEP HOWTOS

* http://dspam.wahlfaelschung.de - German HOWTO/TUTORIAL about setting up a full featured Mailserver (from tarballs, not distribution-specific), with Exim/Courier-IMAP/DSpam/ClamAV/SpamAssassin/Apache2

* [Postfix-DBmail-PostgreSQL + ALT Linux] Russian from Maxim Z

last edited 2007-05-24 04:16:45 by KentTong