Senerio,
We have a Linux server that sends uuencode attached .pdf and .htm files to our users. We migrated from Exchange 2007 to Exchange 2010. In Exchange 2007 everyone was able to open these attached .pdf/.htm file on there iPhones/Ipads. Since we have migrated to Exchange 2010 if you try to open the .pdf its blank and if you open the .htm we are getting "begin 600 file.pdf" M)5!$1BTQ+C0*)<?LCZ(*-2`P(&]...
It could be a issue with iOS as other phones like Android, windows phone can open these files but further testing I have a old mailbox on 2007. when I check the raw data of the email that was sent to Exchange 2007 test email shows:
Content-Type: multipart/mixed;
boundary="_002_201305081528r48FSH4m002843smcbusinesssmcpackagingcom_"
MIME-Version: 1.0
--_002_201305081528r48FSH4m002843smcbusinesssmcpackagingcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
--_002_201305081528r48FSH4m002843smcbusinesssmcpackagingcom_
Content-Type: application/octet-stream; name="file.pdf"
Content-Description: file.pdf
Content-Dis; filename="file.pdf"; size=10325;
creation-date="Wed, 08 May 2013 15:28:27 GMT";
modification-date="Wed, 08 May 2013 15:28:27 GMT"
Content-Transfer-Encoding: base64
And when I check the raw data of the email that was sent to the Exchange 2010 mailbox it shows:
MIME-Version: 1.0
--_801e2b10-f4e1-4207-9e07-9258847b0314_
Content-Type: text/plain
--_801e2b10-f4e1-4207-9e07-9258847b0314_
Content-Transfer-Encoding: uuencode
Content-Dis; filename="file.pdf"
Content-Type: application/octet-stream; name="file.pdf"
begin 600 file.pdf
So I cant figure out why Exchange 2007 does the conversion to Base64 where as Exchange 2010 does not do any conversion. Was Content Conversion change in 2010?
Note: We check with our Linux guys that manage the Application as we are sending the uuencode in 644 formate. As we send a test message to gmail account and look at the raw data there and its showing "begin 644"
So in short Is it a issue with Exchange not doing a conversion or how is the uunencode permission being change from 644 to 600? As i think the iOS device does not like the 600 permission as other devices on active sync like Android, Windows Phone can make the conversion and open the files.
Regards,
Drew