"Deep Exchange 2013"13 send connector

What is a connector?

A connector is an object stored in an ad that is called by Exchange's transport service to obtain a logical connection path to a mail flow. Most of the settings in the current version of the connector can only be set in the Exchange Management shell, and the Exchange Administration Center (EAC) does not contain all of the options (even if the previous version was set up in EMC). In the graphical interface we mainly configure the connector through the Receive Connectors tab and the Send Connectors tab in the Mail Flow section of the EAC. When you select a connector, the right pane will come up with some summary options for changing the connector

650) this.width=650; "height=" 327 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00 /6f/af/wkiol1wlttfb6qyoaad_1emu3-q917.jpg "border=" 0 "/>

The Send connector in Exchange 2013 is somewhat different from the previous version of the Send connector feature (nonsense!). The biggest difference is that the link connector functionality has been discarded and you have to manage the receive and send connectors separately. A link connector is a receive connector that is linked to a Send connector that allows you to manage a Send/Receive connector to the same target domain in the same unit, in other words, all messages received by the Receive connector are forwarded to the Send connector to which it is linked. I don't have much to say about this feature, and I want to know how to play the link connector in Exchange 2010, look at the following page:

(Reference: Create a link connector: https://technet.microsoft.com/zh-cn/library/bb201724 (v=exchg.141). aspx)

The default maximum message size for the Send connector is now 35M instead of 10M, which means that the attachments are getting bigger ...

Last but not least, when the administrator configures the connector in the EAC, the EAC will let the administrator specify the purpose of the connector and allow only the Send/Receive connector for SMTP to be created. Depending on the purpose of the specified connector, the options you see during the configuration process also change. For example, if you configure a Partner connector, the option will specify that the MX record should be used instead of a smart host, because by definition, all mail through this connector must go directly to the partner and have to say that these settings are ...

Send connectors:

A Send connector is a logical pipeline through which outbound mail flows, and when a send connector is created, its definition and configuration are stored in the ad and can be called by MBX servers in any organization. Unlike in previous versions, if your connector has multiple source servers in a cross-ad site, you'll see an event log warning. The most common configuration of a send connector is to configure the message to be sent to the public, with an asterisk, and throw it to DNS resolution. Of course, you can also configure Send connectors that specify which SMTP domains are destined for.

Let's go over the process of configuring a Send connector:

1, first have to take a name, then you have to choose a type. Each send connector has different permissions and network settings, and you can click on the "Learn More" section to see a description of Microsoft.

650) this.width=650; "height=" 401 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00 /6f/b2/wkiom1wltp-si6jsaadmmnelryy817.jpg "border=" 0 "/>

2. Specify that the Send connector is sent through a smart host or through the MX record of DNS. The settings here should be based on the type of connector you chose in the first step, some types will not allow the use of the smart host to send e-mail, the previous said that there is no more chat. If you select Smart Host delivery here, Exchange will let you specify the authentication algorithm to connect with the smart host in the next step. It's also possible that you have an SMTP anonymous relay server in your environment, and you don't have to verify it at this time. The smart host can also be another Exchange server, so you have to choose the Exchange Server Authentication method. I will not talk about the other, according to the environment.

In addition to the above two options, there is another option: Use the external DNS lookup settings on the server with the transport role, which specifies whether the CAS server uses the DNS addresses configured on the network card or uses a different configured address. We'll talk about this in the section on mail routing later. Here, we'll sell a xiaoguanzi.

650) this.width=650; "height=" 419 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00 /6f/af/wkiol1wlttjr2seaaadplquwepu164.jpg "border=" 0 "/>

3. Specify the address space to which the send connector routes messages, and the simplest address space is "*", which means that the Send connector can match any SMTP domain. The Scope Send connector check box is to control whether the connector is valid for all Hub Transport and MBX servers in the organization. By default, this check box is blank, and if you select this check box, Exchange restricts the Send connector to use only the MBX server in the same ad site as the source server, and the server outside the site does not consider the Send connector as a possible destination. The English version of Exchange Server here is scoped Send Connector, so in fact translation is ambiguous.

650) this.width=650; "height=" 411 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01 /6f/af/wkiol1wlttjtlxynaaesr_djrlc361.jpg "border=" 0 "/>

4, then the next step, the request to fill out the source server, Exchange 2010 will give you automatically select some source server, but in the EAC must be required to manually specify, the source server specified here is able to send mail through the Send connector server, So other servers are able to deliver the message to the source server specified here for the next route.

650) this.width=650; "height=" 410 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01 /6f/b2/wkiom1wltqdbdsqjaaeynaoefey277.jpg "border=" 0 "/>

When the above steps are completed, the Send connector is stored in the ad and is immediately valid for all servers that are allowed to use the Send connector (depending on the replication latency of the ad, of course).

In the third step above, the cost of a target address space, 1 of the lowest cost, the highest priority, represents the best possible connection of the address space, the cost of up to 100, the lowest priority. This allows exchange to differentiate between multiple lines. For example, in the environment there are two intelligent host can relay, for the same destination, such as * number, specified a number of send connectors, one in Shanghai site, another in Beijing site, then the Beijing site Exchange Server will only choose to go to the site of the smart host relay send connector, Shanghai's take Shanghai's own, even if two send connectors for the asterisk address space cost is equal, here also take into account the Ad-site link cost. Regarding the cost, we will continue to say in detail in the mail route behind.

The Send connector also has a bunch of settings that are not visible in the EAC and can only be obtained and set through EMS, which lists a get-sendconnector result,

650) this.width=650; "height=" 596 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02 /6f/af/wkiol1wlttnslly7aaj0gl1egqy072.jpg "border=" 0 "/>

Most properties have default custom values, and by property names it is clear that the property is what it is, such as MaxMessageSize and connectioninactivitytimeout, which literally mean what it does. If you want to make adjustments, then use Set-sendconnector, for example I need to adjust the maximum message size to 25MB, and then the inactive connection timeout time is 5 minutes, then use the following command

Set-sendconnector–identity ' ironport Gateway ' –maxmessagesize 25mb–connectioninactivitytimeout 00:05

Finally, the issue of centralized outbound mail flow, when the administrator created a send connector, is actually given the source server permissions to allow it to reach the destination directly, in fact, in the large environment, you have to centralize the management of outbound mail flow, for example, you have a 5 ad sites across the Exchange organization, Each site has several send connectors for redundancy and efficiency, and by default, any outbound mail header is displayed from the MBX server address associated with this Send connector, in which case you might want the MBX server to send through a proxy, in other words, Is that the transport service calls the Send connector to be sent by the FET to proxy, here is an option, after the Send connector is created, the Send connector will appear inside the "proxy through the Client Access server" check box, where the translation is a bit difficult to understand, through the-cas-agent Instead of through the client-access server-the-agent, ha. (Of course, you can also use the set-sendconnector–frontendproxyenabled command to open it, all the premise of this feature is that you do not have the hand to delete the 717-port receive connector-we will talk about this next chapter) Select this option and then OK. The MBX server calls this Send connector agent through the FET service on CAs in the same ad site, and then the address of the CAS appears in the header, not the MBX address. This feature can also cause problems at some point, and we'll talk about it in detail in the back of the message security.

650) this.width=650; "height=" 454 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02 /6f/b2/wkiom1wltqcrtk5laaecrlha09w829.jpg "border=" 0 "/>

OK, send the connector we talk about here, if you do not understand very well, we still more to meet the actual situation encountered more understanding.

This article is from the "Castamere Rainy season" blog, be sure to keep this source http://sodaxu.blog.51cto.com/8850288/1674421

"Deep Exchange 2013"13 send connector