Hi,
>> Is there any reason to not use the bl.score.sendrescore.com with
>> postscreen? I don't understand the distinction
>
> why?
>
> postscreen is supposed to be configured with sensible scoring to reject most
> spam without false positives long before it reachs smtpd or even expesnive
>
Am 03.03.2016 um 02:44 schrieb Alex:
Is there any reason to not use the bl.score.sendrescore.com with
postscreen? I don't understand the distinction
why?
postscreen is supposed to be configured with sensible scoring to reject
most spam without false positives long before it reachs smtpd or
Hi,
Some time ago, David Jones wrote:
> In a related note, I have found that using the senderscore.org score combined
> with postscreen's weighting is very effective in quickly catching new
> spammers.
>
> postscreen_dnsbl_sites =
> score.senderscore.com=127.0.4.[60..69]*2
>
Am 03.03.2016 um 00:07 schrieb Roman Gelfand:
On Wed, Mar 2, 2016 at 1:54 PM RW > wrote:
On Wed, 2 Mar 2016 12:48:18 -0500
Roman Gelfand wrote:
> I have awl disabled and dcc checks configured. Why, sometimes,
>
On Wed, Mar 2, 2016 at 2:50 PM Matus UHLAR - fantomas
wrote:
> On 02.03.16 12:48, Roman Gelfand wrote:
> >I have awl disabled and dcc checks configured. Why, sometimes,
> >spamassassin doesn't do dcc checks?
>
> that has nothing to do with AWL.
>
> You have already asked in
On Wed, Mar 2, 2016 at 1:54 PM RW wrote:
> On Wed, 2 Mar 2016 12:48:18 -0500
> Roman Gelfand wrote:
>
> > I have awl disabled and dcc checks configured. Why, sometimes,
> > spamassassin doesn't do dcc checks?
>
> What makes you think that it doesn't?
>
this
Am 02.03.2016 um 23:13 schrieb RW:
On Wed, 2 Mar 2016 22:45:15 +0100
Reindl Harald wrote:
Am 02.03.2016 um 22:12 schrieb RW:
The only argument you have made against these rules is that they
don't work for you. They do work on the corpus that generates the
rule scores, so clearly the corpus
On Wed, 2 Mar 2016 22:45:15 +0100
Reindl Harald wrote:
> Am 02.03.2016 um 22:12 schrieb RW:
> > The only argument you have made against these rules is that they
> > don't work for you. They do work on the corpus that generates the
> > rule scores, so clearly the corpus does matter
>
>
Am 02.03.2016 um 22:12 schrieb RW:
The only argument you have made against these rules is that they don't
work for you. They do work on the corpus that generates the rule scores,
so clearly the corpus does matter
VERY_LONG_REPTO_SHORT_MSG with a poison-pill score showed how much you
can
On Wed, 2 Mar 2016 15:58:10 +0100
Reindl Harald wrote:
> Am 02.03.2016 um 14:12 schrieb RW:
> > The FSL_HELO_BARE_IP_* rules were a bit broken until the end of
> > January, but for the last month they have been proper mutually
> > exclusive, deep and last-external tests. Any problems with the
Am 02.03.2016 um 16:52 schrieb Marc Perkel:
My Redis bayes keeps growing. It acts like it's not expiring like it
should. Do I need to do something to force expire? Also - anything ekse
I should set?
Google "spamassassin redis expire" and hit number 2:
On 02.03.16 12:48, Roman Gelfand wrote:
I have awl disabled and dcc checks configured. Why, sometimes,
spamassassin doesn't do dcc checks?
that has nothing to do with AWL.
You have already asked in the DCC mailing list (and I have replied), why did
you interrupt the conversation and brought
On Wed, 2 Mar 2016 12:48:18 -0500
Roman Gelfand wrote:
> I have awl disabled and dcc checks configured. Why, sometimes,
> spamassassin doesn't do dcc checks?
What makes you think that it doesn't?
I have awl disabled and dcc checks configured. Why, sometimes,
spamassassin doesn't do dcc checks?
On 03/02/2016 05:32 PM, Marc Perkel wrote:
On 03/02/16 08:02, Axb wrote:
On 03/02/2016 04:52 PM, Marc Perkel wrote:
My Redis bayes keeps growing. It acts like it's not expiring like it
should. Do I need to do something to force expire? Also - anything ekse
I should set?
Here's my settings.
On 03/02/16 08:02, Axb wrote:
On 03/02/2016 04:52 PM, Marc Perkel wrote:
My Redis bayes keeps growing. It acts like it's not expiring like it
should. Do I need to do something to force expire? Also - anything ekse
I should set?
Here's my settings.
bayes_sql_dsn server=localhost:6379
On 03/02/2016 05:02 PM, Axb wrote:
On 03/02/2016 04:52 PM, Marc Perkel wrote:
My Redis bayes keeps growing. It acts like it's not expiring like it
should. Do I need to do something to force expire? Also - anything ekse
I should set?
Here's my settings.
bayes_sql_dsn server=localhost:6379
On 03/02/2016 04:52 PM, Marc Perkel wrote:
My Redis bayes keeps growing. It acts like it's not expiring like it
should. Do I need to do something to force expire? Also - anything ekse
I should set?
Here's my settings.
bayes_sql_dsn server=localhost:6379
use_bayes 1
use_bayes_rules 1
# Your
My Redis bayes keeps growing. It acts like it's not expiring like it
should. Do I need to do something to force expire? Also - anything ekse
I should set?
Here's my settings.
bayes_sql_dsn server=localhost:6379
use_bayes 1
use_bayes_rules 1
# Your choice if you want to use auto_learn
Dear All,
Many thanks for your reply.
> It may not be set where you think it is. IIWY I'd do a recursive grep
Yes, actually true. There is a ' ok_locales en' in file "sa-mimedefang.cf"
I have overlooked this fact. But this explains.
> the SA can use users' ~/.spamassassin/user_prefs
Am 02.03.2016 um 14:12 schrieb RW:
The FSL_HELO_BARE_IP_* rules were a bit broken until the end of
January, but for the last month they have been proper mutually
exclusive, deep and last-external tests. Any problems with the deep
hits are down to the rule generation corpus not matching your
On Wed, 2 Mar 2016 14:12:18 +0100
MAYER Hans wrote:
> pts rule name description
> --
> -- 3.2
> CHARSET_FARAWAY_HEADER A foreign language charset used in headers 3.2
> CHARSET_FARAWAYBODY: Character set
On 02.03.16 14:12, MAYER Hans wrote:
We are an international institute with employees from around the world.
Therefore we send and receive regular e-mails in almost all languages.
Our setup: sendmail, mimedefang and SA version 3.3.2
Generally our spam detection rate is quite OK ( I would say).
On Tue, 01 Mar 2016 23:39:58 +0100
Benny Pedersen wrote:
> That one should not trigger in deap header tests
RCVD_NUMERIC_HELO doesn't do what the description says. It's actually a
*bare* IP address test (i.e. for an RFC violation rather than simply
an IP address), something that is better
Dear All,
We are an international institute with employees from around the world.
Therefore we send and receive regular e-mails in almost all languages.
Our setup: sendmail, mimedefang and SA version 3.3.2
Generally our spam detection rate is quite OK ( I would say). But one of our
user is
25 matches
Mail list logo