Export (0) Print
Expand All
9 out of 14 rated this helpful - Rate this topic

Set-TransportConfig

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1

Topic Last Modified: 2009-07-13

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


Set-TransportConfig [-ClearCategories <$true | $false>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-DSNConversionMode <UseExchangeDSNs | PreserveDSNBody | DoNotConvert>] [-GenerateCopyOfDSNFor <MultiValuedProperty>] [-HeaderPromotionModeSetting <NoCreate | MayCreate>] [-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>] [-WhatIf [<SwitchParameter>]] [-WritingBrandingInDSNEnabled <$true | $false>] [-Xexch50Enabled <$true | $false>]

The Set-TransportConfig cmdlet is used to modify 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.

 

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.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm parameter causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm parameter.

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.

DSNConversionMode

Optional

Microsoft.Exchange.Data.DSNConversionOption

The DSNConversionMode parameter controls how Exchange handles DSNs that are generated by earlier versions of Exchange or non-Exchange messaging systems. You can specify one of the following values for this parameter:

  • UseExchangeDSNs
  • PreserveDSNBody
  • DoNotConvert

By default, this parameter is set to UseExchangeDSNs and Exchange 2007 converts the DSNs to the Exchange 2007 DSN format. Any customized text or attachments that were associated with the original DSN are overwritten.

If you set this parameter to PreserveDSNBody, Exchange 2007 converts the DSNs to Exchange 2007 DSN format. However, the text in the body of the DSN message is retained.

If you set this parameter to DoNotConvert, Exchange 2007 does not modify the DSN message. Instead, Exchange 2007 delivers the message as a standard message.

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.

HeaderPromotionModeSetting

Optional

Microsoft.Exchange.Data.HeaderPromotionMode

Use the XHeaderCreationMode parameter to specify whether named properties will be created for custom X-headers on messages that are received from outside the Exchange organization. You can use one of the following values:

  • MustCreate   Exchange will create a named property for each new custom X-header.
  • MayCreate   Exchange will create a named property for each new custom X-header on messages that are received from authenticated senders. No named properties will be created for custom X-headers on messages that are received from unauthenticated senders.
  • NoCreate   Exchange will not create any named properties based on custom X-headers on incoming messages.

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. The valid input range for this parameter is 0 to 2147483647 kilobytes.

When you enter a value, qualify the value with one of the following units:

  • KB (kilobytes)
  • MB (megabytes)
  • GB (gigabytes)
  • TB (terabytes)

Unqualified values are treated as kilobytes.

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.

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

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.

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 10 MB. When you enter a value, qualify the value with one of the following:

  • KB (kilobytes)
  • MB (megabytes)
  • GB (gigabytes)

Unqualified values are treated as kilobytes. The valid input range for this parameter is 0 to 2097151 kilobytes. If you enter a value of Unlimited, no limit is imposed on the message size that can be received by recipients in the organization.

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 in a message. The default is 5000. The valid input range for this parameter is 0 to 2147483647. If you enter a value of Unlimited, no limit is imposed on the number of recipients in a message. Exchange 2007 treats an unexpanded distribution group as one recipient.

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 value is 10 MB. When you enter a value, qualify the value with one of the following:

  • KB (kilobytes)
  • MB (megabytes)
  • GB (gigabytes)

Unqualified values are treated as kilobytes. The valid input range for this parameter is 0 to 2097151 kilobytes. If you enter a value of Unlimited, no limit is imposed on the message size that can be sent by senders in the organization.

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.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf parameter instructs the command to simulate the actions that it would take on the object. By using the WhatIf parameter, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf parameter.

WritingBrandingInDSNEnabled

Optional

System.Boolean

The WritingBrandingInDSNEnabled parameter specifies if the product name and version number of Exchange 2007 is included in DSNs that are generated by Exchange.

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.

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
To ensure that you are reading the most up-to-date information and to find additional Exchange Server 2007 documentation, visit the Exchange Server TechCenter.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.