Created on
10-21-2024
12:40 AM
Edited on
10-16-2025
10:19 PM
By
Anthony_E
| Description | This article describes local report scheduled email configuration and troubleshooting commands. |
| Scope | FortiGate. |
| Solution |
Before configuring the local reports, it needs to be enabled from System -> Feature Visibility -> Local Reports.
The local Reports tab will now be available under Log & Reports -> Local Reports.
To configure the scheduled email report:
The commands below should be executed in a global VDOM:
config system email-server
Note: Starting from v7.4.4, the default email server has been switched from notification.fortinet.net to fortinet-notifications.com. This default server is only available to registered devices with an active FortiCare support contract. The reply-to field in the source email is automatically updated to DoNotReply@fortinet-notifications.com for all servers, including custom ones.
If the email is not received, troubleshooting will be based on Troubleshooting Tip: Email alert
diagnose debug reset diagnose debug console timestamp enable diagnose debug enable
When using the default Fortinet SMTP server, the email alert debug log may indicate that the email was sent successfully, even if the email is not received:
2024-09-02 12:16:15 <== send mail success, m = 0x963e590 s = 0x9640380
In such cases, verify that the username under the alert email settings is correctly set to 'DoNotReply@fortinet-notifications.com' as this setting is required for proper operation when using the default SMTP server.
Note: Local reports are only available on FortiGates that have local disk storage. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.