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

Create a technical support case if you need further support.

Outbound mails are queuing up after relaying outbound mails to Hosted Email Security (HES) relay servers

    • Updated:
    • 9 May 2014
    • Product/Version:
    • Hosted Email Security 1.9.8
    • Hosted Email Security 2.0
    • Platform:
    • Not Applicable N/A
Summary
HES users can relay their outbound mails to HES relay servers to scan for outbound mails. When the relaying MTA sends an email to an invalid domain or invalid email address, HES relay servers return a 450 temporary error code and allow the sending MTA to retry sending the mail.

In some similar instances, users find that the mails to invalid domains/addresses queue up in the mail server and cause other valid mails to be delayed.

In addition, the SMTP logs show that the customer’s mail server attempts to connect to the same relay server almost every minute:
 
        2009-10-13 18:53:23 216.99.131.12 OutboundConnectionResponse SMTPSVC1 SPI-EXCH1 - 25 - - 450+4.1.2+<unknownuser@invaliddomain.com>:+Recipient+address+rejected:+Domain+not+found 0 0 83 0 10063 SMTP - -

        2009-10-13 18:53:28 216.99.131.11 OutboundConnectionResponse SMTPSVC1 SPI-EXCH1 - 25 - - 450+4.1.2+<
unknownuser@invaliddomain.com >:+Recipient+address+rejected:+Domain+not+found 0 0 83 0 4969 SMTP - -

        2009-10-13 18:53:28 216.99.131.9 OutboundConnectionResponse SMTPSVC1 SPI-EXCH1 - 25 - - 450+4.1.2+<
unknownuser@invaliddomain.com >:+Recipient+address+rejected:+Domain+not+found 0 0 83 0 344 SMTP - -

        2009-10-13 18:53:29 216.99.131.10 OutboundConnectionResponse SMTPSVC1 SPI-EXCH1 - 25 - - 450+4.1.2+<
unknownuser@invaliddomain.com >:+Recipient+address+rejected:+Domain+not+found 0 0 83 0 343 SMTP - -

        2009-10-13 18:54:30 216.99.131.12 OutboundConnectionResponse SMTPSVC1 SPI-EXCH1 - 25 - - 450+4.1.2+<
unknownuser@invaliddomain.com >:+Recipient+address+rejected:+Domain+not+found 0 0 83 0 844 SMTP - -

        2009-10-13 18:54:31 216.99.131.11 OutboundConnectionResponse SMTPSVC1 SPI-EXCH1 - 25 - - 450+4.1.2+<
unknownuser@invaliddomain.com >:+Recipient+address+rejected:+Domain+not+found 0 0 83 0 344 SMTP - - 
Details
Public
By default, if an email could not be sent and a “450” error code is returned, Exchange 2007/2010 will try to send the mail for a period of 2 days. It will only stop the retry when the expiration timeout is met and the mail still could not be delivered. At this point, a permanent Non-Delivery Receipt (NDE) is sent to the sender.
Also, if the Exchange Server tries to route and receives a “4xx” error, the Exchange transport goes into a state known as “glitch retry”. In this state, Exchange Server waits for 60 seconds before attempting to resend the message, and then repeats this process three times before re-sorting.
To resolve the outbound mail queuing issue, please lower the expiration timeout of outbound mails via Exchange Server configuration. Lowering this setting will allow messages to invalid domains expire faster and be removed from the outbound retry queue.
Do the following:
For Exchange 2007/2010
  1. Open the Exchange Management console.
  2. Do one of the following:
    • If Edge Transport Server is installed on the computer:
      1. Click Edge Transport.
      2. Right-click the server name and select Properties.
      3. Click the Limits tab.
      4. Under Message Expiration section, lower the value for the Maximum time since submission (days) field.
    • If Hub Transport is installed on the computer:
      1. On the left pane, expand Server Configurations.
      2. Click Hub Transport.
      3. Right-click the server name and click Properties.
      4. Click the Limits tab.
      5. Under the Message Expiration section, lower the value for the Maximum time since submission (days) field.
  3. Increase Exchange glitch retry interval. Refer to the Microsoft article: Configure Message Retry, Resubmit, and Expiration Intervals
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1054966
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.