Messages: Email Sending Domain

Connecting a email sending domain to your Raisely site can be a great way avoid emails falling into spam folders and improve your branding.

Skip Ahead To

Why setup an email sending domain

Setting up email sending domain

Common issues with verifying a sending domain

FAQ’s

Why setup an email sending domain

Email sending domains allow you to send emails within Raisely from your own domain. Instead of the Raisely default raiselysite.com, emails can be sent from your domain (eg. contact@charity.com). 

Emails sent through a connected domain are less likely to be caught in spam filters, and will arrive in the recipients inbox with a verified signature. 

Though you can have individual custom domains for campaigns, you can only have a single email sending domain since Raisely Messages is universal across all campaigns. Common emails used include:  contact@charity.com,  info@charity.com,  support@charity.com

Setting up email sending domain

The following steps are a guide to setting up your email sending domain. Settings in your DNS may vary depending on your domain provider/manager.

1. From the sidebar select Settings > Email Sending Domain
2. Enter your chosen sending email and select Configure

The popup will now prompt you with 3 steps to configuring your email domain.

1. Domain Login
   • Login to domain provider's website and open DNS settings on one browser tab (You'll want to have the Raisely Admin open on another browser tab).
   • Select Done in Raisely to progress to the next step. This should reveal the DNS records you need to add to your domain provider's website.
2. Add Records
   • In your domains DNS settings, add new records & save
   • Use the popup within Raisely to determine the Type, Name, & Value of the records.
   • TTL values can be left at the defaults.
   • Once finished, select Verify from within Raisely.
3. Wait for Verification
   • Your DNS settings are now verifying. This process can take up to 24hrs, and happens in the background. Simply select Got it to exit.

Once the DNS changes are verified, you’ll be notified via email and the status in the sending email will change from pending to complete. 

Removing Email Sending Domain

To remove an existing email sending domain,

1. From the sidebar, simply select Organisation > Email Sending Domain
2. Select the Trash Icon next to your sending domain, and select Remove to confirm

Common Issues with Verifying a Sending Domain

Here are some common issues and ways to troubleshoot problems with verifying your custom sending domain.

TXT - krs._domainkey.domainname not verifying

Each time you disconnect and reconnect your sending domain, the value you'll need to verify will be re-generated. This means you'll want to copy the new value and add that your DNS record. Do not use any previously supplied records as the verification will fail if so.

TXT - SPF record not verifying

There are two reasons why a SPF record verification might fail:

1. You have multiple SPF records added to a single domain name

A domain can only have one SPF record. Though you can chain multiple values into a single record, you can't have multiple separate records. So you'll want to combine the records like so:

Example of multiple records chained

v=spf1 include:raiselysite.com include:anotherrecord.com include:anotherrecord2.com ~all

2. You have  too many records chained in a single SPF record

SPF records can have a maximum of 10 lookups. This takes into consideration any individual record that might have records nested within. You can use a free tool like SPF Record Checker and Lookup to check if you have too many records chained. 

There are three options here you can consider if so:

• Reduce the number of records chained
• Use a separate custom sending domain to verify with Raisely
• Use a subdomain to verify with Raisely. For example, instead of verifying info@charity.com, you could verify info@fundraise.charity.com. You will then add the necessary records to fundraise.charity.com

CNAME record not verifying

This usually happens if you have multiple CNAME records added to the custom domain. You can only have one CNAME record per custom domain.

"Domain already exists" error message

There are two reasons why this error might appear:

1. You've previously tried to connect the same domain, but the verification was unsuccessful. In those instances, Raisely Support can look into our server to see if the record exists and delete it.

2. The same domain has been verified but with a different server. This can happen with large organisations where they may have an external IT provider/Vendor helping them to manage their custom domains. If Raisely is unable to locate the custom domain in our server, you'll need to reach out to your internal team or verify a different custom domain with Raisely

FAQ

### accordion

## expand

# I am using Cloudflare for my DNS, and the verification in Raisely fails.

If you are using Cloudflare for your DNS, make sure the 'Proxy Status' (cloud icon) is set to DNS only for the CNAME record.

## expand

### accordion

Cannot find the support guide you are after? Head on over to our YouTube channel 📺 for more creative content to help you go further. You can even leave us comments, suggesting new content ideas.