At 11:15 AM 6/18/2007, Theo Van Dinter wrote:
My guess is that you're learning into a different DB than the one you're
trying to scan from. Do a learn with "-D" and then a dump with "-D" and
compare.
I had this problem with the default install on OS X, Apple in their
infinite wisdom has two d
On Monday 18 June 2007 13:15, John D. Hardin wrote:
> On Mon, 18 Jun 2007, Rob Wright wrote:
> > sa-learn --ham -C /etc/mail/spamassassin --showdots --spam --no-sync
> > Maildir/new
> >
> > So, then, spamassassin isn't seeing the ham that I'm feeding it? Why
> > would it see the spam but not the ha
On Mon, 18 Jun 2007 20:06:52 +0200, Rob Wright <[EMAIL PROTECTED]>
wrote:
sa-learn --ham -C /etc/mail/spamassassin --showdots --spam --no-sync
Maildir/new
Don't use the --spam flag when learning ham
On Mon, 18 Jun 2007, Rob Wright wrote:
> sa-learn --ham -C /etc/mail/spamassassin --showdots --spam --no-sync
> Maildir/new
>
> So, then, spamassassin isn't seeing the ham that I'm feeding it? Why would it
> see the spam but not the ham?
--ham *and* --spam ?
--
John Hardin KA7OHZ
On Mon, Jun 18, 2007 at 01:06:52PM -0500, Rob Wright wrote:
> So, I went back to where my ham is and re-ran sa-learn on that with this
> result (after first using --forget):
>
> sa-learn --ham -C /etc/mail/spamassassin --showdots --spam --no-sync
> Maildir/new
What's with the -C ?
> sa-learn -
On Monday 18 June 2007 12:36, ian douglas wrote:
> Rob Wright wrote:
> > So far I've managed to run ~2500 messages through sa-learn over the
> > course of the last week or so, and I've yet to see a single log entry
> > with a BAYES rule match of any kind.
>
> From your own logs:
>
> [24761] dbg: b
Hi Rob,
At 10:23 18-06-2007, Rob Wright wrote:
[24761] dbg: bayes: DB journal sync: last sync: 1182182134
[24761] dbg: bayes: not available for scanning, only 0 ham(s) in bayes DB <
100
http://wiki.apache.org/spamassassin/BayesNotWorking
Regards,
-sm
Rob Wright wrote:
So far I've managed to run ~2500 messages through sa-learn over the course of
the last week or so, and I've yet to see a single log entry with a BAYES rule
match of any kind.
From your own logs:
[24761] dbg: bayes: not available for scanning, only 0 ham(s) in bayes
DB < 100
Greetings,
It seems to be a common question but I haven't yet been able to figure out
what's wrong on my end with this. SpamAssassin itself is working, it's
detecting and flagging messages based on the built in rules, but Bayes seems
to be non-functioning.
I'm using SA 3.2.0, Perl 5.8.8, usin