Re: Spamassassin not working after upgrade

2009-02-13 Thread Karsten Bräckelmann
> :0wf > | /usr/bin/spamassassin If there is even the slightest chance for a mail surge -- you probably should add a lock file to that recipe. (Not to mention using spamc again, which you appear to already have switched to. ;) -- char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\

Re: Spamassassin not working after upgrade

2009-02-13 Thread Karsten Bräckelmann
> This seems to have been SELinux related. When I temporarily disable it, > procmail is able to execute spamc and properly filter incoming messages. > Thanks for the suggestion. This is a huge relief! Ah, goodie. :) Please file a bug with RH against SELinux, for both permission denied issues (

Re: Spamassassin not working after upgrade

2009-02-13 Thread nycsurf
This seems to have been SELinux related. When I temporarily disable it, procmail is able to execute spamc and properly filter incoming messages. Thanks for the suggestion. This is a huge relief! Best, Greg Karsten Bräckelmann-2 wrote: > >> I recently upgraded to spamassassin-3.2.5-1.el5 u

Re: Spamassassin not working after upgrade

2009-02-12 Thread nycsurf
> Can you post the procmail ruleset that tries to run spamassassin? I've been trying several different rulesets. Here's the latest: LOGFILE=/home/gjw10/mail/maillog VERBOSE=on PATH=/bin:/usr/bin:/usr/local/bin SHELL=/bin/sh :0wf | /usr/bin/spamassassin :0: * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*

Re: Spamassassin not working after upgrade

2009-02-12 Thread John Hardin
On Thu, 12 Feb 2009, nycsurf wrote: Spamassassin correctly identifies the sample spam message when I do spamassassin -D < /usr/share/doc/spamassassin-3.2.5/sample-spam.txt Does /usr/bin/spamassassin behave properly from the command line? {sorry for two messages} procmail: Executing "/usr/b

Re: Spamassassin not working after upgrade

2009-02-12 Thread Karsten Bräckelmann
> I recently upgraded to spamassassin-3.2.5-1.el5 using up2date and > spamassassin is no longer filtering messages. Spamassassin correctly > identifies the sample spam message when I do [...] > I've googled extensively to see if anyone else is having this problem and > what possible solutions might

Re: Spamassassin not working after upgrade

2009-02-12 Thread John Hardin
On Thu, 12 Feb 2009, nycsurf wrote: Here is the relevant part of the log file for a sample email after turning the verbose option on in .procmailrc: procmail: Assigning "DROPPRIVS=yes" procmail: Assuming identity of the recipient, VERBOSE=off procmail: Assigning "PATH=/bin:/usr/bin:/usr/local/b