All Collections
How to Ensure Email Deliverability
How to Ensure Email Deliverability
Ensure that learners successfully receive assignment notifications
Hannah Walt avatar
Written by Hannah Walt
Updated over a week ago

In This Article


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 Lessonly, 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.

Lessonly sends emails on behalf of managers when they assign learning content. For example, suppose Aaron, a manager, assigns a lesson to Steve, a learner. Lessonly will send an email from to notifying Steve of the assignment. When this happens, the email is marked as being sent from on behalf of If the SPF DNS record for is not set up to allow to send emails on its behalf, then the recipient's email server may assume this email is spam.

๐Ÿ’ก Important Note: the SPF specification limits the number of DNS lookups to "at most 10 per SPF check." Section 10.1, "Processing Limits", of the SPF RFC reads as follows:

"SPF implementations MUST limit the number of mechanisms and modifiers that do DNS lookups to at most 10 per SPF check, including any lookups caused by the use of the "include" mechanism or the "redirect" modifier. If this number is exceeded during a check, a PermError MUST be returned. The "include", "a", "mx", "ptr", and "exists" mechanisms as well as the "redirect" modifier do count against this limit. The "all", "ip4", and "ip6" mechanisms do not require DNS lookups and therefore do not count against this limit. The "exp" modifier does not count against this limit because the DNS lookup to fetch the explanation string occurs after the SPF record has been evaluated."

This limit prevents SPF lookups from being misused for denial of service attacks.

Adding to Your SPF Record

To allow to send emails on behalf of, an SPF entry must be present in's DNS record. These are text entries that may look like this: IN TXT "v=spf1 ~all"

Additional senders are easy to add to an existing SPF record; just list each one in the same record: IN TXT "v=spf1 ~all"

The example above allows Lessonly to send emails on behalf of 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. The Lessonly app 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 and

Currently, the record reads:

k=rsa\; t=s\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCnIo1zyP/0vzEGusrGEDK1RI3CXK34gRVwWIRkynEGnD+gdcomJvaCQ2d9vHLi1MaDFtLt+WQfOIcdEw+ZFhICQ4S/mr2luO4yT/MzUxw9QpqT4zyp8EzIZkoMFY28OpNuynW4lfQyq9VMGEn0jCMRN8OEreBtnp9IvN97LVtZ8QIDAQAB

The record reads:

k=rsa\; t=s\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDpDCE+FicPuc28f0mppTrjpIHMXo2RQw3wFWU/R5xn657Frh4zF3XSCVkin4R9ZgxUAS/TDQwC5wLf3Y7EmuQZtZVwlrRZEkpMaGUsE8Rn9nuAlNWvSZuxYXz+BoB2cs/iHHEfK4zgb5C/Z+GQk9YhOZuaGUbOEqxJ9xt6BlcigwIDAQAB

For more information on DomainKeys Identified mail, see

Dedicated IP Address

Our email will come from the following IP address:


If SPF and DKIM aren't options, or if you've set them up but Lessonly 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 unchecking this option, Lessonly will send notifications as instead of the person making the assignment.

Questions? Contact the Support team at

Did this answer your question?