Microsoft Exchange Outbound Filtering Setup for Mail Assure
All references of SMARTHOST need to be replaced with the Mail Assure SMTP hostname, see this page for full details.
Exchange 2013/2016/2019
Routing all outgoing mails via the outgoing smarthost:
- Ensure the Exchange's Public IP address is added as an authorized smarthost (without authentication)
Exchange's Public IP address can be either IPv4 or IPv6 if configured
- Ensure the outgoing user has correct limits set matching your traffic volumes
- Update your configuration
A Send Connector must already have been created and configured correctly in Exchange Administration Center:
- Navigate to Mail Flow
- Select Send Connectors
- Select + Add new connector
- Add a relevant name for this connector, Eg: Mail Assure Outgoing Filtering
- Select : Internet (For example, to send internet mail) and click Next
- Select Route mail through smart hosts
- Add the SMARTHOST by clicking on the + sign
- Click Save
- Click Next
- If you are using an IP outgoing user leave None / If you are using an Authenticating user select Basic Authentication > Input the Outgoing User and Password
- Click Next
- Address space: Click the + sign and in the Full Qualified Domain Name (FQDN): input
- Click Save and Next
- Source server: Click on the + sign and select the server from the list
- Click OK and Finish
You need to ensure that the port 587 is being used:
- Open the Exchange Management Shell
- Run the following:
Set-SendConnector -identity "NAME OF CONNECTOR" -Port:587
Exchange 2007/2010
Versions 2013 and earlier of exchange have reached the official End-of-Life (EOL) with Microsoft and Microsoft has ceased support for these products. The following instructions were correct at time of writing, however, as these versions are no longer officially supported, we cannot guarantee the success of configuration.
Routing all outgoing mails via the outgoing smarthost:
- Ensure the IP address is added as an authorized smarthost (without authentication)
- Ensure the outgoing user has correct limits set matching your traffic volumes
- Update your configuration. A Send Connector must already have been created and configured correctly on the Hub Transport server
- Open Exchange Management Console
- Click on the + next to Organization Configuration
- Select Hub Transport
- Open the Send Connectors tab
- Right-click on the existing Send Connector, select Properties and go to the Network tab
- Select "Route mail through the following smart hosts:" and click Add
- Enter SMARTHOST (you need to use port 587)
- If you have more then one Smarthost, repeat the previous two steps
The changes you've made to the Send Connector will take effect straight away without you having to reboot the server or restart any services.
In order to change the port to 587 you will have to issue the following command in the Exchange Powershell Console:
Set-SendConnector -identity "NAME OF CONNECTOR" -Port:587
Afterward restart the transport service and relaying will work
Routing all outgoing mails via the outgoing smarthost with Username Authentication:
A Send Connector must already have been created and configured correctly on the Hub Transport server.
- Open Exchange Management Console
- Click on the + next to Organization Configuration
- Select Hub Transport
- Open the Send Connectors tab
- Right-click on the existing Send Connector, select Properties and go to the Network tab
- Select "Route mail through the following smart hosts:" and click Add
- Enter SMARTHOST in the FQDN section
- Click Change under the smart-host authentication
- Select Basic Authentication
- Add your newly created username and password
- Click OK
The changes you've made to the Send Connector will take effect straight away without you having to reboot the server or restart any services.
In order to change the port to 587 you will have to issue the following command in the Exchange Powershell Console:
Set-SendConnector -identity "NAME OF CONNECTOR" -Port:587
Afterward restart the transport service and relaying will work
Disclaimer: This documentation may contain references to third party software or websites. N-able has no control over third party software or content and is not responsible for the availability, security, or operation, of any third-party software. If you decide to utilize a release involving third-party software, you do so entirely at your own risk and subject to the applicable third party’s terms and conditions of the use of such software. No information obtained by you from N-able or this documentation shall create any warranty for such software.