Can I Customize My Email Domain?
Updated over a week ago

Absolutely! If you are on the Business Plan and higher, then you can customize the email domain that your email notifications are sent from.

If you’ve set up a Custom Domain for your Mighty Network, the process for setting up your Custom Email Domain will be familiar. We can whitelabel emails with any domain or subdomain you own. This requires you to control the administration of DNS records on your domain. Because CNAME and TXT records cannot have the same name, if you’ve mapped your Network to a subdomain (eg community.example.com), you must map your email to a different subdomain (eg mail.example.com).

To set this up, go to Network Settings > Integrations > Custom Email Domain > Manage

Screenshot 2024-03-27 at 11.00.35 AM.png

Adding Your Email Domain

You will see a page to add your email domain

There are some important things to note before setting up your Custom Email Domain:

  • If you use “mail.example.com”, emails will be from “info@mail.example.com”.

  • We support both root and subdomains. Using a subdomain is better for organization and safety.

  • Some domain providers require you to use a subdomain. Refer to your provider’s documentation for their requirements.

  • If you are already sending emails from an existing domain, we recommend using a unique subdomain for your Network’s Custom Email Domain. Ex. If you’re already using info@mail.domain.com for another product, then you should use info@notifications.domain.com on Mighty.

  • It can take up to 30 days before 100% your Network’s email notifications are sent from your domain.

Setting Up Your DNS Records

Before we can send email from your domain, we need you to configure some DNS records. These allow us to reach your members’ inboxes, and stay out of Spam:

1. SPF (Sender Policy Framework) Record: This tells the world our servers are authorized to send emails from your domain, reducing the likelihood of your emails being marked as spam.

2. DKIM (DomainKeys Identified Mail) Record: This allows recipients to verify that your email hasn't been tampered with after it was sent, and it confirms your identity as the sender.

3. MX (Mail Exchange) Records: MX records are generally used to route incoming mail. We do not currently support receiving mail over your Custom Email Domain, but having this record improves deliverability.

Depending on your DNS provider, some details may vary, but the general process should be common to popular providers. As a resource, here are links to common domain providers help centers: GoDaddy, Hover, Bluehost, Namecheap, DNSimple.

1. Log in to your DNS provider’s dashboard where your domain is registered or hosted.

2. Look for a section where you can view and edit DNS records.

3. Add or Update DNS Records with the name and value provided on this page of the wizard:

- For SPF – use a TXT Record

- For DKIM – use a TXT Record

- For MX – use an MX Record

4. After adding or updating the records, save your changes and allow some time for the DNS to propagate. These values usually propagate in minutes, but it can take up to 72 hours.

Screenshot 2024-02-28 at 10.42.17 AM.png

All fields will need to be verified before moving on to the next step. If you are having trouble with this step, MxToolbox is a helpful resource to look up your DNS records and diagnose some common problems. DNS records can take up to 72 hours to propagate. If it is taking longer, we suggest reaching out to your domain provider to help troubleshoot.

After they have been verified, you will see all the boxes below outlined in green:

Screenshot 2024-02-28 at 10.40.33 AM.png

If they are outlined in red, then there is an error that needs to be corrected.

Email Customization

After the DNS records have been verified, you will be able to customize the sender prefix and email footer. You can always edit these later on.

Pending Configuration

After you customize those fields, you will see a screen letting you know that the system is setting up your Custom Email Domain. This process may take a few hours and you can navigate away from the page and come back later.

When it has been configured successfully, we will send you an email to let you know. This is also a test email which is a great time to review it.

There are two important call outs in the email:

  1. If the test email landed in Spam, mark it as “Not Spam” and move it to the inbox.

  2. Verify that the email’s sender matches your domain.

Heading back to your email domain settings, you will see a message that your custom email is ready to activate.

If the configuration was unsuccessful, you will see a message giving you the option to start over:

Domain Warm-Up Period

After you activate your Custom Email Domain, there will be a warm-up period. A warm-up period is needed to prevent your messages from landing in your members’ spam folders, because new domains get flagged when sending mail, especially in bulk.

Boosting your domain’s email reputation during this period is critical. You can assist by:

  • Encouraging all Hosts and Moderators to actively open and engage with emails from your new domain during the next few days.

  • Reminding them to check their spam folders. If emails from your domain are found there, moving them to the inbox and flagging as not spam is vital for improving your domain’s reputation.

  • Ensuring that your notifications are set to As Activity Happens during this warm-up period.

Even if you have other emails sent on your domain, we still require a warm up of your subdomain specific to Mighty Networks. If you pause using Custom Email Domain and later re-enable it, you may be able to skip the warming up period.

Changing or Disabling Your Custom Email Domain

If you choose to disable your email domain, then you will see a warning popup:

Your emails will be sent from @mn.co until you add a new email domain, and you may need to repeat the warm-up process with the replacement email domain.

If you need to change your email domain, then you will see a similar warning message that you will need to restart the setup and configuration process.

Did this answer your question?