This article describes how the Engage platform is integrated with the Mimecast Report Buttons and is intended for Administrators.
Introduction
This integration works with and without Mimecast Email Incident Response (MEIR). See Mimecast Email Incident Response - Reporting Messages.
The Mimecast Report Buttons with the built-in Engage Integration are:
- Mimecast Essentials For Outlook Report Button.
- Mimecast for Outlook Report Message Button.
- Mimecast for Mobile Report Message Button.
- Mimecast for Mac Report Message Button.
- Mimecast Personal Portal Report Message Button.
For more information on Outlook End User Reporting, see Mimecast for Outlook - Blocking Senders and Mimecast Essentials For Outlook - Overview.
Reporting a message flow
When a Engage phishing simulation is reported, the following actions are triggered:
| End User Application | Reported Email Real or AT Simulation | User Blocked | Moved To |
| Mimecast Essentials for Outlook | Real | Yes | Junk |
| Mimecast Essentials for Outlook | Simulated | No | Deleted Items |
| Other End User Applications | Real | Yes | Junk |
| Other End User Applications | Simulated | No | Junk |
The user notification after reporting differs, depending on whether the message was real or Engage simulated:
- If the reported email is a Engage simulated phishing email, the Reported status is accessible via the Phishing Training Dashboard. The reported message is not sent to Mimecast.
We track that the message has been reported, if this was done via Native Reporting (but not if it was reported by any Mimecast End User Applications). - If the reported email is not an Engage simulated email, then the regular MEIR or non-MEIR workflows will be applied.
For more reports relating to Engage, see Reporting & Insights.
Comments
Please sign in to leave a comment.