Share via

Configure Message Retry, Resubmit, and Expiration Intervals

  • Article

Applies to: Exchange Server 2010

You can configure message retry, resubmit, and expiration intervals on a server running Microsoft Exchange Server 2010 that has the Hub Transport server role or the Edge Transport server role installed.

Looking for other management tasks related to managing transport queues? Check out Managing Transport Queues.

Configure the queue glitch retry count

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

The queue glitch retry count specifies the number of connection attempts that are immediately tried when a transport server has trouble connecting with the destination server. The default queue glitch retry count is 4. The valid input range for this parameter is from 0 through 15. Typically, you don't have to modify this parameter unless the network is unreliable and continues to experience many accidentally dropped connections. If you set the queue glitch retry count to 0, the server doesn't immediately attempt to retry an unsuccessful connection, and the next connection attempt is controlled by the transient failure retry attempts.

  1. Open the following file by using Notepad: C:\Program Files\Microsoft\Exchange Server\V14\Bin\EdgeTransport.exe.config.

  2. Modify the following line in the <appSettings> section.

    <add key="QueueGlitchRetryCount" value="<Integer>" />

    This example changes the queue glitch retry count to 6.

    <add key="QueueGlitchRetryCount" value="6" />

  3. Save and close the EdgeTransport.exe.config file.

  4. Restart the Microsoft Exchange Transport service.

Configure the queue glitch retry interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

The queue glitch retry interval specifies the interval between each connection attempt specified by the QueueGlitchRetryCount parameter. The default queue glitch retry interval is 1 minute. To specify an age value, enter the value as a time span, as follows: hh:mm:ss, where h = hours, m = minutes, and s = seconds. Typically, you don't have to modify this parameter unless the network is unreliable and continues to experience many accidentally dropped connections.

  1. Open the following file by using Notepad: C:\Program Files\Microsoft\Exchange Server\V14\Bin\EdgeTransport.exe.config.

  2. Modify the following line in the <appSettings> section.

    <add key="QueueGlitchRetryInterval" value="<hh:mm:ss>" />

    This example changes the queue glitch retry interval to 30 seconds,

    <add key="QueueGlitchRetryInterval" value="00:00:30" />

  3. Save and close the EdgeTransport.exe.config file.

  4. Restart the Microsoft Exchange Transport service.

Configure the number of transient failure retry attempts

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

The number of transient failure retry attempts specifies the number of connection attempts that are tried after the connection attempts controlled by the QueueGlitchRetryCount and QueueGlitchRetryInterval parameters have failed. The default number of transient failure retry attempts is 6. The valid input range for this parameter is from 0 through 15. If you set the number of transient failure retry attempts to 0, the next connection attempt is controlled by the outbound connection failure retry interval.

Use the EMC to configure the number of transient failure retry attempts

  1. 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's 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's directly under the server name.
  2. Click the Limits tab.
  3. Enter an integer next to Transient failure retry attempts.
  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.

Use the Shell to configure the number of transient failure retry attempts

This example changes the number of transient failure retry attempts to 8 on the Edge Transport server Exchange01.

Set-TransportServer Exchange01 - TransientFailureRetryCount 8

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

Configure the transient failure retry interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

The transient failure retry interval specifies the interval between each connection attempt that's specified by the number of transient failure retry attempts. On a Hub Transport server, the default transient failure retry interval is 5 minutes. On an Edge Transport server, the default transient failure retry interval is 10 minutes.

Use the EMC to configure the transient failure retry interval

  1. 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's 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's directly under the server name.
  2. Click the Limits tab.
  3. Enter a value in seconds next to Transient failure retry interval (seconds). In the EMC, the valid input range is from 1 second through 43200 seconds (12 hours).
  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.

Use the Shell to configure the transient failure retry interval

To configure the transient failure retry interval, use the following syntax.

Set-TransportServer <Identity> -TransientFailureRetryInterval <Age>

This example changes the transient failure retry interval to 1 minute on the Exchange 2010 Hub Transport server Exchange01.

Set-TransportServer Exchange01 - TransientFailureRetryInterval 00:01:00

To specify an age value, enter the value as a time span, as follows: hh:mm:ss, where h = hours, m = minutes, and s = seconds. The valid input range for this parameter is from 00:00:01 through 12:00:00.

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

Configure the outbound connection failure retry interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

The outbound connection failure retry interval specifies the retry interval for outgoing connection attempts that have previously failed. The previously failed connection attempts are controlled by the transient failure retry attempts and the transient failure retry interval. The default value for the outbound connection failure retry interval on a Hub Transport server is 10 minutes. The default value on an Edge Transport server is 30 minutes.

Use the EMC to configure the outbound connection failure retry interval

  1. 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's 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's directly under the server name.
  2. Click the Limits tab.
  3. Enter a value in minutes next to Outbound connection failure retry interval (minutes). In the EMC, the valid input range is from 1 minute through 28800 minutes (20 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.

Use the Shell to configure the outbound connection failure retry interval

This example changes the outbound connection failure retry interval to 45 minutes on the Exchange 2010 Edge Transport server Exchange01.

Set-TransportServer Exchange01 - OutboundConnectionFailureRetryInterval 00:45:00

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

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

Configure the mailbox delivery queue retry interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

The mailbox delivery queue retry interval specifies how frequently the mailbox delivery queues on a Hub Transport server try to connect to a Mailbox server destination that can't be successfully reached. By default, the mailbox delivery queue retry interval is 5 minutes. The mailbox delivery queue retry interval is controlled by the MailboxDeliveryQueueRetryInterval parameter in the EdgeTransport.exe.config application configuration file located in the C:\Program Files\Microsoft\Exchange Server\V14\Bin directory. Changes that are saved to the EdgeTransport.exe.config file take effect after the Microsoft Exchange Transport service is restarted.

  1. Open the following file by using Notepad: C:\Program Files\Microsoft\Exchange Server\V14\Bin\EdgeTransport.exe.config.

  2. Modify the following line in the <appSettings> section:

    <add key="MailboxDeliveryQueueRetryInterval" value="<hh:mm:ss>" />

    This example sets the mailbox delivery queue retry interval to 3 minutes.

    <add key="MailboxDeliveryQueueRetryInterval" value="00:03:00" />

  3. Save and close the EdgeTransport.exe.config file.

  4. Restart the Microsoft Exchange Transport service.

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 from 00:00:01 through 1.00:00:00.

Configure the message retry interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

Note

You can't use the EMC to perform this task.

The message retry interval specifies how frequently a Hub Transport server or an Edge Transport server resends a message that has a status of Retry. By default, the message retry interval is 1 minute. We recommend that you don't modify the default value unless Microsoft Customer Service and Support advises you to do this.

This example changes the message retry interval to 2 minutes on the Exchange 2010 computer Exchange01.

Set-TransportServer Exchange01 -MessageRetryInterval 00:02: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 from 00:00:01 through 1.00:00:00.

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

Configure the delay DSN message notification time-out interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

By default, the delay DSN message notification time-out interval is 4 hours. If the message isn't successfully delivered before the notification time-out interval has passed, a delay DSN message is delivered to the sender.

The value of the DelayNotificationTimeout parameter should always be greater than the value of the TransientFailureRetryCount parameter multiplied by the value of the TransientFailureRetryInterval parameter.

Use the EMC to configure the delay DSN message notification time-out interval

  1. 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's 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's directly under the server name.
  2. Click the Limits tab.
  3. Enter a value in hours next to Notify sender when message is delayed more than (hours). In the EMC, the valid input range is from 1 hour through 720 hours (30 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.

Use the Shell to configure the delay DSN message notification time-out interval

This example changes the delay DSN message notification time-out interval to 6 hours on the Exchange 2010 computer Exchange01.

Set-TransportServer Exchange01 -DelayNotificationTimeout 06:00:00

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

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

Enable or disable the sending of delay DSN notifications to external message senders

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

Note

You can't use the EMC to perform this task.

By default, delay DSN notification messages can be sent to message senders who are outside the Exchange organization.

This example prevents the sending of delay DSN notification messages to external senders on the Exchange 2010 computer Exchange01.

Set-TransportServer Exchange01 -ExternalDelayDSNEnabled $false

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

Enable or disable the sending of delay DSN notifications to internal message senders

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

Note

You can't use the EMC to perform this task.

By default, delay DSN notification messages can be sent to message senders who are inside the Exchange organization.

This example prevents the sending of delay DSN notification messages to internal senders on the Exchange 2010 computer Exchange01.

Set-TransportServer Exchange01 -InternalDelayDSNEnabled $false

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

Configure the message resubmit interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

Undelivered messages are automatically resubmitted if the mailbox delivery queue or remote delivery queue is in the status of Retry for a specified amount of time, and the messages aren't in the Suspended state. That amount of time is controlled by the MaxIdleTimeBeforeResubmit parameter in the EdgeTransport.exe.config application configuration file. By default, the value of the MaxIdleTimeBeforeResubmit parameter is 12 hours.

  1. Open the following file by using Notepad: C:\Program Files\Microsoft\Exchange Server\V14\Bin\EdgeTransport.exe.config.

  2. Modify the following line in the <appSettings> section:

    <add key="MaxIdleTimeBeforeResubmit" value="<hh:mm:ss>" />

    This example changes the message resubmit interval to 6 hours.

    <add key="MaxIdleTimeBeforeResubmit" value="6:00:00" />

  3. Save and close the EdgeTransport.exe.config file.

  4. Restart the Microsoft Exchange Transport service.

Configure the message expiration time-out interval

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

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 message 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.

Use the EMC to configure the message expiration time-out interval

  1. 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's 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's directly under the server name.
  2. Click the Limits tab.
  3. Enter a value in days next to Maximum time since submission (days). In the EMC, the valid input range is from 1 day through 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.

Use the Shell to configure the message expiration time-out interval

To configure the message expiration time-out interval, use the following syntax.

Set-TransportServer <Identity> -MessageExpirationTimeout <Age>

This example changes the message expiration time-out interval to 4 days on the Exchange 2010 computer Exchange01.

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 from 00:00:05 through 90.00:00:00.

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