Re: Problems with latest SA upgrade
Well, I'm now up and running...somewhat. I opened up a whole lotta permissions on the server and it's now letting mail be filtered, but the --lint command still renders errors on the user level. But at the same time I'm finding some really nasty problems with the box itself at this point. So since I've got a new one due in about two weeks I'm going to limp along with what I've got, then I'm going to build the new box, get SA setup, and troubleshoot any problems that one has on initial setup from there. So for now I'm going to consider this resolved for the time being. Just perfect timing to have my box go south before I can even get the new one in. -_-;; *sigh*
Re: Problems with latest SA upgrade
CC'ing this to the list. I replied from the wrong address. heh. ^_^ --- I think I found the issue. Went and did "spamassassin --lint" as user and it hurled its cookies. But if I did it under root, it didn't. So somewhere I've got some nasty little permissions issues that weren't there before. Hmm. Drat, drat, drat. I could be all year sorting this out. Anyone got a list of what directories and files SA looks at and what the permissions should be for a user to be able to use SA from the shell? I could find it out eventually myself, but if someone already had a list, that'd make my day SO much easier. At 04:45 PM 3/29/05 -0500, Matt Kettler wrote: Steve Lake wrote: > Hi all. Just upgraded my copy of Spam Assassin to the latest > build on Freebsd 4.10 and suddenly it's not filtering mail. It loads > up fine, and I can see the child processes like what's supposed to be > there, but nothing seems to get handed off to procmail. I'm not > totally sure what's up. I don't even get the typical > "X-spam-whatever" at the top of any of the messages anymore. I > currently have Procmail 3.22 installed on my system and it appears to > be running right, but SA isn't doing anything. Any suggestions on > where I can look? Step 1 - make sure the new version of SA understands your config files spamassassin --lint Step 2 - try manually feeding the sample-spam.txt that comes with SA to spamc. spamc < sample-spam.txt
Re: Problems with latest SA upgrade
Steve Lake wrote: > Hi all. Just upgraded my copy of Spam Assassin to the latest > build on Freebsd 4.10 and suddenly it's not filtering mail. It loads > up fine, and I can see the child processes like what's supposed to be > there, but nothing seems to get handed off to procmail. I'm not > totally sure what's up. I don't even get the typical > "X-spam-whatever" at the top of any of the messages anymore. I > currently have Procmail 3.22 installed on my system and it appears to > be running right, but SA isn't doing anything. Any suggestions on > where I can look? Step 1 - make sure the new version of SA understands your config files spamassassin --lint Step 2 - try manually feeding the sample-spam.txt that comes with SA to spamc. spamc < sample-spam.txt
Problems with latest SA upgrade
Hi all. Just upgraded my copy of Spam Assassin to the latest build on Freebsd 4.10 and suddenly it's not filtering mail. It loads up fine, and I can see the child processes like what's supposed to be there, but nothing seems to get handed off to procmail. I'm not totally sure what's up. I don't even get the typical "X-spam-whatever" at the top of any of the messages anymore. I currently have Procmail 3.22 installed on my system and it appears to be running right, but SA isn't doing anything. Any suggestions on where I can look?
