Error Code 1: authentication / initialization failure

The Outlook plugin first checks if the user is authenticated, and if so, it uses the current session's access token, which gives the application permission to talk to the Graph API.

• If the user is not authenticated, they are prompted to sign in, at which point a new access token will be generated.
• Error Code 1 relates to the button being unable to access the Microsoft Graph API. The app uses the Graph API to get permissions to interact with the current user's mailbox.
• If a user gets Error Code 1, this means the application cannot communicate with https://graph.microsoft.com

Solution

Customer to add the following address to their allowlisting: https://graph.microsoft.com

If adding https://graph.microsoft.com does not resolve the issue, then the following additional URLs - used by the Outlook Web Add-in - may need whitelisting depending on the customer's restrictions:

• https://login.microsoftonline.com
• https://cdnmetacompliancelive.metacompliance.com
• https://sendgrid-live.metacompliance.com 
  
  Additional information
  Browser opening a new window outside of the add-in pane:
  https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/manifests#app-domains 

Other likely causes: 

• MSAL library failed to load; the configured redirectUri / clientId does not match the Azure AD app registration
• the host does not support nested app auth
• browser blocked the auth popup; network failure reaching login.microsoftonline.com.

Error Code 2: Company settings retrieval rejected

This likely refers to the phish plugin not being able to find any company settings stored in our database, in that case this we’ll not be able to successfully complete the phish report.

Solution:

Reach out to MetaCompliance support HERE and we can ensure the company settings are correctly added.

Error Code 3: API rejection

The MetaCompliance API rejected the request or a generic server error while determining whether the email is a MetaPhish simulation. This is a server-returned error.

Solution:

Test the report button again, it could very likely be a temporary issue. Also test this off your main network, e.g. a mobile hotspot if possible.

Error Code 4: Network connectivity loss

The causes of this are;  

• Network connectivity loss
• DNS/TLS failure
• CORS rejection
• SendGrid API endpoint unreachable.

This is a transport error.

Solution:

This will need to be tested again, on a different network if possible and with a tool like Fiddler Trace potentially to see if there’s any apparent blockers.

Error Code 5: Delete message failed

After a successful report and with the setting DeleteMessages enabled, the Graph delete of the original message returns the following  error; failed.Insufficient Mail.ReadWrite permission. It can also be due to the item already being moved/deleted, token expiry, throttling, or a transient Graph error.

Solution:

You will need to check the permissions granted, if there’s any restrictions on users being able to delete messages then this error will likely appear. If there’s any delay with that being actions (e.g. slowness in Outlook) then this error could occur too if trying to report an already reported email. But it’s prudent to look at permissions first.

Error Code 6: move-to-junk failed

This error behaves the same as Error Code 5, only this is when DeleteMessages is disabled and we’re trying to move the emails to the junk folder. Could be to do with permission, missing item, token/throttling, or a transient Graph failure on the move operation.

Solution:

Same as above, this will need an examinations of permissions granted for the user trying to move the email to their junk folder.

Error Code 7: Forward (report) failed

Forwarding the phish to the configured report mailbox failed with an error other than ErrorSendAsDenied. Can be caused by Token expiry, throttling, transient Graph error, or a malformed recipient list.

Solutions:

This could be caused by the ForwardMailBox being undeliverable, either by an incorrectly added email address or some blocker preventing the email from going through. We have also seen this happen when the ForwardMailBox is full. This can likely be seen in the network logs when reporting the phish.

Error Code 8: API rejection miscellaneous

This refers to the API rejecting the report, can be due to auth/token invalid, validation or a server error.

Solution:

This will likely need MetaCompliance support to investigate to find the fault, as this could be a blocker at our side or an issue with our API.

Error Code 9: Request failure

This error is is related to error code 8. Can be Network/DNS/TLS/CORS failure or the API endpoint unreachable.

Solution:

This will likely need MetaCompliance support to investigate to find the fault, as this could be a blocker at our side or an issue with our API.

Error Code 10: Could not read internet message headers

When forwardfullreport is enabled in settings, fetching the raw internet message headers from Graph failed. The likely causes are token expiry/insufficient scope, throttling, transient Graph error, or the item no longer being available available.

Solution:

Will likely need a network trace ran while reporting to see what blockers are effecting our ability to read the internet message headers.

Error Code 11: could not download the original MIME

When forwarding the email as an attachment (or Windows Defender submission is enabled), downloading the raw MIME ($value) of the original message failed.

Solution:

This can often be a Token/permission issue, we have often see this too be due to a very large message trying to be reported. It may have to be tested to see if the issue is limited to certain emails.

Error Code 12: could not create the report draft

Creating the new draft report email (that will carry the original as an attachment) failed.

Solution:

Similar to previous issues,  this can be Token/permission issue, throttling, or transient Graph error.

Error Code 13: could not attach the original email

Attaching the base64-encoded .eml of the original message to the report draft failed.

Solution:

We’ve often seen this be due to the attachment being too large (Graph single-request attachment limits), this will need to be tested with other emails to narrow down the exact cause as it can also happen due to throttling or other transient issues.

Error Code 14: could not send the report email

This is often related to the Mail.Send permission being missing. On a shared mailbox this can also reflect send-permission problems.

Solution:

The permissions of the shared mailbox will need to be examined in order to ensure the required permissions are in place.

Error Code 15: exception reading shared mailbox properties

Host/Outlook version does not support the shared-properties API in this context, or the API was called against an item that is not actually in a shared mailbox.

Solution:

Sharedmailbox permissions need to be examined, this could also be a performance or Outlook caching issue where we’re not detecting that the email is in a shared mailbox and the report then fails.

Error Code 16: no write permission on the shared mailbox

The user has read-only/limited delegate access to the shared mailbox and therefore cannot perform the move/delete/report actions.

Solution:

The mailbox owner must grant Write (and typically Send As) delegate permissions.

Error Code 17: no Outlook settings for this company/user

The user’s email domain has not been approved to use the phish reporter by MetaCompliance Support, all users with this domain will likely receive Error Code 17 until corrected.

Solution:

Reach out to MetaCompliance Support with a full list of email domains used by your users, they can then add them quickly and immediately correct this issue.

Error Code 18: settings request failed

This error can happen for multiple reasons; Auth/token invalid, API server error, or network failure. This is a transport-level failure so there’s been some block in reaching the correct settings in our Database.

Solution: 

A network trace will need to be run while reporting to help us identify where the blocker is.

Error Code 19: "Send As" denied on the shared mailbox

Forwarding the report from a shared mailbox failed specifically because the user lacks the Send As permission. The user has Write delegate access (so they do not receive Error Code 16) but not Send As.

Solution:

The mailbox owner/admin must grant Send As permissions.