This in the web-client/did you type in the full
audit@mm2.domain.com?
So it sound's like your going to combine techniques, which is perfectly fine.
So as your going to use auth plain for the imapsync, you could simply use:
zmprov ca
user@migration.domain.com ‘’
Quote:
Originally Posted by Rich Graves  -When that incremental imapsync is done, rename the Cyrus account to user.migrate (which has the effect of locking out the user); set forwarding for user@carleton.ed to a mailer that simply queues; create a new Cyrus account "user" with a couple placeholder messages to the effect "your mail is being synchronized to the new server, please try Zimbra in 15 minutes"; and run another incremental imapsync
- When the second imapsync is done (typically only a minute, though multi-gigabyte mailboxes took as long as 30 minutes simply to list), rename the Zimbra account from user@migrate.carleton.edu to user@carleton.edu, then set forwarding on the original system to deliver to Zimbra |
Not to add 'one more alternative' to your list, but if your worried about them messing around during migration, you could also provision the accounts then set:
zmprov ma
user@domain.com zimbraAccountStatus locked
Locked means that login is disabled, but mail is still delivered to the account.
(You don't want it but there's also maintenance which is also login disabled, BUT mail is queued at the MTA. An account can be set to maintenance mode for backing up or restoring the mailbox.)
Of course set whatever you need to on the other end to prevent usage (lock/rename/Rich's above method, etc)
Side note: Judging by your email (college of computing at gatech) etc, I'll wager you're on the Network Edition...you do know you could request assistance/professional services for your setup/migration.