none
Reading Body property of Outlook nondelivery receipt (NDR) item results in Chinese characters RRS feed

  • Question

  • Reading the Body property of a nondelivery receipt (NDR) Outlook.ReportItem results in Chinese characters and a save changes prompt. If you read the property from the InspectorClose event the item is saved with those Chinese characters in the body. Is important to note that this does not occur with other types of ReportItems like Read receipt. I've confirmed the behavior on both versions of Outlook tested so far: 2013 and 2016.

    I will post a screenshot as soon as my account is verified.

    Monday, November 2, 2015 5:26 PM

All replies

  • Hello,

    What code exactly do you use? Do you have any other add-ins installed for Outlook?

    Monday, November 2, 2015 5:40 PM
  • This is a known problem in Outlook. You can either build the report body yourself (that is what Outlook does) from the various properties in the message recipient table (you can see the data in OutlookSpy - click IMessage button and go to the GetRecipientTable tab) - use Recipient.PropertyAccessor.GetProperty. Or you can use Redemption and its RDOReportItem object which exposes the ReportText property.

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Tuesday, November 3, 2015 3:08 AM
  • Microsoft,
    Any plan to FIX this known problem with Outlook?

    Eugene,
    Simply reading the property ReportItem.Body for the CurrentItem in an Inspector Close event returns the Chinese characters and this occurs even without any other Add-in loaded.

    Dmitry,
    Using Redemption and reading the ReportText property of the RDOReportItem object does not suffer from the Chinese characters issue. However the text returned does not include the "Diagnostic information for administrators:" section shown by Outlook in the report body. Any suggestions on how to retrieve that will be greatly appreciated?
    Tuesday, November 3, 2015 8:32 PM
  • Do you see that information in the recipient table in OutlookSpy (IMessage | GetRecipientTable)?

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Wednesday, November 4, 2015 5:41 AM
  • Hi JC_Miami,

    Thanks for report this potential issue. I also could reproduce this issue too.

    If this is urgent issue, I suggest that you follow the suggestion provide by Dmitry as a workaround. Or you can try to contact Microsoft support to raise an incident so that our engineer could work closely with him to identify the root cause and resolve this issue as soon as possible.

    If the support engineer determines that the issue is the result of a bug the service request will be a no-charge case and you won't be charged.

    Please visit the below link to see the various paid support options that are available to better meet your needs.
    https://msdn.microsoft.com/subscriptions/bb266240.aspx

    Thanks for your understanding.

    Regards & Fei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, November 5, 2015 6:38 AM
    Moderator
  • I don't see it in OutlookSpy > IMessage > GetRecipientTable. (Forum does not allow me to post image/link so I can e-mail you a screenshot if you want).


    Here is what Outlook displays in the report body:

    Delivery has failed to these recipients or groups:
    dfgsdgsdgsdfgsdfgsdfg@gadfasdfgsdfg.csadfsadf (dfgsdgsdgsdfgsdfgsdfg@gadfasdfgsdfg.csadfsadf)
    The domain name in the email address is incorrect. Check the email address.



    Diagnostic information for administrators:
    Generating server: BY1PR0701MB1127.namprd07.prod.outlook.com
    dfgsdgsdgsdfgsdfgsdfg@gadfasdfgsdfg.csadfsadf
    Remote Server returned '554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain'
    Original message headers:
    Received: from BY1PR0701MB1577.namprd07.prod.outlook.com (10.162.110.143) by
     BY1PR0701MB1127.namprd07.prod.outlook.com (10.160.104.25) with Microsoft SMTP
     Server (TLS) id 15.1.312.18; Mon, 2 Nov 2015 16:42:13 +0000
    Received: from BY1PR0701MB1580.namprd07.prod.outlook.com (10.162.110.146) by
     BY1PR0701MB1577.namprd07.prod.outlook.com (10.162.110.143) with Microsoft
     SMTP Server (TLS) id 15.1.312.18; Mon, 2 Nov 2015 16:42:11 +0000
    Received: from BY1PR0701MB1580.namprd07.prod.outlook.com ([10.162.110.146]) by
     BY1PR0701MB1580.namprd07.prod.outlook.com ([10.162.110.146]) with mapi id
     15.01.0312.014; Mon, 2 Nov 2015 16:42:11 +0000
    From: Jeanny Collazo <<email address masked>>
    To: "dfgsdgsdgsdfgsdfgsdfg@gadfasdfgsdfg.csadfsadf"
     <dfgsdgsdgsdfgsdfgsdfg@gadfasdfgsdfg.csadfsadf>
    Subject: NDR RDO Test 2
    Thread-Topic: NDR RDO Test 2
    Thread-Index: AdEVjWsOKrMvzsxaR4eyyTPxDxgk2g==
    Date: Mon, 2 Nov 2015 16:42:11 +0000
    Message-ID: <BY1PR0701MB15802C9F028C19A1610BD921B22C0@BY1PR0701MB1580.namprd07.prod.outlook.com>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator:
    authentication-results: spf=none (sender IP is )
     smtp.mailfrom=<email address masked>; 
    x-originating-ip: [173.9.148.81]
    x-microsoft-exchange-diagnostics: 1;BY1PR0701MB1577;5:s7xPfU/+Us12v7PhqXEUhIPR0+Xs5HNHEM7dCGDhzZnAGSTxp8hr5GRIIf/7ZoipB4oNqQ9MXAd1A8nbRv3lo1GJsbNpd4um72HnqgDez2ku91UEEG7T1LRtJOIoIedpumljOk25i0QHqaPODPLzTQ==;24:Xqo2fVAm847Sq2VeozMciJi46swiwtvaaizKfzHioJ5PG7w3nEh7Svca5wW1swgDZxM7Ouy1r7DgiMmPGUDEsq7oSarg1oLksSFB6DSHWKM=;20:s152lD8/W0hCTWud46rOQ2Z7nkdp+4QB7eMDhINwro4VmyMOuj+VP/8YmWzNrIRnpKxFEnc+nlF64RfRPwCbsg==
    x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0701MB1577;
    x-microsoft-antispam-prvs: <BY1PR0701MB15779EF79921961178EF21D7B22C0@BY1PR0701MB1577.namprd07.prod.outlook.com>
    x-exchange-antispam-report-test: UriScan:(273882187091885)(108003899814671);
    x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(520078)(5005006)(8121501046)(10201501046)(3002001);SRVR:BY1PR0701MB1577;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0701MB1577;
    x-forefront-prvs: 0748FF9A04
    x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(189002)(199003)(10400500002)(101416001)(54356999)(19627595001)(97736004)(18206015028)(99286002)(109986003)(33656002)(77096005)(5001920100001)(92566002)(5001960100002)(106356001)(40100003)(2900100001)(558084003)(81156007)(15975445007)(110136002)(105586002)(189998001)(16236675004)(19625215002)(86362001)(107886002)(5002640100001)(87936001)(66066001)(74316001)(99936001)(102836002)(17760045003)(229853001)(5007970100001)(5008740100001)(50986999)(76576001)(19580405001)(19617315012)(5003600100002)(19300405004)(4001450100002)(122556002)(5004730100002)(19580395003)(2501003)(11100500001)(7099028)(217873001)(12283535005);DIR:OUT;SFP:1102;SCL:1;SRVR:BY1PR0701MB1577;H:BY1PR0701MB1580.namprd07.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;MX:1;A:1;LANG:;
    received-spf: None (protection.outlook.com: trialworks.com does not designate
     permitted sender hosts)
    spamdiagnosticoutput: 1:23
    spamdiagnosticmetadata: NSPM
    Content-Type: multipart/related;
     boundary="_004_BY1PR0701MB15802C9F028C19A1610BD921B22C0BY1PR0701MB1580_";
     type="multipart/alternative"
    MIME-Version: 1.0
    X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Nov 2015 16:42:11.8017
     (UTC)
    X-MS-Exchange-CrossTenant-fromentityheader: Hosted
    X-MS-Exchange-CrossTenant-id: c18603c9-c364-4d5f-a43f-ee2024d5eebd
    X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0701MB1577
    Return-Path: <email address masked>
    X-Microsoft-Exchange-Diagnostics:
     1;BY1PR0701MB1127;2:wm8LdRkgh9236yWoeR8D6Jy5LoGeLYi7XlHUBvQuAl6FPLCffgbp2o87FCHdNkBuXeCbotfwHmYmynuFt91yQA6vtMbXHduyWQ0nB2NpcIKgDc3KMYOlsKwE9pjDg4vw6tvrVfWfdvPXlkDG5aQwWDcbv+MWctaYAtRl+1uBIv4=;23:yy26KFHFQiVxBz29YQeXXcCs3CR5wah9maQNyGUwGLaq+5YO3OQ/LwCRWkcq8XJk2lHPYGUsgXR6trPDWpzR0vZqDHBFoxpmBEzhivSnPRFKuwwE8QtfpIaweTmi29BvEC21PlAKM7+4TKVSZL5hyYsGKbpWRfrgMXXeEWp2m7Zw6lggbIsASErHkCg8bV3J
    X-OriginatorOrg: trialworks.com


    Thursday, November 5, 2015 4:43 PM
  • Diagnostic information comes from the PR_TRANSPORT_MESSAGE_HEADERS and PidTagReportingMessageTransferAgent properties set on the medsage itself (GetProps tab of the IMessage window in OutlookSpy).

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Thursday, November 5, 2015 4:52 PM
  • Thank you Dmitry . I've confirmed using OutlookSpy that PR_TRANSPORT_MESSAGE_HEADERS contains the same Diagnostic information shown in Outlook body. What is the recommend way to read that property using the RDO object model?
    Thursday, November 5, 2015 5:47 PM
  • You can use RDOMail.Fields[].


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Friday, November 6, 2015 12:45 AM