If staff at your district haven't been receiving emails from Nimble, such as newsletters, job alerts, or account notifications, it may be because your email security system is flagging them before they reach an inbox. This article is for your IT or network administrator and walks through how to make sure Nimble's emails get through.
Why this happens
Districts often use email security gateways that screen incoming messages for spam or phishing risk. Because Nimble sends a high volume of email to many recipients across your organization, some gateways flag those messages even though they're legitimate. Adding Nimble as a "safe sender" or "allowed sender" tells your system to stop screening our emails.
What to allowlist
Ask your IT team to add the following to your organization's safe senders or allow list:
Sending domain: hirenimble.com and email.hirenimble.com
Authentication records: Nimble's email is authenticated with SPF, DKIM, and DMARC. If your gateway supports allowlisting by authenticated domain rather than by IP address, that's the most reliable method.
A note on newsletters specifically
Our newsletter is sent through a tool called HubSpot, not directly from a Nimble email account. It will still look like it's coming from hirenimble.com, so no extra setup is needed on your end.
If your IT team flags that the sending server doesn't quite match our domain, or asks for a specific IP address to allowlist, that's normal and expected with how these newsletter tools work. Just reach out to [email protected] and we'll help you sort it out.
Questions?
If you're still not receiving Nimble communications after adding us to your safe senders list, reach out to [email protected] and we'll help investigate further.