We had a virus that entered our company and .zip attachment with a malicious Javascript file inside. Since detection for this malicious javascipt file was not yet available and the executable file rule did not catch this I decided to turn on the file name blocking rule to catch this and any future viruses that arrived this way.
Unfortunately this also started quaratining all PDF file attachments.
Looking closer I found that every PDF file had a javascript.js file inside, and thus triggerd the file name rule blocking.
Unfortunately using the bypass container files is not an option to stopping the virus we were seeing or any future instance (we do block .js if directly attached to the email).
So this is an enhancement request to be able to add conainer exceptions to the File Name Rule, in this case PDF files, but still have the ability to scan within other container types.
And of course we still want to scan PDF files for viruses.