Monday , October 15 2018

How to Create anonymous relay Connector in Exchange 2010 and

We had to migrate few Exchange servers of to different location , So we had to change the Public IP , and Public DNS replication didn’t work as expected due to a SQL database issue in our Public DNS servers.

So Our new public IP of has been black listed , We didn’t have time to white list all of them and even after whitelisting some banking domains keep on rejecting our new public IP of


We decided to relay the emails on another exchange server in a different domain,  so that production is up and mail is flowing smoothly.

So lets see how to create a relay connector in the Exchange server

Goal – will relay emails using Exchange Server

Logged into Server

Server Configuration – Hub Transport – New Receive Connector


Type a Friendly name – Choose Custom


Choose Next


Please take off All IP range . So that your Server don’t act as open Relay,

Specify an remote IP of , so that Server remains secured


Choose New to Get the Connector Created


Now, Right Click on the Relay Connector you Created . Make Sure Transport Layer Security (TLS) is checked


Make sure anonymous users are checked



Now add the required Ad permission using the below command .

Open Exchange Management Shell and Run

Get-ReceiveConnector "ServerName\Anonymous Relay" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

Now Relaying Server is ready , As it will accept emails from .

Now Redirect the mail flow via Server

Logging into Server

Organization Configuration – Hub Transport – Send Connectors

Open the Internet Connector – Enter the Remote ip of Server

(Restart Transport Service if required)


Now Emails are Relaying via Server.


About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Exchange Server MVP , Publisher of
Supporting/Deploying/Designing Microsoft Exchange for some years.
Extensive experience on Microsoft Technologies.

Check Also

Message submission rate for this client has exceeded

421 4.4.2 Message submission rate for this client has exceeded the configured limit. In my ...

Leave a Reply

Your email address will not be published.