UserAgent: Mozilla/5.0 (Windows NT 10.0; rv:45.0) Gecko/20100101 Firefox/45.0

Steps to reproduce the problem:
objectionable content filter for student OU is catching email when the binary of a x64 attachments contains char strings that are part of my list. (I.E. XxX, fUx, etc) 

What is the expected behavior?
I'd like for the filter to recognize the string is part of the binary code for a x64 bit attachment and ignore the rule so I can leave strings in the rule for plain text violations.  

What went wrong?
Objectionable content filter is filtering emails that it should not due to the email having a x64 encoded attachment

Did this work before? N/A 

Chrome version: <Copy from: 'about:version'>  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

I have submitted two tickets to enterprise support; 
[#09057419] Legitimate emails being blocked by objectionable content rule [ ref:_00D00VNwG._50060wywDN:ref ]
and 
[Case #07260440] Objectionable Content [ref:_00D00VNwG._50060nZDdo:ref]

Just seems to me that if viruses can be scanned for and thus recognizing attachments then this issue can also be addressed.