Since upgrading we are finding problems with Ironport detecting .bin files in docx, xlsx etc. I know that these files are technically zip files and when an Excel spreadsheet has a macro it will carry a .bin file etc. The problem is that this was "fixed" in around 2008 when MS first introduced these attachment types. Why does 7.5 re-introduce this problem?
I'm running into the same problem after the upgrade. Have you found any solution to the problem? It is causing us a major "headache".
The response I got was that this is a "feature" of 7.5.
One possibility to bypass office documents is the a message filter condition
if (attachment-filename !=
Another possibility is to use a content filter condition
Attachment Name Does not End With
Unfortunately there is no other way to bypass Office documents with macros
as long as you have a filter for executable files.
I opened a ticket with TAC. This has been flagged as a bug:
The behavior you are reporting is tracked in our bug database as defect 81190
It will be fixed in a coming MR.
If you can get access to the AsyncOS 7.6.0 for Email FCS, the Office attachment problem is fixed. We deployed it last night and have not had any issues.
We are also experiencing this issue with 7.5.1 and Office files.
Doug Maxfield, I did not see this fix listed on the 7.6.0 FCS announcement, can you confirm that the 7.6.0 release does correct this bug?
I asked the same questions when 7.6 FCS was released. The response that I received back was that not all "bug" that are fixed are included in the Readme.
I can confirm 100% that the issue is resolved.