Exxhange SQL And IIS- P76 docx

■ Internet This option is used to create a Receive connector that will receive e-mail from servers on the Internet.. Note that this connector type will be confi gured to only accept conn

■ Internet This option is used to create a Receive connector that will receive e-mail from servers on the Internet This connector will be confi gured to accept connections from anonymous users

■ Internal Internal Receive connectors are used to receive e-mail from servers within your Exchange organization Note that this connector type will be confi gured to only accept connections from internal Exchange servers

■ Client Client Receive connectors are used to receive e-mail from authenticated Exchange users This means that this connector will be confi gured to only accept client submissions from authenticated Exchange users

■ Partner Partner Receive connectors are used to receive e-mail from partner domains This connector will be confi gured to only accept connections from servers

Figure 6.29 Selecting the Receive Connector Type

included in the list of domain-secured domains You can add domains to this list by

using the -TLSReceiveDomainSecureList parameter in the Set-TransportConfi g

command

5 When you have selected the type of connector you want to create, click Next.

6 As shown in Figure 6.30, you now have the option of modifying the IP address and

port that should be used to receive mail With Custom, Internet, and Partner Receive

connectors, you also have the option of entering a FQDN that should be provided in

response to HELO and EHLO commands When ready, click Next.

7 On the Confi guration Summary page, click New On the Completion page, click

Finish

Figure 6.30 Entering the Local IP Addresses that Should Be Used to Receive Mail

To create a Receive connector via the Exchange Management Shell, you must use the

New-ReceiveConnector cmdlet For example, to create a Receive Connector similar to

the one we generated in the previous steps, run the following command:

New-ReceiveConnector –Name ‘Special Receive Connector’ –Usage ‘Custom’ –Bindings ‘0.0.0.0:25’ –Fqdn ‘mail.exchangedogfood.dk’ –RemoteIPRanges ‘0.0.0.0– 255.255.255.255’ –Server ‘EDFS03’

At any time, you can modify an existing Receive connector as required You do this by selecting

the respective Receive connector and clicking Properties in the Action pane In addition, any

existing Receive connectors can be disabled, enabled, and removed as necessary You do this by

selecting the particular Receive connector and clicking the required task in the Action pane.

Managing Message Size and Recipient Limits

Like previous versions of Exchange, Exchange 2007 allows you to restrict the size of messages users can send and receive The message size limits can be set globally in the organization on a per-server, per-connector level, and/or a per-user basis Message size and recipient limits can only be confi gured using the Exchange Management Shell In the following, I’ll show you how to confi gure these limits Confi guring Global Limits

By default, the global limits are set to unlimited, as can be seen in Figure 6.31

Figure 6.31 Listing Global Limits

use the following command:

Set-TransportConfi g -MaxReceiveSize:<value> -MaxSendSize:<value>

-MaxRecipientEnvelopeLimit:<value>

NOTE

When you set the MaxReceiveSize or MaxSendSize, it’s important to note that if you only specify a number such as 100, it defaults to kilobytes (KBs) This means that it is generally a good idea to specify the number followed by either KB or MB

Confi guring Server Limits

Since message size limits are controlled via Send and Receive connectors, you cannot confi gure

message size limits per server You can, however, confi gure the maximum number of recipients

allowed per message That is, the maximum number of recipients that can be included on a single

e-mail message and submitted to the Pickup directory By default, the maximum number of

recipients is 100, which can be verifi ed by running Get-TransportServer | FL in the Exchange

Management Shell To change this setting, you must use the following command:

Set-TransportServer -PickupDirectoryMaxRecipientsPerMessage:<value>

Confi guring Connector Limits

By default, the default maximum message size for both Send and Receive connectors is 10 MB

You can verify this by running Get-SendConnector | FL and Get-ReceiveConnector | FL, respectively.

Send Connectors

To change the maximum message size limit on a Send connector, use the following command:

Set-SendConnector <name of connector> -MaxMessageSize:<value>

Receive Connectors

To change the maximum message size limit on a Receive connector, use the following command:

Confi guring Per-User Limits

You can also confi gure message size limits on a per-user level, if required Message size limits set on

a user override global limits and connector limits The default message size limit for both sent and

received messages on a user mailbox is unlimited, as can be seen by running Get-Mailbox | FL

In order to change this setting, run the following command:

Set-Mailbox –MaxReceiveSize:<value> -MaxSendSize:<value>

NOTE

When you set the MaxMessageSize, it’s important to note that if you only specify a number such as 100, it defaults to kilobytes (KBs) This means that it is generally a good idea to specify the number followed by either KB or MB

NOTE

When you set the MaxReceiveSize and MaxSendSize, it’s important to note that if you only specify a number such as 100, it defaults to kilobytes (KBs) This means it’s generally a good idea to specify the number followed by either KB or MB

Message Tracking with

Exchange Server 2007

When message tracking is enabled, all Simple Mail Transfer Protocol (SMTP) transport activity on all messages that transfer to and from an Exchange 2007 computer with a Hub Transport, Mailbox, or Edge Transport server role installed are recorded into a log, located by default in the C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\MessageTracking directory Message tracking logs can be used for message forensics, mail fl ow analysis, reporting, and troubleshooting

When message tracking is enabled (which is the case by default), the maximum age for message tracking log fi les is 30 days After 30 days, the oldest message tracking log fi les are deleted using circular logging This is only true if the message tracking log reaches its specifi ed maximum size (which, by default, is 10 MB), or a message tracking log fi le reaches its specifi ed maximum age