Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

Coping Up With Exchange 2007 Error 5.7.1 Unable to Relay

Paul Ryan | September 5th, 2014 | exchange 2007

It is required to make relay off for the Exchange Server with the use of Application Server. This situation may come up to the Exchange users when SharePoint is in use. Sending emails from a Server to the desired customers through employees or using CRM applications is also a concern. The high time to make relay off will be when you will get the SMTP error message “550 5.7.1 Unable to relay”.

It is highly recommended to restrict the relay for servers. No matter if it is connected to the internet or not. Restrictions or/and authentications will get used to stop relay via making use of IP address.

Relay restrictions for Exchange 2003 will be implemented in the manner:

image1

To know more about how to configure relay restriction for Exchange 2007, check out above given segments properly.

  • Authenticating the computers to relay is the first thing for which user needs to go on. For subject messages and other concerns, there will a group for which authentication rights will be submitted. The respected and desired permissions on this group will be:

NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Submit}
NT AUTHORITY\Authenticated Users {ms-Exch-Accept-Headers-Routing}
NT AUTHORITY\Authenticated Users {ms-Exch-Bypass-Anti-Spam}
NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Accept-Any-Recipient}

  • Proper specification of IP address will be the another step to move on, and it will be an effective idea when authentication will not run for Exchange. Protocol listeners like receive connectors will treat as close equivalents for Exchange 2007 under SMTP Virtual Server. Creating a new remote connector to allow the scope of remote connector is a necessary step.

image2

  • “Remote Network settings” is to allow to enter the range of server for which permissions will be restricted or authenticated. Take care while you are entering the IP for server to restrict or permit

image3

  • Now, you need to create scoped connector. This is required when application used will play the role to relay messages not only within a particular domain but also outside. Before performing the task, one need to manage and enable Exchange Server permission groups

image4

image5

Perform above given two steps in order so that you can prevent to the GUI from being blocked. Be sure that you are performing this process intelligently and effectively. Under the bypass limits of CRM properties you need to apply “Externally Secured” permissions with below mentioned commands:

MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Authoritative-Domain}
MS Exchange\Externally Secured Servers {ms-Exch-Bypass-Anti-Spam}
MS Exchange\Externally Secured Servers {ms-Exch-Bypass-Message-Size-Limit}
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Exch50}
MS Exchange\Externally Secured Servers {ms-Exch-Accept-Headers-Routing}
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Submit}
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Any-Recipient}
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Authentication-Flag}
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Any-Sender}

Now provide permissions to the new scoped connector with checkbox Anonymus Users.

image6

It is used for providing most shared and common permissions for the accounts those are created anonymously, but it is not responsible for offering relay permissions. Further commands those will be executed under Exchange Shell are:

Get-ReceiveConnector “CRM Application” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “ms-Exch-SMTP-Accept-Any-Recipient”.

Conclusion: –

Error 5.7.1 Unable to relay is the most common error faced by users when they try to send mail outside the organization. The main cause of the error is that the Exchange mail server is configured in such a manner that don’t allow users to send messages outside the organization.

To proceed further some time administrator wants to block the spam mails that tries to enter into the Orgnization from Outside. The administrator can easily solve the issue by setting up a new role in the transport layer.

The following two tabs change content below.

Paul Ryan

Paul Ryan is a technical blogger and he’s passionate about writing technical blogs and covering all popular issues related to Exchange server / Outlook apps. He is MCSE certified and putting all his knowledge and experience in providing solutions to the Exchange users/administrators.