How to test the CAS URL configured in Symantec Email Submission Client (SESC)

book

Article ID: 180930

calendar_today

Updated On:

Products

Mail Security for Microsoft Exchange Messaging Gateway

Issue/Introduction

 

Resolution

SESC is configured to access the Exchange Client Access Server (CAS) using an Exchange Web Services (EWS) URL.  This article shows how to test access to this URL outside of SESC.

1. Get the CAS URL configured in SESC.

a. In the SESC console click on Settings|Exchange Servers
b. The value in the textbox CAS URL is used to access EWS.

2. Get the username and password on the service account configured for SESC.

a. In the SESC console click on Settings|Configuration.
b. The value in the Service Settings|User name textbox is the service account used by SESC to access EWS.
c. Obtain the password from other sources.  It is not stored by SESC.


3. Access the URL from a browser on the SESC computer. 

a. Hold the shift key down while right-clicking on the IE icon.
b. Click Run as different user.
c. Enter the username and password of the SESC service account.
d. Enter the CAS URL in the browser.

The results will look like this:

 <?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:s="http://www.w3.org/2001/XMLSchema" targetNamespace="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
- <wsdl:types>
- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:import namespace="http://schemas.microsoft.com/exchange/services/2006/messages" schemaLocation="messages.xsd" />
  </xs:schema>
  </wsdl:types>
+ <wsdl:message name="ConvertIdSoapIn">
  <wsdl:part name="request" element="tns:ConvertId" />
  <wsdl:part name="RequestVersion" element="t:RequestServerVersion" />
  </wsdl:message>
- <wsdl:message name="ConvertIdSoapOut">
  <wsdl:part name="ConvertIdResult" element="tns:ConvertIdResponse" />
  <wsdl:part name="ServerVersion" element="t:ServerVersionInfo" />
  </wsdl:message>
- <wsdl:message name="GetFolderSoapIn">
  <wsdl:part name="request" element="tns:GetFolder" />
  <wsdl:part name="Impersonation" element="t:ExchangeImpersonation" />
  <wsdl:part name="MailboxCulture" element="t:MailboxCulture" />
  <wsdl:part name="RequestVersion" element="t:RequestServerVersion" />
  <wsdl:part name="TimeZoneContext" element="t:TimeZoneContext" />
  </wsdl:message>
- <wsdl:message name="GetFolderSoapOut">
  <wsdl:part name="GetFolderResult" element="tns:GetFolderResponse" />
  <wsdl:part name="ServerVersion" element="t:ServerVersionInfo" />
  </wsdl:message>
- <wsdl:message name="CreateFolderSoapIn">
  <wsdl:part name="request" element="tns:CreateFolder" />
  <wsdl:part name="Impersonation" element="t:ExchangeImpersonation" />
  <wsdl:part name="MailboxCulture" element="t:MailboxCulture" />
  <wsdl:part name="RequestVersion" element="t:RequestServerVersion" />
  <wsdl:part name="TimeZoneContext" element="t:TimeZoneContext" />
  </wsdl:message>

If the response is not received, troubleshoot the cause of the issue outside of the SESC product.

Environment

  • SESC 1.X