Select the Hub Transport server you wish to create the new Receive Connector on, and from the Actions pane of the console choose New Receive Connector. Launch the Exchange Management Console and navigate to Server Management, and then Hub Transport. To permit a non-Exchange server to relay mail we can create a new Receive Connector on the Hub Transport server. 220 Microsoft ESMTP MAIL Service ready at Wed, 18 Au However if I try to relay out to an external recipient, the Exchange server does not allow it. But with Anonymous Users enabled on the Receive Connector I can send from an address to a valid local address. You’ll note that relay is denied if I try to send from an address to an address, because neither is a valid domain for the Exchange organization.
In those cases relay would still be denied but will behave differently than the first example. Mail from: 5.7.1 Client was not authenticatedįor some Hub Transport servers that are internet-facing, anonymous connections may already be enabled. 220 Microsoft ESMTP MAIL Service ready at Wed, 18 AuĢ50 Hello You can see this in effect if you telnet to the server on port 25 and try to initiate unauthenticated SMTP communications.
However, this connector is secured by default to not allow anonymous connections (ie, the type of connection most non-Exchange systems will be making). The transport service listens for SMTP connections on it’s default Receive Connector. SMTP communication is handled by the Hub Transport server in an Exchange organization. This is common with multi-function devices such as network attached printer/scanners, or applications such as backup software that send email reports. In most Exchange Server 2010 environments there will be the need to allow relaying for certain hosts, devices or applications to send email via the Exchange server.
0 kommentar(er)
