Benches Uncategorized

2

Changing Mailserver Name Issues?

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I have an older server doing both email and web and I plan to split the services across a couple of boxes and limit this box to just doing email. So far it has used the same domain name like foo.bar.com for both the address of the email and webservers. I have arranged to get foomail.bar.com working and pointed at the same box and I have the SSL cert creating and working. It's my plan to notify the users of the change and push out the new certificate and eventually change foo.bar.com to point to the webserver box instead.

What's the easiest way to make this transition while my users will be using and mix of both names? Can I change the mailserver setting to foomail right away and make foo a virtual server or vice-versa? Is there a better way?

Any input appreciated,
=Tod

2 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Plan for a definite date in the near future for a complete cutover. Notify your users of the impending change -once a week, every other day, everyday- as the date approaches. Issue plenty of instructions as to how they should reconfigure their mail clients -be prepared for the inevitable panic phone calls. Have the boxes ready to switch over with just a boot/reboot. Make sure your DNS is updated so that you can just reload the zone files and everything will work immediately.

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have to admit that is my first inclination - although experience tells me that the frequency of emails to users seems to have little effect on their awareness of these things. Unfortunately the main reason we run our own mailserver is because some of our least technically proficient users have been on some version of our mailserver literally for years. So I was hoping to make the change via a virtual server at first to give everyone time to try it out and handhold our problem users through the process.

    The other issue is that we are in an environment where the DNS is handled by other powers that be which makes timing an exact change-over a little more difficult. (But the trade-off is that they are very good and I don't have to worry about DNS.)

    Switching gears a little is there any easy way to direct any emails that might go to the new server under the old name short of doing the email forwarding thing for every account? Users are supposed to use @bar.com but some still sometimes use (or have used) @foo.bar.com and when the mailserver becomes @foomail.bar.com I'm sure some mail will still go to the new @foo.bar.com which will no longer be a mailserver.
    Obviously I could run mail and do a vacation message warning system but is there a way to set-up forwarding or redirecting without setting up all the user accounts from the current server?

    Thanks,
    =Tod