I checked in raw view and I see:

Content-Type: text/plain; charset="iso-2022-jp"

The subject in raw view is:

The body doesn't display Japanese and looks like this:

I am using Mailwasher.  Japanese is shown in the body of incoming email in mailwasher.  Japanese is shown in the title of the email when it is imported to Pegasus but Japanese in the body gets mangled.  I have instal,led the windows japanese character set.  Is there somthing that I can do to fix this?

Thanks

Usagi

[quote user="Usagi"]

I am using Mailwasher.  Japanese is shown in the body of incoming email in mailwasher.  Japanese is shown in the title of the email when it is imported to Pegasus but Japanese in the body gets mangled.  I have installed the windows Japanese character set.  Is there something that I can do to fix this?

Thanks

Usagi

[/quote]

Not sure.  I guess it really depends on the character set being used in sending the message.  Pegasus Mail is now using  libiconv (http://www.gnu.org/software/libiconv/) to display characters.  If the character set used in the message is not supported or is the wrong one then this can happen.  According to the web page the following Japanese character sets are supported.  EUC-JP, SHIFT_JIS, CP932, ISO-2022-JP, ISO-2022-JP-2, ISO-2022-JP-1

Please forward a copy of one of these messages so I can see which Charset is being identified in the Mime headers or at the start of the html stream

 Please send to my email address: irelam@telus.net

Martin

The raw view says:

Content-Type: text/plain; charset="iso-2022-jp"

I am using SpamAssassin and I just noticed this in the raw view:

X-Spam-Status: No, score=2.8 required=5.0 tests=BAYES_50,
    UNWANTED_LANGUAGE_BODY autolearn=ham version=3.0.6

When I checked I found that Japanese was not in the list of accepted languages in my SpamAssassin settings. I just reset it to accept Japanese.  Maybe this is the problem?

If so, why does the subject appear in Japanese characters?

Content-Type: text/plain; charset="iso-2022-jp"

But is that what is actually shown in the body of the message? Have you passed a copy of the message to Martin for analysis?
 

If so, why does the subject appear in Japanese characters?

Look at the subject in the raw view and you'll probably find it's encoded is something that SpamAssassin can accept. 

This is the Subject in raw view:

This is a part of the body (same in raw view as regular view)

 $B$3$s$K$A$O!" (BYahoo! $B%0%k!<%W (B $B$G$9!# (B

[trianglejapan] $B%0%k!<%W$X$N;22C?=$79~$_$r$$$?$@$-$^$7$?!# (B
 $B$^$@!"%0%k!<%W$X$N;22C<jB3$-$O40N;$7$F$$$^$;$s!# (B

 $B"#$3$N%0%k!<%W$K;22C$9$k$K$O (B
 $B$3$N%a!<%k$K$3$N$^$^JV?.$7$F$/$@$5$$!#<jB3$-$,40N;$7$^$9!# (B

Yes, I did forward the message to irelam@telus.net

 Usagi

[quote user="Usagi"]

This is the Subject in raw view:

This is a part of the body (same in raw view as regular view)

 $B$3$s$K$A$O!" (BYahoo! $B%0%k!<%W (B $B$G$9!# (B

[trianglejapan] $B%0%k!<%W$X$N;22C?=$79~$_$r$$$?$@$-$^$7$?!# (B
 $B$^$@!"%0%k!<%W$X$N;22C<jB3$-$O40N;$7$F$$$^$;$s!# (B

 $B"#$3$N%0%k!<%W$K;22C$9$k$K$O (B
 $B$3$N%a!<%k$K$3$N$^$^JV?.$7$F$/$@$5$$!#<jB3$-$,40N;$7$^$9!# (B

Yes, I did forward the message to irelam@telus.net

 Usagi

[/quote]

The subject is encoded in the  ISO-2022-JP but the body sure does not look like it's using the same encoding in the header.  I hope martin can help here.

I received a copy of the message. I found the following in the html stream:

 Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

<meta http-equiv="content-type" content="text/html;charset=utf-8"/>

7 bit body message bodies are not utf-8 encoded, and certainly not  ISO-2022-JP as both Utf-8 and Japanese contain contain 8-bit characters

So the message stream is corrupted.  I do not recognise strings of characters like: $B%0%k!<%W$X$N;22C?=$79~$_$r$$$?$@$-$^$7$?!# (B

If anything it might be Mime encoded (BASE64 or UTF-7)

The subject line is properly coded Utf-8 that has been converted to Quoted-Printable so it can be translated back to Japanese characters by the recipient

Martin. 

Answer Part 2

I noted that you were using MailWasher so I checked on the Mailwasher site, and even installed it on my home PC. No mention any where of international support, but it states that invalid characters are translated (but doesn't say how).   My bet is that it flips 8-bit characters to 7-bit (safe ASCII) and then does its Spam rating scheme.

I would recommend that you change from Mailwasher and start using Pegasus Mail with its SpamHalter spam solution if you want to receive Japanese mail messages

Martin

I'm sorry but I discovered that forwarding with Pegasus mail, as I did, changes the headers.  I've posted the headers above which were  ISO-2022-JP, for the subject and for the body test.

I just sent an email to myself which had japanese characters in the subject and in the body.  The japanese wqas visible in MailWasher and when passed to Pegasus they came through ok.

This is the header info:

I had changed the default Mime character set in Pegasus "Advance Settings" to UTF-8 which I've read in more universal.  Anyways, I can send myself Japanese, which would be UTF-8 encoded, but I don't know for sure if I can receive Japanese from other sources that may be encoded in ISO-2022-jp.  I don't read Japanese.  The idea is that I didn't want to lose the characters because I could copy and paste them into translation sites to get an idea what they said.

 This also shows that MailWasher is not messing anything up.  I do find it very handy. It has many handy filters that are far easier to set up than Pegasus.  I've used Pagasus for many years now and it is the best for organizing email that I want to save.

 later edit: I changed the email addys in the headers above to avoid spam bots zeroing in on my email addy.

Usagi