Customize the sender email address for notifications (no-reply@360learning.com)

  • Updated

Configure a custom sender email address for notifications

By default, notifications are sent from the email address no-reply@360learning.com. You can replace it with an email address that you own (for instance, an email from your custom domain).

An admin from a private group may change the email address for the notifications of their group. A platform admin may change the email address for the notifications of the platform, and any private group.

Email notifications sent by the classroom block in a program must be sent by no-reply@360learning.com. You cannot customize that email address.

Before you begin, choose a custom email address where you can receive emails. During the configuration below, you'll need to verify the address by clicking a link sent by Amazon Web Services (AWS).

To configure a custom sender email address for notifications:

  1. In the left sidebar, click on a group.
  2. At the top right of the main section, click settings.svg Settings.
  3. In the left sidebar, click Advanced.
  4. In the field Customize the sender email address for notification emails, enter the new email address, then hit the ↵ Enter key.
  5. Below the field, click Validate the status of your sender email address.
  6. Click SEND VALIDATION EMAIL.
  7. Keep the tab open.
  8. In parallel, open the email inbox of the corresponding email address.
  9. Open the email called Amazon Web Services - Email Address Verification Request, sent by AWS.
  10. Click the validation link in the email (expires in 24 hours). You'll be redirected to an AWS page, and your email will be verified unless the page indicates otherwise.
  11. Go back to your 360Learning platform and click REFRESH STATUS.
  12. The new email address is live when the status shows Verified.

You can restore the default email address (no-reply@360learning.com) by deleting the new email address in the text field.

After you’ve verified your email address, we recommend setting up DKIM (DomainKeys Identified Mail) to keep your emails safe and improve deliverability. While optional, setting up DKIM may be required by your IT team for internal email delivery or if you send 5000 emails in a day, even occasionally. Learn more in Configure DKIM for your custom email sender address.

Name displayed as the sender of email notifications

The name displayed as the sender of notifications depends on the type of notifications.

  • If it's a post: the name displayed as the sender of the mail is the name of the author of the post.
  • If it's a like (on a post): the name displayed as the sender of the mail is the group from where the "like" was done.
  • For all other emails: the name displayed as the sender of the mail is the name of the highest-level private group to which the recipient belongs.

    • If the recipient does not belong to any private group (for example, if they only have the administrator role in a public group and no learner role), the name displayed as the sender of the mail is that of the lowest level private group above all the recipient’s groups.

Configure DKIM for your custom sender email address

If you’ve customized the sender email address for notifications, we recommend setting up DKIM↗ (DomainKeys Identified Mail). DKIM adds a digital signature to emails sent from your domain, verifying they are legitimate and secure. This helps ensure that notifications from your 360Learning platform, sent via AWS, reach inboxes and aren't marked as spam. Configuring DKIM also aligns with the latest security requirements of major email providers like Gmail↗ and Yahoo↗.

Before you begin:

  • Ensure your custom sender email address for notifications is verified. For more information, see Configure a custom sender email address for notifications.
  • Make sure you or your IT team can access your DNS (Domain Name System) settings to add the required DKIM records within 72 hours of generation.

To configure DKIM:

  1. In the left sidebar, click on the group with the custom sender email address for notifications.
  2. At the top right of the main section, click settings.svg Settings.
  3. In the left sidebar, click Advanced.
  4. In the Configure your DomainKeys Identified Mail (DKIM) section, click DOWNLOAD .CSV RECORD SET.
  5. Share the CSV file with your IT team and ask them to add the 3 CNAME records from the CSV file to your DNS settings within 72 hours. Below are links to instructions for adding CNAME records for popular DNS providers:
  6. After your IT team updates the DNS, wait up to 72 hours for the DNS changes to take effect. This is because DNS updates can take time to propagate globally, depending on the caching policies of your DNS provider.
  7. Go back to your group's advanced settings on 360Learning and click CHECK DKIM STATUS. The status can show:
    • Not Started: The records haven’t been downloaded yet.
    • Pending: The records were downloaded, but DKIM verification isn’t complete.
    • Verified: DKIM setup is complete and working correctly.
    • Error: AWS couldn’t find the DNS records within the expected time. Make sure the records are set up correctly in your DNS, then click CHECK DKIM STATUS to retry verification.

When the status shows Verified, you're all set!

If you haven't added the records to your DNS within 72 hours of generation or the DKIM status shows as Error, repeat the steps above to restart the DKIM verification process.

The DKIM records are domain-specific. If you change the custom sender email address for your 360Learning notifications and it uses a different domain, you'll need to reconfigure DKIM.

Troubleshoot email delivery issues

If your DKIM status in 360Learning doesn't show as Verified after 72 hours, and you've already added the DKIM records to your DNS, try these troubleshooting steps:

  • Confirm that all 3 DKIM records from the CSV file are added to your DNS.
  • Verify values match exactly, with no extra or missing characters.
  • Double-check the fields to ensure they are correct:
    • Some DNS providers use Host or Hostname instead of Name.
    • Some DNS providers use Points to or Result instead of Value.
  • Check for DNS provider modifications:
    • Verify you've included the period (.) at the end of the DNS record to prevent your DNS provider from appending your domain name. If the domain is automatically added, remove it.
    • Make sure the underscore (_) is included in the Name field, usually in the formatselector._domainkey.yourdomain.com. If your DNS provider doesn’t allow underscores, contact their support for assistance.

If your DKIM is Verified but emails aren't reaching the inbox, try adding these additional authentication methods to your DNS:

  • DMARC↗: Helps manage how email receivers handle failed SPF or DKIM checks and provides reports on authentication issues. Contact your IT team to set it up.
  • SPF↗: Verifies that emails are sent from authorized servers for your domain. Some email providers and DMARC policies require SPF. Contact our Support team for the necessary SPF records.
  • Custom MAIL FROM↗: Allows you to specify a custom domain for the "MAIL FROM" address (the return path for bounce messages). This helps improve deliverability and ensures bounces are sent from your domain. Contact our Support team to set this up.
Check out our blog for more L&D resources.

Was this article helpful?

2 out of 6 found this helpful

Have more questions? Submit a request