On second thought, I think it might be beneficial in this case to keep a
copy on the source mail server. That way if users discover any issues
with the new server after the migration, we can go back without having
to copy any messages (they'd just have to review all messages that had
come in since the migration as "new")
I will add each user to be migrated in /etc/aliases like so:
bhuffman: \bhuffman,bhuffman@mail02
I've tested this and it appears to work as long as the new mail server
has "mail02" as an alias. By default it only accepts mail for our exact
domain (without the host portion).
After the migration, I'll just re-point the MX records to the new
server, turn off the old server and remove the alias for "mail02" on the
new server.
Does anyone see any potential issues with this method?
Thanks,
Brian
On 08/15/2012 11:37 AM, Fernando Maior wrote:
Hi Brian,
Best is IMHO use the transport table. Look at the docs at
http://www.postfix.org/transport.5.html
For example, for each user that is being migrated, you add
one line like below:
{username}@{domainname} smtp:{newserveripaddress}
Best regards---
Fernando Maior
On Wed, Aug 15, 2012 at 12:03 PM, Brian C. Huffman
<bhuff...@etinternational.com <mailto:bhuff...@etinternational.com>>
wrote:
All,
I currently have a postfix server that is handling mail for my
company's domain. However, we're going to migrate to a new mail
server and we're performing the migration in phases.
So, I'd like to move some users' mailboxes and then configure
postfix to forward (relay / bounce?) their mail to the new server
without affecting the other users that will remain until the
migration is complete.
The new mail server is going to answer to the same domain.
What would be the best way to do this?
Thanks in advance!
Brian
