[EMAIL PROTECTED] wrote:
Thanks for the input. I'll give it a try.
On May 24, 2006, at 12:39 PM, [EMAIL PROTECTED] wrote:
Have vpopmail running and its working very well. :) One of my clients
has
xxx.com for their domain. The just changed their company name and need
to
change to a new email domain yyy.com. What is the easiest way to
migrate
to the new yyy.com domain. Should I just create the new domain and copy
the contents of the old one to it, or will this lead to problems. ANy
help
would be appreciated.
The easiest way is to create yyy.com as an alias to xxx.com.
~vpopmail/bin/vaddaliasdomain xxx.com yyy.com
This way, you don't have to change any path names. They can continue
to receive mail for the old domain as well. If you want yyy.com to be
the "real" domain and xxx.com to be the "alias", you can edit
/var/qmail/users/assign. After editing, run qmail-newu. Verify it's
good by using vdominfo and/or vuserinfo.
If you want to change the domain's directory, you'll have to update:
/var/qmail/users/assign
Each user's Maildir path (vpasswd file, or database backend)
Mailing list configurations
and possibly autoresponders (I can't recall if they have full or
relative paths).
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
for the sake of completeness, i ran into the same issue, but at the same
time the customer had 3 extra requests:
1) at the same time, migrate to a new server.
2) the old domain should, after 90 days, be completely gone (i.e. we
delete the dns zone, and delete it from the mail server, so the alias
domain thing was ruled out)
3) migrate from vmailmgr to vpopmail (plus a ton of other upgrades) in
the process
I created the new domain on the new box, wrote a script to migrate the
users, aliases, forwards and passwords over to the new vpopmail+mysql.
wrote another script to read the passwd.cdb file (vmailmgr) and based on
the username, rsync their maildir to the new box. I ran this with the
delete destination file if not exist type setting in rsync to avoid
delivering the same messages twice. There was a gotcha, in that
vmailmgr tree looks like domain/users/username/{cur,new,tmp} whereas
vpopmail uses domain/username/Maildir/{cur,new,tmp}. Some time later, I
had a working rsync command, and it worked like a charm. One more
vmailmgr box bites the dust! =)
the only thing i ran into was that qmailadmin is not as nice as omail )
http://omail.omnis.ch ). But we plan on coding our own, using the
vpopmaild interface in the very near future.
I wonder, are there any actively developed vpopmaild-based
shared-hosting type web gui's right now ? I haven't found any yet.
