Options and database setup (was: Re: [dspam-users] ./configure)

* Kyle Johnson <kjohnson@fixertec.net> [2005-12-28 21:47:57 -0500]:

> >what is the general configure that everyone seams to use? both with mysql
> >and with out.

> Configuration parameters: --enable-daemon
> --with-storage-driver=mysql_drv
> --with-mysql-includes=/usr/include/mysql/ --enable-preferences-extension
> --with-dspam-home-owner=dspam --with-dspam-home-group=dspam
> --with-dspam-home=/usr/local/var/dspam --with-dspam-mode=dspam
> --with-dspam-group=dspam --enable-domain-scale --enable-virtual-users
> --enable-clamav --enable-debug
>
> However, this depends a lot on your setup.

I think the most critical options are the ones that deal with
ownership and storage (although you can change file and directory
ownership later if your settings didn't work).

Start with only the necessary options and get it all working. You can
still rebuild if you need more. I suggest you use a MySQL storage
from the start -- I found it easy enough to set up and it gives you
various advantages over the file storage setup. Migrating later might
lead to hassles.

Also you should know that if you enable virtual users, DSPAM will
expect to find every user in the virtual user database. So if you
have local Unix users as well you have to create a dummy entry for
them in the database (did anyone manage to get around this?).

I have combined my Postfix and my DSPAM databases into one, so that
DSPAM can access the Postfix virtual user database to look up users.
If you don't do this you will have to create every user twice. Make
sure you have some kind of marker attribute that separates real
Postfix virtual mailbox users from DSPAM dummy users (I've got an
'enabled' column as found in many HOWTO setups; it is set to 'no' for
the DSPAM users, so the entries are invisible to Postfix). This all
as well applies to other MTAs using an SQL storage, of course.

Also I would not recommend to use the built in ClamAV support. It
works fine but you get additional control of you run ClamAV
separately. For example, on my server I run *every* message (incoming
as well as outgoing) through AV, while invoking DSPAM only on local
delivery (I don't want to have relayed messages scanned for Spam).
This way you're also able to enable/disable DSPAM on a per-user basis,
while having virus scans for all your mail.

On a simple home office setup with only one mail user you definitely
should go for a simple setup: Enable MySQL and not much else and
invoke DSPAM from your '.forward' file or '.procmailrc' or
'.mailfilter', whatever you are using. The DSPAM homepage has got a
wiki entry about this, which works nicely.

Kyle is right when he says that "it depends". There is no holy
configuration grail out there. I only wish the documentation was a
bit more cleaned up. I'm still missing proper explanations of the
available preferences options.

--Frank
Received on Thu Dec 29 05:04:24 2005