Timeouts for Email.cloud SMTP transmissions

Products

• Email Security.cloud

Issue/Introduction

Timeout occurs when defined value has been reached in each of the phases listed bellow:

1. If the MTA does not exist or there is no return from the connected system call, an error message will be issued stating
              421 4.4.0 [internal] no MXs for this domain could be reached at this time.

2. An error code of 450 4.4.1 [internal] Connection Timed Out will be issued if any one of the following occur:

•  There is no response to the EHLO command.
•  There is no response after MAIL FROM has been issued.
•  There is no response to the RCPT TO command.
•  There is no response to the DATA command.
•  There is no returned data after the 220 OK response.
•  There is no response when RESET is issued.
  

Resolution

The timeouts for Email.cloud are as follows.

Client/Sender to ESS Service
Connect_Timeout = 240 sec / 4 min
EHLO_Timeout = 240 sec / 4 min
Mailfrom_Timeout = 240 sec / 4 min
Rcptto_Timeout = 240 sec / 4 min
Body_Timeout = 240 sec / 4 min
Rset_Timeout = 240 sec / 4 min
Idle_Timeout = 240 sec / 4 min

ESS Service to Client/Recipient
Connect_Timeout = 60 sec / 1 min
EHLO_Timeout = 300 sec / 5 min
Mailfrom_Timeout = 300 sec / 5 min
Rcptto_Timeout = 300 sec / 5 min
Body_Timeout = 600 sec / 10 min
Rset_Timeout = 300 sec / 5 min
Idle_Timeout = 5 sec