On Fri, 27 Feb 2015 15:45:46 +0100
Matteo Dessalvi wrote:
> Thanks a lot for the explanation Mark, it was very clear.
> It would be a good idea considering to add that to the
> perldoc of the BayesStore/Redis.pm module.
It's not particular to Redis, the counts you quoted are simply the total
numb
Thanks a lot for the explanation Mark, it was very clear.
It would be a good idea considering to add that to the
perldoc of the BayesStore/Redis.pm module.
Regards,
Matteo
On 27.02.2015 14:55, Mark Martinec wrote:
When redis automatically expires tokens internally based on their
TTL, this o
On 27.02.2015 13:54, Axb wrote:
Is it possible you reject so much spam tha SA sees very little spam?
I believe it's the case. A combination of Postfix policies, blacklists,
ClamAV plus additional signatures, etc. greatly reduces the amount of
email sent through the filtering pipeline.
If cl
Matteo Dessalvi wrote:
I am using a centralized Redis instance to
host the bayesian data for a bunch of MTAs.
AFAICS the SA filter is working quite well
and the BAYES_* rules are triggered correctly,
no false positive so far.
But I am concerned about the expiration of the
bayesian data. sa-lear
On 02/27/2015 01:38 PM, Matteo Dessalvi wrote:
Hi all.
I am using a centralized Redis instance to
host the bayesian data for a bunch of MTAs.
AFAICS the SA filter is working quite well
and the BAYES_* rules are triggered correctly,
no false positive so far.
But I am concerned about the expirat
RW wrote:
> On Wed, 19 Jan 2011 13:16:09 + (UTC)
> "Helmut Schneider" wrote:
>
> > Michael Scheidell wrote:
> >
> > > On 1/19/11 7:56 AM, Helmut Schneider wrote:
> > > > Michael Scheidell wrote:
> > > >
> > > > > On 1/19/11 6:04 AM, Helmut Schneider wrote:
> > > > > > bayes_auto_expire
Michael Scheidell wrote:
> On 1/19/11 8:16 AM, Helmut Schneider wrote:
> > 1295442708,
> > Last: 1295442672, atime: 0, count: 0, newdelta: 0, ratio: 0, period:
> > 43200
> or, it has been trying (automatically) for a while. remove auto
> expire (at least)
done.
> change to this also
> bayes_sto
On Wed, 19 Jan 2011 13:16:09 + (UTC)
"Helmut Schneider" wrote:
> Michael Scheidell wrote:
>
> > On 1/19/11 7:56 AM, Helmut Schneider wrote:
> > > Michael Scheidell wrote:
> > >
> > > > On 1/19/11 6:04 AM, Helmut Schneider wrote:
> > > > > bayes_auto_expire 1
> > > > di
On 1/19/11 8:16 AM, Helmut Schneider wrote:
1295442708,
Last: 1295442672, atime: 0, count: 0, newdelta: 0, ratio: 0, period:
43200
or, it has been trying (automatically) for a while. remove auto expire
(at least)
change to this also
bayes_store_module Mail::SpamAssassin::BayesStore::MySQL
u
Michael Scheidell wrote:
> On 1/19/11 7:56 AM, Helmut Schneider wrote:
> > Michael Scheidell wrote:
> >
> > > On 1/19/11 6:04 AM, Helmut Schneider wrote:
> > > > bayes_auto_expire 1
> > > disable auto expire and run a cronjob.
> > OK...but..why? :)
> >
> to fix your problem
On 1/19/11 7:56 AM, Helmut Schneider wrote:
Michael Scheidell wrote:
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire 1
disable auto expire and run a cronjob.
OK...but..why? :)
to fix your problem.
plus auto expire can seriously degrade the performance of
Michael Scheidell wrote:
> On 1/19/11 6:04 AM, Helmut Schneider wrote:
> > bayes_auto_expire 1
> disable auto expire and run a cronjob.
OK...but..why? :)
> make sure you run the cronjob for each user in bayes.
The database ist global...
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire 1
disable auto expire and run a cronjob.
make sure you run the cronjob for each user in bayes.
mysql mail -AssBbe 'select username from bayes_vars'
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
IS
On Fri, 10 Jul 2009 02:28:30 +0100
RW wrote:
> On Mon, 06 Jul 2009 16:13:17 -0400
> "Rosenbaum, Larry M." wrote:
>
> > Has anybody considered revising the Bayes expiration logic? Maybe
> > it's just our data that's weird, but the built-in expiration logic
> > doesn't seem to work very well for
On Mon, 06 Jul 2009 16:13:17 -0400
"Rosenbaum, Larry M." wrote:
> Has anybody considered revising the Bayes expiration logic? Maybe
> it's just our data that's weird, but the built-in expiration logic
> doesn't seem to work very well for us. Here are my observations:
>
> There's no point in ch
On Mon, 06 Jul 2009 16:13:17 -0400
"Rosenbaum, Larry M." wrote:
> Has anybody considered revising the Bayes expiration logic? Maybe
> it's just our data that's weird, but the built-in expiration logic
> doesn't seem to work very well for us. Here are my observations:
>
> There's no point in ch
Roger Taranto wrote:
> After an sa-learn --force-expire finishes, there are a couple of
> interesting (I think) statistics printed:
> token frequency: 1-occurence tokens: 62.85%
> token frequency: less than 8 occurrences: 26.36%
> I checked the documentation but couldn't find anything on this outpu
On Tue, Nov 14, 2006 at 07:54:06PM -0800, Roger Taranto wrote:
> token frequency: 1-occurence tokens: 62.85%
> token frequency: less than 8 occurrences: 26.36%
> What do these two lines mean ...
The first says that 62.85% of your tokens only were ever learned once,
and another 26.36% were learned
On Mon, Aug 15, 2005 at 10:23:58PM -0500, Steve Martin wrote:
> 154830 entries kept, 1714 deleted
Ok.
> [1381] dbg: bayes: token count: 154830, final goal reduction size: 42330
> [1381] dbg: bayes: 1382400_62056
>
> So, the first time it only got rid of about 2000 tokens and is stuck?
Yup.
> [
19 matches
Mail list logo
