In This Article
About This Task
When managers or admins assign lessons, learners are notified by email; and those email notifications appear as though they came directly from the manager herself. This enables learners to reply to their manager with any questions or concerns.
Depending on the strictness of your company's email settings, however, these messages may be treated as spam. That's because they originate from Seismic Learning, not the manager's email account.
This is a common problem for apps that send email notifications, but following the steps below will ensure that learners receive assignment notifications as intended.
Sender Policy Framework
Sender Policy Framework (SPF) DNS records identify who is allowed to send emails on your domain's behalf. Without SPF protection, it would be easy to spoof anyone's email address and make it look like a malicious email is from someone the recipient trusts.
Learning sends emails on behalf of managers when they assign learning content. For example, suppose Aaron, a manager, assigns a lesson to Steve, a learner. Learning sends an email from firstname.lastname@example.org to email@example.com notifying Steve of the assignment. When this happens, the email is marked as being sent from seismic.com on behalf of example.com. If the SPF DNS record for example.com is not set up to allow seismic.com to send emails on its behalf, then the recipient's email server may assume this email is spam.
Adding seismiccom to Your SPF Record
To allow seismic.com to send emails on behalf of example.com, an SPF entry must be present in example.com's DNS record. These are text entries that may look like this:
example.com. IN TXT "v=spf1 include:m.seismic.com ~all"
Additional senders are easy to add to an existing SPF record; just list each one in the same record:
example.com. IN TXT "v=spf1 include:_spf.google.com include:m.seismic.com ~all"
The example above allows Learning to send emails on behalf of example.com. To be clear, the domain to include is:
DomainKeys Identified Mail
DomainKeys Identified Mail (DKIM) allows an email system to verify that a message received from a particular domain was indeed sent by the owner of that domain. Learning signs all email notifications using DKIM keys. To verify the authenticity of these emails, you (or more likely, your email system) can check the message's DKIM signature against our DKIM public keys.
These keys are made public as TXT-type DNS records on the subdomains s1._domainkey.seismic.com and s2._domainkey.seismic.com.
Currently, the s1._domainkey.seismic.com record reads:
k=rsa\; t=s\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCnIo1zyP/0vzEGusrGEDK1RI3CXK34gRVwWIRkynEGnD+gdcomJvaCQ2d9vHLi1MaDFtLt+WQfOIcdEw+ZFhICQ4S/mr2luO4yT/MzUxw9QpqT4zyp8EzIZkoMFY28OpNuynW4lfQyq9VMGEn0jCMRN8OEreBtnp9IvN97LVtZ8QIDAQAB
The s2._domainkey.seismic.com record reads:
k=rsa\; t=s\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDpDCE+FicPuc28f0mppTrjpIHMXo2RQw3wFWU/R5xn657Frh4zF3XSCVkin4R9ZgxUAS/TDQwC5wLf3Y7EmuQZtZVwlrRZEkpMaGUsE8Rn9nuAlNWvSZuxYXz+BoB2cs/iHHEfK4zgb5C/Z+GQk9YhOZuaGUbOEqxJ9xt6BlcigwIDAQAB
For more information on DomainKeys Identified mail, see dkim.org.
Dedicated IP Address
Our email comes from the following IP address: 220.127.116.11
If SPF and DKIM aren't options, or if you've set them up but Learning emails are still being filtered as spam, disable the "Send assignment emails from assignor" setting. This option can be found in the Settings menu (the cog icon in the upper right), under Notifications.
By changing this option, Learning will send notifications as firstname.lastname@example.org instead of the person making the assignment.
Questions? Contact the Support team at email@example.com