Hi Bill,
What exactly is the benefit of using clamd-stream-client?
What we do is we have seperate boxes that receive e-mail (6 systems in
total), which are announced as four different MX hosts. They all do spam
(spamassassin) and virus (clam) scanning, and forward e-mail (if it
contains no viruses, and a spam score lower then 15) to the MTA servers.
If such MX servers (as we call it) fails, there are 5 servers left to
replace this one. So concurrency is quite spread out. However, MTA
servers are all single, we are still looking for a good solution to this...
Kind regards,
Harm van Tilborg
Bill Shupp wrote:
On Apr 24, 2008, at 8:37 AM, Gary Bowling wrote:
I have struggled lately with my server utilization and am now planning
to upgrade my hardware. It occurs to me that the majority of my
utilization problems are due to spam and virus checking and not
general email.
How difficult is it to split the spam and clam components off to a
different server?
Does someone have a "cook book" on how to set this up?
It's not hard. I believe simscan let's you specify the spamc arguments
(to talk to a remote spamd server). Regarding clamdscan, I use
clamd-stream-client, and call it with a shell script. On the client
system, I simply replace the clamdscan binary with my shell script
(which calls clamd-stream-client to talk to the remote clamd server).
No changes to the simscan setup needed for this.
Regards,
Bill
