They
can be specified separately or using the Usage parameter but cannot be used in conjunction with this
parameter. If no usage type is specified, the default usage type of custom will be set; and a Receive
Connector identical in attributes to the Default Receive Connector with the exception of the specified
parameters is created.
Chapter 7: Confi guring the Hub Transport Role
205
Note that in Exchange Server 2007 SP1, you must specify a usage type when using the
New-ReceiveConnector cmdlet. Also note that Exchange Server 2007 SP1 supports the Internet
Protocol Version 6 (IPv6) addresses and when deployed on Windows Server 2008, you can specify both
IPv4 and IPv6 addresses for the RemoteIPRange parameter. Figure 7 - 11 shows how to create a new
Receive Connector, and then display the connectors created with differences in authentication methods
and permission groups. Some connectors have been created in advance.
Figure 7-11
Part II: Working with Server Roles
206
Next, you use the Remove-ReceiveConnector cmdlet to bulk remove the connectors created, as shown
in Figure 7 - 12 .
Figure 7-12
Setting Relay Restrictions and Submit Permissions
After creating the Receive Connector, you can control how messages flow through the connector. In
Exchange Server 2000/2003, you could configure relay restrictions to determine if messages could be
relayed to users not in the Exchange organization.
Pages:
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311