Notifications Page 72 FortiRecorder 2.4.2 Administration Guide
2. Click New.
3. Configure the following setting and then click Create.
4. To verify email connectivity, from FortiRecorder, trigger an alert event that matches the type
and severity levels that you have chosen. Then, check your email.
If you do not receive an alert email within a few minutes, verify that you have configured an
email address for the account. Next, verify the FortiRecorder NVR’s static routes (see
“Configuring the network settings”) and the policies on any firewalls or routers between the
appliance and the SMTP relay. (They must allow SMTP traffic from the FortiRecorder
network interface that is connected to the gateway between it and the email server.) To
determine the point of connectivity failure along the network path, if the SMTP server is
configured to respond to ICMP ECHO_REQUEST (ping), go to Monitor > System Status >
Console and enter the CLI command:
execute traceroute <syslog_ipv4>
where <syslog_ipv4> is the IPv4 address of your email server.
If that connectivity succeeds, verify that your alert email has not been classified as spam by
checking your junk mail folder.
See also
• Connectivity issues
Setting name Description
Name Enter a name for the notification entry.
Description Optionally enter a descriptive comment.
Enable Select to enable this notification entry.
Trigger number Specify how many times the motion event should happen before
the notification is sent out.
Trigger period Specify the period in which these motion events occur.
Message method Select how the notification should be sent out: either Email or
SMS. At least one method should be selected.
Notification Period Specify when notifications should be sent out. For details, see
“Configuring schedules” on page 28.
Select Camera Specify which camera’s motion events should be notified.
Select User Specify which user should be notified.
To prevent classification as spam, it usually helps to add the FortiRecorder NVR’s email address
to your address book.