Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Mail security is not able to scan hqx files.

Created: 16 Aug 2010 | 2 comments
Christian Tripputi's picture
3 Agree
0 Disagree
+3 3 Votes
Login to vote

Hi all,

*.hqx Machintosh files BinExe are detected like unscannable.

I tested several messages with the attachment and I got the following error from Symantec Mail Security for Exchange version 6.0.11 :
 

"2.jpg.hqx" located in message with subject "xxxxxxxx xxxxxxxxxx", located in SMTP has violated the following policy settings:


                Scan: Auto-Protect
                Rule: Unscannable File Rule

The following actions were taken on it:
                The attachment "2.jpg.hqx" was Deleted for the following reason(s):
Scan Engine Error.  CSAPI DEC result: 0x15. Decomposer failed to extract the file from a container.

At the moment if I disable the action to quarantine Unscannable files and moved to: Log Only + disabled Autoprotect it works normally, but obviuosly there is a concern about the security.

First solution:
Convert the file in jpg before to delivery the file to the Symantec server.

Second workaround:
Set quarantine for unscannable and release the files manually as files.

third workaround:
Set log only for unscannable files. (Not suggested).

The same issue has been reproduced in SMS for Exchange 6.5 and Symantec Brightmail Gateway version 9.x since the error is trigered by the decomposer.
Also most of the operating systems are not able to open the file. Moreover if the file is received cannot be opened. The enduser should convert the file in a standard format using a tool in order to open it.

It would be nice to have a decomposer capable to decompose the file since it is a good file. It will be user responsibility to open the file then.

regards
Christian

Comments

BenDC's picture
25
Aug
2010
1 Vote +1
Login to vote

Often we we see these files

Often we we see these files are corrupted once they arrive at the user or un openable because the file is only a resource fork once it arrives.

TSE-JDavis's picture
17
Sep
2010
1 Vote +1
Login to vote

You need to have the OS X

You need to have the OS X client send 'Windows-friendly' attachments