Fix Manual IMAP Copy Dates in Thunderbird

Why Manual IMAP Copy Shows the Wrong Date in Thunderbird

Thunderbird is a popular free email client often used for manual email migration between IMAP accounts. Users add both the source and destination IMAP accounts to Thunderbird and copy or move messages between them. When Thunderbird uploads a message to the destination IMAP server via APPEND, it does not pass the original INTERNALDATE parameter. The destination server sets the INTERNALDATE to the upload timestamp, and adds its own Received header with the current date.

Thunderbird's date display behavior depends on the column configuration. By default, Thunderbird shows the "Date" column (from the Date header) rather than a "Received" column. This can partially mask the problem: if a user only sees the Date column, the dates may appear correct because the Date header is preserved during the copy. However, the underlying INTERNALDATE on the server is wrong, which affects server-side sorting, search, and any other client that connects to the same account.

The issue becomes fully visible when the user adds the "Received" column to Thunderbird's message list, or when they access the same mailbox from a different client (Outlook, Apple Mail) that displays the Received date by default. The corrupted INTERNALDATE on the server persists regardless of which client is used to view the mailbox, and it affects all IMAP operations that reference the message date.

How This Affects Thunderbird

In Thunderbird, the default "Date" column shows the email's Date header, which is preserved during the copy and may display correctly. However, Thunderbird's "Received" column (if enabled) shows the IMAP INTERNALDATE, which displays the copy date. Server-side sorting in Thunderbird (which sorts by INTERNALDATE when sorting by received date) produces incorrect chronological order for copied messages.

Thunderbird's message search can produce mixed results depending on whether it searches locally cached data or performs a server-side IMAP search. Local searches may use the Date header (correct), while server-side searches use the INTERNALDATE (incorrect). Thunderbird's message filters that trigger on received date use the INTERNALDATE, potentially misrouting or misfiling copied messages. Quick Filter bar date filtering also uses server-side dates, returning inaccurate results for copied messages mixed with normally-received ones.

Frequently Asked Questions

Thunderbird shows the correct Date column. Is there still a problem?

Yes. The Date column shows the email header date, which is correct. But the IMAP INTERNALDATE on the server is wrong. This affects server-side search, sorting, other clients connected to the same account, and backup tools. Redate.io corrects the INTERNALDATE to match the original Date header.

Can Thunderbird fix the INTERNALDATE itself?

No. Thunderbird does not have a feature to modify the INTERNALDATE of messages already on the server. The IMAP protocol does not support changing the INTERNALDATE after message insertion. The only way to fix it is to re-insert the message with the correct date, which Redate.io automates.

I used Thunderbird to copy emails to multiple destination accounts. Can Redate.io fix all of them?

Yes. Redate.io can connect to any IMAP-compatible server and fix the dates. Each destination account can be connected and fixed independently through the Redate.io dashboard.

Start Free Scan