Reverse DNS does not match SMTP Banner

I am having issues with some company's not being able to send emails to staff on our exchange server because it fails a Ehlo test. the users sending the email get the following message.

<User@renfrewhosp.com>:
host exchange.renfrewhosp.com[142.46.224.120] said:
554 5.7.1 This message has been blocked because the HELO/EHLO
domain is invalid. (in reply to MAIL FROM command)  now our Exchange servers domain is not the same as our email address domain. I have set the FQDN on the send connector to renfrewhosp.com but when I go to change the receive connector I get the following error

April 20th, 2015 11:23am

I understand that your Exchange is directly connected to Internet? You'll need to create a specific receive connector for Internet mailflow, and don't use Exchange Servers auth mecanism on it.

You'll need to scope the remoteIpRange of this connector so you'll have a unique binding on the IP : Port : RemoteIPRange. This can be done by NATing the incoming connection with your router IP, then creating a new receive connector for Internet.

I don't recommand messing with the default Exchange 2013 receive connectors, what work today may be messy tomorrow.

Free Windows Admin Tool Kit Click here and download it now
April 20th, 2015 11:30am

OK.  well that sounds good but this is my first time working with exchange so any guidance on how to do this?
April 20th, 2015 11:42am

You could use this code, be aware that if you use some antispam on your Exchange server, some features won't work anymore (reverse DNS, SPF and like) :

New-ReceiveConnector -Bindings 0.0.0.0:25 -RemoteIPRanges 'your firewall NATed IP' -Internet -Name "From Internet"  -AuthMechanism Tls -Fqdn 'your public FQDN' -PermissionGroups AnonymousUsers -TransportRole FrontendTransport
A simplier way would be to uncheck all "exchange server" stuff on the "Default Frontend" receive connector on both Auth and Permissions group, but usually I don't like to mess with default connector. It will work if you don't have any Exchange 2007 or 2010 server in your organisation.


Free Windows Admin Tool Kit Click here and download it now
April 20th, 2015 11:55am

we only have Exchange 2013 in our organisation but if I uncheck all the Exchange server stuff does that not make it less secure?
April 20th, 2015 12:09pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
error

If the AuthMechanism attribute on a Receive connector contains the value ExchangeServer, you must set the FQDN parameter on the Receive connector to one of the following values: the FQDN of the transport server "EXCH01.rvh-win2k3.com", the NetBIOS name of the transport server "EXCH01", or $null.

any help would be appreciated. I'm running exchange 2013 cu6 on server 2012.