User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0 Build ID: 20120420145725 Steps to reproduce: Replying or forwarding a multipart/mixed mail with charset=ISO-2022-JP message-body and a attached file(Content-Type: text/plain; charset=Shift_JIS) Actual results: on mail edit window, messages does not displaied correctly. For example, $B$F$9$H(B ISO-2022-JP message is displayed as Shift-JIS. For UTF-8 plain text file attached mail, reply/forward message is displayed as UTF-8. Expected results: ISO-2022-JP mailbody should treated as ISO-2022-JP on replying or forwarding.

same as bug 716983 ?

(In reply to WADA from comment #1) > same as bug 716983 ? Yes. I think a bug in somewhere makes both bug 71698 and Bug 755169

Root cause of "charset is pcked up from last attachment" was resolved by bug 1026989 at last. Some valuable bug reports from users were hidden/lost/ignored by "duping to bug 716983, then duping bug 716983 to other bug". Unfortunately, or fotunately, only "garbled display in Forward Inline case" was resolved by unknown bug while the other bug was being processed, so nothing was resolved by the other bug. Duping this bug to bug 1026989, for ease of tracking, search, understanding current status of problem.

FYI. Patch of bug 1026989, one liner patch, was proposed in the other bug to which bug 716983(and bug 701818 too) had been duped to. The patch was dig out from the other bug by bug 1026989, and long lived "charset is picked up from last attachment" issue has been resolved by bug 1026989. Why such "digging out hidden important patch from the other bug" should be needed in B.M.O?

(1) this bug was duped to bug 716983 which is for "garbled display in Forward Inline case", (2) then bug 716983 was duped to bug 715823 which is also for "garbled display in Forward Inline case". So, pretty important "charset is picked up from last attachment" of this bug was masked by interesting phenomenon of "garbled display in Forward Inline case" in bug 715823, despite that patch used by bug 1026989 was proposed in the bug 715823. I think a cause of such chaos is inappropriate duping and repeated duping. I belieave "duping in B.M.O" should be done on "actual dup" only. I hope duping by "duplicate bug == similar external symptom for who closed as dup" will stop. And, I believe that who does duping should care about loss of important information by duping. In this bug's case, "Reply case" was lost by duping. This is a reason of that we have to wait for "fixing of problem pointed by this bug" until the problem is fixed by bug 1026989 on 2016-12-10 despite that this bug was reported at 2012-05.