Hi there, On Fri, 8 Jun 2012, c0re wrote:
Architecture is pretty simple: 1st server with clamd, clamav-milter. 2nd server with sendmail.
You're stil being pretty economical with the information. What's the network connection between the servers? What volumes of traffic does it carry?
So when email arrives to sendmail, it checks via spamassassin local socket, then send via inet to clamav-milter, then to other milters in a row.
I would never call SpamAssassin first. The vast majority of the mail that attempts to pass through my servers never gets as far as a Perl script, it's dropped by something much less CPU and memory intensive before it gets that far down the milter chain.
There is no memory problems: Mem: 350M Active, 2235M Inact, 466M Wired, 417M Buf, 880M Free Swap: 4096M Total, 4096M Free No CPU problems: load averages: 0.06, 0.04, 0.06 CPU 0: 7.1% user, 0.0% nice, 1.1% system, 0.0% interrupt, 91.8% idle CPU 1: 6.7% user, 0.0% nice, 0.4% system, 0.0% interrupt, 92.9% idle
Well there were no problems at the time you took those snapshots. :) I run things like "top -b -n1 >/var/log/top.log" (and similar) fairly frequently from the crontab, I can analyze the logfiles as needed by means of assorted coreutils for simple stuff and even graph plotting if it seems necessary. -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
