Fix Manual IMAP Copy Dates in Gmail

Manual IMAP copy to Gmail sounds simple enough: add both your source account and Gmail to an email client like Outlook, Thunderbird, or Apple Mail, then drag messages over. What nobody tells you is that every email client drops the original date metadata during this operation. The client uploads messages to Gmail without specifying the original INTERNALDATE, so Gmail records the upload timestamp instead. Thousands of emails, one date.

Gmail adds its own wrinkle to the problem. When it receives an uploaded message, Gmail's IMAP gateway adds a new Received header stamped with the current date and time. This header sits at the top of the header chain. The Gmail web interface is smart enough to use the Date header from the email body for display purposes, so dates may look correct in the browser. But every IMAP client that connects afterward reads the corrupted INTERNALDATE from Google's servers.

Who actually does manual IMAP copy? More people than you would think. Small businesses consolidating from Yahoo Mail or a cheap hosting provider into Gmail. Freelancers merging three accounts into one. IT consultants migrating a client's mailbox from a provider that has no official migration tool. The drag-and-drop approach feels intuitive and safe. But at the IMAP protocol level, date metadata is silently destroyed during the transfer - and by the time anyone notices, the source account may already be closed.

The impact splits into two worlds. In Gmail's web interface, dates may appear correct because Gmail reads the Date header from the email body. In any IMAP client - Outlook, Apple Mail, Thunderbird, the Gmail app on Android - the copy date shows up instead. This creates a confusing situation where the same email displays different dates depending on how you access it.

But the damage goes deeper than display inconsistencies. Ever tried running a compliance audit on a mailbox where 30,000 emails all have the same INTERNALDATE? Google Vault searches by date return misleading results. Backup tools like MailStore, Veeam, or custom archiving scripts that connect via IMAP permanently record the wrong dates. Google Takeout exports may reference the INTERNALDATE for file naming, creating archive folders where 2017 emails sit next to 2023 emails under a single date. For someone who consolidated years of email from multiple providers into Gmail, this can mean their entire email history has incorrect date metadata on Google's servers.

Redate.io addresses this through a proprietary correction engine that uses pattern matching across migration tool signatures to identify affected messages. The process performs targeted metadata correction at the server level - preserving message content, labels, read status, and attachments while restoring accurate date information. Every message receives individual verification before and after correction.