Perbaiki Tanggal Migrasi BitTitan MigrationWiz di Exchange Online
Mengapa Migrasi BitTitan MigrationWiz Menampilkan Tanggal yang Salah di Exchange Online
Exchange Online is the mail backend powering Microsoft 365 kotak surat, and BitTitan MigrationWiz is frequently used to migrate kotak surat from on-premises Exchange, Lotus Notes, GroupWise, or other platforms into Exchange Online. Selama migrasi, MigrationWiz uploads each message using EWS or IMAP APPEND, and Exchange Online's pipeline transport stamps each message with a header Received containing the stempel waktu unggah.
Exchange Online uses this header Received and the associated PR_MESSAGE_DELIVERY_TIME property to determine the displayed tanggal diterima. Tidak seperti some mail systems that allow migration tools to set a custom waktu pengiriman, Exchange Online's processing consistently applies the actual stempel waktu unggah. This means every migrated email carries the tanggal migrasi in its waktu pengiriman metadata, terlepas dari the original send date.
The problem is amplified in Exchange Online karena the corrupted date propagates through all connected services: Outlook desktop reads it, OWA displays it, klien seluler show it, and Exchange Online's built-in pencarian indexes it. PowerShell scripts that administrator use to query kotak surat content by date also return results based on the stempel waktu migrasi daripada the tanggal asli, complicating post-migration verification and troubleshooting.
Bagaimana Hal Ini Mempengaruhi Exchange Online
In Exchange Online, the corrupted waktu pengiriman affects every layer of the mail stack. The Outlook klien desktop, Outlook on the web, and mobile apps all display the tanggal migrasi in the received kolom. Exchange Online's pencarian service indexes the stempel waktu migrasi, so date-range queries in Outlook and OWA return incorrect results.
For administrator, Exchange Online Management Shell commands like Get-MessageTrace and Search-Mailbox use the waktu pengiriman property, which now reflects the tanggal migrasi. Mailbox auditing, journaling rules, and transport rules that reference message dates all operate on the corrupted timestamps. Organizations that rely on Exchange Online's native kepatuhan features (In-Place Hold, Retention Tags) find that these policies apply based on the tanggal yang salah, potentially retaining or deleting messages at incorrect intervals.
Pertanyaan yang sering diajukan
Is this different from the Microsoft 365 date issue?
Exchange Online is the backend service that powers Microsoft 365 kotak surat. The root cause is the same: BitTitan adds a header Received selama migrasi that overrides the displayed date. Fixing it in Exchange Online corrects the date across all Microsoft 365 applications.
Can Exchange Online administrator fix this with PowerShell?
PowerShell cannot modify the header Receiveds or INTERNALDATE of existing messages in Exchange Online. The only way to fix the dates is to re-insert the corrected messages, which is exactly what Redate.io automates at scale.
Does Redate.io support Exchange Online hybrid environments?
Ya. Redate.io terhubung ke Exchange Online kotak surat directly. Whether the organisasi runs a hybrid Exchange setup or is fully in the cloud, Redate.io can fix the kerusakan tanggal on any kotak surat accessible via IMAP or Exchange protocols.