I've been experiementing, as I mentioned once before, with SA 3.0. I've found rules that need tweaking based upon either 50+ character descriptions or 22+ character names, but have noted another curiosity.

My setup is SurgeMail running on RH Linux 9, with BitDefender command line scanner for virus protection, and SA for spam filtering. I'm flagging anything that scores over a certain level, and deleting anything that scores arbitrarily higher, pretty standard stuff. Surgemail spawns spamc on each message and filters the mail. Now here's my dillemma:

I have been running spamd using the distributed spamassassin script in the old /etc/init.d directory. This worked fine through versions 2.63. the spamc client runs from /usr/bin/spamc. spamd starts normally on system startup or be calling the script, but I can run spamc from the MTA or from the command line, and nothing happens. The original message just passes through. I suspect that spamd is not responding. If I start spamd from the command line as user spamd "spamd -d -u spamd" it works great. If I change the spamdoptions variable in the startup script or in the sysconfig directory to match the command line, it runs but doesn't respond. The only thing I see immediately in the script is it calls spamd with the daemon function, with runlevel NICELEVEL$ as set somewhere else. Further, if I comment out that line and insert the text of the command line above, it doesn't behave any differently.

Anyway, there is something I don't understand here, so if anybody has a bit of insight I'd appreciate it. I'm getting ready to migrate a user base from one system to another in a few weeks, and would just like to not have to be experiementing at a later date with things like permissions and runlevels on a live system.

Thanks

Ben Hanson
I.S. MGR
Transprint USA Inc.

Reply via email to