Exchange 2013 五个接收连接器功能与解释

简介:

Default Receive connectors created during setup

Certain Receive connectors are created by default when you install the Mailbox server role.

Default Receive connectors created on a Mailbox server running the Transport service

When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change. These connectors are the following:

  • Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.

  • Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.

Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously mentioned, their TransportRole value is HubTransport.

To view the default Receive connectors and their parameter values, you can use the Get-ReceiveConnectorcmdlet.

Default Receive connectors created on a Front End Transport server

During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:

  • Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.

  • Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.

  • Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.

In a typical installation, no additional Receive connectors are required.

---------------------------------------------------------------------------------------------------------------------------------------------

Mailbox Server running with Transport Service
=========================
Default <server>: 用来给本身或者其他MBX或者Edge服务器上的transport service提交邮件 。
Client Proxy <server>:用来给Front-End服务器的transport service提交邮件。


FrontEnd Transport Server
=========================
Client Frontend <server> (TCP 587):SMTP客户端通过 TLS的加密通道提交邮件。
Default Frontend <server> (TCP 25):SMTP客户端通过 TCP端口25提交邮件。缺省情况下,邮件从外部服务器传输就是通过这个端口的。
Outbound Proxy Frontend <server>:如果在后端服务器上有开启 FE proxy功能, 那么这个receive connector就是用来给后端服务器的send connector 来提交邮件的。

本文转自   流原炫   51CTO博客,原文链接:http://blog.51cto.com/xiaoyuanzheng/1702094

相关文章
|
6月前
|
JSON 网络协议 物联网
MQTT协议问题之消息类型分类如何解决
MQTT协议是一个轻量级的消息传输协议,设计用于物联网(IoT)环境中设备间的通信;本合集将详细阐述MQTT协议的基本原理、特性以及各种实际应用场景,供用户学习和参考。
|
消息中间件 定位技术 调度
《移动互联网技术》第八章 消息与服务:掌握不同类型广播监听方式,以及创建通知的方法
《移动互联网技术》第八章 消息与服务:掌握不同类型广播监听方式,以及创建通知的方法
48 0
|
Java Maven
java实现发送接收邮件的功能(详细代码步骤和jar包)
可以通过java代码发送A邮箱发送到B邮箱。
365 0
java实现发送接收邮件的功能(详细代码步骤和jar包)
EMQ
|
存储 物联网 Docker
v1.8.3 进行中:MQTT X CLI 支持多主题订阅,优化输出显示
九月,MQTT 5.0客户端工具MQTT X 1.8.3版本持续开发中,为会话过期间隔添加默认值,并优化了MQTT X CLI(命令行)的默认输出显示。
EMQ
165 0
v1.8.3 进行中:MQTT X CLI 支持多主题订阅,优化输出显示
|
Java 容器 应用服务中间件
|
数据安全/隐私保护 网络协议 网络安全