Error codes for Phishing Report Button

Read this article in: English, Deutsch, Dutch, French

The Phishing Report Button displays different codes in case of an error to indicate the technical cause. The following list provides an overview of the different codes and their meaning:

Phishing Report Button error codes:

Code	Description	Possible solutions
1	Cannot retrieve License	File / URL deployment Make sure you received the correct Manifest XML / URL from SoSafe AppSource Your account is not connected to an Azure AD tenant
2	The SoSafe Phishing-Reporting is not activated for your organization.	Make sure you have an active SoSafe license.
3	Settings could not be retrieved from the SoSafe API.	Make sure the client can access all required SoSafe resources: https://reporter.sosafe.de https://api.sosafe.de
4	Exchange access token could not be retrieved.	This token is necessary for accessing the user's mailbox. Make sure the client has access to the required Microsoft Exchange Services: EWS or REST API is not activated on the Exchange server Outlook cannot determine the URL of the Exchange server Expired Exchange certificates
5	This item type is not supported. Only email messages are supported.	Check if you are trying to report something other than an email: e.g. Calendar entry or SMTP Non Delivery Notification ("bounce message")
6	Loading email failed.	Make sure the client has access to the required Microsoft Exchange Services: GraphAPI, EWS or REST API is not activated on the Exchange server Outlook cannot determine the URL of the Exchange server Expired Exchange certificates Make sure the following URLs are accessible bidirectional https://api.sosafe.de/ https://appsforoffice.microsoft.com/ https://ajax.aspnetcdn.com/ https://reporter.sosafe.de/ REST API (Drepcated): Make sure your Outlook client supports the REST API. See the compatibility matrix.
7	Reporting to SoSafe services failed.	Make sure the client can access all required SoSafe resources: https://reporter.sosafe.de https://api.sosafe.de
8	Reporting to SoSafe services failed.	Make sure the client can access all required SoSafe resources: https://reporter.sosafe.de https://api.sosafe.de
9	Reporting to SoSafe services failed.	Make sure the client can access all required SoSafe resources: https://reporter.sosafe.de https://api.sosafe.de
10	Sending the email failed.	Recipient addresses are not available Permissions are missing REST API: Make sure your Outlook client supports the REST API. See the compatibility matrix.
11	Deleting / Moving email failed.	Permissions are missing The target folder is not available
12	Deleting / Moving email failed.	Permissions are missing The target folder is not available