The problem still works if I send the email from Goodreader to a non-Outlook account (where the attachement shows as a normal PDF) and then forward that email to my Outlook account (where the attachement stillĪfter a bit of playing, the workaround I am using is, in Goodreader select the file and 'Open in.' iAnnotate PDF and then email it from there.

I have a similar set up and the same problem. Name*0='NAME_ Fire Department ext signage requirements dated 02-14-11 Re'

Thread-Index: AcvU9YAHDwnyyEsFSfmxu4u8Jl4o5g=įilename*0='NAME_ Fire Department ext signage requirements dated 02-14-11 Re' įilename*1='vised 2-16-11 NAME - annotated 2.pdf' Thread-Topic: Mail with GoodReader attachments Subject: Mail with GoodReader attachments Received: from 172.17.2.13 () by () with Microsoft Exchange Server HTTP-DAV Microsoft Mail Internet Headers Version 2.0 Shown below is an example header with some information changed (just removing names, company information, etc.): I also tested the emails using other non-Microsoft email clients configured to talk to exchange and they displayed the email properly, so this is not an exchange issue. Receive PDFs from both inside and outside with no problems. We use Panda Antivirus for Exchange as our email antivirus solution. The DAT file as a PDF and opening it in any number of PDF readers works fine, but it is just odd that they are getting renamed only when being sent to our exchange server, not from. To an outside mail account, the attachments show up just fine, but if he sends it to a fellow employee, the PDF attachment shows up as ATT#.DAT, and any text that he adds is attached as ATT#.txt, both numbers have been the same so far. The user has an app called GoodReader which he uses to mark up PDFs and emails them to people from that program. User has an iPad which synchronizes with our exchange server. Here's the hardware/software environment that causes the issue:

Goodreader app for fire