إصلاح تواريخ ترحيل BitTitan MigrationWiz في Exchange Online
لماذا تعرض عمليات ترحيل BitTitan MigrationWiz التاريخ الخاطئ في Exchange Online
Exchange Online is the mail backend powering Microsoft 365 صناديق البريد, and BitTitan MigrationWiz is frequently used to migrate صناديق البريد from on-premises Exchange, Lotus Notes, GroupWise, or other platforms into Exchange Online. During the migration, MigrationWiz uploads each message using EWS or IMAP APPEND, and Exchange Online's transport pipeline stamps each message with a رأس Received containing the upload timestamp.
Exchange Online uses this رأس Received and the associated PR_MESSAGE_DELIVERY_TIME property to determine the displayed received date. Unlike some mail systems that allow migration tools to set a custom delivery time, Exchange Online's processing consistently applies the actual upload timestamp. This means every migrated email carries the تاريخ الترحيل in its delivery time metadata, بغض النظر عن the original send date.
The problem is amplified in Exchange Online because the corrupted date propagates through all connected services: Outlook desktop reads it, OWA displays it, mobile clients show it, and Exchange Online's built-in search indexes it. PowerShell scripts that المسؤولين use to query صندوق البريد content by date also return results based on the الطابع الزمني للترحيل rather than the التاريخ الأصلي, complicating post-migration verification and troubleshooting.
كيف يؤثر ذلك على Exchange Online
In Exchange Online, the corrupted delivery time affects every layer of the mail stack. The Outlook desktop client, Outlook on the web, and mobile apps all display the تاريخ الترحيل in the received column. Exchange Online's search service indexes the الطابع الزمني للترحيل, so date-range queries in Outlook and OWA return incorrect results.
For المسؤولين, Exchange Online Management Shell commands like Get-MessageTrace and Search-Mailbox use the delivery time property, which now reflects the تاريخ الترحيل. 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 الامتثال features (In-Place Hold, Retention Tags) find that these policies apply based on the التاريخ الخاطئ, potentially retaining or deleting messages at incorrect intervals.
الأسئلة الشائعة
Is this different from the Microsoft 365 date issue?
Exchange Online is the backend service that powers Microsoft 365 صناديق البريد. The root cause is the same: BitTitan adds a رأس Received during migration that overrides the displayed date. Fixing it in Exchange Online corrects the date across all Microsoft 365 applications.
Can Exchange Online المسؤولين fix this with PowerShell?
PowerShell cannot modify the رأس 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?
نعم. Redate.io connects to Exchange Online صناديق البريد directly. Whether the المنظمة runs a hybrid Exchange setup or is fully in the cloud, Redate.io can fix the تلف التاريخ on any صندوق البريد accessible via IMAP or Exchange protocols.