Thanks for all the quick replies!  I was able to get both the mileters
up and running.  Now I have one new question... When I run spamd...

/usr/local/bin/spamd -d -u nobody

I get these errors...

[24001] warn: unix dgram connect: Socket operation on non-socket at
/usr/perl5/site_perl/5.8.4/Mail/SpamAssassin/Logger/Syslog.pm line 79
[24001] error: no connection to syslog available at
/usr/perl5/site_perl/5.8.4/Mail/SpamAssassin/Logger/Syslog.pm line 79

Any ideas?

Thanks Again!!!!

---

Chris Edwards


-----Original Message-----
From: Mike Jackson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 10, 2006 12:41 PM
To: users@spamassassin.apache.org
Subject: Re: Big Idiot Needs Instructions

> I have spent two days trying to figure out how to get the following to

> work.  I have set up Spamassassin and ClamAV, I am running sendmail on

> the Solaris 10 platform.  I would like to be able to scan for all spam

> and virus (in, out and relayed email).  Can someone please point me in

> the right direction?  Do I use procmail or something else.  I set this

> particular combination up years ago on a Linux box but I have had a 
> lot of gigo since then.

Both SA and ClamAV can run from milters - ClamAV comes with its own, but
you'd have to Google for the SA one (or check the FAQ; I don't know if
it's listed in there). That would scan the messages before they come in
the door, and you can reject accordingly at the MTA level. You can also
use procmail; for SA you'd likely want to run spamd, then invoke spamc
from procmail (either system-wide or on a per-user basis, your call). I
use this script to pass messages to clamscan (or clamdscan) via
procmail:

http://www.virtualblueness.net/~blueness/clamscan-procfilter/clamscan-pr
ocfilter.pl

You can bounce messages that were detected via procmail, but it's a bad
idea. 



Reply via email to