Can anyone provide some information on exactly what triggers the "Suspicious.PDF" detection?
My company distributes software components used to process PDF files. A customer contacted me, complaining that his executable, which is linked with my static library, is triggering Norton's "Suspicious.PDF".
How do I avoid this problem?