Re: Scanning email

dspam seems to work well for me. The following is my two cents regarding
dspam, for what it is worth.

I have trouble seeding data for new email accounts.

I have also setup some honeypot email addresses for innoculations
according to the dspam documentation. However. the messages that come
in via the innoculations still appear in my quarrantine list. I get
200-400 spam per day and I have to log into the dspam.cgi and manually
clear out my quarrantine. This issue has been haunting me for a few
months because I am too lazy / unassertive to take the time to fix this
situation.

as far as I can tell, dspam does not scan images or other attachements to
the email message so these new fangled image spams blow right through
dspam unless it is able to trigger on the header information.

the latest dspam version that I am setting up now in my spare time has
some fancy dspam log rotation addon that looks nice. I never really had
any trouble with the log files growing too large though.

I had one system with everything (to do with email) on one spindle.
/var/mail and /var/db/mysql/dsapmdb and /var/spool/mqueue. That did not
survive under load.

I have one with the mysql database on a seperate machine connected via
100 Mb ethernet. It seems to work ok, the other has the database and
mail store on seperate spindles and that also seems to work ok.

I'd recommend storing the user preferences in the sql tables, the
procedure is in the documentation, and then running the sql maintenance
cronjobs. This helps keep the sql data under control.

Anyway, that's all I have to say about that.
Received on Thu Dec 14 14:05:15 2006