> :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\
> 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 (
+,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i 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.
d changing .procmailrc to use spamc, but I'm getting the same
"permission denied" error--i.e., it complains:
/bin/sh: /usr/bin/spamc: Permission denied
procmail: Program failure (126) of "/usr/bin/spamc"
--
View this message in context:
http://www.nabble.com/Spamassas
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
> 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
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
hat didn't
do anything.
I could only find one relevant posting with a similar error (located here
http://use.perl.org/~samtregar/journal/29278), but that doesn't sound like
my problem.
Thanks for any suggestions.
--
View this message in context:
http://www.nabble.com/Spamassassin-not-working-after-upgrade-tp21982029p21982029.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
