Attempting to scan some .mht files results in a virus detection due to a malformed container violation.
This issue currently only appears to affect .mht files created with Windows Problem Steps Recorder(WPSR).
Some *.mht fies which are not compliant with RFC 822 and/or RFC 2046-defined MIME format specification can trigger malformed container errors (structure mismatch). In such a case, this behavior is by design.
If you wish to allow malformed container files do as follows.
To configure Symantec Protection Engine to allow malformed container files:
In the console on the primary navigation bar, click Policies.
In the sidebar under Views, click Filtering.
Click the "Container Handling" tab at the top of the page.
Ensure "Enable Malformed Container Handling" is checked
Under "Enable Malformed Container Handling", select "Log only".
By default, Symantec Protection Engine is set to block malformed container files.
Rate this Article
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.