Receive Connectors are the connectors that are responsible to handle inbound emails to receive emails both from internal and external domains. Servers having the Transport Roles should have Receive connectors to receive emails from Client or other servers or from external network.
With the architecture changes in Exchange Server 2013, both the Server Roles are having the Transport components where Mailbox Server role has the Hub Transport component and the Client Access Server role has the Front end Transport Component and both the server roles will have a receive connectors
Send connectors are organization specific, where the settings are applied globally but the receive connector are server based and below shows the default Receive Connectors in Exchange Server 2013 and their responsibilities
Default connectors created in Mailbox Server Role
“Default Chennai-EX-01″ is the connector created in Mailbox server role which accepts connection from Mailbox Servers and from Exchange 2010 Edge Transport Servers
“Client Proxy Chennai-EX-01″ will accept connection from Front End Servers (Client Access Server)
Default Connectors created in Client Access Server Role
“Default Frontend Chennai-EX-01″ accepts connection form all SMTP sender using port 25, message enters to the organization using this connectors
“Outbound Proxy Frontend Chennai-EX-01″ accepts messages from the send connector on a Mailbox Server with Front end proxy enabled. By default newly created Send Connectors will not be enabled with Front end proxy option and if we need we need to enable this option on respective send connector
“Client Frontend Chennai-EX-01″ Accepts secure connections with TLS applied
Note: To find whether the connector is associated to Mailbox Server role or Client Access Server role, we have to check the Transport Role option, where the HubTransport refers the connector is associated with Mailbox Server Role and the FrontEndTransport refers that connector is associated with the Client Access Server Role
How to create a Relay Connector in Exchange Server 2013
If we want to create a new Receive Connector in Exchange Server 2013, login to Exchange Control Panel -> Mailbox Flow -> Receive Connectors and Click New (+)
Enter a name and Select the Role as Hub Transport, and on the Type select Custom to create Relay connector to accept emails from Scanner or Printer in Exchange Server 2013
Note: Role option is used to specify whether to create the receive connector related to mailbox server or client access server and below are the types of receive connectors and their functions, based the type of receive connector selection the required type of authentication and the permission will be assigned to that connector
For more information about the Permission – Click here
For more information about the authentication – Click here
On the Network Adapter Bindings page, check All available IPv4 are added and click next to continue
On the Remote Network Settings, remove all IP address and add the Printer or Scanner or the application IP address and click Finish
Note: By default all the internal Receive Connectors are set to receive 35 MB of emails, based on your requirement modify this limit
With the architecture changes in Exchange Server 2013, both the Server Roles are having the Transport components where Mailbox Server role has the Hub Transport component and the Client Access Server role has the Front end Transport Component and both the server roles will have a receive connectors
Send connectors are organization specific, where the settings are applied globally but the receive connector are server based and below shows the default Receive Connectors in Exchange Server 2013 and their responsibilities
Default connectors created in Mailbox Server Role
“Default Chennai-EX-01″ is the connector created in Mailbox server role which accepts connection from Mailbox Servers and from Exchange 2010 Edge Transport Servers
“Client Proxy Chennai-EX-01″ will accept connection from Front End Servers (Client Access Server)
Default Connectors created in Client Access Server Role
“Default Frontend Chennai-EX-01″ accepts connection form all SMTP sender using port 25, message enters to the organization using this connectors
“Outbound Proxy Frontend Chennai-EX-01″ accepts messages from the send connector on a Mailbox Server with Front end proxy enabled. By default newly created Send Connectors will not be enabled with Front end proxy option and if we need we need to enable this option on respective send connector
“Client Frontend Chennai-EX-01″ Accepts secure connections with TLS applied
Note: To find whether the connector is associated to Mailbox Server role or Client Access Server role, we have to check the Transport Role option, where the HubTransport refers the connector is associated with Mailbox Server Role and the FrontEndTransport refers that connector is associated with the Client Access Server Role
How to create a Relay Connector in Exchange Server 2013
If we want to create a new Receive Connector in Exchange Server 2013, login to Exchange Control Panel -> Mailbox Flow -> Receive Connectors and Click New (+)
Enter a name and Select the Role as Hub Transport, and on the Type select Custom to create Relay connector to accept emails from Scanner or Printer in Exchange Server 2013
Note: Role option is used to specify whether to create the receive connector related to mailbox server or client access server and below are the types of receive connectors and their functions, based the type of receive connector selection the required type of authentication and the permission will be assigned to that connector
For more information about the Permission – Click here
For more information about the authentication – Click here
On the Network Adapter Bindings page, check All available IPv4 are added and click next to continue
On the Remote Network Settings, remove all IP address and add the Printer or Scanner or the application IP address and click Finish
Note: By default all the internal Receive Connectors are set to receive 35 MB of emails, based on your requirement modify this limit
No comments:
Post a Comment