Hello Jay, when you use the browser it's making a GET request to the /EWS/Exchange.asmx URL and Exchange just returns the WSDL service in that scenario.  SmarterMail doesn't return anything for the GET request.  When a client uses EWS it makes POST requests.  So you are correct that SmarterMail behaves differently in this scenario.  You can use something like Postman if you want to send off POST requests but you would have to make numerous other changes, like making a text/xml format request, properly formatted XML requests, etc.  The best way to test would be to just use a client like eM Client and see if it connects and returns messages.

Got it.  Thanks for the explanation and confirmation.

Any chance Smartermail could return the WSDL response in a future build, so there is no misunderstanding in cases like this?