>On Thursday, June 20, 2002, at 02:34 PM, M. Brownsworth wrote: > >>I'm running spamd 2.20 as root on a FreeBSD 4.5 server, with >>system-wide filtering. It seems to be disregarding anything in >>/etc/mail/spamassassin/local.cf. Yesterday, I added my address as >>"all_spam_to [EMAIL PROTECTED]," but spamd/procmail then >>subsequently filtered and intercepted numerous messages, completely >>ignoring the entry. A few messages have been posted by folks >>reporting the same problem, but I've seen no responses suggesting a >>cause or a solution. I hope someone on the list can shed some >>light. >> > >Have you restarted spamd since making the change? This is the usual >cause of the problem.
I've -HUP'ped spamd every time local.cf has been modified. But just for grins I killed it completely and restarted it. It came up for a short while then died. Odd, I thought. I restarted it again with the same result. So figuring it was time to upgrade to the latest version, I downloaded 2.31 and installed it. After it was installed, the first time I tried to start spamd it complained about the following missing modules: Can't locate Time/HiRes.pm in @INC Can't locate Pod/Usage.pm in @INC So away to CPAN to get them. Started spamd again, using the following script as usual: #!/bin/sh [ -x /usr/bin/spamd ] && /usr/bin/spamd -d -F 1 && echo -n ' spamd' Again it ran briefly (until it was invoked by spamc, I think) then died. Seeking more information, I added a "-D" switch for debugging, and restarted spamd. This time it stayed running when it was invoked by spamc, with these entries from procmail.log: procmail: Executing "spamc" procmail: [1597] Thu Jun 20 13:41:51 2002 procmail: Skipped "* ^X-Spam-Status: Yes" procmail: Skipped "/var/log/spam" It stays running in debug mode, but without the "-D" it expires quietly and unceremoniously. This is very strange behavior, all of a sudden. I have spamd 2.20 installed on 6 servers and, although I think they're disregarding /etc/mail/spamassassin/local.cf, they're filtering messages and -- most importantly -- they stay running. I'm headed back to CPAN for 2.30, to rule out the problems being caused by the brand-new 2.31 version. In the meantime, do any of you folks have any explanations for the problems I'm seeing that do not involve the supernatural? .\\ichelle --------------------- Michelle Brownsworth System Administrator PrimeLogic Corporation http://www.primelogic.com ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
