Google Workspace에서 imapsync 마이그레이션 날짜 수정

imapsync is a popular choice for migrating 사서함 to Google Workspace because it is open-source, scriptable, and supports the IMAP protocol that Google Workspace exposes. 그러나, Google Workspace's IMAP implementation has specific behaviors that interfere with date preservation. When imapsync uploads messages via IMAP APPEND, Google's mail infrastructure processes each message through its own pipeline, adding a Received 헤더 and potentially overriding the INTERNALDATE.

The --syncinternaldates flag in imapsync instructs the tool to request the original INTERNALDATE from 소스 서버 and pass it to 대상 서버 during APPEND. Google Workspace may accept this date for some messages but override it for others, depending on the message content and how it passes through Gmail's filters. The result is an unpredictable mix of messages with correct and in올바른 날짜s within the same migrated 사서함.

Google Workspace 관리자 often discover the problem when 사용자 report that their Outlook or Apple Mail clients (connected via IMAP to their Google Workspace account) show in올바른 날짜s. The Gmail 웹 인터페이스 일반적으로 shows 올바른 날짜s (using the Date 헤더), which adds to the confusion. A Google Workspace 사서함 can appear perfectly normal in the browser while being completely date-corrupted from the perspective of any IMAP client.

The split between Gmail web (showing correct Date 헤더 dates) and IMAP clients (showing corrupted INTERNALDATE) is the defining characteristic of this issue in Google Workspace. Organizations where some 사용자 prefer the Gmail 웹 인터페이스 and others use Outlook or Apple Mail experience inconsistent date displays from the same 사서함. Collaborative workflows break down when colleagues reference email dates that appear differently in their respective clients.

Google Workspace admin tools provide limited visibility into the INTERNALDATE issue. The Google Admin Console does not expose INTERNALDATE metadata for individual messages. Google Vault, used for 규정 준수 and eDiscovery, may reference either the Date 헤더 or the INTERNALDATE depending on the search method, producing inconsistent results in legal discovery scenarios. The only way to comprehensively resolve the issue is to correct the INTERNALDATE and Received 헤더s at the message level.