On Mon, 2009-07-13 at 12:03 +0200, Matus UHLAR - fantomas wrote:
> On 10.07.09 10:28, Admin wrote:
> > I do not see spamassassin processing information in the SMTP header of
> > incoming messages. So I am fairly sure that the processing is not
> > working. I am hoping to get the postfix->proc
On 10.07.09 10:28, Admin wrote:
> I do not see spamassassin processing information in the SMTP header of
> incoming messages. So I am fairly sure that the processing is not
> working. I am hoping to get the postfix->procmail->spamc processing
> path working system-wide. I need some help th
Hi there,
I do not see spamassassin processing information in the SMTP header of
incoming messages. So I am fairly sure that the processing is not
working. I am hoping to get the postfix->procmail->spamc processing
path working system-wide. I need some help though since it is not working.
> :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.
Thanks for your kind response. That change did resolve the problem.
Appreciatively,
Joey
-Original Message-
From: SM [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 3:01 PM
To: users@spamassassin.apache.org
Subject: RE: spamassassin not working - spamass.sock unsafe
At 11
At 11:15 21-03-2007, Joey Davis wrote:
If the spamass-milter creates the following socket:
srwxr-xr-x 1 sa-milt sa-milt0 Mar 21 13:08 spamass-milter.sock
[EMAIL PROTECTED] spamass-milter]# pwd
/var/run/spamass-milter
Should the lines in sendmail config file point to the same exact socket?
then that is my problem. Sendmail is looking for:
/var/run/spamass.sock
From: Sietse van Zanen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 4:11 AM
To: users@spamassassin.apache.org
Subject: RE: spamassassin not working - spamass.sock unsafe
And
Do you look for your car exactly where you parked it?
-Original Message-
From: Joey Davis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 19:15
To: users@spamassassin.apache.org
Subject: RE: spamassassin not working - spamass.sock unsafe
pardon my ignorance here.
If the
Hi,
I had the same problem where an update from spamass-milter seemd to
cause spamassassin milter stop working and give the same error messages
in /var/log/maillog:
Milter (spamassassin): local socket name
/var/run/spamass-milter/spamass.sock unsafe
Milter (spamassassin): to error state
I
Joey Davis wrote:
Greetings ...
I can not get spamassassin to work. I have seen this problem in some
newgroups but no definitive solution. Here is the information
OS Version: FC5
Sendmail: 8.13.7
Spamassassin: 3.1.3
Log entries:
Mar 19 17:28:32 obwat sendmail[29903]: l2JMSW21029903: Mil
And configure the milter to use the same socket location as sendmail. You have
probably only configured sendmail to use the new location and left the milter
with the old loaction.
-Sietse
From: SM
Sent: Tue 20-Mar-07 4:14
To: users@spamassassin.apache.org
Subject: RE: spamassassin not
At 19:08 19-03-2007, Joey Davis wrote:
Don't think it's a permission problem, at least not on this directory.
drwx-- 2 sa-milt sa-milt 1024 Mar 19 17:29 spamass-milter
The milter is not running. Start it.
Regards,
-sm
Joey Davis wrote:
It never creates the socket.
And you're expecting it to work? :)
Initially, the socket was set to reside in
/var/run/spamass.sock and then I saw one suggestion that said to change it
to /var/run/spamass-milter/spamass.sock. I made the change but still
received the unsafe
. O'Shea [mailto:[EMAIL PROTECTED]
Sent: Monday, March 19, 2007 8:14 PM
To: Joey Davis
Cc: users@spamassassin.apache.org
Subject: Re: spamassassin not working - spamass.sock unsafe
Joey Davis wrote:
> Greetings ...
>
> I can not get spamassassin to work. I have seen this problem in som
is'
Subject: RE: spamassassin not working - spamass.sock unsafe
yuo may have wrong perms on /var/run/spamass-milter/ , probably too much.
try chmoding to 755 and check for correct ownership.
i think it's sendmail's thing, not SA's. i've seen this with other milters,
partic
Joey Davis wrote:
Greetings ...
I can not get spamassassin to work. I have seen this problem in some
newgroups but no definitive solution. Here is the information
OS Version: FC5
Sendmail: 8.13.7
Spamassassin: 3.1.3
Log entries:
Mar 19 17:28:32 obwat sendmail[29903]: l2JMSW21029903: Mil
Greetings ...
I can not get spamassassin to work. I have seen this problem in some
newgroups but no definitive solution. Here is the information
OS Version: FC5
Sendmail: 8.13.7
Spamassassin: 3.1.3
Log entries:
Mar 19 17:28:32 obwat sendmail[29903]: l2JMSW21029903: Milter
(spamassassin): lo
At 11:54 AM 10/21/2004, Gary Manigault wrote:
I have
Spamassasin version 2.63. I have some allowed and denied addresses
setup but it doesn't seem to be working. The spamd process it
running. It doesn't seem to be tagging mail from the denied domain
names. I have been testing this with a telnet
Title: Message
I have Spamassasin
version 2.63. I have some allowed and denied addresses setup but it
doesn't seem to be working. The spamd process it running. It doesn't seem
to be tagging mail from the denied domain names. I have been testing this
with a telnet to my postfix box which i
26 matches
Mail list logo
