On 2021-12-29 at 19:07:06 UTC-0500 (Wed, 29 Dec 2021 18:07:06 -0600)
Robert Nicholson
is rumored to have said:
I just updated from 3.4.0 to 3.4.6 and the output in perl debugger
when I programmatically using SA is quite noisy.
Where can I find 3.4.1 etc so I can incrementally update from 3.4.
I just updated from 3.4.0 to 3.4.6 and the output in perl debugger when I
programmatically using SA is quite noisy.
Where can I find 3.4.1 etc so I can incrementally update from 3.4.0 so I can
see where the dramatic change is coming from?
When I use my script in the debugger from 3.4.0 there is
On Mon, 10 Jun 2019, Shreyansh Shrivastava. wrote:
On Mon, Jun 10, 2019 at 11:04 PM @lbutlr wrote:
On 10 Jun2019, at 11:29, Shreyansh Shrivastava. <
shreyansh.171co...@nitk.edu.in> wrote:
Hey everyone is there a way to add an extra DEBUG output for
"spamassassin -D” ?
I don’t
On Mon, Jun 10, 2019 at 11:04 PM @lbutlr wrote:
> On 10 Jun2019, at 11:29, Shreyansh Shrivastava. <
> shreyansh.171co...@nitk.edu.in> wrote:
> > Hey everyone is there a way to add an extra DEBUG output for
> "spamassassin -D” ?
>
> I don’t understand the question
On 10 Jun2019, at 11:29, Shreyansh Shrivastava.
wrote:
> Hey everyone is there a way to add an extra DEBUG output for "spamassassin
> -D” ?
I don’t understand the question. What are you trying to do?
--
A.D. 1517: Martin Luther nails his 95 Theses to the church door and
Hey everyone is there a way to add an extra DEBUG output for "spamassassin
-D" ?
Thanks,
Shreyansh Shrivastava
ee any options that would do this, so I suspect it will
> require changing the code, but I thought I'd ask in case I just missed
> something.
Mmm, not a direct answer, but...
What is in the debug output that you regularly need to see? It might be
better to patch spamd to log that at a
I currently run spamd (3.4.1) with the --debug flag and a subset of
debug channels and it handles enough traffic that the debug
information for emails regularly overlap in the log file. While each
line contains the literal text "spamd" followed by the pid of the
child (in brackets), those pids ob
On Wed, 21 Mar 2012 12:02:24 -0400
Kevin A. McGrail wrote:
>
> On 3/21/2012 11:42 AM, Adrian Gruntkowski wrote:
> > Hello,
> >
> > I'm having problems with bayes database. When I issue "spamassassin
> > --lint -D", I see a following phrase: "bayes: not available for
> > scanning, only 0 spam(s) i
On 3/21/2012 11:42 AM, Adrian Gruntkowski wrote:
Hello,
I'm having problems with bayes database. When I issue "spamassassin --lint
-D", I see a following phrase: "bayes: not available for scanning, only 0
spam(s) in bayes DB< 200".
However, a bit further I see this: "corpus size: nspam = 5987
ble.com/Conflicting-information-about-bayes-database-contents-in-lint-debug-output-tp33544583p33544583.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
On Sun, Jan 21, 2007 at 07:43:11PM -0500, Tom Allison wrote:
> But call this directly from my "main" script eg:
>
> Mail::SpamAssassin::Logger::add(method => 'file', filename =>
> '/var/log/syslog')
> ??
Yes, but I wouldn't log to the same file that syslog is going to write to...
Just use the sy
Theo Van Dinter wrote:
On Sun, Jan 21, 2007 at 07:17:14PM -0500, Tom Allison wrote:
When using Mail::SpamAssassin with new( {debug => 'all'} ) or similar
How do you capture the output from the debug to syslog or other logging
file?
Take a look at Mail::SpamAssassin::Logger. ie:
Mail::Sp
On Sun, Jan 21, 2007 at 07:17:14PM -0500, Tom Allison wrote:
> When using Mail::SpamAssassin with new( {debug => 'all'} ) or similar
> How do you capture the output from the debug to syslog or other logging
> file?
Take a look at Mail::SpamAssassin::Logger. ie:
Mail::SpamAssassin::Logger::a
When using Mail::SpamAssassin with new( {debug => 'all'} ) or similar
How do you capture the output from the debug to syslog or other logging file?
I can run it via a command line but if I run Mail::SpamAssassin under a
daemon/fork process similar to Net::Server::PreForkSimple I can't seem
I have enabled dcc, pyzor, and razor2 and network checks, so I find the
following debug output confusing so I'm unable to tell with any certainty
that I have this optimized the way I want to.
Why does it tell me "dcc: local tests only, disabling DCC" and likewise for
pyzor and
I have enabled dcc, pyzor, and razor2 and network checks, so I find the
following debug output confusing so I'm unable to tell with any
certainty that I have this optimized the way I want to.
Why does it tell me "dcc: local tests only, disabling DCC" and likewise
for pyzor and
That is the same thing I observed here after adding that plugin. I
am not sure if it is in the dnsbl code or the way ClamAV-plugin
uses the dnsbl code. Regardless it would be nifty were it to be
fixed.
{^_-}
- Original Message -
From: "Steve Martin" <[EMAIL PROTECTED]>
Yes, in fact an
Yes, in fact and that is part of it. But, in the process of
investigating, I do think I found a bug (or at least an "issue") in
the uridnsbl code.
There is a check inside an inner loop there to see if any progress
has been made reading the results of lookups and if nothing changes
for 2
You added ClamAV plugin?
{^_^}
- Original Message -
From: "Steve Martin" <[EMAIL PROTECTED]>
SA seems unusually slow today and I'm trying to figure out if I've
done something to my configuration that is causing the problem or if
it is just slow rbl lookups or something.
I ran spa
SA seems unusually slow today and I'm trying to figure out if I've
done something to my configuration that is causing the problem or if
it is just slow rbl lookups or something.
I ran spamassassin with -t and -D and this output looks like it may
be problematic, but I'm not sure what to look
On Tue, 7 Jun 2005, Bob McClure Jr wrote:
> On Tue, Jun 07, 2005 at 10:42:07AM -0400, Mike Schrauder wrote:
> > pardon my complete unix ignorance, I have been trying to figure
> > out how to get debug output to a file so I can go back and look
[snip..]
> > i've also
ay, June 07, 2005 10:53 AM
> To: users@spamassassin.apache.org
> Subject: Re: debug output to file?
>
> On Tue, Jun 07, 2005 at 10:42:07AM -0400, Mike Schrauder wrote:
> > pardon my complete unix ignorance, I have been trying to figure out
> > how to get debug output to a file
On Tue, Jun 07, 2005 at 10:42:07AM -0400, Mike Schrauder wrote:
> pardon my complete unix ignorance, I have been trying to figure
> out how to get debug output to a file so I can go back and look
> at it. I also want to look at the marked up email w/ report so
> I am using this:
>
> pardon my complete unix ignorance, I have been trying to figure
> out how to get debug output to a file so I can go back and look
> at it. I also want to look at the marked up email w/ report so
> I am using this:
>
> spamassassin -D -t < test2.txt > test2.out
>
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 07, 2005 9:42 AM
To: users@spamassassin.apache.org
Subject: debug output to file?
pardon my complete unix ignorance, I have been trying to figure
out how to get debug output to a file so I can go back and look
at it. I also want to look at the marked up
>&test2.out spamassassin -D.
-Original Message-
From: Mike Schrauder [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 07, 2005 10:42 AM
To: users@spamassassin.apache.org
Subject: debug output to file?
pardon my complete unix ignorance, I have been trying to figure
out how to ge
pardon my complete unix ignorance, I have been trying to figure
out how to get debug output to a file so I can go back and look
at it. I also want to look at the marked up email w/ report so
I am using this:
spamassassin -D -t < test2.txt > test2.out
How could I also redirect the debug
-Original Message-
From: Ben Wylie [mailto:[EMAIL PROTECTED]
Sent: 14 March 2005 13:28
To: users@spamassassin.apache.org
Subject: RE: save debug output and errors
>
> Having managed to capture the errors which pop up when my mailserver runs
> the spamassassin batch script, it is
> > where should I look for this to fix?
>
> Theo has the answer for that one - a bad meta rule somewhere.
>
> Given that --lint seemingly didn't catch it, and this pure perl error is
> less than descriptive of the problem, once you find the rule in question,
> I think it deserves a Bugzilla entry
> where should I look for this to fix?
Theo has the answer for that one - a bad meta rule somewhere.
Given that --lint seemingly didn't catch it, and this pure perl error is
less than descriptive of the problem, once you find the rule in question, I
think it deserves a Bugzilla entry for failure
On Mon, Mar 14, 2005 at 05:03:05AM -, Ben Wylie wrote:
> Scalar found where operator expected at (eval 57) line 724, near "} $self"
> (Missing operator before $self?)
> Failed to run meta SpamAssassin tests, skipping some: syntax error at (eval
> 57)
> line 724, near "} $self"
>
> whe
-Original Message-
> From: Loren Wilton [mailto:[EMAIL PROTECTED]
> Sent: 14 March 2005 02:36
> To: users@spamassassin.apache.org
> Subject: Re: save debug output and errors
>
> You probably have some broken rules or other lines in your local rules
> file, or poss
You probably have some broken rules or other lines in your local rules file,
or possibly elsewhere in the rules files. To catch thos you want to run
"spamassassin --lint" without the debug stuff. This will give you a
managable output.
Assuming you are on NT of some flavor, "spamassassin 2>&1
>o
Hello All,
This is the first time I have used this list so if should have done it a
different way, or have said something wrong, I beg your forgiveness.
I have been running spamassassin for over a year now on my Windows 2003
system using perl 5.6.1. My SA version is 3.0.2.
I run Spamassassin from
35 matches
Mail list logo
