At SMC side
Make sure that the RMCC.ini has the below configuration
Path of RMCC.ini
\\SMC server IP\c$\Program Files\Huawei Technologies Co., Ltd\SMC\ResourceManager\rmcc.ini
At Email server side. login to
We’ll click the tab called receive connectors which will allow us to see all receive connectors that exist..
Let’s take a look at the “Default B-E15DAG1″ receive connector that belongs to the HubTransport role as well as the “Default Frontend B-E15DAG1″ that belongs to the FrontendTransport role.
To create our relay connector, we’ll choose the + symbol to create a new Receive Connector.
Give the connector a name and be sure to choose Frontend Transport and Custom. Click Next.
The default settings here are fine. We want port 25 due to what I mentioned above. Click Next.
In the remote network settings, it is important to ensure that you remove 0.0.0.0-255.255.255.255. We want to explicitly define what servers are allowed to relay to ensure our server does not turn into an open relay for everybody. In my case, I am going to add SMC IP Address
But the server that owns SMC IP Address
would need to relay. Once this is done, click Finish.
Once the relay connector is created, open its properties, go to security, and make sure you check Anonymous Users.
So, as you can see, there is no Ms-Exch-SMTP-Accept-Any-Recipient permission added by default. Because of this, users will NOT be able to relay off your Exchange Server by default.
To activate Anonymous users to use this connector for relaying, you must issue the following command:
Get-ReceiveConnector “Email Server\Receive Connector Name” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “Ms-Exch-SMTP-Accept-Any-Recipient”
The command should be easy enough to read, but what it essentially does is retrieve the receive connector that you created, add a permission into Active Directory for the Anonymous Logon group, and assign that group the Ms-Exch-SMTP-Accept-Any-Recipient permission for that group on that connector. Once this is done, any server IPs you added to the Remote Network settings will be allowed to relay off your server utilizing port 25.
Now, for servers that will have a lot of relay traffic, there are some more steps you need to do on your Receive Connector. If you see that you have mail flow issues where things periodically work with relaying and sometimes they don’t, it’s recommended to run the following commands on your Relay Connector.
Set-ReceiveConnector -identity “Relay Connector Name” -TarpitInterval 00:00:00
Set-ReceiveConnector -identity “Relay Connector Name” -ConnectionTimeout 00:30:00
Set-ReceiveConnector -identity “Relay Connector Name” -ConnectionInactivityTimeout 00:20:00
Set-ReceiveConnector -identity “Relay Connector Name” -MaxAcknowledgementDelay 00:00:00
Set-ReceiveConnector -identity “Relay Connector Name” -MaxInboundConnection 10000
Set-ReceiveConnector -identity “Relay Connector Name” -MaxInboundConnectionPercentagePerSource 100
Set-ReceiveConnector -identity “Relay Connector Name” -MaxInboundConnectionPerSource unlimited
So in my case, I would run the following command which would allow me to do Get-ReceiveConnector and pipe into Set-ReceiveConnector to make all the modifications in one command:
Get-ReceiveConnector -Identity “Relay Connector Name” | Set-ReceiveConnector -TarpitInterval 00:00:00 -ConnectionTimeout 00:30:00 -ConnectionInactivityTimeout 00:20:00 -MaxAcknowledgementDelay 00:00:00 -MaxInboundConnection 10000 -MaxInboundConnectionPercentagePerSource 100 -MaxInboundConnectionPerSource unlimited
Run the following to view the defaults before running Set-ReceiveConnector.If you are wondering what the default settings were
Test by convene a meeting and you will have
<description>The mail has been sent successfully to, email@example.com</description>
you will receive notification if you configure your email at confmanager site management