Hello all,
I noticed in my spamd logs that the port that spamd/c connect on is
always incremented upward. Is this normal behavior? What happens
when a port number is hard coded for spamd and spamc? Do they start
to increment from there?
I'd just like to know what is supposed to happen. I wa
I downloaded and installed 2.0. When I ran the spamassassin -t test
I got a weird error:
enterprise# ./spamassassin -t < sample-spam.txt > spam.out
Failed to run MISSING_HEADERS SpamAssassin test, skipping: (Can't
locate object method "check_for_missing_headers" via package
"Mail::SpamAssassi
Even with the spamassassin.cf fix in place, spamd processes
occasionally don't close and start to monopolize the CPU. I'm not
sure if it is related but in the procmail log I'm seeing this:
procmail: Timeout, terminating "spamc"
procmail: Rescue of unfiltered data succeeded
It sounds like sp
At 5:28 PM -0500 1/15/02, CertaintyTech - Ed Henderson wrote:
> > On Tue, Jan 15, 2002 at 02:15:43PM -0500, Cayce Will wrote:
>> > Every so often one or more children of the spamd -d daemon
>> don't die
>> > and they start to gobble up all the CPU o
Every so often one or more children of the spamd -d daemon don't die
and they start to gobble up all the CPU on my E250 running Solaris
2.6. Eventually I have to kill them manually (i'm not sure if they
die by themselves if I just let them go, some have sat there over
half an hour sucking up
