On Tuesday 13 December 2005 13:31, Kai Schaetzl wrote: >Gene Heskett wrote on Tue, 13 Dec 2005 12:15:46 -0500: >> /var/log/mailman/maillog > >Then your syslogd.conf is, ahm, "unconventional" ;-) > >Kai
If it is, its the fedora core 2 default, I haven't changed it. Now, pursuant to someone elses advice, I've got those directories, both /root/.spamassassin and /etc/mail/spamassasin have been subjected to a chown -R spamd:spamd, but the perms problems continue, and this frigging paypal/ebay phishing is coming in at about 200 copies a day. From the logs in the last 5 minutes or so: Dec 14 01:22:56 coyote spamd[2843]: locker: safe_lock: cannot create tmp lockfile /root/.spamassassin/auto-whitelist.lock.coyote.coyote.den.2843 for /root/.spamassassin/auto-whitelist.lock: Permission denied Dec 14 01:22:56 coyote spamd[2843]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /root/.spamassassin/auto-whitelist.lock.coyote.coyote.den.2843 for /root/.spamassassin/auto-whitelist.lock: Permission denied Dec 14 01:22:56 coyote spamd[2843]: Can't call method "finish" on an undefined value at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Plugin/AWL.pm line 397, <GEN17> line 77. Dec 14 01:22:56 coyote spamd[2843]: spamd: clean message (1.5/5.0) for root:1002 in 0.3 seconds, 3620 bytes. Dec 14 01:22:56 coyote spamd[2843]: spamd: result: . 1 - FROM_HAS_MIXED_NUMS scantime=0.3,size=3620,user=root,uid=1002,required_score=5.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=33632,mid=<[EMAIL PROTECTED]>,autolearn=no /root/.spamassassin isn't mentioned in any of the config files that I know about. The passwd entry for spamd=spamd:x:1002:1002::/home/spamd:/bin/bash But, it hasn't touched that directory. It persists in using the /root/.spamassasin directory even though there is a user named spamd now, and the launch argument -u spamd is given in /etc/int.d/spamd. But, according to htop, all incarnations of spamd are in fact running as root. There is not an actual entry for a password been setup for spamd that I know of. Is that part of the problem? However if thats the case, would I not have to pass that as an argument to the spamd launch in addition to the -u spamd argument? I'm running out of hair, and at 71, thre isn't all that much anyway... Gawd, I wish I'd never replaced 3.0.4, it worked reasonably well until this phishing crap got out of hand. -- Cheers, Gene People having trouble with vz bouncing email to me should use this address: <[EMAIL PROTECTED]> which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) 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.
