Email PDF Attachments are being received at text files.
Problem: Hopefully, I will be able to explain my issue with some clarity. We have an application that creates an email and attaches a supporting document in a PDF format. The email is being sent to two address. The first address is to an email address where it is recieved and the data scraped and populated into an HP Service Desk ticket with the associated attachment. The second email is to an employee who is using MS Outlook 2003. The employee receives that email with attachment and the attachment has a .pdf file extension as expected. However when the Service Desk email arrives the attachment has a .txt file extension. If you rename the file extention to .pdf then you can read the attachment using a pdf reader.
Information: In the case of the employee email the path is from our Exchange Server (2003), to our customers Frontend Exchange Server (2003) to the employee's Outlook mailbox.
In the case of the Service Desk email the path is from our Exchange Server (2003), to our customers Frontend Exchange Server (2003) to a Unix box Gateway to the HP Service Desk Server. When we look at the email header information it shows the data as being converted to base64. See email header information (Customer IP and Names removed):
Microsoft Mail Internet Headers Version 2.0
Received: from xxxxxxxx.na.xxxxxxxxxx.net
Mon, 16 Jun 2008 09:16:33 -0400
Received: from xxxxxxxx.xxxxxxxx.com ([xxx.xx.xxx.xxx]) by xxxxxxxx.na.xxxxxxxxxx.net
Mon, 16 Jun 2008 09:16:33 -0400
Received: from ([xxx.xx.xxx.xxx])
by xxxxxxxx.xxxxxxxx.com with ESMTP id 5502559.55808630;
Mon, 16 Jun 2008 09:17:15 -0400
Received: from ([xxx.xx.xxx.xxx])
by edgex.xxxxxxxx.net with ESMTP id 5302078.EDGE;
Mon, 16 Jun 2008 09:17:14 -0400
Received: from localhost ([xxx.xx.xxx.xxx]) by xxxxxxxx.xxxxxxxx.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 16 Jun 2008 09:17:14 -0400
From: order@xxxxxxxx.com
To: xxx.xxxxxxxx@xxxxxxx.com
Subject: XX2951029-P001 - Purchasing request for Requestor John Doe
Date: Mon, 16 Jun 2008 09:17:14 -0400
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
boundary="Mark=_2008616131
Return-Path: order@xxxxxxxxx.com
Message-ID: <XXXXXXXXXXXXXX1R0rmTI0000
X-OriginalArrivalTime: 16 Jun 2008 13:17:14.0522 (UTC) FILETIME=[4B0BCFA0:01C8CFB
--Mark=_2008616131714335Bc
Content-Type: text/Plain; charset="US-ASCII"
Content-Transfer-Encoding:
--Mark=_2008616131714335Bc
Content-Type: Application/Octet-stream;
name="CP2951029-P001.pdf";
type=Unknown
Content-Transfer-Encoding:
--Mark=_2008616131714335Bc
Information: In the case of the employee email the path is from our Exchange Server (2003), to our customers Frontend Exchange Server (2003) to the employee's Outlook mailbox.
In the case of the Service Desk email the path is from our Exchange Server (2003), to our customers Frontend Exchange Server (2003) to a Unix box Gateway to the HP Service Desk Server. When we look at the email header information it shows the data as being converted to base64. See email header information (Customer IP and Names removed):
Microsoft Mail Internet Headers Version 2.0
Received: from xxxxxxxx.na.xxxxxxxxxx.net
Mon, 16 Jun 2008 09:16:33 -0400
Received: from xxxxxxxx.xxxxxxxx.com ([xxx.xx.xxx.xxx]) by xxxxxxxx.na.xxxxxxxxxx.net
Mon, 16 Jun 2008 09:16:33 -0400
Received: from ([xxx.xx.xxx.xxx])
by xxxxxxxx.xxxxxxxx.com with ESMTP id 5502559.55808630;
Mon, 16 Jun 2008 09:17:15 -0400
Received: from ([xxx.xx.xxx.xxx])
by edgex.xxxxxxxx.net with ESMTP id 5302078.EDGE;
Mon, 16 Jun 2008 09:17:14 -0400
Received: from localhost ([xxx.xx.xxx.xxx]) by xxxxxxxx.xxxxxxxx.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 16 Jun 2008 09:17:14 -0400
From: order@xxxxxxxx.com
To: xxx.xxxxxxxx@xxxxxxx.com
Subject: XX2951029-P001 - Purchasing request for Requestor John Doe
Date: Mon, 16 Jun 2008 09:17:14 -0400
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
boundary="Mark=_2008616131
Return-Path: order@xxxxxxxxx.com
Message-ID: <XXXXXXXXXXXXXX1R0rmTI0000
X-OriginalArrivalTime: 16 Jun 2008 13:17:14.0522 (UTC) FILETIME=[4B0BCFA0:01C8CFB
--Mark=_2008616131714335Bc
Content-Type: text/Plain; charset="US-ASCII"
Content-Transfer-Encoding:
--Mark=_2008616131714335Bc
Content-Type: Application/Octet-stream;
name="CP2951029-P001.pdf";
type=Unknown
Content-Transfer-Encoding:
--Mark=_2008616131714335Bc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Only answer to question. Must be something that I need to speak with MFG support. Thanks anyway.
ASKER
Here is the information from their site. www.ghostscript.com:
Using Unicode True Type fonts
Ghostscript can handle True Type fonts with the full Unicode character set. For doing that, a 3d party software should generate a Postscript or PDF document with a text, which is encoded with the UTF-16 encoding. Ghostscript may be used for converting such Postscript documents to PDF and for re-distilling such PDF documents to PDF subsets.
To render an UTF-16 encoded text, one must do the following :
Provide a True Type font with Unicode Encoding. It must have a cmap table with platformID equals to 3 (Windows), and SpecificID eqials to 1 (Unicode).
Describe the font in lib/cidfmap with special values for the CSI key : [/Artifex /Unicode 0].
In the PS or PDF document combine the font with one of CMap Identity-UTF16-H (for the horizontal writing mode) or Identity-UTF16-V (for the vertical writing mode). Those CMaps are distributed with Ghostscript in Resource/CMap.
Please note that /Registry (Adobe) /Ordering (Identity) won't properly work for Unicode documents, especially for the searchability feature (see CID font substitution).