Adding newsletter sender addresses

You can add multiple sender addresses for your newsletters. Add a sender address to personalize how your newsletter displays to recipients. Your sender addresses will require a display name and an email address. Your recipients will see both the display name and email address when receiving a newsletter. Application Managers or users with Application Settings Access Control can update this setting.

1. Navigate to Manage Application > Setup > Newsletters

2. Click on Sender Addresses > Add Sender

3. Add Sender name (display name)

4. Add Sender email (diplayed as the email address in email clients)

5. Click Add

Updating newsletter sender address permissions

This feature allows you to manage who can use the specific sender address in newsletters. Add or remove users who can use the sender address.

Users have to be an App Manager, or Newsletter feature owner, admin, or manager. Application Managers or users with Application Settings Access Control can update this setting.

1. Navigate to Manage Application > Setup > Newsletters

2. Click on Sender addresses

3. Click on the "All" verbiage underneath Sender permissions for that specific sender address

4. Select or deselect users who are allowed to send newsletters from that sender address.

5. Click Update access

Setting Up Newsletter Sender Domains

By default, newsletters are sent from noreply@simpplr noreply@simpplrnewsletter.com or noreply@eu.simpplr.com. Setting up a Custom Sender Domain allows you to send from your own brand (e.g., newsletters.yourcompany.com), which significantly improves open rates and brand trust.

Step 1: Adding your sender domain

To setup your sender domain, you need to be an Application Manager or have Application Settings permission via Access Control Groups. Sender domains are the domains from which a newsletter can be sent.

Add a domain and verify it with the provided DNS records to send newsletters. Not that it may take 72 hours for these changes to reflect. Simpplr uses AWS SES for sending email. Adding an MX record is mandated by SES if you want to use Custom Mail from the domain.

1. Navigate to Manage Application > Setup > Newsletters

2. Click Add domain

3. Enter your desired domain

   1. You can add multiple domains if you have multiple email domains within your organization

4. Set up Advanced mail settings

   1. We recommend creating a custom subdomain, such as 'news.' Otherwise, your newsletter sender domain will read as newsletters.yourcompany.com.

5. Click Add.

6. A new modal will pop up for you to copy DNS records. See step 2.

Step 2: Update DNS records (IT action)

Copy the values from the modal and provide them to your IT/Infrastructure team. They will need to update CNAME, MX, and TXT records for each sender domain added.

1. Copy the DNS records and send them to your IT department.

2. Click done

Here is an example of what the DNS record screen looks like:

Step 3: Sender domain is verified

Once DNS records are updated and verified, your Domain status will change from "Verification pending" to "Verified."

Technical notes

Messages that you send through Amazon SES automatically use a subdomain of amazonses.com as the default Mail from domain. Sender Policy Framework (SPF) authentication successfully validates these messages because the default Mail from domain matches the application that sent the email—in this case, SES.

If you don't want to use the SES default Mail from domain, and would rather use a subdomain of a domain that you own, this is referred to in SES as using a custom Mail from domain. To do this, it requires you to publish your own SPF record for your custom Mail from domain. In addition, SES also requires you to set up an MX record so that your domain can receive the bounce and complaint notifications that email providers send you.

Updating both MX and TXT records is necessary to:

• Authenticate the custom sender address: Ensuring that emails sent from the custom sender address are verified and trusted by recipient mail servers, reducing the risk of being marked as spam.

• Improve email deliverability: Properly configured MX and TXT records improve the chances of your emails reaching the intended recipients’ inboxes, as many email providers check these records to fight spam and phishing.

• Protect domain reputation: Ensuring that only authorized servers send emails on behalf of your domain helps maintain your domain’s reputation and prevents misuse by spammers.

• Enable proper email routing: MX records ensure that incoming emails are correctly routed to the appropriate servers, enabling seamless communication and management of the custom sender address.