Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Microsoft Exchange Server 2010 : Completing Transport Server Setup (part 1) - Configuring Transport Limits

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
3/10/2014 9:40:04 PM

After you install Transport servers running Exchange Server 2010, you need to finalize the configuration by creating and configuring a postmaster mailbox and performing any other necessary tasks. For Exchange organizations with only Hub Transport servers, you should enable anti-spam features. For Exchange organizations with Edge Transport servers, you need to subscribe the Edge Transport servers to your Exchange organization. For either type of Exchange organization, you might also want to configure journal and transport rules on your Hub Transport servers.

1. Configuring the Postmaster Address and Mailbox

Every organization that sends and receives mail should have a postmaster address. This is the e-mail address listed on nondelivery reports and other delivery status notification reports created by Exchange Server. The postmaster address is not set by default. You must manually set the postmaster address.

To view your Exchange organization's postmaster address, enter the following command at the Exchange Management Shell prompt:

Get-TransportConfig | Format-List Name,ExternalPostMasterAddress

This command lists the postmaster address for the organization, as shown in this sample output:

Name: Transport Settings
ExternalPostmasterAddress : [email protected]

If you don't set the postmaster address, the address typically is set to $null, except when you have an Edge Transport server that hasn't been through the Edge Sync process. To change the postmaster address, you can use the –ExternalPostMasterAddress parameter of the Set-TransportServer cmdlet, as shown in this example:

Set-TransportConfig -ExternalPostMasterAddress "[email protected]"

If you want the postmaster address to be able to receive mail, you must either create a mailbox and associate it with the postmaster address or assign the postmaster address as a secondary e-mail address for an existing mailbox.

You also can view or change the organization's postmaster address by completing the following steps:

  1. In the Exchange Management Console, expand the Organization Configuration node, and then select the Hub Transport node.

  2. In the main pane, select the Global Settings node and then double-click Transport Settings. This displays the Transport Settings Properties dialog box.

  3. On the General tab, the current postmaster e-mail address is listed. If you want to change the postmaster address, enter the address you want to use, and then click OK.

2. Configuring Transport Limits

Exchange Server 2010 automatically places receive size, send size, and number of recipient limits on messages being routed through an Exchange organization. By default, the maximum message size that can be received by or sent by recipients in the organization is 10,240 KB and messages can have no more than 5,000 recipients. You configure maximum message size limits on individual Receive and Send connectors as discussed previously.

You can view or change the default limits for the Exchange organization by completing the following steps:

  1. In the Exchange Management Console, expand the Organization Configuration node, and then select the Hub Transport node.

  2. In the main pane, select the Global Settings tab and then double-click Transport Settings. This displays the Transport Settings Properties dialog box with the General tab selected by default, as shown in Figure 1.

    Set transport limits for the Exchange organization.

    Figure 1. Set transport limits for the Exchange organization.

  3. To set a maximum receive size limit, select the Maximum Receive Size check box and then type the desired receive limit in the related text box. The valid input range is 0 to 2,097,151 KB. If you clear the check box or use a value of 0, no limit is imposed on the message size that can be received by recipients in the organization.

  4. To set a maximum send size limit, select the Maximum Send Size check box and then type the desired send limit in the related text box. The valid input range is 0 to 2,097,151 KB. If you clear the check box or use a value of 0, no limit is imposed on the message size that can be sent by senders in the organization.

  5. To set a maximum number of recipients limit, select the Maximum Number Of Recipients check box and then type the desired limit in the related text box. The valid input range is 0 to 2,147,483,647. If you clear the check box or use a value of 0, no limit is imposed on the number of recipients in a message. Note that Exchange handles an unexpanded distribution group as one recipient.

  6. Click OK to apply your settings.

In the Exchange Management Shell, you assign the desired transport limits using the Set-TransportConfig cmdlet, as shown in Example 1. The –MaxReceiveSize and –MaxSendSize parameters set the maximum receive size and maximum send size, respectively. MaxRecipientEnvelopeLimit sets the maximum number of recipients in a message. When you use the –MaxReceiveSize and –MaxSendSize parameters, you must specify the units for values using KB for kilobytes, MB for megabytes, or GB for gigabytes. Your changes are made at the organization level and apply to the entire Exchange Server 2010 organization.

Example 1. Setting transport limits

Syntax

Set-TransportConfig [-Identity OrgId] [-DomainController DCName]
[-MaxReceiveSize <'MaxSize' | 'Unlimited'>]
[-MaxSendSize <'MaxSize' | 'Unlimited'>]
[-MaxRecipientEnvelopeLimit <'MaxRecipients' | 'Unlimited'>]


Usage

Set-TransportConfig -MaxReceiveSize '15MB' -MaxSendSize '15MB'
-MaxRecipientEnvelopeLimit '1000'
Other -----------------
- SharePoint 2013 : Health and Monitoring (part 4) - Timer Jobs, The Developer Dashboard
- SharePoint 2013 : Health and Monitoring (part 3) - Analytics, The Health Analyzer
- SharePoint 2013 : Health and Monitoring (part 2) - Correlation IDs, The Logging Database
- SharePoint 2013 : Health and Monitoring (part 1) - Logging
- SharePoint 2013 Request Management (part 2) - Request Management Administration
- SharePoint 2013 Request Management (part 1) - The Request Management Process
- Windows Server 2012 : Deploying Storage Spaces (part 5) - Implementing Storage Spaces, Using Windows PowerShell
- Windows Server 2012 : Deploying Storage Spaces (part 4) - Planning a Storage Spaces deployment - Availability, Management
- Windows Server 2012 : Deploying Storage Spaces (part 3) - Planning a Storage Spaces deployment - Hardware, Performance, Resiliency
- Windows Server 2012 : Deploying Storage Spaces (part 2) - Understanding Storage Spaces - Fixed vs. thin provisioning
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server