Troubleshoot 550 5.7.1 Unable to Relay Exchange 2010 – Top 4 Solution

The user can fix the 550 5.7.1 Unable to Relay Exchange 2010 problem with the help of EMC or PowerShell Commands. In this blog, we are going to explain both EMC and PowerShell commands to fix the issue. Now, before implementing the solution it is important to know the possible cause behind this issue. This will help the user to prevent the issue in the future.

Why 550 5.7. 1 Unable to Relay Exchange 2010’ Occurs?

550 5.7.1 error occurs because the receive connector in Exchange Server 2010/2007 does not have its default domain value set. Whereas in Exchange 2000/2003 if no domain name is provided, it automatically appends the default domain to values that are submitted to MAIL FROM: or RCPT TO: in the message envelope by sending server.

In Exchange Server 2010, the default domain value on the receive connector is not set by default. In the MAIL FROM: or RCPT TO: commands if no domain name is specified Exchange Server 2007 rejects the message with ‘501 5.1.7 Invalid Address’ response.

Basically, in simple words, one can say that this error message appears when the user tries to deliver email messages outside the domain.

Some Other Possible reasons responsible for the occurrence of 550 5.7.1 error are:

1. If the sender is not recognized by the outgoing mail server
2. If the Recipient’s policy defined by the receiver domain has imposed several restrictions on the Sender’s domain
3. Corruption may exist in the Exchange Database
4. Authentication fails for the sender domain

For Better Understanding, You Can Also Go Through The Scenario Given Below:

“I am having a website application and I need to send email to that application via our Exchange Server. Now, when I send email internally it was sent perfectly. But I was sending email to an external address I got 550 5.7.1 unable to relay error. I am not able to figure out why this error is occurring. Please provide me an instant and simple way to fix this issues.”

Methods to Fix 550 5.7.1 Unable to Relay Exchange 2010 Issue

The user can resolve 550 5.7.1 error by implementing the methods in the section given below:

Solution 1: Use the EMC to create the Receive connector

1. First, you have to perform one step according to your choice:
   • To create a Receive Connector on a system having the Edge Transport Server role installed on it. The user needs to select Edge Transport and then click the Receive Connectors tab in the work pane.
   • To create a Receive connector on a Hub Transport Server role the user needs to expand the Server Configuration and then select Hub Transport. Now, in the result pane, you have to select the server on which you want to create the connector. After that, click on the Receive Connectors tab.
2. Click New Receive Connector in the action pane. The New Receive Connector wizard will open
3. On the Introduction page, you have to follow the steps:
   • Type a meaningful name for this connector in the Name field.
   • In the Select the intended use for this Receive Connector field, select Custom
   • Click on the Next button
4. Now, on the Local Network Settings page, follow the steps given below:
   • First, you have to select the existing All Available IPv4 entry and then click on the
   • Now, click Add, and then in the Add Receive Connector Binding dialog box, select Specify an IP address
   • After that, you have to type an IP address assigned to a network adapter on the local server
   •  In the Port field, type 25 and then click on the OK button.
   • You have to leave the Specify the FQDN this connector will provide in response to HELO or EHLO field blank
   • Finally, click on the Next button
5. On the Remote Network Settings page, you have to follow the steps given below:
   • First, select the existing 0.0.0.0 – 255.255.255.255 entry and then click on
   • Now, you have to click on the Add or the drop-down arrow located next to Add
   • Type the IP address or IP address range for the remote messaging server or servers that are allowed to relay mail on this server.
   • Click on the OK and then click on Next
6. Review the configuration summary for the connector on the New Connector page. To create the Receive connector by using the settings in the configuration summary, you have to click on the New
7. On the Completion page, click on the Finish button
8. Select the Receive connector that you created in the work pane
9. Now, under the name of the Receive connector in the action pane, click on Properties
10. The Properties page will open. Click the Permission Groups tab and select Anonymous users
11. Finally, click on the OK button to save your changes and exit the Properties page

Solution 2: Use the Shell to Create the Receive Connector

Create the Receive Connector

Here, you have to use the New-ReceiveConnector cmdlet to create the Receive connector Anonymous Relay that listens on local IP address 10.2.3.4 on port 25 from a source server at IP address 192.168.5.77.

New-ReceiveConnector -Name “Anonymous Relay” -Usage Custom -PermissionGroups AnonymousUsers -Bindings 10.2.3.4:25 -RemoteIpRanges 192.168.5.77

Grant relay permission to anonymous connections on the new Receive connector

Get-ReceiveConnector “Anonymous Relay” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGIN” -ExtendedRights “Ms-Exch-SMTP-Accept-Any-Recipient”

Solution 3: Use Exchange Server Manager to Troubleshoot 550 5.7.1 Unable to Relay Exchange 2010

1. First, start Exchange Server Manager and navigate to Administrative Groups in the Exchange Server Manager
2. Now, you have to select Administrative Group Name and select Server > Server Name
3. After that, you have to click on the Protocols and select SMTP
4. Select Properties by right-clicking Default SMTP Virtual Server
5. Click on the Access tab > Relay to select only the list below
6. Next, you need to select the IP that you want to relay and the domain
7. Finally, you have to check the box associated with ‘Allow all computers which successfully authenticate to relay regardless of the list above

Solution 4: For Corruption Issue – Use Exchange Recovery Software

If 550 5.7.1 Unable to Relay Exchange 2010 is encountered due to the corruption in the EDB file, the user can use advanced software i.e. Exchange Recovery Software to recover corrupted Exchange Server mailboxes and repair multiple EDB Exchange databases. Moreover, the software also supports the recovery of deleted emails from Exchange mailboxes.

Download Now

Purchase Now

The software is integrated with numerous features which makes it an efficient software. The utility is also capable to support recovery from dismounted and offline Exchange database files, repairing Exchange mailbox databases, private mailboxes, and public folders using the dual scan mode option.

The quick scan is used to remove minimal corruption from the EDB files and to recover the highly corrupted/damaged/unhealthy Exchange database file select the advance scan. This option to recover permanently deleted EDB mailboxes and items from the loaded .edb file. After recovery, users can export mailbox to PST from offline EDB files and various other formats.

Also Read: Easy way to recover purged emails Exchange 2016/2013/2010

This utility is capable enough to export selective or multiple Exchange mailboxes (user, disconnected, legacy, archive, shared) and items (calendars, emails, tasks, journals, notes, contacts) to Live Exchange Server, Office 365, and EML, HTML, MBOX, PST, PDF, MSG file formats.

Key Features of Automated Software

1. Repair & Recover corrupted Exchange EDB file
2. Preview recovered MS EDB mailbox data items after conversion
3. Preserve original folder structure & keep metadata intact
4. Date and category option export selectively Exchange mailbox data
5. Remove email encryption (SMIME/OpenPGP) option in bulk from EDB mailboxes
6. Compatible with all Microsoft Outlook, Exchange Server, and Windows OS version

Stepwise Method to Recover Corruption EDB File

Step 1: Firstly, download the utility in your machine > Install > Run it

Step 2: After that, click Add File > Load offline Microsoft EDB file

Step 3: Then, select on Advance scan mode > Click on the Add button

Step 4: Now, preview recovered Microsoft offline EDB file > Click export

Step 5: Finally, click on the Exchange mailboxes > Select the export option > Click on browse button to set destination file location > Click on the export button

Final Words

When any type of error occurs it interrupts the workflow. Thus, it becomes necessary to fix the error as soon as possible. In the above section, we have explained various solutions to fix 550 5.7.1 unable to relay Exchange 2010 error. With the help of the solutions, the user can easily troubleshoot this error without any hassle. In case of corruption in the Exchange database file, it is highly suggested to use the automated wizard mentioned here easily remove corruption from EDB file and repair corrupted Exchange 2010 mailbox along with another version without any data loss and export the healthy as well as recovered mailboxes directly to the Live Exchange Server, O365 and multiple file formats in a simplified manner.