Message Tracking - Time Zone - Apr 2022

Service Update

Availability	Week of April 12th, 2022
Product(s)	Email Security Cloud Gateway
Who's affected	All users

Overview

Mimecast is pleased to announce a fix to a bug where user searches within Message Tracking could return incorrect results if the user’s Time Zone offset was different to that of the Mimecast data center being queried.

Following investigation, we found that if a user was in a different Time Zone (TZ) to the data center they were querying, their search period would be incorrectly interpreted for archived messages within a Message Tracking search.

This caused the search period to be shifted either too early (if the user was in a TZ to the west of the grid) or too late (if the user was in a TZ to the east of the Data Center). Consequently, legitimate results could be omitted in some circumstances.

This issue only affected messages with a status of Archived. Active content was not impacted by this bug.

What's changing

Message Tracking will continue to offer the same search periods as before (see below):

Each of these options, including custom range will construct a query using the user’s local time zone offset, as today.

The query will now be translated with the appropriate offset to Data Center time (taking into account daylight savings time where necessary).

All search results will continue to be displayed in data center time for now. We are aware that many customers would like to see the results displayed in their local time zone and this is something we intend to address in the future.