Subject: | MIME Parsing Issue |
Date: | Fri, 11 Sep 2009 09:08:43 -0500 |
To: | "bug-MIME-tools [...] rt.cpan.org" <bug-MIME-tools [...] rt.cpan.org> |
From: | Jamie Hill <jamie.hill [...] norlight.com> |
I have run across an issue MIME::Parser and our Cisco T.37 Fax Gateway. The Fax Gateway accepts incoming fax calls from the PSTN and takes the information and encodes it into a TIFF-F document and sends it via an attachment in email onto a destination. We have been using MIME::Parser to extract the TIFF attachment so that we could convert them to PDF and send onto the final destination. I recently realized that a small percentage of the conversions were failing. Upon further examination it appears in those cases MIME::Parser is improperly decoding the attachment. If we use the MIME extractor in PINE (http://www.washington.edu/pine/) it decodes the attachment properly. The interesting thing is that both MIME parsers produce a file with the same number of bytes, but a binary diff shows they do not contain the same data.
I've included three attachments:
1. 1252256623214170-msg - is the original email message
2. Cisco_fax-MIME-Parser.tif - The attachment decoded using MIME::Parser
3. Cisco_fax-PINE.tif - The attachment decoded using PINE's MIME parser
Please let me know if you need any additional information.
Thanks,
--Jamie
--
Jamie Hill
Office of Technology: Senior Member, Technical Staff
Norlight, Inc.
jamie.hill@norlight.com
Voice 812 456-1231
http://www.norlight.com/inc
Message body not shown because it is not plain text.
Message body is not shown because sender requested not to inline it.
Message body is not shown because sender requested not to inline it.