Set-TransportConfig (RTM)

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007, Exchange Server 2007 SP1

Use the Set-TransportConfig cmdlet to modify the transport configuration settings for the whole Microsoft Exchange Server 2007 organization.

Syntax

Set-TransportConfig [-ClearCategories <$true | $false>] [-DomainController <Fqdn>] [-GenerateCopyOfDSNFor <MultiValuedProperty>] [-Instance <TransportConfigContainer>] [-InternalSMTPServers <MultiValuedProperty>] [-JournalingReportNdrTo <SmtpAddress>] [-MaxDumpsterSizePerStorageGroup <ByteQuantifiedSize>] [-MaxDumpsterTime <EnhancedTimeSpan>] [-MaxReceiveSize <Unlimited>] [-MaxRecipientEnvelopeLimit <Unlimited>] [-MaxSendSize <Unlimited>] [-TLSReceiveDomainSecureList <MultiValuedProperty>] [-TLSSendDomainSecureList <MultiValuedProperty>] [-VerifySecureSubmitEnabled <$true | $false>] [-VoicemailJournalingEnabled <$true | $false>] [-Xexch50Enabled <$true | $false>]

Detailed Description

The Set-TransportConfig cmdlet is used to display configuration information for e-mail transport settings that are applied across the Exchange 2007 organization.

To run the Set-TransportConfig cmdlet, the account you use must be delegated the Exchange Organization Administrator role.

To run the Set-TransportConfig cmdlet on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.

For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

Parameters

Parameter	Required	Type	Description
ClearCategories	Optional	System.Boolean	This parameter specifies whether to clear Microsoft Office Outlook categories during content conversion. The default value is $True.
DomainController	Optional	Microsoft.Exchange.Data.Fqdn	To specify the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to the Active Directory directory service, include the DomainController parameter on the command. The DomainController parameter is not supported on computers that run the Edge Transport server role. The Edge Transport server sole reads and writes only to the local ADAM instance.
GenerateCopyOfDSNFor	Optional	Microsoft.Exchange.Data.MultiValuedProperty	This parameter controls the non-delivery reports (NDRs) that are copied to a mailbox by specifying the delivery status notification (DSN) codes that you want to monitor. You must configure the list of monitored DSNs on one Hub Transport server and locally on each Edge Transport server in your Exchange 2007 organization. On a Hub Transport server, NDRs are copied to the mailbox that is assigned to the Microsoft Exchange Recipient. On Edge Transport servers, NDRs are copied to the mailbox that is assigned to external postmaster address. DSN codes are entered as x.y.z and are separated by commas. By default, the following DSN codes are monitored: 5.4.8 5.4.6 5.4.4 5.2.4 5.2.0 5.1.4 Although these DSN codes are monitored by default, the associated NDRs aren't copied to the Microsoft Exchange Recipient or to the external postmaster address if no mailbox is assigned to the Microsoft Exchange Recipient or to the external postmaster address. By default, no mailbox is assigned to the Microsoft Exchange Recipient or to the external postmaster address. To assign a mailbox to the Microsoft Exchange Recipient, use the MicrosoftExchangeRecipientReplyRecipient parameter in the Set-OrganizationConfig cmdlet. To assign a mailbox to the external postmaster address, create a new mailbox that is named "Postmaster". The default e-mail address policy of the Exchange organization should automatically add an SMTP address of postmaster@<Authoritative domain> to the mailbox.
Instance	Optional	Microsoft.Exchange.Data.Directory.SystemConfiguration.TransportConfigContainer	This parameter enables you to pass an entire object to the cmdlet to be processed. This parameter is useful in scripts where an entire object must be passed to the cmdlet.
InternalSMTPServers	Optional	Microsoft.Exchange.Data.MultiValuedProperty	This parameter specifies a list of internal Simple Mail Transfer Protocol (SMTP) server IP addresses or IP address ranges that should be ignored by Sender ID and connection filtering.
JournalingReportNdrTo	Optional	Microsoft.Exchange.Data.SmtpAddress	This parameter specifies the e-mail address to which journal reports are sent if the journaling mailbox is unavailable. By default, if this parameter is left empty, Exchange continues to try to deliver the journal report to the journaling mailbox.
MaxDumpsterSizePerStorageGroup	Optional	Microsoft.Exchange.Data.ByteQuantifiedSize	This parameter specifies the maximum size of the transport dumpster on a Hub Transport server. The default value is 18 MB. To enable the transport dumpster, the value of the MaxDumpsterSizePerStorageGroup parameter must be greater than 0, and the value of the MaxDumpsterTime parameter must be greater than 00:00:00. When you enter an integer, qualify the value with one of the following units: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) TB (terabytes) Unqualified values are treated as bytes. The valid input range for this parameter is 0 to 18446744073709551615 bytes.
MaxDumpsterTime	Optional	Microsoft.Exchange.Data.EnhancedTimeSpan	This parameter specifies how long an e-mail message should remain in the transport dumpster on a Hub Transport server. The default value is seven days. To enable the transport dumpster, the value of the MaxDumpsterSizePerStorageGroup parameter must be greater than 0, and the value of the MaxDumpsterTime parameter must be greater than 00:00:00. To specify a 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:00 to 24855.03:14:07.
MaxReceiveSize	Optional	Microsoft.Exchange.Data.Unlimited	This parameter specifies the maximum message size that can be received by recipients in the organization. The default value is Unlimited. When you enter a value, qualify the value with one of the following: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) Unqualified values are treated as bytes. The valid input range for this parameter is 0 to 2147483647 bytes. Note   This parameter is not used on an Edge Transport server. You must use the message size limits on the Send and Receive connectors that are configured on the Edge Transport server. This controls the size of messages that are processed by the server.
MaxRecipientEnvelopeLimit	Optional	Microsoft.Exchange.Data.Unlimited	This parameter specifies the maximum number of recipients to which a sender can send. This includes distribution list expansion. The default size is Unlimited. The valid input range for this parameter is 0 to 2147483647. Note   This parameter is not used on an Edge Transport server. You must use the message size limits on the Send and Receive connectors that are configured on the Edge Transport server. This controls the size of messages that are processed by the server.
MaxSendSize	Optional	Microsoft.Exchange.Data.Unlimited	This parameter specifies the maximum message size that can be sent by senders in the organization. The default size is Unlimited. When you enter a value, qualify the value with one of the following: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) Unqualified values are treated as bytes. The valid input range for this parameter is 0 to 2147483647 bytes.
TLSReceiveDomainSecureList	Optional	Microsoft.Exchange.Data.MultiValuedProperty	This parameter specifies the domains from which you want to receive domain secured e-mail by using mutual Transport Layer Security (TLS) authentication. To fully support mutual TLS authentication, you must also perform the following steps: Enable Domain Security (Mutual Auth TLS) and the TLS authentication method on the Receive connectors that receive messages from the domains that you specified with the TLSReceiveDomainSecureList parameter. Specify the domains to which you want to send domain secured e-mail by using the TLSSendDomainSecureList parameter. Enable Domain Security (Mutual Auth TLS) on the Send connectors that send messages to the domains that you specified in the TLSSendDomainSecureList parameter. Multiple domains may be separated by commas. The wildcard character (*) is not supported in the domains that are listed in the TLSReceiveDomainSecureList parameter or in TLSSendDomainSecureList parameter. The default value for both parameters is an empty list ({}).
TLSSendDomainSecureList	Optional	Microsoft.Exchange.Data.MultiValuedProperty	This parameter specifies the domains from which you want to send domain secured e-mail by using mutual TLS authentication. To fully support mutual TLS authentication, you must also perform the following steps: Enable Domain Security (Mutual Auth TLS) on the Send connectors that send messages to the domains that you specified in the TLSSendDomainSecureList parameter. Specify the domains from which you want to receive domain secured e-mail by using the TLSReceiveDomainSecureList parameter. Enable Domain Security (Mutual Auth TLS) and the TLS authentication method on the Receive connectors that receive messages from the domains that you specified in the TLSReceiveDomainSecureList parameter. Multiple domains may be separated by commas. The wildcard character (*) is not supported in the domains that are listed in TLSSendDomainSecureList parameter or in TLSReceiveSecureList parameter. The default values for both parameters an empty list ({}).
VerifySecureSubmitEnabled	Optional	System.Boolean	The valid values for this parameter are $True or $False. The default value is $False. The VerifySecureSubmitEnabled parameter verifies that e-mail clients that are submitting messages from mailboxes on Mailbox servers are using encrypted MAPI submission. By default, Outlook 2007 uses encrypted MAPI submission to send messages from Exchange 2007 mailboxes. By default previous versions of Outlook do not use encrypted MAPI submission to send messages from an Exchange mailbox. If the VerifySecureSubmitEnabled parameter is set to the value of $True, and Outlook 2007 is used to submit the message, the message is marked as secure. If a previous version of Outlook is used to submit the message, the message is marked as anonymous. If the VerifySecureSubmitEnabled is set to the value of false $False, all MAPI message submissions are marked as secure. Messages that are submitted from mailboxes on the Mailbox server by using any MAPI client are not checked for encrypted MAPI submission. If you use previous Outlook versions in your Exchange organization, you should set VerifySecureSubmitEnabled to $False.
VoicemailJournalingEnabled	Optional	System.Boolean	This parameter specifies whether Unified Messaging voice mail messages are journaled by the Journaling agent. The default value is $True.
Xexch50Enabled	Optional	System.Boolean	This parameter specifies whether Xexch50 authentication should be enabled for backward compatibility with Exchange 2003 servers. The default value is $True.

Example

The first example in the following code shows how to configure the Exchange 2007 organization to forward all DSN messages that have the DSN codes 5.7.1, 5.7.2, and 5.7.3 to the postmaster e-mail account.

The second example in the following code shows how to configure the Exchange 2007 organization to redirect all journaling reports that can't be delivered to the journaling mailbox to the e-mail account journalingndr@contoso.com.

Set-TransportConfig -GenerateCopyOfDsnFor 5.7.1,5.7.2,5.7.3
Set-TransportConfig -JournalingReportNdrTo journalingndr@contoso.com