I've been using SA and other software for few years for antispam gateway.
During first few month, the results was very good, most spam was
rejected and finaly SA examine the rest.
However, after almost 2 years now, the spam rate received by user are
high, so I think that I have to change
Craig Morrison wrote:
beast wrote:
Is it possible to make different tag for a different score/classes,
for example:
high: [SPAM!!!] if score 50
medium: [SPAM!!] if score between 20 - 50
low: [SPAM] if score between treshold - 20
The reason is client filter or other redirection program
/ quarantined for further inspection) can not parse the
score directly.
--beast
jdow wrote:
From: Beast [EMAIL PROTECTED]
Hi,
From some (spam) mail which not caught by SA, it seems that bayes is
not applied to this mail.
X-Spam-Report:
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 1.7 SARE_SPEC_ROLEX Rolex watch spam
X-Spam-Status: No, score=1.7 required
applicable to other address also.
--beast
[EMAIL PROTECTED] wrote:
I don't understand your point.
I run a Mac. I don't care for _any_ .exes period.
You could use your MTA to do a light content filtering, so it will
reject mail with .exe atachment at MTA level.
Try postfix.
--beast
,
HTML_MESSAGE,SARE_MSGID_LONG40,SUB_HELLO autolearn=no version=3.1.4
From my understanding, SA should automatically learn any mail which has
score 12 as spam and 0.2 as a ham. Am I correct?
--beast
autolearn=no version=3.1.4
Is bayes check is not run for every mail?
--beast
:
bayes_auto_learn_threshold_spam 12.0
[11919] warn: lint: 2 issues detected, please rerun with debug enabled
for more information
# spamassassin --version
SpamAssassin version 3.1.4
running on Perl version 5.8.5
--beast
Anthony Peacock wrote:
Hi,
Beast wrote:
Any reason why this config failed?
According to Mail::SpamAssassin::Plugin::AutoLearnThreshold it is a
valid config.
# spamassassin --lint
[11919] warn: config: failed to parse line, skipping:
bayes_auto_learn_threshold_nonspam 0.1
[11919] warn
Beast wrote:
Anthony Peacock wrote:
Hi,
Beast wrote:
Any reason why this config failed?
According to Mail::SpamAssassin::Plugin::AutoLearnThreshold it is a
valid config.
# spamassassin --lint
[11919] warn: config: failed to parse line, skipping:
bayes_auto_learn_threshold_nonspam 0.1
Hi,
What rules are implemented by this mailing list server? it seems very
good to detect spam.
TIA.
--beast
Loren Wilton wrote:
*X-Spam-Status:* No, score=3.8 required=5.2
tests=BAYES_99,FORGED_RCVD_HELO,
HTML_50_60,HTML_MESSAGE autolearn=disabled version=3.1.4
Bayes is doing fine. You can't get much better than Bayes_99 as a
spam indicator.
On the other hand, having Bayes_99 and three
I have implemented site wide SA and it works pretty well except for this
kind of spam.
postmaster account has been receiving many spam and its not being
blocked by SA, I have feed SA to learns hundred of similar spam
manually, but still not able to catcth up.
spamassassin --lint -D
...
[26113]
, skipping: use_razor2 0
[28678] warn: lint: 2 issues detected, please rerun with debug enabled
for more information
Is it ok to just put a comment on ok_lang, use_dcc and use_razor2?
--
--beast
Beast wrote:
Daryl C. W. O'Shea wrote:
I believe this was fixed in 3.0.4. Bug 4080 if I remember correctly.
Upgraded from 3.0.3 to 3.0.4 and problem gone.
Sorry, it still.
---
Received: from mail.indorama.com (blowfish [127.0.0.1])
by localhost.localdomain (Postfix
? but blabblabscoobydoo
means enlarge your .
That means using bayes filter for non-english is useless?
--
--beast
Beast wrote:
Evan Platt wrote:
Received by your system: Wed, 31 Aug 2005 12:15:29 +0700
Header Date: Wed, 31 Aug 2005 08:59:56 -0700
Isn't that should be date in the past?
Sorry, my mistake. It was correct.
15:59:56 GMT vs 5:15:29 GMT.
--
--beast
] spamassassin]#
--
--beast
Lem Tomas wrote:
if you're using the rpm version its usually in /usr/share/spamassassin
Thanks, its on 50_scores.cf. I've overwrite it on local.cf
score FORGED_YAHOO_RCVD 0.1
--
--beast
Matt Kettler wrote:
At 04:57 AM 8/30/2005, Beast wrote:
How do I disable FORGED_*_RCVD rule? my SA is installed after some
mail gateway, so it does not received directly from remote server.
Thus it alway triger this rule.
Did you add that some mail gateway to your trusted_networks?
I'd
Daryl C. W. O'Shea wrote:
I believe this was fixed in 3.0.4. Bug 4080 if I remember correctly.
Upgraded from 3.0.3 to 3.0.4 and problem gone.
Thanks!
--
--beast
probability is 99 to 100%
* [score: 1.]
--
--beast
from where it calculate 1.0 and 3.5?
--
--beast
]
---
1. Why it triger DATE_IN_FUTURE_06_12?
2. How do I pass all bounce email?
3. I have train hundreds (or thousands) spam/ham mail to sa-learn but it
seems it still not quite good detecting non-english mail.
--
--beast
--
--beast
26 matches
Mail list logo
