SecureEmailGateway Setup Admin Student Guide Final 22 10 13
SecureEmailGateway Setup Admin Student Guide Final 22 10 13
LOGGING IN 7
NAVIGATION 8
MIMECAST STATUS PAGE 9
NOTIFICATION FEED 9
EMAIL QUEUES 10
DIRECTORY CONNECTORS, JOURNAL CONNECTORS AND EXCHANGE SERVICE 10
ACTIVITY OVER 24 HOURS 10
TOTAL EMAIL TRAFFIC 11
REJECTIONS 11
ACCOUNT SUMMARY 11
ACCESSING OTHER DASHBOARDS 11
ACCOUNT SETTINGS 12
DIRECTORY OPTIONS 13
USER ACCESS AND PERMISSIONS 13
SYSTEM NOTIFICATION 14
ACCOUNT CONTACT 14
PASSWORD COMPLEXITY AND EXPIRATION 15
ENHANCED LOGGING 15
LESSON 4: ROLES 18
SECURITY PERMISSIONS 18
ROLE EDITOR 19
ELEVATE BASIC ADMINISTRATOR ROLE 21
CUSTOM ROLES 21
PARTNER (EXTERNAL) ADMINISTRATOR ROLES 22
LESSON 5: CONNECTIVITY 24
INTERNAL DIRECTORIES 31
INTERNAL DOMAINS 32
EXTERNAL DIRECTORIES 37
GROUPS 37
LESSON 7: ATTRIBUTES 41
LESSON 9: REPORTING 45
ACCESS REPORTING 45
ACCOUNT ASSESSMENT REPORT 45
PDF REPORTS 46
CSV DATA 47
OVERVIEW REPORTS 48
CUSTOM REPORT DEFINITIONS 48
Course Objectives
Following the course, you should be able to:
• Navigate and understand the functionality the Administration Console
• Explain the relevancy of the Mimecast Services status page.
• Explain the Account Settings menu item and its subsections
• Create and manage Mimecast administrators
• Understand Connectivity
• Manage your users and groups
• Explain what Attributes and how they are used
• Control user access to End User Applications and the limits within
• Schedule delivery and read the reports Mimecast provides.
• Explain the service monitor features and create alert notifications.
• Locate and act on emails within Mimecast in the Message Center
Scenario
These will highlight real-life use cases that will be covered with students in class.
Those targets without a green background are for students to have as added take-
aways from the session.
Discussion
There may be times in the course where the instructor asks participants to take part
in a discussion about a particular topic (e.g., to discuss something where there may be
more than one solution to a problem).
Warning or Alert
This is meant to provide you with a warning about something.
Logging In
You can login using the Login button on mimecast.com. The options are Access my email - My Apps
- Partner Portal. To open the Administration Console, you will click the My Apps option. Here you
will also see the other applications you have purchased from Mimecast (e.g., Awareness Training,
Case Review, DMARC Analyzer)
Your login credentials will either be a Mimecast cloud account controlled by Mimecast or your
domain directory account password controlled by your organization’s directory.
Navigation
The top bar will be the main means of navigating the Administration Console.
Selecting Administration will reveal the menu of items you have permissions to see. Depending on
your role you may be limited to what you have access to.
The Mimecaster Central Search Bar allows you to search Mimecaster Central, our knowledge base
of page breakdowns and best practices.
This page is separate from Mimecast infrastructure to provide an accurate and independent status.
Use this page when troubleshooting any Mimecast related problems to keep yourself informed
Status
A general status indicator at the top provides immediate overview of Mimecast’s services. Selecting
any of the regions provides the breakdown of the services Mimecast provides.
History
Here you can view any previous incidents as well as the timeline of actions Mimecast has taken to
investigate and resolve the situation.
Notification Feed
The Notification Feed displays notifications sent by Mimecast to you about your account. The
notifications are displayed in a list with the latest at the top. You can filter the notification feed by
either Product which displays only notifications about things like new releases or by Service which
will display only notifications about your Mimecast service.
In situations where we want to draw your
attention to a notification, for example a service
outage, this will be the only filter type available.
Service notifications will have a color-coded title
and icon that have the following statuses.
Use the path next to each item to navigate to the areas identified below and act.
• Attachments Blocked - Monitoring | Attachments
• Rejected Messages - Message Center | Rejected and Deferred Messages
• Bounced Messages - Message Center | Bounced Messages
• Policy Edits - Gateway | Policies
• Held Messages - Message Center | Held Messages
• Attachments Linked - Monitoring | Attachments
Note: You can zoom in on the graph’s data to display the hourly breakdown by dragging over the
date range and releasing the mouse.
Rejections
Displays the top five rejection types for your account, in no specific order, over a 24-hour period.
You can hover over a graph's data point to display the date, time, and the number of rejections at a
given point in time.
Account Summary
This summary provides you with information about your account.
• Your account name
• Mimecast ID
• Your account code
• Your security passphrase (if one has been configured with us)
• Your support code. This must be quoted when calling Mimecast Support to log a call.
• Your account's maximum retention period for messages
1. Click the icon in the top left-hand corner of the Administration Dashboard.
2. Select either the:
• Attachment Protect menu item to display the Targeted Threat Protection - Attachment
Protect dashboard.
• URL Protect menu item to display the Targeted Threat Protection - URL Protect
dashboard.
• Large File Send menu item to display the Large File Send dashboard.
Note: You will only see the dashboards for the services you have purchased.
Account Settings
The Account Settings sub-group provides license and retention details regarding your Mimecast
account. Much of what you see here cannot be edited even as a super administrator.
Account Settings
Account Name The name for your Mimecast account. This is usually your organization's
name.
Mimecast ID The ID of your Mimecast account. This is to be used for interactions with
Mimecast Service Delivery.
Account Code A unique identifier for your Mimecast account to log a support ticket.
Database Code A reference for the database instances of your Mimecast account.
Account Status Enabled by default. This is only disabled if your account has been
terminated.
DNS Authorization Used to verify permissions for sending through the Mimecast SPF IP
Code Addresses. Added during account implementation.
Maximum Retention Added during account implementation, this specifies the maximum
(Days) number of days messages will be retained in the archive. This setting
cannot be increased by administrators, but it can be reduced for retention
of specific messages.
Maximum Retention Specifies that the Maximum Retention (Days) value has been approved by
Validated a user with Super Administrator, Full Administrator, or Partner
Administrator permissions. Occasionally requested to verify account
retention setting is still accurate.
Number of Users The number of users licensed within this Mimecast account.
Directory Options
This grouping deals with either linking or not, the Aliases within your environment.
Automatically Link Uses the mailbox information from Active Directory to link alias addresses
Aliases to primary mailbox addresses in Mimecast. This allows users to login using
their primary address, and access emails for the aliases.
Clear All Aliases Removes the alias links to the primary addresses in Mimecast Directory.
System Notification
Systems notifications control who gets notified by SMS, the postmaster address, and who is alerted
for specific events such as archive searches or when export blocks are finished.
SMS Attribute Specifies the Active Directory or Mimecast attribute that identifies the
mobile phone number of users. When sending an SMS to a user, we use
the number associated with this attribute.
Notification Specifies the email address from which all user notifications are sent. A
Postmaster Address postmaster address is created by default in the internal domains and is
selected by default. The address cannot be deleted but a different email
address can be used by clicking the "Lookup" button.
Privileged Access This email address will be notified when an archive search is performed
Notifications by an administrator.
Enforce Archive When selected, Administrators will be required to provide a reason when
Search Reason searching for emails under Administration | Archive | Archive Search or
Administration | Message Center | Message Tracking. The reason
provided will be reflected within Administration | Archive | Search Logs
under the “Reason” column as well as within the Privileged Access
Notifications email that is sent to the email address listed within the
“Privileged Access Notifications” field under Administration | Account |
Account Settings | System Notification Options.
Send Notification This option enables automatic email notifications when exports are
When Export Block is requested.
Complete
Account Contact
The contact information here provides Mimecast the point of contact to alert regarding Mimecast
services. Keep this information up to date as frequently as possible.
Enhanced Logging
If you are using a SIEM or any other data analytics platform, you can enable additional logging of
email transactions on your account. These logs are available using the SIEM Logs API.
For more information, see the Mimecast Documentation site and SIEM Logs API here.
These additional settings do not impact the current Reporting features available in the
Administration Console and are only available using an API integration.
Common Examples
Some common examples of logs are as follows:
Event Description Information Provided
Logon A user attempted to log on to • User’s login
Authentication the Administration Console, but • Date and time
Failed their authentication failed • IP address
• Application used to access Mimecast
New Policy A policy was created • Administrator
• Date and time
• Policy type
• Full policy details
On the Audit Logs page, select a log to display its information. The log displays details about each
event.
• User: Email address of who triggered the event
• Category: Category of the event that generated the log file (e.g., Policy Logs, Account Logs)
• Type: Displays the type of event (e.g., New Policy, Completed Directory Sync)
Exporting
When exporting, you can select which columns of the log you want
included. Click the Export button in the top left corner to see the panel
shown here.
Default Roles
Protected Roles have a padlock next to them (see items 1-5 below).
1. Super Administrator: Can manage application roles and has full privileges to all account
options, including the content view of all email, delegate mailbox access, and the
assignment of protected permissions (for example, the assignment of content view).
2. Full Administrator: Can manage application roles and has high-level administrator
privileges, including the content view of all messages, delegate mailbox access, message
exports, and the creation and approval of retention adjustments.
3. Partner Administrator: Can manage application roles and has full privileges for Partner
Administrators, including delegate mailbox access, but excludes protected permissions.
4. Discovery Officer: Cannot manage roles but has access to common eDiscovery features
such as archive search with content view, messages exports, and the creation or
approval of retention adjustments.
5. Reviewer: Cannot manage roles but has access to the Case Review application as a
reviewer, where discovery cases can be reviewed for relevance and privilege.
6. Gateway Administrator: Has read access to common gateway functionality (e.g., policy
management, message tracking, service connections, and user settings) and rights to
create other administrator accounts without protected permissions.
7. Basic Administrator: A primary administrator account with rights to create other Basic
Administrator accounts, but with no access to protected permissions. You can do basic
things such as create policies, but you cannot read email for example.
8. Help Desk Administrator: Has access to common help desk tasks (e.g., message tracking,
read-only access to policy management, service connections, and user settings).
Read Administrator Role Permissions for a detailed list of permissions.
Security Permissions
Your account comes with a list of default roles. Each role has a security permission assigned. The
security permissions are as follows:
• Cannot Manage Roles: Access to the Roles tab is disabled.
• Manage Application Roles: The Application Role also allows Administrators the ability to
control the Administration Console menu items that other administrators can access. The
exception is if the application areas are marked as protected with the "Protected Roles"
permission.
• Manage Protected Roles: A Protected Role is one that allows an Administrator to control
the Administration Console menu items that other administrators can access, including
functionality with protected content (e.g., viewing email content, archiving email content,
exporting messages, managing retention and smart tag assignment). Protected roles have a
padlock icon located to the left of the "View Role" button.
Role Editor
Administrator roles are managed using the Role Editor. This allows administrators to:
• Control the users assigned to roles
• Create custom roles in addition to the default roles provided
To access the Role Editor, the administrator must have the correct Security Permissions. Without
these permissions, the Roles tab is not displayed in the Administration Console.
To display the Role Editor:
1. Navigate to Administration | Account | Roles
Within the Role Editor, you will see the following.
• Default Roles: Default roles are listed and indicated by a View Role button next to them.
These can only be viewed and not edited.
• View Role and Edit Role Buttons: In the list of roles you will notice, some have a View Role
button and others have an Edit Role button. Those with the ability to edit are Custom Roles
(names and description displayed in italics. These are a copy of an existing role. The roles
with the View Role button are roles that you cannot edit.
• Right-Click options: Right-clicking on a role will allow you to do things such as Add Users to a
Role, Manage Users for a Role, Copy a Role, and Remove a Role for those Administrators
with the proper permissions.
• Padlock: Roles with a Padlock have access to the Role Editor and have Protected
Permissions, meaning they can modify access to protected application areas (e.g., archive
email content, exporting messages, managing message retention).
• Custom Roles: Custom roles can be changed / deleted and are displayed in italics.
Right-click a role to
display a pop-up
menu
View a Role
To view what permissions a particular role has in detail:
1. Click View Role next to any of the roles
2. Once opened, you will see Properties and Security
Permissions sections.
3. Under Security Permissions you will see what
type of security permissions that role has.
4. Under the Application Permissions area you will
see all the menus in the Administration Console
that role has access to and what type of access
[e.g., Read, Edit, etc.]
Custom Roles
You can only create a role with the permission level up to or lesser than the logged in administrator.
Depending on administrative permissions, you can only create an administrator with the same or
lesser permissions.
When creating a role, we suggest copying a role instead of creating new. The best practice is to
assign permissions less than what the user needs and then add permissions. Another
recommendation is to keep part of the name of the original role as part of the description.
• As a Customer, this is the area where you will see any 3rd party administrators that have
access to your Administration Console.
• As a Managed Service Provider (MSP), this is the area where you will see who you have at
your partner organization set up to manage that customer’s account.
MSPs should be encouraged as a part of best practice to link their External Address to
any Customer they are supporting, ensuring they have both access to the
Administration Console and can Raise Support tickets for that account.
• As a customer, if you are logged on as a Super or Full Administrator, you can see the
Manage External Administrator button.
• When you click the button, you can see a list of the 3rd party administrators that have access
to your Administration Console.
Partner Use
Managed Service Providers (MSPs) are added to this area by the original MSP that Mimecast
connected to this customer account. Mimecast does this so that MSPs can have SSO access to
customers through the Partner Portal. Mimecast will have given them special credentials for
accessing the customer account through the Partner Portal (e.g.,
[email protected])
If you are an MSP, you should know that when you log into the Partner Portal, there is a place where
you can see all the customers whose Administration Console you have access to. It is here where you
will click an Administration Console button next to their company name and be logged in with SSO.
1. To do this in the Administration Console, click the Manage External Administrators button
2. Click the Add External Admin button
3. Enter the External Admin Email Address of the partner you want to manage this account
and use the Select Role drop-down menu to assign them the Partner Administrator role
4. Click Save and Exit.
• If you click on the Partner Admin Role at the home page of the Role Editor, you
will see the external admin you added is located here and listed as a member.
• If you click on any of the users listed as an External Administrator, you will notice
an External Admin Account Code. This is auto generated when you create a new
External Admin and Save.
• If adding multiple email addresses, you will add them one by one here or they
can be added via the MSP Portal. See article below.
More information on delegating access here. See also the Managed Service Providers (MSPs) Portal.
Directory Synchronization allows you to securely automate the management of Mimecast users and
groups using your company directory, whether that be hosted on-premises or in the
cloud. Integrating your company's directory with Mimecast has several benefits, ranging from
feature enablement to reducing the administrative overhead of configuring and maintaining
Mimecast features.
If you want to integrate your Directory, the following options are available to you:
Google Workspace
• Google Directory: To configure a directory synchronization integration for Google
Workspace, you must perform external tasks in the Google API and Administration Console.
See the Configuring Google Workspace for Directory Synchronization page for full details.
Domino Directory
• Domino Directory (LDAP): If your organization uses Domino Directory Mimecast offers a
LDAP Sync feature to automate the management of your users and groups. See the Enable
LDAP Directory Sync for Domino Directory page for full details.
A common reason for manually synchronizing your directory data is when you have just added new
users to your environment, and you wish to sync them with Mimecast before the next
synchronization to ensure appropriate security and policies are applied.
If you need to completely remove a user’s access to Mimecast, the easiest way is to remove their
Active Directory account. Once the next directory synchronization is complete, they will be unable to
access any of our services.
Click the Ellipsis to view, edit, disable or delete an integration. Take note of the
search field in the upper left and the filter options on the right.
See Directory Synchronization for detail and links to configuring for different environments.
Outbound Traffic
Once your Mimecast account has been created, your Technical Point of Contact (TPOC) should log
onto the account to confirm they can access it. If this is successful, your email server can be
configured to route outbound emails through Mimecast.
This requires that your:
• Public IP addresses are added to Mimecast's authorized outbounds. The Connect Team or
Mimecast Support will configure these. If utilizing a Cloud service (e.g., Office 365, GSuite),
the Connect Team or Support can add these.
• Firewall is configured to allow access to Mimecast Data Center IP Ranges for SMTP port 25.
See the Mimecast Data Centers and URLs page for more information. You will need to be
logged into Mimecaster Central to access this page.
Note: This step may not be applicable on Hosted Exchange (HEX) and Microsoft 365
implementations.
• Email server or cloud service is configured to deliver emails to Mimecast
See Connect Process: Setting up Your Outbound Email for further detail.
Authorized Outbounds
The goal is to configure your environment to ensure Mimecast is accepting email on behalf of your
company only over the IP ranges that your Technical Point of Contact tells us are authorized for your
company. If you are on-premises, you need to have a connection created. This is called an
Authorized Outbound.
We add at least one IP address to your authorized outbounds, based on the information you
provided when your Mimecast account was created. These IP addresses are the only ones that
Mimecast will accept outbound email from. You can have multiple authorized outbounds, but
networks cannot be added.
To check your Authorized Outbounds:
1. Navigate to Administration | Gateway | Authorized Outbounds
Note: The information here cannot be changed without the assistance of Mimecast.
On-Premises
If you have on-premises you would see the name of the connection, the IP address range and Mask.
Journaling
The external email communications (inbound or outbound) for a business are automatically Archived
based on an organization’s compliance and global retention values, however some organizations
wish for internal email communication to also be retained. This can be achieved using a Journal
connector.
Inbound Email
Having previously set up your outbound email, messages should be successfully being routing
outbound. You are now ready to set up inbound email to be routed through Mimecast.
External messages destined for your organization must be directed to Mimecast, not left directed to
your email server or hosted email service. Once the messages reach Mimecast, they are processed
by Recipient Validation and other Mimecast security systems. Only once we are satisfied it is safe to
do so, is the message delivered to your organization's infrastructure or hosted service.
The first step you need to take to set up your inbound mail is to create a delivery route. This will
ensure you are connecting properly.
Our delivery routes are configured to deliver all inbound messages to a specified hostname. Take the
steps below to set up Delivery Routing.
A default delivery policy tied to a default definition will have been set during
implementation. For more information, read the Configuring Delivery Routing
Definitions and Policies article.
See the Testing Delivery Routing Connectivity article for full details.
Internal Directories
An internal domain is a domain that your organization has registered with Mimecast to send,
receive, and / or archive email for. This section details the domains you have under your Mimecast
account and are owned by your organization. You should have at least one domain already
populated here from your implementation process.
Note: This isn’t compulsory but is recommended to prevent spoofing messages from the
domain.
• Click Finish.
For further instruction on Adding a Domain through the Administration Console, read Configuring
Internal Domain / Subdomains. Read Connect Application: Validating Your Domains for detailed
instructions on how to do this with the Connect Application.
Recipient Validation
Recipient Validation is the process of checking the recipients(s) of an inbound email to one of your
Internal Domains from an external sender.
For us to accept your inbound email, recipient validation must be configured. To do this, we must
have a complete list of all internal users.
Address Types
When viewing the email addresses associated with one of your internal domains, you will notice to
the left of each email address is an icon indicating how the user was created in the directory. See
explanations for each below.
Actions
New Address Allows you to create an email address.
Purge Selected Addresses Deletes the selected email addresses including linked aliases. This
can be performed by any administrator who has the ability to read
and edit Internal Directories. A warning will be displayed to
confirm the removal of the address and all list entries. Addresses
will not be purged while emails are still being processed for the
address (e.g., if related emails are held). Administrators can
prevent the purge from taking place by removing the address from
the purge list under View | Address Purge list in your domain view
with a right-click Remove Item. This has to be done before
housekeeping runs (which generally occurs overnight).
Import Delegate Mailboxes Allows you to import delegated mailboxes. Note: This button is
only available when logged on as an Administrator with protected
permissions.
Export Data Export a list of email addresses to a .XLS, or CSV file.
View Filters the list of email addresses displayed by:
External Directories
A domain is considered external if it is not one of your Mimecast registered Internal Domains. These
are automatically added to your service as email is sent or received by an internal user.
To list your external domains:
1. Navigate to Administration | Directories | External Directories
2. Select the relevant external domains
3. Select a user to see options for purging the address, creating new or exporting
If your subscription includes Secure Messaging and an external sender needs to reset
their Secure Messaging Portal password, you will come here.
Groups
Groups are internal Mimecast folders containing email addresses and/or email domains. It is
important to use good naming conventions and be organized in the way that your structure your
groups to ensure proper policy application.
There are two types of Groups: Profile and Directory.
• Profile Groups – These groups are local to Mimecast and are manually created and
maintained within the Administration Console by your Administrators.
• Default Groups – Please be aware that some groups are created by default during your
initial implementation and will be attached to “out-of-the-box” policies and services, also
created during your implementation. For example, Administrator Alerts, Blocked Senders
and Permitted Senders are some of the default groups you’ll find under your Profile groups.
• Directory Groups – These groups are visible in
Mimecast after syncing with your organization’s
directory environment (e.g., Active Directory,
Azure, etc.) These groups are read-only and can
only be added, removed, renamed or have their
contents altered by first making those changes in
your directory service and then running a directory
synchronization (Administration | Services |
Directory Synchronization.) To view the Directory
groups that have been synchronized with
Mimecast, navigate to Administration | Directories | Directory Groups, while also being
aware of any folder with a + sign next to it, which will allow you to delve deeper into the
synchronized directory structure.
Groups are used primarily to be referenced in policies or end user applications to control mail flow
for specific user groups. This has the following benefits:
• Mail routing can be specified for users in different regional locations with different mail
servers.
Creating a Group
All groups are displayed in a hierarchy, linked to a root group. This allows changes made to one
group, to also apply to all other sub-groups in that group.
Note: You cannot create a group inside the Root folder. A sub-folder must be created inside it to
enable a group to be created.
1. Navigate to Administration | Directories | Profile Groups
2. Either:
• Select the Folder into which the group is to be created.
• Create a Sub-Folder as follows:
a) Click on the + Icon in the bottom right-hand corner of the folder where you want the
group created. A folder called "New Folder" is created in the group's hierarchy in a
collapsed state.
b) Rename the group:
o Expand the Group's Hierarchy
o Click on the "New Folder" Group
o Type the Group Name in the Edit Group field at the top of the hierarchy
o Press the Enter key
3. See the "Adding Group Entities" section below for details of how to add email addresses or
domains to the group.
Adding Group Entities
You can add email addresses or domain names to a group using one of the following methods:
• Add Email Addresses
• Add Email Domains
• Group List Imports (email addresses only)
Wildcard characters are not supported for groups. See the Using Wildcards in Policies
page for full details.
After the group is made you will see a number next to the folder in the hierarchy. This
is an indicator of how many entries are in that group.
WARNING: Prior to deleting a group’s entities, you should consider using the Export
Data option, as unlinking cannot be undone, and the export would be the only record
of the entities in this group.
Deleting a Group
When deleting a group, the following must be considered:
• A default group located in the Root folder cannot be deleted.
• Only empty groups or sub-groups can be deleted. If a group contains an empty sub-group,
this must be deleted before the other group or sub-group can be deleted.
• Only groups or sub-groups not used in any policy can be deleted.
• The number displayed in brackets to the right of a folder shows how many email addresses
or domain names are in the group.
To delete a group:
1. Navigate to Administration | Directories | Profile Groups
2. Select the Group to be deleted
3. Click on the Red Cross Icon to the left of the folder
Moving a Group
You can either move the group or all its entries, as well as copy any entry into another group of your
choosing. In any group or subgroup, you can add domains or email addresses.
Note: A default profile group located in the Root folder cannot be moved.
To move a group to a new location in the hierarchy:
1. Navigate to Administration | Directories | Profile Groups
2. Select the Group to be moved in the hierarchy.
3. Click on the Move Group button.
4. Select the Group in the hierarchy into which the group being moved is to be placed. The
group is moved to the chosen location.
Group
Each definition is specific to a group of users, including
any sub-groups. This requires a group to be created that
can consist of individual users or entire domains.
Propagation
It may take up to 15 minutes for application settings definition to propagate. For example, if you
made a change relating to Mimecast for Outlook, it will take about 15 minutes to apply. Users will
have to exit Outlook and go back in to see the change.
Registered Applications
For troubleshooting purposes, the Registered Applications view displays filterable information
related to active users and applications.
1. Navigate to Administration | Services | Applications and select the Registered Applications
button.
Lesson 9: Reporting
Mimecast Reporting provides Administrators with a view of what is happening in their email
environment. This includes detailed statistics on:
• How many messages are being sent or rejected
• The data volumes being transmitted
• These reports can assist with infrastructure planning through data load analysis, show spam,
virus trends, and supply usage reports on a per user basis
• Administrators can also schedule reports to be emailed out or download the reports from
the Administration Console. These reports can then be analyzed, and any necessary changes
made.
Access Reporting
To access the reporting functionality, navigate to Administration | Reporting:
The following menu items are displayed:
• Account Assessment: A report created for your account by Mimecast at the end of each
reporting period. The report is available for one week from Monday to Sunday, and over
each calendar month. See the Account Assessment Report Overview page for more details.
• PDF Reports: Schedule weekly or monthly reports to be emailed to specific recipients or
made available for download. See the Reporting: PDF Reports page for more details.
• CSV Data: Download and view the daily CSV data for certain account logs, including
rejections. See the Reporting: CSV Data page for more details.
• Overview: Provides graphs that show email volumes, bandwidth, and statistics for your
account. This includes outbound, inbound, and internal emails, and rejected email traffic.
See the Reporting Overview page for more details.
Scheduling a Report
If you wish certain individuals to have
weekly or monthly reports delivered to
their mailbox, follow the steps below.
1. Navigate to Administration |
Reporting | Account Assessment
2. Select the Weekly Report or
Monthly Report heading
3. Expand the Email Schedule
Section: Choose Send Report.
When you select Send Report,
the ‘Report Recipients’ section
displays (send up to 5 recipients).
4. Use the Lookup buttons to look up the recipients you wish to receive the weekly report
5. Click Save.
PDF Reports
The PDF Reports function allows you to schedule reports to be run on either a weekly or monthly
schedule and save the output to a PDF file. You can also download reports directly.
Administrators with read only access to the Reporting module will not have access to edit Reporting
Schedules.
You can select:
• Whether the report should be emailed or saved locally on Mimecast.
• Whether you want a PDF of a standard report or a custom report of your choice of data
• Which graphs should be saved / sent
• How often these graphs should be run (weekly or monthly).
• The email addresses where the PDFs should be sent (up to 5 individuals)
Administrators with read only access to the Reporting module will not have access to
edit Reporting Schedules.
The PDF and Overview reports are focused on email traffic data, while the Account
Assessment provides a full report of every facet of your Mimecast services.
CSV Data
The CSV reports consist of daily rejection data. Administrators can download the report data in a
comma separated (.CSV) format. This has many uses, including sharing it with colleagues who do not
have access to the Mimecast Administration Console.
For data that is not retained on Mimecast eternally (e.g., Rejection Viewer logs) Administrators can
access this data, even after it is no longer visible in the Administration Console.
Overview Reports
These reports provide a graphical representation of email volumes and flows. These default reports
give Administrators a quick view of their environment, showing different aspects of their email data
volumes and bandwidth usage. Administrators can also determine which users in the company are
sending large volumes of emails and analyze what is causing inbound emails to be rejected.
To access, navigate to Administration | Reporting | Overview:
Reporting Overview shows groups of graphs as follows:
• Summary Graphs - display the volumes of email split into Outbound, Inbound, and Internal
messages, as well as Rejected volumes
• Outbound Email - displays email communication from internal users to external users and
domains
• Inbound Email - displays email communication from external users to internal users and
domains
• Internal Email - displays email communication between internal users
• Custom Reports - displays any Custom Report Definitions that have been configured
View the Reporting Definitions page for a detailed breakdown of what each of the
different graph data types represent. Reporting data is available for a year, although
scheduled reports can be stored in PDF for a longer period.
Functionality
The Service Monitor displays information in one of the
following tabs:
• Dashboard: The dashboard displays a graphical representation of your outbound delivery,
inbound delivery, and journaling queues. Access to the status of your Journaling and Active
Directory (AD) services is also available.
• Alerts: Enables you to set the thresholds for each alert type.
• Subscribers: Enables you to set up users to receive alert messages for Mimecast services.
• Notifications: Displays a list of any recent alerts issued to subscribers.
Dashboard
Queue and Service Meters
The meters on the dashboard display the number of messages in each respective queue (outbound,
inbound, journal) as well as the recommended threshold for the queue at the max level of the
meter.
The service detail display differs depending on the service type. The status of each service can be
viewed as follows:
• Indicates there is an issue with the service. See the "Last Error" message for further
information.
Service History
From the Services page, you can access a view of all the configured service's history. This allows you
to analyze the service to determine if there are any ongoing issues. The history is displayed in a
graphical format in the following time frames:
• 15 minutes with history up to 2 days
• Hourly with history up to 7 days
• Daily with history up to 60 days
• Graph: Displays an interactive graph of the average number of "OK" service connections
versus the average number of "Error" connections, in selected time intervals. The "15
Minute" tab displays by default. Optionally click on the "Hourly" or "Daily" tab to update the
graph's data on display.
Note: Hover your mouse over the graph to display the number of "OK" or "Error" service statuses
during the selected interval.
• Date / Time: Displays the date and time when the data was collected.
• Status: Displays an icon of the service's status when the data was collected. This can be
either:
• The service's status was OK at the time of the data entry.
• The service's status has an error at the time of entry, and an alert has been sent to
subscribers (if configured).
• Show / Entries: Click on the drop-down arrow and select to display 10, 25, 50, or 100 entries
per page. This will also update the graph.
• Time Zone: Select a specific time zone to apply to the data from the drop-down menu.
• Next / Previous: Use the buttons to switch between the pages displayed. This will also
update the queues graphical display.
Queues
1. Escalation Level – Specifies the number of sequential alerts that must be sent to subscribers
before the escalation point is reached. Once reached, subscribers configured to receive
escalation notifications receive notifications in addition to regular subscribers. This is
defaulted to 5.
2. Alert Level – How many problems (service disruptions/items in queue) have to occur before
an alert is sent. Once the number of items in a queue goes beyond this threshold an alert is
generated. A minimum value of 50 should be specified. If a value less than 50 is specified, it
is ignored and a value of 50 is used instead.
3. Recommended Threshold - This is an auto generated threshold based on the recent history
of your account. It is intended as a starting point, based on the account's profile.
4. Acknowledge the alerts – Once this option is checked, no further notifications for this alert
are sent until another threshold is reached. Once the queue is no longer in alert this flag is
re-set.
Journal Services
1. Escalation Level - How many alerts are reached before escalation notifications are sent out.
This is defaulted to 5.
1. Escalation Level - How many alerts are reached before escalation notifications are sent out.
This is defaulted to 5.
2. Acknowledge - Once this option is checked, no further notifications for this alert are sent
until another threshold is reached. Once the queue is no longer in alert this flag is re-set.
3. Enabled – enable or disable this
4. Click Save AD Services
Refer to the Service Monitor: Managing Alert Notifications article for more detail.
Subscribers
The Subscribers page will allow you to set up who will
receive notifications on alerts and escalations via
email or SMS. These users are typically administrators responsible for the efficient running of the
Mimecast account and internal email systems.
Click Subscribers in the upper right corner to get to the Subscribers page.
The Subscribers page will allow you to set up who will receive notifications on alerts and escalations.
1. Enter in a user’s credentials
Note: The password is a local password which should be used to login to Service Monitor if
your Directory server is unavailable. The password will only be accepted when used with the
configured email address.
Alert notifications can be sent out as emails, SMS messages, or both. The distribution schedule for
delivery of email and SMS alerts differs.
Note: All specific service details regarding the IP address and email address, are automatically
populated based on your journal / directory connection configuration in the Administration Console.
• Email alerts are sent to subscribers every 15 minutes when a queue / service reaches its
threshold
• One SMS message per alert type is sent to each subscriber when a queue / service reaches
its threshold. When the alert reaches the escalation point, all subscribers to that alert type
get one further SMS message.
Note: It is highly recommended to create two or more subscribers.
Notifications
Notifications are a record of all alerts sent out up to the past 90 days.
1. Click Notifications in the upper right corner to
get to the Notifications page.
You can display alert notifications for up to three months in the past in the Service Monitor. These
can be used to determine:
• What triggered an alert
• Who the alert was sent to
• The date and time the alert was sent
You can filter the alert notifications by selecting / deselecting:
• Queues and / or services
Message Tracking
Message tracking allows you to search across all email queues to find specific messages that may
have been delayed in delivery (inbound or outbound) or that were never delivered.
You can search by any of the following:
• Data or Message ID
• Partial email address or domain name (minimum of 3 characters)
Note: Wildcards are not supported and may return unpredictable results
Using Search by Data allows you to search using content that could be in the To and From fields, the
subject, or IP address.
Search by Data
1. Enter a From Address: This can be an email address or domain
2. Enter a To Address: This can be email address or domain
3. Enter Date Range: Drop-down will give you between 24 hours and 30 days
Note: After 30 days, you need to search the archive
4. Show More will allow you to do a search via subject or IP address to help you narrow down
the search
Search by ID
This allows you to search for a Message ID so you find the specific message in case the same sender
has sent 100 messages for example. The Message ID is a unique ID for that message and can be
found in the header.
The actions you are able to perform have to do with the Queue that the message is
sitting in.
Accepted Messages
The Accepted messages queue is where you would go to troubleshoot mail flow after configuration.
These messages can be found by navigating to Administration | Message Center | Accepted
Messages.
Administrators come here to review recently sent and received messages that are awaiting indexing.
Once indexing is complete, messages are moved to the Mimecast Archive.
Before being archived, administrators can access the metadata and SMTP transmission information,
which is useful for troubleshooting message delivery.
Click here for more information on Accepted Messages.
Held Messages
Messages are held when policies are triggered: such as content examination, spam scanning,
attachment management, and attachment protection. Messages are held for 14 days until moving
to the archive, unless it has been released, permitted, or blocked.
These messages can be found by navigating to Administration | Message Center | Held Messages.
On the page, you will see three tabs: Overview, Held Queue, and Release Logs.
Overview Tab
The Overview tab provides an overview of all held messages split into the following sections:
• Held Reason: Lists all held reasons and the number of messages held for each one.
Note: Use the Search box to filter the list by entering a held reason.
• Top Ten Held Reasons: Lists the top ten reasons why a message is held.
• Messages Held by Group: Displays a graphical pie chart of the held messages.
Bounced messages (both inbound and outbound) are still available in the archive, as
the message was originally accepted by Mimecast before being bounced.
Message Details
To troubleshoot failed delivery, you can view information about the message through the details
panel. Here you will see the Bounce Properties and much more.
Message Delivery
The Message Delivery page shows you the delivery and bulk queues of messages that passed the
processing queue. The Bulk Queue tab includes messages that are subject to the bulk sender's
policy. These messages can be found by navigating to Administration | Message Center | Message
Delivery.
We attempt to deliver messages to the recipient for up to four days (96 hours) or 30 retry attempts
by default, with the Delivery Queue displaying all inbound and outbound messages waiting to be
delivered. The time between the retry attempts increase incrementally. The longer the message is in
the queue, the longer the interval between retries.
The delivery queue is used to troubleshoot or investigate delayed email delivery. You can also:
• Force an immediate retry
• Reject the message for delivery
• Perform an early (hard) bounce
Processing Queue
Before Mimecast can deliver emails, certain checks are performed, and the applicable policies need
to be applied. While these activities are being performed, emails are temporarily queued in the
Processing Queue. Once completed, emails are moved into the Delivery Queue awaiting delivery.