How Thunderbird Handles Email Dates
Mozilla Thunderbird is one of the most popular free email clients, widely used by individuals and organizations that prefer an open-source alternative to Outlook. Thunderbird's approach to displaying email dates is more flexible than most email clients, which is both an advantage and a source of confusion when migration date issues occur.
Thunderbird's Two Date Columns
Thunderbird distinguishes between two date values: "Date" and "Received." The "Date" column shows the value from the RFC 2822 Date header, the timestamp set by the sender. The "Received" column shows the date derived from the IMAP server's metadata (INTERNALDATE) and the "Received" headers in the message.
By default, Thunderbird displays the "Date" column (the sent date). This means that immediately after migration, Thunderbird users may not even notice the date problem because the Date header is preserved. The "Received" column, however, will show the migration date for every email. Users who've customized their view to show the "Received" column or who sort by received date will see the wrong dates.
The "Order Received" Sort vs "Date" Sort
Thunderbird offers separate sort options: "Date" (sorts by the Date header) and "Order Received" (sorts by the received timestamp). Sorting by "Date" produces the correct chronological order. Sorting by "Order Received" groups all migrated emails to the migration date, breaking the chronological order.
Many users don't realize these are different sort options.
Why the Thunderbird "Date" Column Isn't a Real Fix
Search Is Affected
Thunderbird's search can filter by date ranges. When a user searches for "emails received in January 2024," Thunderbird uses the received date metadata from the server, not the Date header. After migration, this search returns no results for January 2024 and returns every email for the migration date. For users who frequently search by date range (accountants looking for invoices from a specific quarter, lawyers gathering correspondence from a case period), this makes the mailbox functionally broken.
Message Filters and Saved Searches
Thunderbird's message filters can trigger based on date conditions. Filters referencing the "Received" date or "Age in Days" will malfunction after migration. Saved searches (virtual folders) that use date criteria are similarly affected.
Other IMAP Clients on the Same Account
Even if a Thunderbird user switches to the "Date" column, the underlying problem remains on the server. If anyone else accesses the same mailbox through Outlook, Apple Mail, a mobile app, or webmail, they'll see the wrong dates. The problem is server-side, not client-side.
Inspecting Headers in Thunderbird
Using Thunderbird's Header View
Thunderbird makes it easy to inspect email headers. Open the affected email, then click View, then Message Source (or press Ctrl+U). This displays the complete raw message. You can also use View, then Headers, then All to see an expanded header view.
Identifying Migration Received Headers
In the raw message source, look at the "Received" headers at the top. The topmost Received header is the most recently added, after migration, this is the migration tool's header. It typically contains a timestamp matching the migration date and may reference the migration tool explicitly (for example, "mx.migrationwiz.com" for BitTitan, "cloudm.io" for CloudM, or "gmailapi.google.com" for GSMMO).
Below the migration header, the original Received headers are still intact. The original Date header is also preserved. This confirms that the correct date information exists, it just needs to be restored.
Why Client-Side Fixes Don't Work
The Problem Is Server-Side
Every workaround that involves changing Thunderbird settings is a client-side change that affects only what Thunderbird shows on screen. The actual email data on the server still contains the migration Received header. This means other devices and clients see wrong dates, server-side search returns wrong results, compliance and archival tools get wrong dates, and backup tools capture the wrong dates. The only permanent fix is to correct the data on the server itself.
Thunderbird Add-ons Can't Fix This
While Thunderbird's extension system is powerful, no add-on can modify email headers on the IMAP server. An add-on could potentially change how dates are displayed locally, but this would only affect Thunderbird on that specific computer. So what's the actual solution?
Fixing Thunderbird Dates at the Server Level
How Redate.io Fixes the Problem
Redate.io connects to the email server (Google Workspace, Microsoft 365, or any IMAP server including Zimbra and Zoho) and corrects each affected email directly on the server.
Redate.io's proprietary correction engine analyzes the complete header chain of every affected message, applying pattern matching across hundreds of known migration tool signatures. The multi-stage analysis pipeline handles edge cases that would trip up a DIY approach: S/MIME signed messages, PGP-encrypted content, multipart structures with nested boundaries, non-ASCII headers, and Content-Transfer-Encoding variations. After correction, integrity verification confirms every message is intact. Originals are kept in a backup folder for 30 days.
After the fix, Thunderbird syncs with the server and picks up the corrected dates. Both the "Date" and "Received" columns display the correct values. Search by date range works correctly. Filters and saved searches based on received date function as expected.
Could you try building a script to do this? Sure. But how do you verify that 8000 corrected emails all have intact attachements, preserved threading, and valid MIME structures? That verification challenge is where DIY approaches fall apart.
Verifying the Fix in Thunderbird
After Redate.io completes the fix, force Thunderbird to re-sync by right-clicking the account in the folder pane and selecting "Subscribe" then closing the dialog, or by compacting folders. Thunderbird downloads the updated message headers from the server. The "Received" column should now show the original received dates.
Common Thunderbird Migration Scenarios
Thunderbird as the Migration Tool
A common scenario involves using Thunderbird itself as a migration tool. An administrator sets up both the source and destination IMAP accounts in Thunderbird, then drags emails from one account to the other. While this "works" in the sense that emails are transferred, the destination server adds a Received header to every copied message, stamping them all with the copy date. See the manual IMAP copy date fix guide for Thunderbird.
Thunderbird After a Server-Side Migration
When the migration happens at the server level (using BitTitan, CloudM, imapsync, or another tool), Thunderbird users are affected like any other IMAP client. The migration dates appear in the "Received" column, while the "Date" column may still be correct. Administrators should verify dates in Thunderbird specifically because its dual-column display can mask the problem.
Thunderbird showing wrong dates after migration? Start a free scan with Redate.io to identify affected emails and restore correct dates across all your email clients.