We will be changing our company name and thus our e-mail domain name soon. What are the steps I need to take in MDaemon to switch over to the new domain, yet still continue to receive e-mail at the old domain name for some amount of time? Can I set things up in advance and then switch, or will it all have to be done in one fell swoop?
Obviously, I'll have to get a new security certificate and change DNS and SPF and DMARC and DKIM and write new firewall rules.... I'm really looking forward to this. ;-(
I would reccomend renaming your existing domain and then adding an alias for *@olddomain.com = *@newdomain.com.
To do this, you'll probably first want to add the DNS records and get SPF, DMARC, and DKIM set up. Then open MDaemon and go to Setup / Domain Manager. MDaemon won't allow you to rename the default domain, so you'll need to add a temporary domain name. For example, mytempdomain.com. Then set mytemdomain.com as the default domain. Select your old domain name and click rename. Enter the new domain name. Once the rename is complete, set the new domain name as the default domain and delete mytempdomain.com.
Then go to Accounts / Account Settings / Aliases. Add an alias for *@olddomain.com = *@newdomain.com. Make sure all the aliases using the old domain name have been updated and are using the new domain name now, if they are not, you'll want to update them manually. You can do this by going to the MDaemon\app directory and editing the alias.dat file using a text editor (make sure you backup the file before making chanes). Move the wildcard alias for old domain to the top of the list so that it is processed first. And make sure that you enable recursive aliasing on the Settings dialog.
After the domain name change, the rDNS will also be changed to the new domain. Will that cause problems continuing to receive e-mail sent to the old domain?
So, when doing the domain name change, and I install the new certificate for the new domain and make it the default certificate, I assume that's the only certificate MDaemon will use. Will THAT cause issues continuing to receive e-mails for the old domain?
No... wait. I'll be changing the old domain's MX records to point to the new domain-name mail server name, so that ought to fix both the above -- correct?
Changing the reverse DNS will not cause an issue as long as the reverse DNS points to an A record that resolves to the IP. So if your IP is 1.2.3.4 and you have reverse DNS setup to point to mail.mynewdomain.com, then mail.mynewdomain.com must point to 1.2.3.4.
The certificates will not cause issues with receiving mail for the old domain. Just make sure you update the MX record for the old domain to point to mail.mynewdomain.com and that the certificate that is being used supports mail.mynewdomain.com.
Also, MDaemon can be configured to use multiple certificates, which you will probably want to do for a while so that any clients connecting to mail.myolddomain.com will still be able to connect without getting a certificate error.
Yes, I've been working with the support team for the discussion groups to get the notifications working. They are finally working, but we have a few more issues to address.
English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
