gasratalk.blogg.se

We have an internet facing company that relays access for a back-end company, both companies have independent active directory forest with their own Exchange 2010 servers in their own email domains – let’s call these EXCHDOMAIN1 and EXCHDOMAIN2.ĮXCHDOMAIN1 (internet facing) is configured with EXCHDOMAIN2 as an Accepted Domain, with the Internal Relay Domain option. Very interesting article, it helped with some of my configuration but I have an issue that I would appreciate your guidance on.

Select the Authentication Tab and tick the Externally Secured box.Īpply the changes and the Receive Connector is now ready for the server to relay through. Select the Permission Groups tab and tick the Exchange Servers box. Go back to the Exchange Management Console, right-click the newly created Receive Connector and choose properties. The Receive Connector has now been created but is not yet ready to allow the server to relay through it. Click OK to add it and then Next to continue.Ĭlick the New button to complete the wizard. Now click the Add button and enter the IP address of the server you want to allow to relay through the Exchange server. Highlight the default IP range in the remote network settings and click the red X to delete it. Using dedicated IP addresses for each connector is sometimes required if you need to create connectors with different authentication settings, but for a general relay connector it is not necessary to change it. You can leave the local network settings as is, or optionally you can use a dedicated IP address for this connector if one has already been allocated to the server. Give the new connector a name such as “Relay ” and click Next to continue. 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.