Description | This article describes when the two-factor authentication email code has been set up properly but never received. This issue can be identified from the debug log. |
Scope | FortiGate v7.0. |
Solution |
The email server configuration on FortiGate has been set up properly but never received.
get system email-server
To check more details by running the commands below:
diagnose debug console timestamp enable diagnose debug application sslvpn -1 diagnose debug application fnbamd -1 diagnose debug application alertmail -1 diagnose debug enable
2024-07-02 14:18:20 [786] create_auth_token_session-Created auth token session 1738883391 2024-07-02 14:18:20 mail_info: ...... 2024-07-02 14:19:25 details: M.14 <donotreply@notification.fortinet.net>... Non-local sender is not allowed to relay when SMTP Auth passed <- Send mail failed caused by the local mail server is not allowing a non-local sender (DoNotReply@notification.fortinet.net). 2024-07-02 14:19:25 session: 0xa8413a0, rsp_state: quit, code: 221
Modified the email sender (same local domain) under the setting below and the email two-factor authentication code can be received from the email server.
config system email-server end
|
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.