This article explains how to configure the platform to send emails from SMARTFENSE's servers, and what information you need to provide to the client's IT team to ensure correct message delivery.
When to use the SMARTFENSE email server
The SMARTFENSE email server is the option selected by default under Settings > Email server. With this configuration, welcome emails, content assignment notifications, reminders, and system notifications are sent from SMARTFENSE's infrastructure.
If the client's organization has strict email filters, block lists, or quarantine rules, emails may not reach users. Configuring the whitelist prevents this issue.
For better adherence to the awareness program, we always recommend configuring your own email server. Emails sent from the organization's own domain build greater user trust and reduce delivery friction. See the article How to configure your own email server in SMARTFENSE for more information.
Configuration in SMARTFENSE
- Sign in to SMARTFENSE with an administrator account.
- Go to Settings > Email server.
- Select the SMARTFENSE email server option and click Next.
- Fill in the Reply to field with the email address to which end users' replies to platform notifications will be directed.
- Click Save.
The address defined in Reply to must belong to the organization and should be checked frequently, as end users often reply to platform emails with questions, requests for assistance, or feedback.
Whitelist data
Emails are sent from the account info@mail-takesecurity.com. The client's IT team must authorize the sending domain and IPs to ensure delivery.
Sending domain
| Domain |
|---|
| mail-takesecurity.com |
Fixed sending IPs
| IP |
|---|
| 52.16.33.192 |
| 50.6.200.66 |
| 160.153.250.248 |
| 190.210.135.44 |
What to configure on the client's email server
The client's IT team must perform the following actions depending on their infrastructure:
- Add the domain mail-takesecurity.com to the safe senders list.
- Authorize the four listed IPs in the firewall rules or inbound email filtering policies.
- If using Microsoft Exchange Online or Google Workspace, create a connector or transport rule that accepts messages from those IPs and that domain.
- Check that no quarantine rules or blocklists are blocking the domain mail-takesecurity.com.
If users report not receiving SMARTFENSE emails, the first diagnostic step is to check the spam or quarantine folder and confirm that the domain and IPs are on the whitelist.
💡 Best practices
- For better adherence to the awareness program, configure the Own server option instead of the SMARTFENSE server: emails sent from the organization's own domain build greater user trust and improve open and engagement rates. See the article How to configure your own email server in SMARTFENSE.
- Share the sending domain and IPs with the client's IT team before the first campaign launch, to prevent delivery issues from the start.
- Use a Reply to address that belongs to the organization and is checked regularly, as end users often reply to platform emails with questions.
- Ask the IT team to confirm that the whitelist has been applied before sending mass emails.
- If the client uses Microsoft Exchange Online, consider configuring an inbound connector that explicitly accepts messages from mail-takesecurity.com.
- For persistent delivery issues, ask the IT team for the email server's reception logs to identify the cause of the block.