On Wed, May 15, 2019 at 4:29 PM Lucio wrote:
> Is there any configuration to have spamd log a particular message
> header long with the other informations it usually logs?
>
I've not seen that mentioned by anybody, but, you can always write a
filter that sits immediately downstream of spamc and l
Even I am new, check if this works.
Go to /etc/default/spamassassin and change the following,
OPTIONS="--create-prefs --max-children 2 --username spamd \-H ${SAHOME} -s
${SAHOME}spamd.log"
(This specifies the username Spamassassin will run under as spamd, as well
as add the home directory, create
Hello,
I'm new here but I've been using SA for quite a few years. I'm using SA
3.4.2 as packaged by Debian.
Is there any configuration to have spamd log a particular message header
along with the other informations it usually logs?
2)
I figured out the issue ... apparently razor is changing the log facility to
local3.
I disabled razor and spamd is logging correctly now.
david
--
IBM i on Power Systems: For when you can't afford to be out of business!
I'm riding 615 miles (Yes, you read that right)
On 1/10/19 6:03 PM, David Gibbs wrote:
I'm trying to get spamd to log to my maillog but can't figure out what's
going wrong.
Also, spamd is logging oddly even in the messages file...
Jan 10 18:11:32 listmail spamd[21867]: logger: removing stderr method
Jan 10 18:11:33 listm
OK, I'm confused.
I'm trying to get spamd to log to my maillog but can't figure out what's going
wrong.
I'm invoking spamd like this ...
/usr/bin/perl -T -w /usr/bin/spamd --syslog=mail -d -c -m5 -H
--razor-home-dir=/var/lib/razor/ --razor-log-file=sys-syslog -r /var/run/spamd.pid
I have t
Hi,
That information should be in the spamd log file.
I don't know which Toaster you are using but mine is in
/var/log/spamd/current
Regards,
Rick
On 9/17/2015 3:27 PM, Rajesh M wrote:
hi
we are using qmailtoaster with spamassassin
currently the spamassasin log details show as such
is i
hi
we are using qmailtoaster with spamassassin
currently the spamassasin log details show as such
is it possible to log the detailed information in the log files ?
ie sender email , recipient email spam rules applied and the spam score.
thanks,
rajesh
not a solution, there's a reason why the
spamfirewall is the *only* machine not logging to mysql because you
really don't want a dozen millions of sql-inserts each month
sql can have engine=memory, with very fast expire of data, then tools
can use that info in sql faster then anyon
irewall is the *only* machine not logging to mysql because you
really don't want a dozen millions of sql-inserts each month
sql can have engine=memory, with very fast expire of data, then tools
can use that info in sql faster then anyone can say redis :-)
On 19/06/15 16:57, Steve Freegard wrote:
spamd will already log the envfrom= line provided it has this
information passed through from whatever calls it. I send it over via a
X-Envelope-From: (see 'envelope_sender_header' in man
Mail::SpamAssassin::Conf).
Actually - I'm talking rubbish; I ju
isagree because you don't need to convince people
that your interest in logging changes is "right".
Instead, recommend you spend the energy working up a patch on the code
that does what you want. That's the brilliance of OSS and as a
committer on the project, I will give you my
On 19.06.2015 17:04, Reindl Harald wrote:
Am 19.06.2015 um 16:55 schrieb Axb:
again: "Your system design limits you"
my glue allows me to log all that in SQL and Xref it
boah we talk about spam-assassin logging and not the glue and my first
post at all on this list was about spam
Am 19.06.2015 um 16:55 schrieb Axb:
again: "Your system design limits you"
my glue allows me to log all that in SQL and Xref it
boah we talk about spam-assassin logging and not the glue and my first
post at all on this list was about spamass-milter with a warm "creep
away
ree to disagree because you don't need to convince people
that your interest in logging changes is "right".
you missed the point, it's not about convince people, it's a matter of
contradict and pretend there is a way to dig to the sender from a spamd
log-entry without
On 19.06.2015 16:43, Reindl Harald wrote:
Am 19.06.2015 um 16:34 schrieb Axb:
On 19.06.2015 16:24, Reindl Harald wrote:
Am 19.06.2015 um 16:19 schrieb Axb:
Postfix/MTA/Glue Session IDs, etc... having the data in a DB also
allows all kinds of stats.
nonsense, there is *nothing* to xfer the
onvince people
that your interest in logging changes is "right".
Instead, recommend you spend the energy working up a patch on the code
that does what you want. That's the brilliance of OSS and as a
committer on the project, I will give you my word that I will look
serious
Am 19.06.2015 um 16:34 schrieb Axb:
On 19.06.2015 16:24, Reindl Harald wrote:
Am 19.06.2015 um 16:19 schrieb Axb:
Postfix/MTA/Glue Session IDs, etc... having the data in a DB also
allows all kinds of stats.
nonsense, there is *nothing* to xfer the other log entries and the
timestamp is for
d and not a solution, there's a reason why
the spamfirewall is the *only* machine not logging to mysql
because you really don't want a dozen millions of sql-inserts
each month
*YOU* don't want them. If you have a cluster of more than the one
"spamfirewall" it can be very
on why the
spamfirewall is the *only* machine not logging to mysql because you
really don't want a dozen millions of sql-inserts each month
*YOU* don't want them. If you have a cluster of more than the one
"spamfirewall" it can be very practical to have central SQL logging.
; syslog to SQL and you can xref all the info you need
>>>
>>> that's a workaround and not a solution, there's a reason why
>>> the spamfirewall is the *only* machine not logging to mysql
>>> because you really don't want a dozen millions of sql-inserts
&
achine not logging to mysql because you
really don't want a dozen millions of sql-inserts each month
*YOU* don't want them. If you have a cluster of more than the one
"spamfirewall" it can be very practical to have central SQL logging.
and for messages without a MID you h
Am 19.06.2015 um 15:56 schrieb Reindl Harald:
envelope=_SENDERDOMAIN_, from=_AUTHORDOMAIN_
syslog to SQL and you can xref all the info you need
that's a workaround and not a solution, there's a reason why the
spamfirewall is the *only* machine not logging to mysql because you
re
Am 19.06.2015 um 15:50 schrieb Axb:
On 19.06.2015 15:34, Reindl Harald wrote:
Am 19.06.2015 um 15:08 schrieb Rajesh M:
i am using qmailtoaster on centos6.6 64 bit
is there a way to have detailed logging for spamassassin
which includes the sender and the recepient and the scan result
+1
On 19.06.2015 15:34, Reindl Harald wrote:
Am 19.06.2015 um 15:08 schrieb Rajesh M:
i am using qmailtoaster on centos6.6 64 bit
is there a way to have detailed logging for spamassassin
which includes the sender and the recepient and the scan result
+1
template based like for headers would
Am 19.06.2015 um 15:08 schrieb Rajesh M:
i am using qmailtoaster on centos6.6 64 bit
is there a way to have detailed logging for spamassassin
which includes the sender and the recepient and the scan result
+1
template based like for headers would be much more helpful in the logs
than in
hi
i am using qmailtoaster on centos6.6 64 bit
is there a way to have detailed logging for spamassassin
which includes the sender and the recepient and the scan result.
my current logs are as such which does not show the
Jun 19 18:31:45 ns1 spamd[48983]: spamd: connection from localhost
On 9/12/2014 11:57 AM, Reindl Harald wrote:
Am 12.09.2014 um 17:54 schrieb Kevin A. McGrail:
On 9/12/2014 11:49 AM, Reindl Harald wrote:
Am 12.09.2014 um 16:43 schrieb Kevin A. McGrail:
On 9/11/2014 10:58 AM, Reindl Harald wrote:
not a big deal but the second line has a rounding bug
or maybe
On 11.09.14 16:58, Reindl Harald wrote:
not a big deal but the second line has a rounding bug
or maybe it don't round but just cut the comma part
precisely.
however, syncing those two might e a good idea.
Sep 11 16:54:46 localhost spamd[8205]: spamd: identified spam (8.0/4.5) for
sa-milt:189
not a big deal but the second line has a rounding bug
or maybe it don't round but just cut the comma part
Sep 11 16:54:46 localhost spamd[8205]: spamd: identified spam (8.0/4.5) for
sa-milt:189.
Sep 11 16:54:46 localhost spamd[8205]: spamd: result: Y 7 -
BAYES_99,BAYES_999,DKIM_SIGNED
On Mon, 24 Feb 2014, Matus UHLAR - fantomas wrote:
On Sun, 23 Feb 2014, Amish wrote:
> *.info;mail.none;authpriv.none;cron.none /var/log/messages
> mail.* -/var/log/maillog
>
> Any idea what is going on here? How to stop this?
On
On Sun, 23 Feb 2014, Amish wrote:
*.info;mail.none;authpriv.none;cron.none /var/log/messages
mail.* -/var/log/maillog
Any idea what is going on here? How to stop this?
On 23.02.14 18:03, John Hardin wrote:
Try reversing the order
On Mon, 2014-02-24 at 19:44 +0800, Amish wrote:
> Version 3.4.0 is in rawhide. So you would not get
> the update unless its pushed to F20.
>
OK. Thanks for the info.
Martin
- Original Message -
From: Martin Gregorie
> On Mon, 2014-02-24 at 14:17 +0800, Amish wrote:
>> This was due to recent changes in Fedora service file.
>> It removed -d (daemonize) option from SPAMDOPTIONS
...
>> Adding -d option (i.e. reverting the change) fixes the problem.
> When
On Mon, 2014-02-24 at 14:17 +0800, Amish wrote:
> This was due to recent changes in Fedora service file.
> It removed -d (daemonize) option from SPAMDOPTIONS
>
> Spamassassin without -d option enables stderr logging.
> (in addition to syslog logging)
>
> This logs were re
Ok found a solution.
This was due to recent changes in Fedora service file.
It removed -d (daemonize) option from SPAMDOPTIONS
Spamassassin without -d option enables stderr logging.
(in addition to syslog logging)
This logs were redirected to syslog by systemctl.
Adding -d option (i.e
On Sun, 23 Feb 2014, Amish wrote:
*.info;mail.none;authpriv.none;cron.none /var/log/messages
mail.* -/var/log/maillog
Any idea what is going on here? How to stop this?
Try reversing the order of those lines. I expect *.info appea
Hello,
I have recently upgraded to SpamAssassin v 3.4.0. (on Fedora 16 64bit)
Everything works fine but after upgrade I have started to see double logging.
1) normal logging to /var/log/maillog in proper format
2) same lines repeated in /var/log/messages BUT in weird fashion
In previous
For future readers: rsyslog has it all:
http://www.rsyslog.com/doc/imfile.html
On Thu, Mar 24, 2011 at 5:07 PM, polloxx wrote:
> Dear,
>
> Is it possible to log FuzzyOcr logs to syslog? As default config is
> using focr_logfile.
>
> Thx,
> P.
>
I have never seen an option for that in the cf.
There is one note though regarding log file permissions - wherever you log to,
fuzzyocr user needs permission to write, obviously...
Ed
On Mar 24, 2011, at 9:07 AM, polloxx wrote:
> Dear,
>
> Is it possible to log FuzzyOcr logs to syslog? A
Dear,
Is it possible to log FuzzyOcr logs to syslog? As default config is
using focr_logfile.
Thx,
P.
I'd like to change the way SA/Milter reports a rejected message.
Namely, to include the IP address that was rejected in the Milter
rejection line. This will make it much easier to parse with scripting.
Otherwise, you have to parse for the Milter reject, grab the (Sendmail,
in my case) queue
On Mon, 28 Dec 2009, Dan Mahoney, System Admin wrote:
Somewhere within the spamd guts there's a print/printf line that prints
that last line, and is supplied a list of variables. I mean only to add
a couple more. I'm quite surprised it's not a tunable.
I'm also surprised that, unline sendma
ther network traffic (like erroneous DNS lookups, I
think I might be on to something).
However, one of the annoying things about spamassassin's logging is that it
fails to log the remote connecting ip, even though it places it in special
places in the logs:
take for example:
Dec
ffic (like erroneous DNS lookups, I think
I might be on to something).
However, one of the annoying things about spamassassin's logging is that it
fails to log the remote connecting ip, even though it places it in special
places in the logs:
take for example:
Dec 26 08:41:51 quark spam
neous DNS lookups, I think
I might be on to something).
However, one of the annoying things about spamassassin's logging is that it
fails to log the remote connecting ip, even though it places it in special
places in the logs:
take for example:
Dec 26 08:41:51 quark spamd[87490]: spamd:
thing).
However, one of the annoying things about spamassassin's logging is that
it fails to log the remote connecting ip, even though it places it in
special places in the logs:
take for example:
Dec 26 08:41:51 quark spamd[87490]: spamd: connection from prime.gushi.org
[72.9.101.130] at port
slogd
> >(8) and
> >syslog.conf(5) man pages for more.
>
> man spamd(1) says:
>
> facility is
>interpreted as a file name to log to if it contains any
> characters
>except a-z and 0-9. "null" disables logging completely (used
>
:
facility is
interpreted as a file name to log to if it contains any
characters
except a-z and 0-9. "null" disables logging completely (used
internally).
So, setting it to spamd.log should log to that
On Sun, 04 Oct 2009, LuKreme wrote:
> >As documented in the spamd(1) man page:
> >
> >-s facility, --syslog=facilitySpecify the syslog facility
> >
> >So, specifly a syslog FACILITY instead of a FILENAME. See syslogd
> >(8) and
> >syslog.conf(5) man pages for more.
>
> So setting the -s to '
On 3-Oct-2009, at 23:54, Sahil Tandon wrote:
On Sat, 03 Oct 2009, LuKreme wrote:
My spammed.log file is empty:
Do you mean spamd.log?
Yes (sometimes auto-spelling correcting sucks)
$ cat /var/log/spamd.log
Oct 3 00:00:00 mail newsyslog[82079]: logfile turned over
OK, so newsyslog(8)
On Sat, 03 Oct 2009, LuKreme wrote:
> My spammed.log file is empty:
Do you mean spamd.log?
> $ cat /var/log/spamd.log
> Oct 3 00:00:00 mail newsyslog[82079]: logfile turned over
OK, so newsyslog(8) is working as expected.
> $ psa spam
> root 921 0.0 0.9 76268 4536 ?? Ss 26Sep09
My spammed.log file is empty:
$ cat /var/log/spamd.log
Oct 3 00:00:00 mail newsyslog[82079]: logfile turned over
$ psa spam
root 921 0.0 0.9 76268 4536 ?? Ss 26Sep09 5:04.07 /usr/
local/bin/spamd -c -s /var/log/spamd.log -d -r /var/run/spamd/
spamd.pid (perl5.10.0)
$ ls -ls
On Tuesday September 8 2009 12:10:41 Clunk Werclick wrote:
> I'm using syslog-ng, but despite listening to;
> unix-stream("/dev/log");
> It gets nothing - but I don't expect it to as the default spamassassin
> conf has this line;
>
> OPTIONS="--create-prefs --max-children 5 --username spamd
> --hel
ternal IP and rDNS are available as templates (see the
Conf docs), it is trivial to have SA add them as a custom Last-External
header. However, you also said you Reject spam [1], so you don't deliver
these anywhere. Yet, you want the info.
If there is (or would be) procmail somewhere in that c
ngle threaded,
this MUST be the msgid of the message fetchmail last read because its
reported as spamd receives it from spamc
- spamkiller reports what it will do with the message, logging the
envelope sender. Again, this MUST be the message that spamd last
released because its output im
I have no Spamassassin
> > log I can view to see what they caught on and if I need
> > to take any action.
> >
> > I had a look at:
> > Mail::SpamAssassin::Logger - SpamAssassin logging module
> >
> > But I'm not entirely sure how to invoke that or i
On Tue, 8 Sep 2009, Clunk Werclick wrote:
On Tue, 2009-09-08 at 09:34 -0700, John Hardin wrote:
On Tue, 8 Sep 2009, Clunk Werclick wrote:
I have it now - the only disappointment for me is it does not log the
'to' or 'from' or client ip.
You may be able to determine that if you correlate mor
On Tue, 2009-09-08 at 09:34 -0700, John Hardin wrote:
> On Tue, 8 Sep 2009, Clunk Werclick wrote:
>
> > I have it now - the only disappointment for me is it does not log the
> > 'to' or 'from' or client ip.
>
> You may be able to determine that if you correlate more than one log. SA
> logs the m
On Tue, 8 Sep 2009, Clunk Werclick wrote:
I have it now - the only disappointment for me is it does not log the
'to' or 'from' or client ip.
You may be able to determine that if you correlate more than one log. SA
logs the message-ID, and the MTA log should give you enough information to
det
On Tue, 2009-09-08 at 09:08 -0700, John Hardin wrote:
> On Tue, 8 Sep 2009, Clunk Werclick wrote:
>
> > Can I get SpamAssassin to fully log what it is doing? The best I can
> > ever get is something like this;
> >
> > Mon Aug 3 06:27:57 2009 [4290] info: logger: removing stderr method
> > Mon Aug
On Tue, 8 Sep 2009, Clunk Werclick wrote:
Can I get SpamAssassin to fully log what it is doing? The best I can
ever get is something like this;
Mon Aug 3 06:27:57 2009 [4290] info: logger: removing stderr method
Mon Aug 3 06:27:58 2009 [4292] info: spamd: server started on port
783/tcp (runni
Fetchmail has picked up from a pop account, before
> dumping them into Postfix - and I have no Spamassassin
> log I can view to see what they caught on and if I need
> to take any action.
>
> I had a look at:
> Mail::SpamAssassin::Logger - SpamAssassin logging module
>
>
and if I need to take any action.
I had a look at:
Mail::SpamAssassin::Logger - SpamAssassin logging module
But I'm not entirely sure how to invoke that or if I can get it to give
me what I need. It is very terse in information.
Perhaps I can start SA differently to produce a log of the scanni
ink these are two sides of the same coin: if spamc could pass
debugging control flags to spamd via a message wrapper then it would be
simple to add the ability to control logging as well.
Martin
From: Martin Gregorie
Date: Tue, 02 Jun 2009 16:54:11 +0100
How difficult would it be to let spamc control spamd's logging output on
a per-message basis?
My reason for asking is this: I maintain a body of spam that I use to
develop and regression test local rule
How difficult would it be to let spamc control spamd's logging output on
a per-message basis?
My reason for asking is this: I maintain a body of spam that I use to
develop and regression test local rules and, during rule development,
use spamc to pass the test messages through my only co
On Fri, 2009-05-08 at 15:16 -0500, Tim Connolly wrote:
> I’m running a CentOS5.2 box with Cpanel.
How you actually incorporate the settings mentioned below will be left
as an exercise to the reader, or a cpanel support thingy. :)
> How do I turn on verbose logging so that within each m
I'm running a CentOS5.2 box with Cpanel. How do I turn on
verbose logging so that within each message header I see each rules results?
Hello,
Using SA 3.2.5 I was wondering it is possible to get SA to log
additional information when a rule matches? For example, if I create a
simple rule such as:
body LOCAL_PWD_CHK/password/
to see if the word 'password' is in the message body, then I would
probably want to have things
> Len Conrad wrote:
> > example:
> >
> > Sep 16 01:18:22 mx1 amavis[11483]: (11483-01-31) Passed CLEAN,
> > [12.xx.40.141] [12.xx.40.141] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>,
> > Message-ID: <[EMAIL PROTECTED]>, mail_id: 2M64mzvIA3wf, Hits: -,
> > queued_as: 2CC9D1AF49B, 407 ms
> >
> > is "-
Len Conrad wrote:
> example:
>
> Sep 16 01:18:22 mx1 amavis[11483]: (11483-01-31) Passed CLEAN, [12.xx.40.141]
> [12.xx.40.141] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Message-ID:
> <[EMAIL PROTECTED]>, mail_id: 2M64mzvIA3wf, Hits: -, queued_as: 2CC9D1AF49B,
> 407 ms
>
> is "-" the same as "
example:
Sep 16 01:18:22 mx1 amavis[11483]: (11483-01-31) Passed CLEAN, [12.xx.40.141]
[12.xx.40.141] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Message-ID: <[EMAIL
PROTECTED]>, mail_id: 2M64mzvIA3wf, Hits: -, queued_as: 2CC9D1AF49B, 407 ms
is "-" the same as "0.0", or something else?
Len
On Wed, 2008-09-03 at 12:01 +0200, Thinline Maillist wrote:
> Now I'm gonna to write an analyzer, which will walk through spamd log
> daily and collect these records (only for spam with defined overscore)
> and add some host information (whois).
>
You might consider writing it as an additional l
Thanks. I did a slight change in Received.pm to log only untrusted
relays, all on one line for each mail (through enabling own debug channel).
Now I'm gonna to write an analyzer, which will walk through spamd log
daily and collect these records (only for spam with defined overscore)
and add some
Thinline Maillist wrote:
Hi,
I'd like to log IPs from "Received" headers to spamd's log file for
statistics and further analysis (but only from messages marked as spam).
I tried to modify the code of spamd program, but unsuccessfully, since I
chose to add it to parse_headers() subroutine, whe
Hi,
I'd like to log IPs from "Received" headers to spamd's log file for
statistics and further analysis (but only from messages marked as spam).
I tried to modify the code of spamd program, but unsuccessfully, since I
chose to add it to parse_headers() subroutine, where only protocol
specific
Skip wrote:
> I am on a linux, shared hosting site (Bluehost.com). I don't
> know how I can get it into the startup script for that box, and I only have
> access to my own home directory. That may be a showstopper right there.
> I'll have no way of knowing when they reboot the box.
Earlier,
> > Generally it gets installed in /etc/init.d or /etc/rc.d/init.d, and
> > then symlinked to various /etc/rc.d directories to
> > cause it to be called at various runlevels. If your system has
> > redhat-ish and chkconfig, it can automate this part for you, as the
> > redhat init script that c
Matt Kettler wrote:
Skip wrote:
One more dumb question (and this really is more of a linux question
than a SA question), but if I start spamd -d from a console, and then
quit that console, won't the daemon quit too?
No, that's what makes it a daemon.. it detaches from the console
completely,
Skip wrote:
One more dumb question (and this really is more of a linux question
than a SA question), but if I start spamd -d from a console, and then
quit that console, won't the daemon quit too?
No, that's what makes it a daemon.. it detaches from the console
completely, thus remains active ev
One more dumb question (and this really is more of a linux question than
a SA question), but if I start spamd -d from a console, and then quit
that console, won't the daemon quit too? I think the only other option
is to "run it from cron" to get it out of a console, but that's a real
kludge an
On Fri, 21 Mar 2008, Skip wrote:
If I did go this route, how would I make sure that my spamc talks to my
spamd and not the other one that is already running on the box?
Don't use the default network port number.
--
John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
[EMAIL
any shared hosting setups will also limit CPU time, which
typically means you can't run daemons.
Unfortunately the "spamassassin" script isn't much use for logging :(
--j.
That's what I was afraid of. I think running the daemon is a no-go,
but I guess I could ask the
uot; switch to log to a file.
However, many shared hosting setups will also limit CPU time, which
typically means you can't run daemons.
Unfortunately the "spamassassin" script isn't much use for logging :(
--j.
My email is hosted on a shared hosting site where I don't have much
access to the good stuff, like syslog and /var/*anything*. For that
reason, I believe spamc/spamd is out for me. They do in fact have spamd
running. Here's the ps -aux output
root 9532 0.0 0.6 69628 24544 ? Ss
.
-Original Message-
From: Kris Deugau [mailto:[EMAIL PROTECTED]
Sent: 10 March 2008 18:00
To: users@spamassassin.apache.org
Subject: Re: Spamassassin slow - how to enable logging of times
Paul J. Smith wrote:
> Our spamassassin is taking around 30 seconds per message, way too
> long
Paul J. Smith wrote:
> Our spamassassin is taking around 30 seconds per message, way too
> long. I'm trying to find out how to enable some timing logging so I
> can see exactley what tests are taking the time. I read about
> 'timelog_path'm, which seems to be exac
Hi,
Our spamassassin is taking around 30 seconds per message, way too long. I'm
trying to find out how to enable some timing logging so I can see exactley what
tests are taking the time. I read about 'timelog_path'm, which seems to be
exactley what I was looking for, how
on't need to be root to send to syslog.
The real reason is that "spamassassin" is a user-level tool, and as such
shouldn't log to the system logging daemon. There's no benefit to doing that,
since the user, likely, can't see the system logs, for example.
--
Rand
> gather that it's nowhere near as preferred as running spamd.
>
> However, I can't help but notice that SA doesn't seem to be logging
> anything anywhere. Spam is getting caught and dealt with by procmail
> (moved to .spam folder) and the SA headers are there and corre
kage. I'm using Postfix for an MTA and Procmail as MDA, with mail
being filtered through SA by procmail.
I can't seem to find much verbose documentation on this method - I
gather that it's nowhere near as preferred as running spamd.
However, I can't help but notice that SA
xt version I'll make the '-d info' a default, as in spamd.
If you want a pre-release please drop me a line.
> Could you please take a minute to explain the underlying issue to me.
> I don't understand why SA does not log without the patch.
> Is SA intentionally logging
not used object
oriented
> > Perl before. Thankfully it doesn't seem that different from other
OO
> > languages. Anyway I don't mind hacking up a temporary version of
> > Amavisd if you could tell me how to get SA to quit logging to
STDERR.
>
> Ok, here is a patch to
d
> Perl before. Thankfully it doesn't seem that different from other OO
> languages. Anyway I don't mind hacking up a temporary version of
> Amavisd if you could tell me how to get SA to quit logging to STDERR.
Ok, here is a patch to amavisd-new 2.5.2 (works with SA 3.2.3), which
achieves
> When SpamAssassin is invoked by amavisd, the SA debug log goes to
STDERR.
> There is currently no configurable way to let amavisd hook into SA
logging
> and capture its output, although it is doable and on a TODO list.
> For the moment you can redirect STDERR to a file and let it r
debug log goes to STDERR.
There is currently no configurable way to let amavisd hook into SA logging
and capture its output, although it is doable and on a TODO list.
For the moment you can redirect STDERR to a file and let it running
for a while for diagnostic purposes, e.g.:
# amavisd de
I'm working on a SpamAssassin plugin for a university research project.
I've debugged a lot of it by running SpamAssassin from the command line,
and using the SA logger's dbg() and info() methods to output stuff.
Now I need to put it in a production server and see the same debug
information in the
On Tue, Aug 07, 2007 at 03:07:23PM +0200, Starckjohann, Ove wrote:
> Is it possible to make the logging more verbose and to add the scores
> beside the names like it is done my mailscanner on another machine?
There is no verbosity option for the logging, you get what you get. So you
could
Hi!
We're using spamd on Debian Sarge.
Logging in /var/log/mail.log looks like:
Aug 7 14:49:35 admin05 spamd[31778]: spamd: result: Y 29 -
BAYES_99,DATE_IN_FUTURE_03_06,FB_B0NUS,HTML_10_20,HTML_MESSAGE,MIME_BASE
64_NO_NAME,MIME_BASE64_TEXT,MIME_HTML_ONLY,RAZOR2_CF_RANGE_51_100,R
1 - 100 of 180 matches
Mail list logo
