none
What about undeliverable emails where that actually goes ? RRS feed

  • Question

  • Folks, i know it might be basic but need to know to bit more, with exchange 2007 we know by default, if Exchange Server is unable to deliver a message, it will try again in 10 minutes. If Exchange is still unable to deliver a message, it will wait 10 more minutes before making another attempt. If the message is still undeliverable, Exchange perform a third retry.

    At that point, if the message hasn't been delivered, Exchange will try to deliver it in 15 minute intervals for the next two days. If the two days go by, and Exchange still hasn't been able to deliver the message, a non-delivery report will be issued but what will happen the queue which has been piled up with undeliverable message ? Is all the mails will be deleted after certain time or it will store some where ..

    Suppose mails are getting piled up on exchange 2007 Edge box for some external domain say XYZ.com and some how the mails are not getting delivered and the mails are getting piled up so what will happen to those emsils ?

    Thursday, August 2, 2012 9:34 AM

Answers

  • They just get discareded.

    By default, any undelivered message is returned to the sender with an NDR and deleted from the queue.

    Working with the Queue Database on Transport Servers

    http://technet.microsoft.com/en-us/library/bb124343(v=exchg.80).aspx


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    • Proposed as answer by cara chenModerator Friday, August 3, 2012 6:39 AM
    • Marked as answer by amit79 Monday, August 6, 2012 6:13 AM
    Thursday, August 2, 2012 3:12 PM
  • Thanks for your reply James, so i gone through the article so the message expiration time-out interval  will play the role and once it reaches the mentioend time the value of the MessageExpirationTimeOut parameter which is 2 days so after that the message will be deleted CORRECT ? till then all the undelivered message will be in the queues.

    Got the more info on this mentiuoend below ..

    The message expiration time-out interval specifies the maximum length of time that an Edge Transport server or a Hub Transport server tries to deliver a failed message. If the message can't be successfully delivered before the expiration time-out interval has passed, a non-delivery report (NDR) that contains the original message or the message headers is delivered to the sender, and the original message is removed from the queue.

    By default, the message expiration time-out interval is 2 days.

    1. Open the Exchange Management Console. Perform one of the following steps:

      • On a computer that has the Edge Transport server role installed, in the console tree, select Edge Transport, and then click the Properties link that is directly under the server name.
      • On a computer that has the Hub Transport server role installed, in the console tree, expand Server Configuration, and then select Hub Transport. In the result pane, select a server. In the action pane, click the Properties link that is directly under the server name.
    2. Click the Limits tab.

    3. Enter a value in hours next to Maximum time since submission (days). In the Exchange Management Console, the valid input range is 1 day to 90 days.

    4. Click Apply to save your changes and remain in the Properties page, or click OK to save your changes and exit the Properties page.

    • Run the following command:

      Set-TransportServer <Identity> -MessageExpirationTimeout <Age>
      

      For example, if you want to change the message expiration time-out to 4 days on an Exchange 2007 computer named Exchange01, run the following command:

      Set-TransportServer Exchange01 -MessageExpirationTimeout 4.00:00:00
      

    To specify an age value, enter the value as a time span: dd.hh:mm:ss, where d = days, h = hours, m = minutes, and s = seconds. The valid input range for this parameter is 00:00:05 to 90.00:00:00.

    For detailed syntax and configuration information, see Set-TransportServer.

    • Edited by amit79 Monday, August 6, 2012 6:13 AM
    • Marked as answer by amit79 Monday, August 6, 2012 6:13 AM
    Monday, August 6, 2012 6:09 AM

All replies

  • They just get discareded.

    By default, any undelivered message is returned to the sender with an NDR and deleted from the queue.

    Working with the Queue Database on Transport Servers

    http://technet.microsoft.com/en-us/library/bb124343(v=exchg.80).aspx


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    • Proposed as answer by cara chenModerator Friday, August 3, 2012 6:39 AM
    • Marked as answer by amit79 Monday, August 6, 2012 6:13 AM
    Thursday, August 2, 2012 3:12 PM
  • Thanks for your reply James, so i gone through the article so the message expiration time-out interval  will play the role and once it reaches the mentioend time the value of the MessageExpirationTimeOut parameter which is 2 days so after that the message will be deleted CORRECT ? till then all the undelivered message will be in the queues.

    Got the more info on this mentiuoend below ..

    The message expiration time-out interval specifies the maximum length of time that an Edge Transport server or a Hub Transport server tries to deliver a failed message. If the message can't be successfully delivered before the expiration time-out interval has passed, a non-delivery report (NDR) that contains the original message or the message headers is delivered to the sender, and the original message is removed from the queue.

    By default, the message expiration time-out interval is 2 days.

    1. Open the Exchange Management Console. Perform one of the following steps:

      • On a computer that has the Edge Transport server role installed, in the console tree, select Edge Transport, and then click the Properties link that is directly under the server name.
      • On a computer that has the Hub Transport server role installed, in the console tree, expand Server Configuration, and then select Hub Transport. In the result pane, select a server. In the action pane, click the Properties link that is directly under the server name.
    2. Click the Limits tab.

    3. Enter a value in hours next to Maximum time since submission (days). In the Exchange Management Console, the valid input range is 1 day to 90 days.

    4. Click Apply to save your changes and remain in the Properties page, or click OK to save your changes and exit the Properties page.

    • Run the following command:

      Set-TransportServer <Identity> -MessageExpirationTimeout <Age>
      

      For example, if you want to change the message expiration time-out to 4 days on an Exchange 2007 computer named Exchange01, run the following command:

      Set-TransportServer Exchange01 -MessageExpirationTimeout 4.00:00:00
      

    To specify an age value, enter the value as a time span: dd.hh:mm:ss, where d = days, h = hours, m = minutes, and s = seconds. The valid input range for this parameter is 00:00:05 to 90.00:00:00.

    For detailed syntax and configuration information, see Set-TransportServer.

    • Edited by amit79 Monday, August 6, 2012 6:13 AM
    • Marked as answer by amit79 Monday, August 6, 2012 6:13 AM
    Monday, August 6, 2012 6:09 AM