This month, as well as the usual bundle of bug fixes and minor improvements, we’ve made it possible to include shared mailboxes in “all mailbox” Email Scout Reports (ESRs) and made the timestamp filter in ESRs far less confusing.

Optionally Create Email Scout Reports for Shared Mailboxes

In the past, when you chose “all mailboxes” when creating an Email Scout Report, this would not include any mailboxes marked as shared, and you would need to manually create these using the log search page. In this version, anew option is available “Include shared mailboxes” in case you do want to also generate ESRs for those mailboxes. This is visible when the “All mailboxes” checkbox is checked. Note that ESRs will still not be created for distribution lists.

The new option “Include shared mailboxes” needs to be checked to generate ESRs for shared mailboxes using automatic ESRs.

For now, this is only available for new created auto-ESR. The possibility to include the shared mailboxes for the exiting auto-ESR (Edit mode) will be added with future improvements.

Clearer ‘timestamp’ filters for Email Scout Reports

The ‘timestamp’ filter in Email Scout Reports has long confused users. Different methods of creating Email Scout Reports, in different versions, have set differing values for the ‘timestamp’ filter, and using the “Execute this search” action on an ESR would rarely show the actual saved filter.

In this release, we have tidied this up so that it’s always clear what ‘timestamp’ filter ESRs are using. A bit less magic in exchange for a lot more clarity. This involves a set of changes:

• A new timestamp filter is available on the log search pages, “since last run”.
• When you use the “Email this search” button to create a scheduled ESR (for one recipient or for all) it will be saved with exactly the timestamp filters that are displayed on the page.
• The “execute this search” action for ESR will run the search with exactly the saved filters.

The new timestamp filter, “since last run”, can be found alongside the existing “after”, “between”, “before”, and other options:

When “since last run” is first used (each session), the filter is ignored, and you’ll see “This rule will have no effect because no last run value has been set yet.”

Any other time the search is run, the result contains only matches after the last time you ran the search. You’ll also see this in the message on the page, which changes to: “This will only show entries matching the query rules after the last similar run at” and the time at which the search was run.

When an Email Scout Report has the “since last run” filter, if it is a one-off report, or the first delivery of a scheduled report, it will have no effect. Every subsequent ESR will include results since the last scheduled ESR time. For example, if you have a daily 9 a.m. report Monday-Friday, on Wednesday it will limit results to those since Tuesday 9 a.m., and on Monday it will limit results to those since Friday 9 a.m..

Group table actions and filters

It is easier now to find the action you need on log search pages. Rather than just have a single list of actions, we now group the actions logically, so that the menu is more intuitive and it’s easier to find the needed information. This only applies when taking action on a single message.

Changelog 

Since the last major release, we’ve also fixed the following issues: 

• MMA-7492: Fixed training reports (triggered when users train a message) not being sent to Splunk.
• MMA-7418. Fix an issue with the bandwidth overview not displaying after adding new domains.
• MMA-7436. Fix an issue with accessing logging and quarantine data for newly added domains.

We’ve also made the following improvements: 

• MMA-7428: Make Microsoft 365 SSO configuration easier as the provider URL is prefilled with the tenant during this process.
• MMA-6421: Decrease downtime during the weekly maintenance period.
• MMA-6584: Show the hostname that was used for access in the new log-in notification.