PDF Attachment Issues

I am having quite the puzzler of an issue with PDF attachments.

Whenever we send a PDF attachment over a few pages to someone outside of our network and they do not use outlook (thunderbird, gmail, yahoo, hotmail) the pdf file will display fine in any pdf reader (Adobe Reader, Foxit Reader, chrome in browser or in reader), but when they print it black lines come out instead of text or graphics.

The same file will work fine for someone if they use outlook to download the attachment.

Our environment is:

Outlook 2010 > Exchange 2003 > Cisco ASA 5512-X > App River SmartHost

I have disabled esmtp inspection on the ASA for traffic as I read that can corrupt attachments, but no luck.

The attachments are not bothered if I zip the file before sending it, or do not send it through our environment. (Log into my gmail, send it to another gmail account no issue. Send the same file from our work domain to the same gmail account, when you print the lines show up instead of text or images.)

This is happening to a wide variety of printers with different drivers as well so I do not think the issue is related to that. (Tested with HP, Toshiba, Kyocera and Brother Printers all print it the same).

Here is a picture of the printed pdf file

We had no reports of this issue until we recently moved offices, and the infrastructure bit that changed was the ASA-5512-X is now in place instead of a Cisco PIX 515, so that is why I was originally leaning towards the firewall causing this issue.

The attachment is also affected no matter if your e-mail is sent as HTML, Plain Text or RT.

Anyone have any ideas for this one?

EDIT: Setting exchange to send to the domains with the issue to use uuencode resolved the issue with the this attachment for us. Example. Additionally, we found that printing as an image in adobe bypassed the issue.

Posted Aug 4, 2014, 4:43 PM UTC · edited

37
isakmp•

What is creating the PDFs? Adobe software or something else? What you describe sounds more like a rendering problem than an attachment problem, as if the file has embedded fonts or is graphics, not text.

2
notacceptableOPJack of All Trades•

The files are being created with CutePDF.

The reason I did not think that it was an issue with the creation of the file, is that the files do not have the issue until they are e-mailed through our exchange server.

If I take the the file I create with CutePDF, open up a browser and e-mail to someone using gmail.com: They can open and print the document without the issue.

If I take that same exact file and then e-mail it using outlook through our exchange server and send it to the exact same recipient: They can open and view the file perfectly, but when they print the file it appears as the image above (black lines).

Do you still think it could be related to the creation of the PDF? I will try some other PDF creators to see if the issue repeats itself.

1
remotefixonlineJack of All Trades•

I don't think it's cute pdf. I use it at 20 different clients and never had an issue... is there any filtering or anything in the email flow?

2
[deleted]•

[deleted]

2
Jope-Ga•

Have you tried modifying the MIME type on the outgoing message? Exchange servers and Outlook like to use TNEF encapsulation which holds everything in a winmail.dat file in the body. The receiving client may be opening the winmail.dat file but screwing something up when it sends it to the printer. Your options for Encapsulation are TNEF or standard MIME in an exchange environment.

I'm typing this up at the end of the day so sorry for not finding you some links but I believe the easiest way to test TNEF is to go into a new mail message in Outlook 2010 -> Format Text Tab -> Choose plain text and test the message. If this fixes your problem you can use the Exchange server to force this update on any accounts you want. If you have questions I can answer them tomorrow for you. Good luck and I hope this fixes your issue.

2
notacceptableOPJack of All Trades•

Just as an FYI, your suggestion ultimately led me to finding a fix. I set exchange to use UUENCODE instead of MIME for the domains in question and the issue stopped happening.

I looked back at the test and for some reason using the plain text option you suggested and then looked at the e-mail and it was still MIME encoded when I checked the source. Not sure why it didn't work.

Thank you very much for the suggestion however as it led me to the resolution.

2
Jope-Ga•

I'm glad to hear everything worked for you :-)

2
notacceptableOPJack of All Trades•

I tested this just now. I was sure it would be a fix, but choosing plain text did not resolve the issue.

I did try forcing the encoding on exchange to a few different types as well and that did not resolve the issue.

We did find if we print as image the file comes thorough without issue.

1