We have been experiencing intermittent corruption of PDF files sent as attachments, and blaming Outlook 2000. However, we now find that it's Spamfilter ISP doing it. We've tried version 1.1.2.124 as well as the new beta, with the same result.

We've tracked it down to certain PDFs, not all, but the result is consistent no matter how many times we try, with or without other PDF attachments that get through fine. It looks like every occurrence of the hex sequence "0A 2E" is being truncated to "0A" throughout the file. The real mystery is that other PDFs get through all right with that sequence unscathed.

Anybody else have similar problems?

Thanks.

Not too difficult, really. I did a plain old file compare between an original and the munged copy, noted a pattern in the discrepancies, then used a hex editor and searched for the unique strings immediately preceding the differences. After checking a few like this, the pattern leapt out. Confirmed no other munging by counting the string instances in the original and getting the exact byte difference between the two. It didn't happen to every file with that string, though, so I'm presuming there was something in the PDF header that triggered it.

The fine LogSat techs nailed it, though, and deserve kudos for blazing fast resolution. You certainly wouldn't find such technical support responsiveness from the likes of McAfee et al.

Great product, folks.

Cheers.