Hello ;)
I want ask you if you are willing to make plugin to SA which allow
logging into database instead of file.
There is already sa-stats plugin, but its only logging numbers of
spam/ham. Im not perl programmer ;( but I believe that can be
relatively easyli done just put all line into database
Miki writes:
Hello ;)
I want ask you if you are willing to make plugin to SA which allow
logging into database instead of file.
There is already sa-stats plugin, but its only logging numbers of
spam/ham. Im not perl programmer ;( but I believe that can be
relatively easyli done just put
Hello Justin,
Monday, February 26, 2007, 11:44:21 AM, you wrote:
JM Miki writes:
Hello ;)
I want ask you if you are willing to make plugin to SA which allow
logging into database instead of file.
There is already sa-stats plugin, but its only logging numbers of
spam/ham. Im not perl
On Monday 21 August 2006 22:21, Stefan Bauer took the opportunity to say:
iam using Debian with Spamassasin 3.1.1-1 and exim 4.62.
Iam looking forward to use sa-stats[1] with the stats from spamassasin
from /var/log/exim4/mainlog.log like:
Aug 21 17:58:51 main spamd[4064]: spamd: result: .
Hello List,
iam using Debian with Spamassasin 3.1.1-1 and exim 4.62.
Iam looking forward to use sa-stats[1] with the stats from spamassasin
from /var/log/exim4/mainlog.log like:
Aug 21 17:58:51 main spamd[4064]: spamd: result: . -1 - AWL,BAYES_00
On Apr 21, 2006, at 12:50 PM, Michael Monnerie wrote:
The other idea I have is to disable SA support in amavis, and just use
it for the virus checks, and call SA directly. I'm not sure this would
why not teach your log analyzer to understand amavisd-new's log
format, too?
You don't get a spamd log when SA is called via amavis. That's not good
if you want stats. So what could we do to have that?
SA is called directly via Mail::SpamAssassin from amavis. Is it possible
to configure that to log like spamd?
The other idea I have is to disable SA support in amavis,
On 4/21/06, Michael Monnerie [EMAIL PROTECTED] wrote:
You don't get a spamd log when SA is called via amavis. That's not good
if you want stats. So what could we do to have that?
SA is called directly via Mail::SpamAssassin from amavis. Is it possible
to configure that to log like spamd?
Folks,
I'm running SA 3.0.4 on a Solaris 10 system.
Everything was working fine, and I went to restart SA and when it came back
up, it no longer is logging to syslog.
I've restarted syslog, rebooted the box, everything. Here is an output from
SA Debug:
trying to connect to
At 12:55 PM 10/8/2004, [EMAIL PROTECTED] wrote:
Im sure SA should be logging something to somewhere, probably maillog right?
Well I dont have anything in the maillog from SA. Am I missing something?
Anyone help me debug why it's not logging?
How are you calling SA?
If you're using spamc/spamd
: Matt Kettler [EMAIL PROTECTED]
Date: Fri, 08 Oct 2004 13:03:59 -0400
To: [EMAIL PROTECTED] [EMAIL PROTECTED], users@spamassassin.apache.org
Subject: Re: SA logging
At 12:55 PM 10/8/2004, [EMAIL PROTECTED] wrote:
Im sure SA should be logging something to somewhere, probably maillog right?
Well
At 01:16 PM 10/8/2004, [EMAIL PROTECTED] wrote:
Yea, ive been asked this before. I inherited this setup, so Im trying to
work that out.
i can restart SA by using rc.d/init.d/spamassassin
it shows in ps aux as /usr/bin/spamd -d -c -a
and when mail comes in it shows as
/usr/bin/perl -T -w
disclaimer
seriously.
Before I go on, anyone that uses spamd confirm this info...?
From: Matt Kettler [EMAIL PROTECTED]
Date: Fri, 08 Oct 2004 13:48:40 -0400
To: [EMAIL PROTECTED] [EMAIL PROTECTED], users@spamassassin.apache.org
Subject: Re: SA logging
At 01:16 PM 10/8/2004, [EMAIL
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Thank you Matt!
You're info is great, but I'm sure you dont mind if I take your
disclaimer seriously.
Before I go on, anyone that uses spamd confirm this info...?
His suggestions sound right on to me. For the most part all you need
to
Subject: Re: SA logging
His information is all correct.
Change your procmailrc lines so they're something like this:
# Pass through spamassassin
:0fw
* 256000
| /usr/bin/spamc
Mojo
On Fri, 8 Oct 2004, [EMAIL PROTECTED] wrote:
Thank you Matt!
You're info is great, but I'm sure
[EMAIL PROTECTED] wrote:
Thank you, appeared to work great, logging to maillog and all, the problem
now becomes where it's putting spam.
previously my procmailrc looked like this:
:0fw
| /usr/bin/spamassassin
:0
* ^X-Spam-Status: Yes
$HOME/spam
which routed spam to the users spam folder
when i
Kettler [EMAIL PROTECTED], users@spamassassin.apache.org
Subject: Re: SA logging
You have two separate things happening in two recipes:
The first recipe:
:0fw
| /usr/bin/spamassassin
Adds the X-SpamStatus: header to the email. The second recipe:
:0
* ^X-Spam-Status: Yes
$HOME
17 matches
Mail list logo
