[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-dev] [Bug #1288] spamassassin configuration on Japanese
From: |
nobody |
Subject: |
[Savannah-dev] [Bug #1288] spamassassin configuration on Japanese |
Date: |
Sat, 28 Sep 2002 00:35:50 -0400 |
=================== BUG #1288: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1288&group_id=11
Submitted by: okuji Project: Savannah
Submitted on: 2002-Sep-28 04:35
Category: Mail Severity: 5 - Average
Priority: None Bug Group: None
Resolution: None Assigned to: None
Status: Open Effort: 0.00
Summary: spamassassin configuration on Japanese
Original Submission: The mail server seems to start using SpamAssassin, and my
mail was blocked because of it.
In some mailing lists (i.e. gnu-devels-jp and pupa-staff),
we speak Japanese, as we know all of us understand it and
even prefer it to English. So SpamAssassin shouldn't say
that any mail is likely to be a SPAM, just because it is
written in Japanese.
However, SpamAssassin tagged my (non-SPAM) mail with this:
X-Spam-Report: 5.4 hits, 5 required;
* 2.4 -- BODY: Contains at least 3 dollar signs in a row
* 3.0 -- BODY: message body is 50-75% uppercase
Clearly, this is bogus, because I didn't write any dollar
sign, and such a concept as "uppercase" doesn't exist in
Japanese.
Because I have been using SpamAssassin locally with no
problem, I think it's just a problem of the configuration.
In my configuration file, this line is included:
ok_locales ja
Since we always use Japanese, I expect all mails will be
blocked, as long as the current configuration is used.
Okuji
No Followups Have Been Posted
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1288&group_id=11
- [Savannah-dev] [Bug #1288] spamassassin configuration on Japanese,
nobody <=