Aug 25 07:22:43 samx2 amavisd[23078]: SpamControl: initializing Mail::SpamAssassin
Also, you can watch only SA related items by starting it with: amavisd debug-sa Lastly, are you running amavisd in a chroot jail? If so did you correctly setup all the chroot directories and copy the needed files over? -matt Matt: Thanks for the reply: Will try the debug-sa. Looks like I have some other reading to do. Not sure about running amavisd in a chroot jail. I following the instructions in the Scott Henderson document and copied files where indicated. Ron -------------------------------------------------------------------- Ron Nutter [EMAIL PROTECTED] Network Manager Information Technology Services (502)863-7002 Georgetown College Georgetown, KY 40324-1696 -------------------------------------------------------------------- -----Original Message----- From: Matt Yackley [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 10:29 AM To: [email protected] Subject: RE: Questions about SA Ronald I. Nutter said: > I am trying to figure out how SA is being called. So far, according > to the Scott L Henderson instructions, I installed Spamassassin but > don't see how it is being called. I tried emailing scott about > another question and didn't get a response, so I didn't even try to > ask him on this. > > I looked in maillog and see postfix and amavisd reporting in but no > SA. > > Will see about adding some more memory. > > Ron > > -------------------------------------------------------------------- > Ron Nutter [EMAIL PROTECTED] > Network Manager > Information Technology Services (502)863-7002 > Georgetown College > Georgetown, KY 40324-1696 > -------------------------------------------------------------------- > > > -----Original Message----- > From: Ed Kasky [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 25, 2004 9:36 AM > To: Ronald I. Nutter > Subject: Re: Questions about SA > > > Ron - > > How are you calling SA? there are 2 options: > 1. calling the perl script spamassassin for each email to be scanned > 2. using spamc to call spamd - the deamonized version. > > I wouldn't suggest anything lower than 512 mb ram. I am running a 500 > mhz p3 with 512 but it only handles about 5,000 emails a day. I am > assuming > > you're going to have a few more than that... > > hth, > > Ed > > On Wed, 25 Aug 2004, Ronald I. Nutter wrote: > >> I just finished getting SA up and running using the Scott L Henderson >> document. It passes the tests in the documents. I don't see Spam >> assassin running as a process like postfix and amavisd. Is there a >> way to check that it is running ? >> >> Also, what is suggested for hardware to run it on ? I will be >> dealing > >> with 1500 faculty/staff/students. I have it on a 400 mhz pentium >> with > >> 32 megs of ram. I know I will need to add more memory before going >> to > >> production but wasn't sure about the processor. >> >> Ron [Snip] Hi Ron, If you are using amavisd-new, then you won't see SA loaded anywhere like you see amavis or postfix. Amavisd-new runs the SpamAssassin script in its own daemonized mode. If you want to see what amavisd is doing try starting it from the command line like this: amavisd debug Watch for the lines where it loads the various modules: Aug 25 07:22:43 samx2 amavisd[23078]: Lookup::SQL code NOT loaded Aug 25 07:22:43 samx2 amavisd[23078]: Lookup::LDAP code NOT loaded Aug 25 07:22:43 samx2 amavisd[23078]: AMCL-in protocol code loaded Aug 25 07:22:43 samx2 amavisd[23078]: SMTP-in protocol code loaded Aug 25 07:22:43 samx2 amavisd[23078]: ANTI-VIRUS code NOT loaded Aug 25 07:22:43 samx2 amavisd[23078]: ANTI-SPAM code loaded and Aug 25 07:22:43 samx2 amavisd[23078]: SpamControl: initializing Mail::SpamAssassin Also, you can watch only SA related items by starting it with: amavisd debug-sa Lastly, are you running amavisd in a chroot jail? If so did you correctly setup all the chroot directories and copy the needed files over? -matt
