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

Create a technical support case if you need further support.

"Scanexception" in mail headers on InterScan Messaging Security Suite (IMSS) or InterScan Messaging Security Virtual Appliance (IMSVA)

    • Updated:
    • 21 Oct 2015
    • Product/Version:
    • InterScan Messaging Security Suite 7.1 Linux
    • InterScan Messaging Security Suite 7.1 Windows
    • InterScan Messaging Security Suite 7.5 Windows
    • InterScan Messaging Security Virtual Appliance 8.2
    • InterScan Messaging Security Virtual Appliance 8.5
    • InterScan Messaging Security Virtual Appliance 9.0
    • Platform:
    • Linux - Red Hat RHEL 3 32-bit
    • Linux - Red Hat RHEL 4 32-bit
    • Linux - Red Hat RHEL 5 32-bit
    • Linux - Red Hat RHEL 6 32-bit
    • Linux - SuSE 10
    • Linux - SuSE 9.0
    • Unix - Solaris (Sun) version 10 (SunOS 5.10)
    • Unix - Solaris (Sun) version 8 (SunOS 5.8)
    • Unix - Solaris (Sun) version 9 (SunOS 5.9)
    • Windows 2000 Advanced Server
    • Windows 2000 Server
    • Windows 2003 Enterprise
    • Windows 2003 Standard
    • Windows 2008 Enterprise
    • Windows 2008 Standard
Summary

This article discusses the purpose of  scanexception in mail headers on IMSS and IMSVA like in the following example:

X-imss-reprocess-rules: scanexception.12
X-imss-reprocess-type: quarantine

Details
Public

The X-imss-reprocess headers are used by IMSVA and IMSS to keep track of what security policy was responsible for quarantining an email.

The version number is used to track if there are changes in the security policy settings from the time IMSS/IMSVA quarantined the email to the time the admin tried to release the email.

If there are no changes, IMSS/IMSVA will skip that specific security policy.

Below are the X-imss-reprocess headers:

  • X-imss-reprocess-rules - This shows the identifier and the version of the rule that queued the message.
  • X-imss-reprocess-type - This shows the type of the action (quarantine, notification, etc.).

For more information on the specific exception triggered by the mail, check the log.imss file.

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