Tools

Exchange Error: 550.571 unable to relay

This article provides brief information and steps to resolve the following error when sending email from Serv-U: 550.571 - Unable to relay This can be seen if telnet is used to the server on port 25 and initiate unauthenticated SMTP communications.

First published date

10/11/2018 3:47 PM

Last published date

10/11/2018 3:47 PM

Overview

This article provides brief information and steps to resolve the following error when sending email from Serv-U:

550.571 - Unable to relay

This can be seen if telnet is used to the server on port 25 and initiate unauthenticated SMTP communications.

Product section

Serv-U Managed File Transfer & Serv-U FTP Server

Cause

The 550 5.7.1 means that it will not relay the message from the sending machine, You need to have a receiver connector that allows your client's IP to relay through Exchange.

Resolution

To permit a non-Exchange server to relay mail we can create a new Receive Connector on the Hub Transport server.

Launch the Exchange Management Console and go to Server Management > Hub Transport.
Select the Hub Transport server you wish to create the new Receive Connector on.
From the Actions pane of the console, select New Receive Connector.

Name the new connector as Relay and click Next to continue.

Note: 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. 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.

Highlight the default IP range in the remote network settings and click the red X to delete it.

Click Add and enter the IP address of the server you want to allow to relay through the Exchange server. Click OK to add it and then Next to continue.

Click New to complete the wizard.
Note: The Receive Connector has now been created but is not yet ready to allow the server to relay through it.

Go back to the Exchange Management Console (© 2018 Quadrotech Solutions AG, available at https://practical365.com/, obtained on October 11, 2018), right-click the newly created Receive Connector, and then select Properties.
Click the Permission Groups tab and select the Exchange Servers box.

Click the Authentication Tab and select the Externally Secured box.

Apply the changes.

The Receive Connector should now be ready for the server to relay through.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.