MDaemon Technologies, Ltd.

DAVID

2/24/23, 10:04 AM

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. ;-(

Thanks!

Dave

10
Posts

767
Views

A

Arron Staff

2/27/23, 8:55 AM

Hi David,

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.

Let us know if you run into issues.

D

DAVID

2/27/23, 10:57 AM

Arron:

Thanks. This helps a lot!

Dave

D

DAVID

3/14/23, 3:38 PM

Arron:

A couple questions:

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?

Thanks,

Dave

D

DAVID

3/14/23, 3:40 PM

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?

Dave

A

Arron Staff

3/15/23, 8:12 AM

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.

Arron

D

DAVID

3/15/23, 4:58 PM

So as long as the old certificate is still listed in MDaemon, even if it's not the default certificate, all will be good?

Thanks, Arron!

Dave

A

Arron Staff

3/20/23, 10:16 AM

Yes it should be. MDaemon will look for a valid certificate that supports the host name that was used to connect to the server.

D

DAVID

3/21/23, 2:19 PM

Thanks, Arron.

I wanted to mention that this notification e-mail I received about your post was caught by MDaemon due to failing its SPF test. Here are the headers:

X-MDAV-Result: clean
X-MDAV-Processed: mail.mycompany.com, Mon, 20 Mar 2023 10:17:06 -0500
Return-path: <notifications@mdaemon.com>
Authentication-Results: mail.mycompany.com;
spf=fail smtp.mailfrom=notifications@mdaemon.com;
dkim=pass (good signature) header.d=xenforum.net header.b=dQH4Rd0vq0;
dmarc=fail header.from=mdaemon.com (p=quarantine sampling=63 pct=100);
iprev=pass policy.iprev=51.222.24.169 (PTR vps-4fe7cbbc.vps.ovh.ca);
iprev=pass policy.iprev=51.222.24.169 (HELO mailpro.xenforum.net);
iprev=fail reason="does not match" policy.iprev=51.222.24.169 (MAIL notifications@mdaemon.com)
Received-SPF: fail (mail.mycompany.com: domain mdaemon.com
does not designate 51.222.24.169 as permitted sender)
receiver=mail.mycompany.com; client-ip=51.222.24.169;
mechanism=all; envelope-from="notifications@mdaemon.com";
helo=mailpro.xenforum.net;
Received: by mail.mycompany.com (MDaemon PRO v23.0.0) with ESMTPS id md50008433597.msg;
Mon, 20 Mar 2023 10:17:05 -0500
X-Spam-Flag: YES
X-Spam-Level: **********
X-Spam-Status: Yes, score=10.80 required=5.0
X-Spam-Report:
* -4.7 BAYES_00 BODY: Bayes spam probability is 0 to 1%
* [score: 0.0008]
* 15 MDAEMON_SPF_FAIL MDaemon: failed SPF verification
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
* 0.4 KHOP_HELO_FCRDNS Relay HELO differs from its IP's reverse DNS
X-Spam-Processed: mail.mycompany.com, Mon, 20 Mar 2023 10:17:05 -0500
(processed during SMTP session)
X-MDDKIM-Result: unapproved (mail.mycompany.com)
X-MDDMARC-Fail-policy: quarantine
X-MDSPF-Result: fail (mail.mycompany.com)
X-MDRemoteIP: 51.222.24.169
X-MDHelo: mailpro.xenforum.net
X-MDArrival-Date: Mon, 20 Mar 2023 10:17:05 -0500
X-MDOrigin-Country: CA, NA
X-Rcpt-To: dbrhoten@mycompany.com
X-MDRcpt-To: dbrhoten@mycompany.com
X-Return-Path: notifications@mdaemon.com
X-Envelope-From: notifications@mdaemon.com
X-MDaemon-Deliver-To: dbrhoten@mycompany.com
Received: from mailpro.xenforum.net (localhost [127.0.0.1])
by mailpro.xenforum.net (Postfix) with ESMTP id 4PgJHh2CnFz4KRMc
for <dbrhoten@mycompany.com>; Mon, 20 Mar 2023 15:17:04 +0000 (UTC)
Authentication-Results: mailpro.xenforum.net (amavisd-new);
dkim=pass (2048-bit key) reason="pass (just generated, assumed good)"
header.d=xenforum.net
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xenforum.net; h=
content-transfer-encoding:content-type:mime-version:subject
:message-id:date:to:reply-to:from; s=dkim; t=1679325423; x=
1681917424; bh=zBU96VGK2l4q43BcXVOV4XojESEkiCuw9NMBnrS73V0=; b=d
QH4Rd0vq0m2MDTH63/o8MXMWNsFCjhpiMkogNKHaWy/qhKid9EuiHKOvfEz/4MG6
awvFGbQHHwpTD+jNHLnH0wAAmixRHUKdebG/iBeAA2ucuilERXhttJRfomaM+4f2
zi6f137HBEt56hCkkumhQ7SGJJoCk6pKewYtdumvQ+dsglREG3ruO5wbxDaY3/F8
42S+nXr1PBfsndI979sw/fTX3mVB9GxIQqe9IZ/p3kFkAwHK6lcHKHb59InQXr13
1yRr/DSJxZ1GrBIgDDtE6PJ8RR5H1bGpfVDEiDgk638PhNvtuEig8KAXVmkNV0Lc
15wUU4pHeucU4njILwbOw==
X-Virus-Scanned: amavisd-new at mailpro.xenforum.net
Received: from mailpro.xenforum.net ([127.0.0.1])
by mailpro.xenforum.net (mailpro.xenforum.net [127.0.0.1]) (amavisd-new, port 10026)
with ESMTP id Z-u-w6yhQjTC for <dbrhoten@mycompany.com>;
Mon, 20 Mar 2023 15:17:03 +0000 (UTC)
Received: from localhost (vmi1001219.contaboserver.net [144.126.155.166])
by mailpro.xenforum.net (Postfix) with ESMTPSA id 4PgJHg4gk9z4KRVG
for <dbrhoten@mycompany.com>; Mon, 20 Mar 2023 15:17:03 +0000 (UTC)
From: "MDaemon Technologies Community Forum (notifications@mdaemon.com)" <notifications@mdaemon.com>
Reply-To: notifications@mdaemon.com
To: dbrhoten@mycompany.com
Date: Mon, 20 Mar 2023 15:17:03 +0000
Message-ID: <a8f11d115f5640768f662df6efd0bb7b@mdaemon.com>
Subject: SPAM Score/Req: 10.80/5.0 -- Arron Caruth also commented on topic New Company Name/Domain
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-MDBadQueue-Reason: CF Rule "Send All Other SA Messages to BadMsg Queue"

A

Arron Staff

3/21/23, 2:30 PM

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.

Thanks for letting me know.