Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

"Timed out while sending message body" appears in InterScan Messaging Security Virtual Appliance (IMSVA)

    • Updated:
    • 14 Sep 2015
    • Product/Version:
    • InterScan Messaging Security Virtual Appliance 8.2
    • InterScan Messaging Security Virtual Appliance 8.5
    • InterScan Messaging Security Virtual Appliance 9.0
    • Platform:
    • N/A N/A
Summary
The IMSVA server cannot send a large message on a particular domain. The mails are deferred and the following error message shows:
Lost connection with "domain" [MX IP] while sending message body
Timed out while sending message body
Details
Public
This issue occurs because the MTU size of the router/switch/server of the data to be transferred is different from the MTU size of IMSVA.
The packet is dropped when it is too large for the MTU path. Thus, the sending host retransmits the packet by fragmenting it to smaller packets. If there are too many dropped packets while retransmitting, the connection will fail and the message will not be sent.
When sending a message fails on your first attempt, MTA retries to send the message at a later time. However, the path for resending may change due to various processes (e.g. load balance, congestion, outages, etc.). At some point, the IMSVA server may find a path with enough MTU to successfully send the message to the destination server.
To resolve the issue, decrease the MTU size on the network interface of IMSVA:
  1. Log in to IMSVA via SSH.
  2. Go to /etc/sysconfig/network-scripts.
  3. Determine which interface is used by IMSVA by running the following command:
    ifconfig
  4. Identify which eth# uses the IP address for outgoing connection.
    By default, it is set to eth0 (e.g. vi ifcfg-eth0).
  5. Edit the interface ifcfg-eth# and add the parameter "MTU=1472".
  6. Save the file.
  7. Restart the network interface using the command below:
    service network restart
  8. Verify if the issue is resolved. If not, set the MTU value to a lower one (e.g. 1450, 1425, 1400, etc.) until the issue is fixed.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1102768
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.