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

Create a technical support case if you need further support.

Reading mail tracking log detail events in Hosted Email Security (HES)

    • Updated:
    • 24 Aug 2016
    • Product/Version:
    • Hosted Email Security 2.0
    • Platform:
    • N/A N/A
Summary

View and interpret the mail tracking log detail events in HES.

Details
Public

The events portion of mail tracking details displays the Mail Transfer Agent (MTA)-level logs and shows information on what happens to an email as it is delivered from one HES MTA server to another. The error messages displayed are directly taken from raw MTA logs; no modifications to the error messages or SMTP response codes are altered by the service. HES Support Admin accounts to view more detailed mail tracking information has been deployed to the HES production site. Mail tracking log details events are available for both incoming and outgoing traffic.

  1. Log in to the HES console.
  2. Go to Mail Tracking.
  3. Enter the query criteria.

     
    For inbound query, Recipient field is required. While Sender field is required for outbound query.
  4. Click the result timestamp. The mail tracking and event details are displayed.

    Mail tracking and event

    Click image to enlarge

  • Sample 1:

    Sample 1

    Click image to enlarge

    Interpretation:

    1. Incoming mail was received by HES inbound MTA from 66.180.82.11. HES inbound MTA forwarded this mail to Scanner.
    2. Scanner received the mail from inbound MTA .After scanning, Scanner forwarded the mail to Outbound MTA.
    3. Outbound MTA received the mail from Scanner and delivered it successfully to 125.212.43.8.
  • Sample 2:

    Sample 2

    Click image to enlarge

    Interpretation:

    Mail direction is outgoing (via Relay MTA). The mail is queued in Outbound MTA [216.99.131.35] because the host being delivered to (mx.fakemx.net) could not be resolved. The mail is queued (not bounced) because the returned SMTP error code (421) is a temporary error. Outbound MTA will keep retrying to send this mail until it expires.

  • Sample 3:

    Sample 3

    Click image to enlarge

    Interpretation:

    Mail direction is incoming (via Inbound MTA). The mail is queued in Outbound MTA [216.99.131.78] because the sender’s domain name (fotocasa.es) could not be resolved. Again, the SMTP error code returned (450) is temporary; hence, mail is queued and retried for delivery.

  • Sample 4:

    Sample 4

    Click image to enlarge

    Interpretation:

    Incoming mail delivery (via Inbound MTA). Outbound MTA cannot deliver the mail due to customer's wrong configuration in their mail server. Returned with SMTP error code (530) which is permanent; hence mail is bounced.

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