Posts tagged Recipient Validation
I’ve been deploying Exchange 2010 more and more now. Most of them are single server installations or at the very least they only have one server available for exchange. Below are a few tricks I’ve found that help in the deployment.
To reduce the load on the server and the amount of Non-Delivery Reports sent by the server (which can get you on blacklists) I strongly recommend that you use Recipient Validation. This will allow Exchange 2010 to reject unknown recipients immediately rather than let your server accept the message and attempt to deliver it and fail. Also, while Microsoft has documentation on how to do this, it is all written with the assumption that you’re using/have an Edge Transport Server. This is how to do it on a Hub Transport server.
First open the Exchange Management Shell
Change the directory to:
C:\Program Files\Microsoft\Exchange Server\V14\Scripts
Run the following command:
Restart the Exchange Transport service.
After it restarts you need to tell the service what your internal SMTP servers are, even if you only have one you have to specify it.
Set-TransportConfig -InternalSMTPServers 192.168.254.200
Where 192.168.254.200 is the internal IP of your server.
Last but not least you want to enable Recipient Validation you can do that with this command:
Set-RecipientFilterConfig -RecipientValidationEnabled $true
You’re all set! You can test it out with nwtools.com or some other tool of your choosing.
I find that this gets skipped a lot. By default your server is probably not reporting your external mail server’s address. This should be the same address that the reverse DNS is reporting. To change this you must do it in the shell. It can be achieved with this command:
Set-ReceiveConnector "From the Internet" -Banner "220 mail.contoso.com"
You must include 220, however, you can change everything else after.
Hope this helps!