Greetings; I did have SA-2.64 installed and was using it with kmail from the kde-3.3.0 install, heavily hacked FC2 system, present kernel 2.6.12-rc1-mm1.
This had generated a series of files in /root/.spamassassin including a bayes_journal, which after about a years running, was only expanded to about 2700 bytes. After setting spamd to be run from /etc/init.d, using the options in /etc/sysconfig/spamassassin of: ---------------- # Options to spamd SPAMDOPTIONS="-d -c -m10 -H" ---------------- which are the defaults apparently, and changing kmails filter for the spam disposal so it was piped thru spamc, it ran and filtered about 20 spams properly over the next 20 minutes. Then I suddenly start seeing this in the /var/log/maillog: ---------------- Mar 23 21:49:26 coyote spamd[21906]: connection from localhost.localdomain [127.0.0.1] at port 46232 Mar 23 21:49:26 coyote spamd[21906]: info: setuid to root succeeded Mar 23 21:49:26 coyote spamd[21906]: Still running as root: user not specified with -u, not found, or set to root. Fall back to nobody. Mar 23 21:49:26 coyote spamd[21906]: processing message <[EMAIL PROTECTED]> for root:99. Mar 23 21:49:26 coyote spamd[21906]: cannot write to /root/.spamassassin/bayes_journal, Bayes db update ignored: Permission denied Mar 23 21:49:26 coyote spamd[21906]: clean message (0.0/5.0) for root:99 in 0.2 seconds, 5182 bytes. Mar 23 21:49:26 coyote spamd[21906]: result: . 0 - BAYES_50 scantime=0.2,size=5182,mid=<[EMAIL PROTECTED]>,bayes=0.455596022142826,autolearn=failed ---------------- FWIW, any attempt to add the --username=root to the above options file results in spamd failing to restart on a 'service spamd restart'. And yes, I run as root, there is lots of firealling between this box and the real planetary network, firewalling thats never, in 2 years of dsl connection, been penetrated any farther than a single "New not syn: etc etc" message in the logs. My guard dogs are good. This snippet is indicating that A: it apparently cannot run as root so it falls back to 'nobody' and B: that it cannot write to /root/.spamassassin/bayes_journal. The file had disappeared! I went back thru the shell history to make sure I hadn't done anything stupid, but the only thing between the time it worked, and the files disappearance was my looking at it with the 'less' file viewer. So I touched a new one and set the perms to 0666 so it would be writable. Didn't make any difference. The other files in that directory are being updated if I run a session of sa-learn, but that file isn't being touched, and although the dates are being updated for the other 2 main files, no content is actually being added to them by the sa-learn session as evidence by their unchanging size of several megs each. However, it does seem to be filtering the spam as well as before after I updated the rules for the 2nd filter in kmail as the marker strings had been changed some from the 2.64 version. Its also not marking the subject line [SPAM] like it did before. I'd like it to if possible. From this amount of data, can it be determined whats wrong? Any help accepted with glee & thanks. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
