Relevant Products: Signature Manager Exchange Edition | Signature Manager Outlook Edition
WARNING! The following product was discontinued on 1st April 2021 and is no longer available for purchase or support:
- Mail Disclaimers
For more information, please see the Discontinued Questions and Answers page.
WARNING! The following products were discontinued on 30 September 2022:
- Exclaimer Signature Manager Outlook Edition
- Exclaimer Signature Manager Exchange Edition
The end of Support for these products is 30th September 2024.
For more information, please see the Discontinued Questions and Answers page.
Scenario
You have an Exclaimer on-premises product that utilizes Exchange Web Services (EWS) that is installed on the same Exchange server that it connects to using EWS.
You notice that these connections are failing and an EWS error stating 401 unauthorized is logged - despite the service account being used and having the appropriate permissions in the Exchange environment.
Status: Warning
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (401) Unauthorized. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
Reason
This error is caused by Microsoft's workaround for CVE-2018-8581 which is automatically applied as part of security or Exchange Cumulative Updates (CU); for more information, see CVE 2018 8581.
Resolution
You can resolve this issue in either one of the following ways:
- Use the following manually specified Exchange URL: https://localhost/ews/exchange.asmx
Note: For some versions of Exchange, you will need to use port 444 instead of port 443.
To confirm the port being used - examine the bindings in the Internet Information Services (IIS).
OR
- Configure a BackConnectionHostname.
Follow the steps outlined in Method 1 (recommended): Create the Local Security Authority host names that can be referenced in an NTLM authentication request.
Note: The DisableStrictNameChecking registry setting mentioned in the above Microsoft article is not required.