dovecot - Apr 2012 - migrate 15K users to new domain name

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 at old-domain $user at new-domain
	done

Configure sieve vacation filter to forward all messages from
$user at old-domain to $user at 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 at old-domain $user at new-domain
		dsync mirror $user at old-domain $user at new-domain  # twice in case the
first was slow
		drop all messages for $user at old-domain
		Leave notice message for $user at old-domain saying he should use new-domain
	done

Wait a few weeks/months, and then drop all users at old-domain.


Does this look sensible? 


  -jf

On Thu, Apr 19, 2012 at 11:22, Jan-Frode Myklebust <janfrode at
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 at old-domain $user at new-domain
>        done
>
> Configure sieve vacation filter to forward all messages from
> $user at old-domain to $user at 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 at old-domain $user at new-domain
>                dsync mirror $user at old-domain $user at new-domain  #
twice in
> case the first was slow
>                drop all messages for $user at old-domain
>                Leave notice message for $user at old-domain saying he
should
> use new-domain
>        done
>
> Wait a few weeks/months, and then drop all users at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 652 bytes
Desc: not available
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20120419/92478512/attachment-0004.png>

On Thu, Apr 19, 2012 at 02:01:44PM +0300, Odhiambo Washington
wrote:
> 
> What do you mean by a "new domain" in this context?
The user's email addresses are changing from username at old.domain to
username at new-domain.
> Is the server changing?
No.
> Is the storage changing?
The user's home directory is based on the user's email address, so this
is changing.
> In my thinking, a domain change is as simple as using a rewrite rule in
> your MTA.
Also the user's login-names needs to change from old to new domain, and
all their data needs to move from old to new domain.


  -jf

On Thu, Apr 19, 2012 at 05:59:39PM +0300, Timo Sirainen
wrote:
> 
> With v2.1.4 you could do something like:
> 
> doveadm -c dummy.conf user -m user at domain
> 
> where dummy.conf contains the minimum configuration needed:
> 
> mail_home = /srv/mailstore/%256LRHu/%Ld/%Ln
> ssl = no
> 
Thanks! Works perfect.


  -jf