You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by ji...@jidanni.org on 2011/07/18 04:41:35 UTC
debugging UNWANTED_LANGUAGE_BODY
Gentlemen, it turns out it is very hard to debug UNWANTED_LANGUAGE_BODY.
They forgot to put debugging features in the code, apparently TextCat.pm.
Lately spamassassin has decided that several of my mails contain
UNWANTED_LANGUAGE_BODY
X-Spam-Languages: ja.shift-jis
despite that being hogwash.
Well I tried to debug using
spamassassin -D
And got as far as
dbg: rules: ran eval rule UNWANTED_LANGUAGE_BODY ======> got hit (1)
Further grepping led to TextCat.pm.
Now we ask, exactly what caused TextCat.pm decide my message was Japanese?
Do I have to post it here, full of its personal information, or is there
some additional debugging flag I can set?
Re: debugging UNWANTED_LANGUAGE_BODY
Posted by Henrik K <he...@hege.li>.
On Mon, Jul 18, 2011 at 10:41:35AM +0800, jidanni@jidanni.org wrote:
> Gentlemen, it turns out it is very hard to debug UNWANTED_LANGUAGE_BODY.
>
> They forgot to put debugging features in the code, apparently TextCat.pm.
>
> Lately spamassassin has decided that several of my mails contain
> UNWANTED_LANGUAGE_BODY
> X-Spam-Languages: ja.shift-jis
> despite that being hogwash.
>
> Well I tried to debug using
> spamassassin -D
> And got as far as
> dbg: rules: ran eval rule UNWANTED_LANGUAGE_BODY ======> got hit (1)
>
> Further grepping led to TextCat.pm.
>
> Now we ask, exactly what caused TextCat.pm decide my message was Japanese?
>
> Do I have to post it here, full of its personal information, or is there
> some additional debugging flag I can set?
Are you running 3.3.2 or 3.4? They include fixes to something just like
that.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6229
Re: debugging UNWANTED_LANGUAGE_BODY
Posted by Bowie Bailey <Bo...@BUC.com>.
On 7/18/2011 12:23 PM, Bowie Bailey wrote:
> Make a copy of the message and start removing content. When you get to
> a version that does not trigger the rule, then the rule is most likely
> hitting on whichever piece you removed last. If you can remove the
> personal information and still get a rule hit, you can post it on
> pastbin.com and send us the link so we can check it out.
Make that "pastebin.com"...
(and sorry about the top-post)
--
Bowie
Re: debugging UNWANTED_LANGUAGE_BODY
Posted by Bowie Bailey <Bo...@BUC.com>.
Make a copy of the message and start removing content. When you get to
a version that does not trigger the rule, then the rule is most likely
hitting on whichever piece you removed last. If you can remove the
personal information and still get a rule hit, you can post it on
pastbin.com and send us the link so we can check it out.
Bowie Bailey
BUC International
954-565-6715
800-327-6929
On 7/17/2011 10:41 PM, jidanni@jidanni.org wrote:
> Gentlemen, it turns out it is very hard to debug UNWANTED_LANGUAGE_BODY.
>
> They forgot to put debugging features in the code, apparently TextCat.pm.
>
> Lately spamassassin has decided that several of my mails contain
> UNWANTED_LANGUAGE_BODY
> X-Spam-Languages: ja.shift-jis
> despite that being hogwash.
>
> Well I tried to debug using
> spamassassin -D
> And got as far as
> dbg: rules: ran eval rule UNWANTED_LANGUAGE_BODY ======> got hit (1)
>
> Further grepping led to TextCat.pm.
>
> Now we ask, exactly what caused TextCat.pm decide my message was Japanese?
>
> Do I have to post it here, full of its personal information, or is there
> some additional debugging flag I can set?