Skip to main content
MichaelTorres
Staff
Staff
April 21, 2025

Troubleshooting Tip: In FortiGate VMs PAYG licenses default SMTP server from Fortinet stops working after upgrading to v7.4.4

  • April 21, 2025
  • 0 replies
  • 903 views
Description This article describes a behavior where the default SMTP server stops working after upgrading to v7.4.4.
Scope FortiGate PAYG VMs use the default Fortinet SMTP server.
Solution

Users have the default SMTP server in the FortiGate Configuration

 

config system email-server
    set server "fortinet-notifications.com"
    set port 465
    set security smtps
end

 

After upgrading to v7.4.4 the SMTP default server stops working due to the modifications included and explained in Technical Tip: Default email server changes and unable to send alert email due to no valid support.

 

In the GUI, users start seeing the following message: 'The default server is only available for registered devices with a valid entitlement'.

 

Screenshot 2025-04-18 191358.png

 

Solution:

Upgrade to v7.4.5 or v7.6.0.

 

Note:

After upgrading FortiGate to the recommended versions, users may continue seeing the warning notification in the GUI. 

However, in CLI, users can verify that the mails are correctly sent:


from:fortinet-notifications.com user:DoNotReply@fortinet-notifications.com
mail_info:
reverse path:DoNotReply@fortinet-notifications.com
user name:DoNotReply
=== send len: 489
session: 0x563194ae9770, rsp_state: data2, code: 250
session: 0x563194ae9770, rsp_state: quit, code: 221
session finined
_session_on_destroy
<== send mail success, m = 0x563194b19cc0 s = 0x563194ae9770

 

The GUI Issue is currently under internal investigation.

 

This has been documented in Default email server available to registered devices with FortiCare - FortiOS v7.4.4 release notes.