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

Create a technical support case if you need further support.

Unable to deliver emails to the second or third MX servers

    • Updated:
    • 12 Oct 2015
    • Product/Version:
    • InterScan Messaging Security Suite 7.1 Windows
    • InterScan Messaging Security Suite 7.5 Windows
    • Platform:
    • Windows 2003 Enterprise Server
    • Windows 2003 Standard Server Edition
    • Windows 2003 Standard Server Edition 64-bit
    • Windows 2008 Enterprise Server
    • Windows 2008 Enterprise Server Edition 64-bit
    • Windows 2008 Standard Server Edition
    • Windows 2008 Standard Server Edition 64-bit
Summary

The messages sent to domain A with multiple mx records are not delivered, returned, and marked as undeliverable once the retry limit is reached. The first MX server for domain accepts a TCP connection. However, it does not respond with an SMTP banner.

After the InterScan Messaging Security Suite (IMSS) times out, it fails to try the second or third MX server for this domain. It attempts to deliver via the first MX server again, repeating the same process until the maximum number of delivery attempt expires.

Details
Public

This issue happens because IMSS is designed that way. If IMSS can establish the initial connection but failed to send the mail, IMSS will not try to send it to the next MX or A record. However, if IMSS already has problems connecting to the downstream MTA (e.g. TCP handshake failed) or it received a 4xx response, then IMSS will try to send the mail to the next MX or A record.

If there is just a delay sending the SMTP banner, you may increase the "IdleWaitingSecond" value to "300" (5 mins) as a workaround. This allows IMSS to wait until it receives a response from the remote MTA server.

  1. Go to the ..Program Files\Trend Micro\IMSS\ config folder.
  2. Locate and back up the tsmtpd.ini file.
  3. Open the original tsmtpd.ini file using a text editor.
  4. Look for the "IdleWaitingSecond=30" parameter and change the value to "60".
  5. Make sure that the "#" sign is removed to enable the parameter.
  6. Save and close the file.
  7. Restart the following services:
    • Trend Micro IMSS SMTP service
    • Trend Micro Scanner service

If there is no banner response being sent back, or if the respond takes too long (more than 5 minutes), you can create a smarthost entry for domain A, and then assign the second and third MX record IP to prevent IMSS from sending mails to slow-responding MTA.

Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1057418
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.