Outlook에서 Exchange IMAP Migration 마이그레이션 날짜 수정

Microsoft Exchange Server includes a built-in IMAP migration feature (available through the Exchange Admin Center and PowerShell) that allows 관리자 to migrate 사서함 from third-party IMAP servers into Exchange Online or on-premises Exchange. This native migration tool connects to the source IMAP server, downloads each message, and uploads it to the destination Exchange 사서함.

During the upload phase, Exchange's transport pipeline processes each message as though it were a newly received email. The pipeline adds transport headers, including a Received 헤더 with the current processing timestamp. Exchange also sets the PR_MESSAGE_DELIVERY_TIME (the property Outlook reads for its "Received" column) to the upload timestamp. The original IMAP INTERNALDATE from 소스 서버 is not carried over to the destination Exchange 사서함.

Administrators who use Exchange's native IMAP migration expect Microsoft's own tool to handle date preservation correctly. The discovery that all migrated emails now display the 마이그레이션 날짜 in Outlook is unexpected, 특히 because Exchange's migration documentation does not prominently warn about this behavior. The issue affects every 사서함 processed by the migration batch, and Exchange provides no built-in mechanism to correct the dates after migration.

Outlook connected to the migrated Exchange 사서함 displays the 마이그레이션 날짜 in the "Received" column for every email. The "Sent" column for 보낸 항목 also reflects the 마이그레이션 타임스탬프 because Exchange's transport pipeline processes 보낸 항목 the same way during upload. The Outlook calendar pane, which references email dates for meeting-related messages, shows in올바른 날짜s for migrated meeting invitations and responses.

Exchange's native search (used by Outlook's search bar) indexes the corrupted delivery time. Date-based searches return wrong results. Outlook's AutoArchive feature, which moves or deletes emails based on age, miscalculates message age because it uses the 마이그레이션 날짜. Rules that trigger on received date and Conditional Formatting rules that highlight emails by age also operate on the 잘못된 날짜s, producing unexpected behavior across the Outlook experience.