You can use dsync migration via IMAP protocol, but there are a few things different with Gmail compared to other IMAP servers. Some clients re-download all mails if you change the hostname in the client configuration. Some (many?) POP3 clients also require that the message ordering is preserved. Even going back to your old server is unlikely to help at that point. If a client already saw changed UIDLs and decided to start re-downloading mails, it’s unlikely there is anything you can do to stop it. Ensure both source and target system agree on usernames.Ĭonfigure IMAP client on the target system. Preparations ¶Ĭonfigure authentication on the source system to match your preference. See Master users/passwords for more details. This depends entirely on the source system. You can either use master password, master user or individual user authentication. When migrating mails over IMAP, you need to have valid credentials to the source system. At best this causes warnings about GUID or UIDVALIDITY changes, and at worst it fails the sync entirely. There is no way to throttle the synchronization.Īvoid accessing the target mailboxes before the first sync. Migration can cause unexpectedly high loads on the source system, beware. Especially if you have ACLs that only permit writing to folder, but not reading it. If you are using ACLs, some ACL types can cause problems. To migrate Shared namespaces, you need to use -n Shared -n Shared/Mailbox. Migrating shared namespaces is difficult prior v2.3.15+.
0 Comments
Leave a Reply. |