Technical Tip: Reviewing the Log: 'Timeout Waiting For Input From x.x.x.x' During the Server CMD Read

[burakyigit]

Description	This article describes the message log: 'Timeout waiting for Input From x.x.x.x' During the Server CMD Read.
Scope	FortiMail.
Solution	The following error message means that FortiMail did not receive any input information from the sender server. Most likely because the mail server did not respond or the connection dropped. date=2024-08-07 time=09:04:38.511 device_id=FEVM010000XXXX log_id=0003027742 type=event subtype=smtp pri=notice user=mail ui=mail action=NONE status=N/A session_id="47773gCI026610-47773gCU026610" msg="timeout waiting for input from [10.40.1.73] during server cmd read" Initially, increase the IDLE timeout value on the specific session profile-associated emails: Input in CLI: config profile session     edit TEST         set conn-idle-timeout 60  <----- Default is 30. Enter a limit to the number of seconds a user may be inactive before the FortiMail unit drops the connection. Set the value between 5-1200. end When FortiMail accepted an email(clean after scan) and tries to connect to the backend SMTP server, it is possible to use the below CLI to adjust the timeout value: config system mailserver     set timeout-connect 60  <----- Default is 30. Enter the maximum amount of time to wait, after the FortiMail unit initiates it, for the receiving SMTP server to establish the network connection. The valid range is 10 to 120.     set timeout-greeting 60 <----- Default is 30.  Enter the maximum amount of time to wait for an SMTP server to send SMTP reply code 220 to the FortiMail unit. The valid range is 10 to 360. end Those are the commands to increase the timeout to the maximum value of 60 seconds.