Fix GSMMO Migration Dates in Gmail
Why GSMMO Migrations Show the Wrong Date in Gmail
GSMMO (Google Workspace Migration for Microsoft Outlook) uploads emails from PST files or Outlook profiles directly to Gmail using the Gmail API. While the Gmail API technically supports setting a custom INTERNALDATE during message insertion, GSMMO's upload process results in Gmail recording the upload timestamp as the INTERNALDATE for most messages. The original Date header from the email is preserved, but the INTERNALDATE is overwritten.
In the Gmail web interface, this issue is partially hidden. Gmail web uses the Date header from the email body for its display date, so most emails appear with the correct date in the browser. However, the IMAP INTERNALDATE stored on the server is wrong. This becomes visible when users access their Gmail account through any IMAP client (Outlook, Thunderbird, Apple Mail) or when third-party tools query the mailbox via IMAP.
GSMMO is typically used by end users who are transitioning from Microsoft Outlook to Google Workspace. These users may not immediately notice the INTERNALDATE issue if they primarily use the Gmail web interface. The problem surfaces weeks or months later when they install an IMAP client, set up a backup tool, or when a compliance team runs a date-based search on the mailbox through Google Vault or IMAP-based archiving software.
How This Affects Gmail
For Gmail web users, the visual impact is minimal because the Date header displays correctly. However, the corrupted INTERNALDATE affects several non-obvious areas. Gmail's IMAP SEARCH DATE command uses INTERNALDATE, so any IMAP-based tool or client that performs date searches against the mailbox gets incorrect results. Backup tools like MailStore, Veeam, or custom scripts that archive Gmail via IMAP record the wrong dates in their backups.
Gmail's sorting within labels when accessed via IMAP uses the INTERNALDATE. Users who access their Gmail account from mobile IMAP clients or desktop email applications see an unsorted mess of emails all dated to the migration day. Google Takeout exports may also reference the INTERNALDATE for file naming or metadata, potentially creating confusing archives. The corrected Date header is inside the message, but the INTERNALDATE governs how external tools and IMAP clients perceive the message timeline.
Frequently Asked Questions
If Gmail web shows the correct date, why should I fix the INTERNALDATE?
The INTERNALDATE affects IMAP clients, backup tools, Google Vault compliance searches, and any third-party integration that connects via IMAP. Even if the Gmail web display is correct, the underlying data is wrong and can cause issues in backup, compliance, and multi-client environments.
How does Redate.io fix GSMMO dates in Gmail?
Redate.io reads the original Date header from each email, strips the GSMMO migration Received header, and re-inserts the email with the correct INTERNALDATE matching the original date. The original email is moved to a backup label for safety.
Will the fix change how emails appear in Gmail web?
No. Gmail web already shows the correct date (from the Date header). The fix corrects the INTERNALDATE so that IMAP clients also display the correct date. The Gmail web experience remains unchanged.