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 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 be, but nothing that I've tried (changing
>> config files, restarting spamd, etc.) has worked.
>
> Uhm, according to your procmail logs below, you are not using spamd
> anyway. I do however strongly recommend to do so -- that is, in procmail
> use spamc instead of 'spamassassin'.
>
> This will result in less load on the server and faster mail processing,
> since spamassassin doesn't have to be started for each mail. The spamd
> daemon needs to be running for that. (Yes, this isn't related to the
> issue at hand.)
>
>
>> Here is the relevant part of the log file for a sample email after
>> turning
>> the verbose option on in .procmailrc:
>
>> procmail: Executing "/usr/bin/spamassassin"
>> /bin/sh: /usr/bin/spamassassin: Permission denied
>> procmail: Program failure (126) of "/usr/bin/spamassassin"
>> procmail: Rescue of unfiltered data succeeded
>
> RHEL5. Any chance this problem is SELinux related?
>
>
> --
> char
> *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
> main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8?
> c<<=1:
> (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0;
> }}}
>
>
>
--
View this message in context:
http://www.nabble.com/Spamassassin-not-working-after-upgrade-tp21982029p21999350.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
