Configure the Critical Events Report mail template
The server Critical Events Report email is sent once a day listing the Critical Event Check results for all of the Client's servers.
We recommend you make a copy of the default template before making any template changes.
To configure the Critical Events Report mail template:
- On the N-sight RMM Dashboard, go to Mail Templates > Critical Events Report Mail
- Enter the From address the Reports are to come from. We recommend you use the format, Descriptive Name <Email Address>, to ensure acceptance by all email clients.
- Enter the information for the Subject line, Plain Text Message, and HTML Text message
All content changes must be applied to both the Plain Text Message and the HTML versions.
- Click OK to save
You can use substitution strings in the email template. See the Substitution String information below or see Mail Template Substitution Strings .
HTML Body Editor
When you edit the body of the email, you can change both the Plain Text and HTML versions. For greater flexibility, when you configure the HTML version of the template there is a visual WYSIWYG (What You See Is What You Get) and an HTML Source editor.
To use the HTML Source Editor:
- Click the HTML button above the HTML body
- Edit the HTML in the to open the HTML Source Editor
- Click Update to save and return to the Mail Template dialog
- Review the HTML changes in the WYSIWYG editor
- After making any further changes click OK to save the template
Substitution Strings (Wildcards)
Substitution strings replace the wildcard entered in the template with the corresponding value from the database so you can replace generic terms and provide a more personalized message containing your Client's Dashboard details and other information.
Templates support substitution strings in their From address, Subject line and Body (both text and HTML).
To include substitutions strings in a template:
- In the template you are configuring, select where to add the string in the template's From address, Subject line or Body
- Choose the substitution string from the drop-down. Only those supported in the selected template field are displayed.
- Click Insert Code to insert the string at the selected spot
- Click OK to save the template
If you add substitution strings in the template body, we recommend you insert the string in the Plain Text Message and the HTML versions.
The following substitution strings are available for the Critical Events Report email:
|Variable||Substitution String||Supported in From address?||Supported in Subject line?||Supported in Body?||Note||Example|
|Account Name||#ACCOUNT#||Yes||Yes||Yes||Dashboard Name||
|Client Name||#CLIENT#||Yes||Yes||Yes||Dashboard Client Name||
|Report Content||#CONTENT#||No||No||Yes||Lists the Critical Events discovered on|
|Report Attachment||#ATTACHMENT#||No||No||Yes||Includes the report as an attachment to the email|
|Date Generated||#DATE#||No||No||Yes||Date and time of Report||
|Logo Image||#LOGO_IMG#||No||No||Yes||Dashboard and Dashboard Report logo image|
|Tagline Image||#TAG_IMG#||No||No||Yes||Dashboard and Dashboard Report footer image|
SPF Records and the Allowed List
Changes to the template From address, for example to an email address from your domain, can result in the email being classified as coming from a spoofed domain.
To avoid this situation, we recommend you create an SPF record in your domain DNS pointing to our mail generating servers. For more information on spoofed emails and SPF, see SPF Records.
To avoid potential delivery problems, if you retain the default email From address, we recommend you allow our email generating servers IP addresses. For more information, see Allow mail server IP Addresses.
From Address Format
The N-sight RMM Dashboard supports the use of commas as separators when you configure multiple email recipients. If the From address contains a descriptive name with a comma, or the possibility of a comma when using substitution strings, we recommend you encapsulate the name in inverted commas " ". For example:
- "Descriptive, name" <firstname.lastname@example.org>
- "#ACCOUNT#" <email@example.com>
- "#CLIENT#" <firstname.lastname@example.org>