Configure SPF Records for N-sight RMM
When you change the From address in your Mail Templates, for example to an email address from your domain, it can result in the email being classified as coming from a spoofed domain. Your recipients may fail to receive the email because of filtering intended to prevent email address spoofing.
If you use a custom From address in a mail template, you must ensure the address exists. If the From address does not exist, our sender verification check may fail.
You can set up Sender Policy Framework (SPF) for the domain to help prevent spoofing. SPF is an email authentication method to prevent spammers from sending messages on behalf of your domain. An SPF record lists all authorized hostnames / IP addresses that are permitted to send email on behalf of your domain.
To ensure emails generated by N-sight RMM are accepted by your recipient’s mail exchangers as originating from a valid host, we recommend you set up SPF for the N-sight RMM.
Set up SPF for N-sight RMM
If you have an existing SPF record, ensure the following is added between v=spf1 and -all:
include:_spf.remote.management
If you do not have an SPF record, you need to create a TXT record (DNS record type 16) with the following data:
v=spf1 include:_spf.remote.management -all
The record must contain:
| Component | Description |
|---|---|
| v=spf1 | Version of the SPF record |
| include:_spf.remote.management | Allows use of the N-sight RMM server SPF record |
| all | The all mechanism is required but you can select the following options:
|
When the SPF record is written, publish the SPF record (TXT record) to the authoritative DNS server for your domain. Instructions on how this can be done will differ from each domain provider. For assistance, please contact your domain provider.
If you have an email security firewall in place, we recommend you allow our mail server for N-sight RMM.
What do you want to do?