On Thu, Apr 19, 2012 at 11:22, Jan-Frode Myklebust <janfr...@tanso.net>wrote:
> I need to migrate 15K users to a new domain name, and plan to use "dsync > mirror" in the transition phase. Could someone confirm that this should > work: > > Before giving users access to new-domain do a first sync to get all the > stale data over: > > for user in $old-domain; do > dsync mirror $user@old-domain $user@new-domain > done > > Configure sieve vacation filter to forward all messages from > $user@old-domain to $user@new-domain, and notify sender of changed > address. > > Give users access to both new-domain and old-domain, and do a final > sync. > > for user in $old-domain; do > dsync mirror $user@old-domain $user@new-domain > dsync mirror $user@old-domain $user@new-domain # twice in > case the first was slow > drop all messages for $user@old-domain > Leave notice message for $user@old-domain saying he should > use new-domain > done > > Wait a few weeks/months, and then drop all users@old-domain. > > > Does this look sensible? > > > -jf > What do you mean by a "new domain" in this context? Is the server changing? Is the storage changing? In my thinking, a domain change is as simple as using a rewrite rule in your MTA. I am sure I didn't understand your requirement and as such my response is equally vague. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.
<<image001.png>>
