Outlook 2016 - chinese characters appearing in messages when replying/forwarding

Anonymous
2017-04-24T13:29:42+00:00

Hello,

I am investigating an issue with Outlook 2016 and seemingly random appearances of chinese characters in email messages when replying or forwarding. I have a Exchange 365 hybrid environment and O365 pro plus office installed on workstations.

I have not been able to pinpoint a common factor why or when this happens. It is possible to reproduce the issue by sending a plain text message to a O365 group and then reply/forward the same message > header information is transformed into "chinese" (I have no idea what they actually are) characters. This does not happen with all groups or senders which is why I am looking into Outlook at the moment.

I`ve tried to change Outlook settings: use UTF8 with mailto protocol, change the encoding settings to different options etc. without success. 

I`d like to hear how would you start to troubleshoot this issue?

BR,

Sam

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

132 answers

Sort by: Most helpful
  1. Anonymous
    2018-11-15T17:36:51+00:00

    I also had it happen just the other day when I resent an old message, my original text got replaced by this string of characters in the received email (the one in sent items looks fine). So I tried a clean profile on the same computer, send myself an excel file as an attachment from excel, get the string. Remove click-to-run office 2019 and go back to MSI office 2016 and it seems to have inherited the problem.

    I have never seen this issue in my environment until I used click-to-run ms office.

    I don't seem to have any choice but to wipe my system and start from scratch to try to fix it.

    I just starting getting this when I upgraded to office 2019, it only happens so far when I "share" a document via attachment, then the body of the message is always:

    格浴浸湬㩳㵶產湲猺档浥獡洭捩潲潳瑦挭浯瘺汭•浸湬㩳㵯產湲猺档浥獡洭捩潲潳瑦挭浯漺晦捩㩥景楦散•...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-11-08T21:27:52+00:00

    Hi Rob,

    Did you gather more valuable intel? And if so, would you mind sharing. Currently this is a rather big nuisance for my organization and even as i long for a solution, it does not seem like it is happening. I'm looking for a way to recreate the issue so that i can inform my users on how avoid it, "damage-control" if you will - Any thoughts?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-11-06T13:42:44+00:00

    格浴㹬格慥㹤਍ヘンャ⁡小寵ソ秤ョ族]∽捩ャ梨」⵴オyハ幅豫梨」㵴ラチウ⽴荻兆I※オオトオ抜㵴ォC先鍔炉㸢⼼鉢陶㰾蓐オ€ാ㰊㹰茸㰾チハャ瞭モ姙・∽ゥB〰㘰。テェeキ€㵥㌢舞Wノ「∽・X≬夾畯⁲醗ォAフ⁥S⁳クメ悒゙Dー]ー働ャ_桴⁥チハ姨イJ悸⁧ヌテ鮖婁悒ォB㰺ハヌ忰㹴⼼㹢⼼㹰਍昼湯ゥ・㵲⌢〰〰〰葺M塙∽∲モウシ㵥ツ鞳莇≡㰾㹰染戻ヌテ㵦屶蓮ャ㩯銘⹲ロ賦䁡ヨエ疏撞⹳攪≭䄾オ䬠ソョ路糎⠠流⹲靖ホロ賦䁡ヨエ疏撞⹳攪⥭⼼㹡⼼㹰਍桴リメ探発ャ惚梍ウ䤠荻裏ー曽朗忰ホロ䔠髪・⁹・鮑ノ「㌠㔶壯゙譛」弄本・ォA筏⼼㹰਍⼼チハャാ㰊雷Y摯㹹਍⼼ャ兆I

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-11-06T12:43:11+00:00

    The Same thing happen to me all the time with All read receipts delivery on Office365 Pro-plus. I checked with support and asked me to try using OWA and i didn't receive that message. The problem only appears with Outlook however i can't depend on OWA and couldn't find a resolve to outlook.

    格浴㹬格慥㹤਍ヘンャ⁡小寵ソ秤ョ族]∽捩ャ梨」⵴オyハ幅豫梨」㵴ラチウ⽴荻兆I※オオトオ抜㵴ォC先鍔炉㸢⼼鉢陶㰾蓐オ€ാ㰊㹰茸㰾チハャ瞭モ姙・∽ゥB〰㘰。テェeキ€㵥㌢舞Wノ「∽・X≬夾畯⁲醗ォAフ⁥S⁳クメ悒゙Dー]ー働ャ_桴⁥チハ姨イJ悸⁧ヌテ鮖婁悒ォB㰺ハヌ忰㹴⼼㹢⼼㹰਍昼湯ゥ・㵲⌢〰〰〰葺M塙∽∲モウシ㵥ツ鞳莇≡㰾㹰染戻ヌテ㵦屶蓮ャ㩯銘⹲ロ賦䁡ヨエ疏撞⹳攪≭䄾オ䬠ソョ路糎⠠流⹲靖ホロ賦䁡ヨエ疏撞⹳攪⥭⼼㹡⼼㹰਍桴リメ探発ャ惚梍ウ䤠荻裏ー曽朗忰ホロ䔠髪・⁹・鮑ノ「㌠㔶壯゙譛」弄本・ォA筏⼼㹰਍⼼チハャാ㰊雷Y摯㹹਍⼼ャ兆I

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-10-22T09:44:22+00:00

    I've seen this too and some of the translation is worrying to say the least.

    Microsoft - you need to take this seriously.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments