Troubleshooting Tip: How to debug FortiManager workflow email
Description
This article describes the debug commands to run to debug FortiManager Workflow emails.
Scope
FortiManager.
Solution
Make sure the correct email address is added to the admin user under: System Settings -> Administrator -> Edit a user -> Meta Fields -> 'Contact Email'.
For FortiManager Cloud, the Meta Fields are not shown on the GUI, but can be set under CLI:
config system admin user
edit "<USER>"
config meta-data
edit "Contact Email"
set fieldvalue "<EMAIL_ADDRESS>"
next
end
next
end
- If workflow emails are not received or to verify if FortiManager is sending out the emails, run the following diagnostic commands:
diagnose debugs application alertmail 255
diagnose debug enable
- In FortiManager GUI, submit the workflow for approval.
- The debug commands will populate, showing the TLS handshake and the full body of the email as HTML.
Sample output:
FMG-VM64 # diagnose debug application alertmail 255
FMG-VM64 # diagnose debug enable
FMG-VM64 # handle_workflow_notification:recv:{ "adom": "root", "subject": "[FortiManager 'FMG-VM64'] Workflow session 5 in adom
'root' was submitted for approval by 'test_admin'", "datafile": "\/var\/tmp\/workflow_root_5_request_9ckXDW",
"attachfile": "\/var\/tmp\/FMG-VM64_root_workflow_5_test_admin_diff.html" }
mail_info:
server:notification.fortinet.net from:DoNotReply@fortinet.com
mail_info:
reverse path:DoNotReply@fortinet.com
auth:enabled
user:DoNotReply
from:DoNotReply
passwd:
to[0]:[user@domain.com]
<==_init_mail_info
*** Host notification.fortinet.net:465 was resolved.
*** IPv6: (none)
*** IPv4: 208.91.114.151
*** Trying 208.91.114.151:465...
*** TLSv1.3 (OUT), TLS handshake, Client hello (1):
*** TLSv1.3 (IN), TLS handshake, Server hello (2):
*** TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
*** TLSv1.3 (OUT), TLS handshake, Client hello (1):
*** TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
*** TLSv1.3 (IN), TLS handshake, Server hello (2):
*** TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
*** TLSv1.3 (IN), TLS handshake, Request CERT (13):
*** TLSv1.3 (IN), TLS handshake, Certificate (11):
*** TLSv1.3 (IN), TLS handshake, CERT verify (15):
*** TLSv1.3 (IN), TLS handshake, Finished (20):
*** TLSv1.3 (OUT), TLS handshake, Certificate (11):
*** TLSv1.3 (OUT), TLS handshake, CERT verify (15):
*** TLSv1.3 (OUT), TLS handshake, Finished (20):
------[OUTPUT OMITTED]------
--> MAIL FROM:<DoNotReply@fortinet.com>
<-- 250 2.1.0 <DoNotReply@fortinet.com>... Sender ok
--> RCPT TO:<user@domain.com>
<-- 250 2.1.5 <user@domain.com>... Recipient ok
--> DATA
<-- 354 End data with <CR><LF>.<CR><LF>
--> To: user@domain.com
From: DoNotReply@fortinet.com
Subject: [FortiManager 'FMG-VM64'] Workflow session 5 in adom 'root' was submitted for approval by 'test_admin'
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="chunk_fgmail_x1_1769892684"
Content-Transfer-Encoding: 7bit
------[OUTPUT OMITTED]----------
<table class='content'>
<!DOCTYPE html>
<html>
<head>
<title>Workflow Session</title>
<style>
* {
font-size:10pt;
}
h4 {
font-family:'Georgia', serif;
margin-bottom: 1ex;
margin-top: 1ex;
}
td.t1 {
text-align: right;
font-family:'Georgia', serif;
}
td.t2 {
font-family:'Verdana', sans-serif;
font-weight: bold;
}
------[OUTPUT OMITTED]------
<td>4</td>
<td>test_admin</td>
<td>submit</td><td>2026-01-31 12:51:21 PST</td>
<td align=left></td></tr>
</table>
</td></tr>
</p>
</table>
</body>
</html>
------[OUTPUT OMITTED]------
<-- 250 2.0.0 60VKpOVp021604-60VKpOVq021604 Message accepted for delivery29w
*** Connection #0 to host notification.fortinet.net left intact
curl_send_mail: curl_easy_perform successfully.
send mail 0x561dd1efbb90 session (nil)
- To disable the debugs:
diagnose debug disable
diagnose debug reset
Related documents:
Mail Server
Workflow Mode
Technical Tip: Configuring FortiManager and FortiAnalyzer to use GMAIL
Technical Tip: How to set up Email Notifications with notification.fortinet.net
Technical Tip: How to send alerts with Gmail, when using Workflow on FortiManager