none
Error message on Delay Delivery

    Question

  • Hello my chamelle,

    One user received an email from the server that a message has been delayed but this email also contains the name of every transport rules that exist in the organization.

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    From: Microsoft Outlook <MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@newad.com>
    Date: 22 August, 2012 19:31:36 EDT
    To: <user@tamere.com>
    Subject: Delivery delayed:Dossier 500-80-016808-108
    Delivery is delayed to these recipients or groups:
    tonpere@compagnie.com (tonpere@compagnie.com)
    Subject: Dossier 500-80-016808-108
    This message hasn't been delivered yet. Delivery will continue to be attempted.
    The server will keep trying to deliver this message for the next 1 days, 19 hours and 55 minutes. You'll be notified if the message can't be delivered by that time.
    Reporting-MTA: dns;danzka.newad.ca Received-From-MTA: dns;newad.com Arrival-Date: Wed, 22 Aug 2012 19:26:41 +0000 Final-Recipient: rfc822;tonpere@compagnie.com Action: delayed Status: 4.4.7 Diagnostic-Code: smtp;400 4.4.7 Message delayed Will-Retry-Until: Fri, 24 Aug 2012 15:26:41 -0400 X-Display-Name: tonpere@compagnie.com
    Received: from SLIVOVITZ.newad.ca ([fe80::c4c0:63bb:761d:e6a]) by danzka.newad.ca ([10.1.1.181]) with mapi id 14.01.0355.002; Wed, 22 Aug 2012 15:26:41 -0400 From: "User Tamere" To: "tonpere@compagnie.com" CC: USER2, "USER3" Subject: CONFFIDENTIAL SHHOUTING Thread-Topic: Dossier 500-80-016808-108 Thread-Index: Ac2Amow927bI0/+1RR+JA/IPR3z8dwAAHs3g Date: Wed, 22 Aug 2012 19:26:40 +0000 Message-ID: <2D6B6FAF9C6EE641BDCD88179328C70A3619A1F1@slivovitz.newad.ca> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 04 X-MS-Exchange-Organization-AuthSource: danzka.newad.ca X-MS-Has-Attach: yes X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: x-ms-exchange-organization-originalsize: 1935704 x-ms-exchange-organization-originalarrivaltime: 22 Aug 2012 19:26:40.8682 (UTC) x-ms-exchange-organization-messagesource: StoreDriver x-ms-exchange-organization-messagedirectionality: Originating x-ms-exchange-forest-messagescope: 00000000-0000-0000-0000-000000000000 x-ms-exchange-organization-messagescope: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Organization-BCC: x-ms-exchange-organization-originalclientipaddress: 10.1.5.56 x-originating-ip: [10.1.5.56] x-ms-exchange-organization-originalserveripaddress: 10.1.1.182 x-ms-exchange-organization-messagelatency: SRV=SLIVOVITZ.newad.ca:TOTAL=0 x-ms-exchange-organization-hygienepolicy: Standard x-ms-exchange-organization-recipient-limit-verified: True x-ms-exchange-forest-rulesexecuted: danzka x-ms-exchange-organization-rules-execution-history: TRANSPORT RULE NAME 1 TRANSPORT RULE NAME 2 TRANSPORT RULE NAME 3 x-ms-exchange-organization-processed-by-journaling: Journal Agent Content-Type: multipart/mixed; boundary="_007_2D6B6FAF9C6EE641BDCD88179328C70A3619A1F1slivovitznewadc_" MIME-Version: 1.0 X-MS-Exchange-Organization-ContentConversionOptions: False;00160000;True;;iso-8859-1 X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=danzka.newad.ca:TOTAL=0;2012-08-22T19:26:41.989Z 

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Thanks for your help.

    Marc


    • Edited by Marc3k Thursday, August 23, 2012 2:13 PM
    Thursday, August 23, 2012 2:12 PM

Answers

  • Hello,

    Did the issue happen on internal users or external users?

    From the notification email, we could find one key sentence:

    The server will keep trying to deliver this message for the next 1 days, 19 hours and 55 minutes. You'll be notified if the message can't be delivered by that time.

    I suggest you wait for the final status of the email delivery. If the email can’t be sent out, you will receive the NDR.

    Best Regards,

    Lisa

    • Marked as answer by cara chen Thursday, September 6, 2012 6:45 AM
    Friday, August 24, 2012 7:24 AM

All replies

  • Hello,

    Did the issue happen on internal users or external users?

    From the notification email, we could find one key sentence:

    The server will keep trying to deliver this message for the next 1 days, 19 hours and 55 minutes. You'll be notified if the message can't be delivered by that time.

    I suggest you wait for the final status of the email delivery. If the email can’t be sent out, you will receive the NDR.

    Best Regards,

    Lisa

    • Marked as answer by cara chen Thursday, September 6, 2012 6:45 AM
    Friday, August 24, 2012 7:24 AM
  • Was there ever an answer on this.  We have a user that received an NDR that has every transport rule listed as well.  We do NOT want these listed as part of the diagnostic message for the NDR.

    James Right Size Solutions

    Monday, June 9, 2014 9:27 PM