Gmail에서 CloudM Migrate 마이그레이션 날짜 수정

CloudM Migrate (formerly Cloud Migrator) is widely used for migrating 사서함 into Google Workspace. CloudM uses the Gmail API to upload emails to the destination Gmail account. During this upload, Gmail's infrastructure records the insertion timestamp as the message's INTERNALDATE, overwriting the original delivery date with the date the migration was performed.

CloudM attempts to preserve the original Date 헤더 within the email body, and Gmail's 웹 인터페이스 일반적으로 uses this Date 헤더 for display purposes. 그러나, the IMAP INTERNALDATE is permanently set to the 마이그레이션 날짜. Every IMAP client that connects to the Gmail account (Outlook, Apple Mail, Thunderbird, mobile clients using IMAP) reads this INTERNALDATE and displays the 마이그레이션 날짜 in the received column.

Organizations migrating from Microsoft 365, on-premises Exchange, or other platforms to Google Workspace using CloudM discover this problem when 사용자 connect desktop clients to their new Gmail accounts. The Gmail 웹 인터페이스 may look fine, but Outlook and Apple Mail show every email as received on the 마이그레이션 날짜, generating confusion and support tickets across the 조직.

In Gmail, the impact depends on how the 사용자 accesses their 사서함. The Gmail 웹 인터페이스 일반적으로 displays dates correctly because it reads the Date 헤더 from the email itself. 그러나, any IMAP-connected client (Outlook, Apple Mail, Thunderbird) shows the 마이그레이션 날짜 because these clients rely on the IMAP INTERNALDATE rather than the Date 헤더.

Gmail's label system and search are also affected in subtle ways. While Gmail's web search uses the Date 헤더 for "before:" and "after:" operators, the IMAP SEARCH DATE command uses INTERNALDATE. Third-party 백업 tools and email archiving solutions that connect via IMAP archive the 마이그레이션 날짜 as the message date, creating permanent inaccuracies in 백업 records. Google Vault, used for 규정 준수 and legal hold, may also reference the INTERNALDATE for certain operations, impacting the accuracy of date-based legal discovery.