إصلاح تواريخ ترحيل Exchange IMAP Migration في Outlook
لماذا تعرض عمليات ترحيل Exchange IMAP Migration التاريخ الخاطئ في Outlook
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
Outlook connected to the migrated Exchange صندوق البريد displays the تاريخ الترحيل in the "Received" column for every email. The "Sent" column for sent items also reflects the الطابع الزمني للترحيل because Exchange's transport pipeline processes sent items 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.
الأسئلة الشائعة
Does Exchange IMAP Migration have an option to preserve dates?
Exchange IMAP Migration does not provide a reliable option to preserve the original delivery dates. The transport pipeline processes uploaded messages as new deliveries, stamping them with the current timestamp. This is a fundamental limitation of the built-in IMAP migration approach.
Is the Exchange IMAP Migration date issue different from other migration tools?
The root cause is the same: خادم الوجهة adds a رأس Received with the الطابع الزمني للترحيل. Exchange IMAP Migration and third-party tools like BitTitan or imapsync all produce the same type of تلف التاريخ. Redate.io fixes dates بغض النظر عن which tool caused the issue.
Can Redate.io fix dates on an on-premises Exchange server?
نعم. Redate.io connects via IMAP to any Exchange server that has IMAP enabled. This includes Exchange Online (Microsoft 365), Exchange Server 2016, Exchange Server 2019, and other versions with IMAP access configured.