Exchange Online에서 BitTitan MigrationWiz 마이그레이션 날짜 수정
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 Received 헤더s 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.