[Rt-devel] Hi, have a question about outgoing email encoding.

[Kihong Lee]

Hello.

About a month ago, I have upgraded a RT system from 3.0.9 to 3.6.3. But 
after that some people started to complain about broken Japaneses. So 
I've investigated this issue and what I've found so far is,

If we reply the ticket which is created by email which has 
"Content-Transfer-Encoding: 7bit" header, it works fine. But if we reply 
the ticket which is create by email which doesn't have 
"Content-Transfer-Encoding: 7bit", the requester complains that they get 
broken Japanese.

For example,
This is the part of header of requestor's email who gets broken Japanese.
content-type: text/plain; charset="utf-8"; format="flowed"
X-RT-Original-Encoding: iso-2022-jp

And this is the part of header of requestor's email who gets clear Japanese.
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: iso-2022-jp

Whatever the header is, incoming emails to RT are fine. But, again, if 
the email of requestor to RT system has " Content-Transfer-Encoding: 
7bit" header in it, they don't get broken Japanses when we reply it. And 
if the email of requetor to RT system DOESN't have 
"Content-Transfer-Encoding: 7bit" header, they GET BROKEN Japanses.

It looks like 3.6.3 use 8 bit encoding. So can I change the outgoing 
encoding options to make it not use 8 bit encoding? I'd like to try with 
7 bit encoding. Which file should I modify to try 7 bit encoding for 
outgoing email?

Or any other comment, advice, please?

Thanks,
Kihong Lee