Q: Email forwarding issue

I've tested this again after updating to 9.3.2 but still seeing the same problem.

I was premature.  With iOS 9.3.2 forwarding an attachment from my iPhone to myself worked if I then opened the attachment on my phone.  However, on my workstation using Outlook 2016 attached to Exchange 2010 the attachment does not open.  Additionally, if I forward multiple attachments only one goes through, exactly as it was behaving with 9.3.1.

We are still having this issue with 9.3.2.

Not sure if this is on Apple's radar or not, hopefully so.  We have had a similar thing occur, and I found a workaround for it if the attachment can't be recovered by just resending from the iPhone or iPad, maybe someone else will know a way to fix or improve the method.  Once received on a computer, it requires saving the email as an eml file and opening via text editor.  Once opened in the text editor looking for the section that has the base64 encoded information for the particular attachment, you will find that the text is not actually encoded properly for just the particular attachment file such as:

--_007_2DBFBC07AE554C9FBBECACB7232533E8_

Content-Type: application/pdf; name="attachment.pdf"

Content-Description: attachment.pdf

Content-Disposition: attachment; filename="attachment.pdf"; size=531340;

  creation-date="Tue, 17 May 2016 19:11:43 GMT";

  modification-date="Tue, 17 May 2016 19:11:43 GMT"

Content-Transfer-Encoding: base64

Receivedfromsomewhere123123123123bymymailserver

234234234234withMicrosoftSMTPServerTLSid1432792Tue17May201613484905

00Receivedfromhostinformationbyp3plwbeout1503prodphx3secureservernetwit

hbizsmtpidvWoo1s0010FDBWt01WooAQTue17May20161148480700XSIDvWoo1s0010FDBWt01R

eceivedqmail8172invokedbyuid9917May20161848480000ContentTypemultipart/mixedb

oundaryf8c68204d8f2b879567551c3bf13eb7fXOriginatingIP199116157114UserAgentWo

rkspaceWebmail629MessageID201605171148462d72b9a84ca577e8313ec065200ea7849f4b

9d1ad8wbeemail15godaddycomFromsomesubjecttext

SubjectDataDateTue17May20161148460700ReturnPathmoreheaderdata

XMSExchangeOrganizationAuthSourcemail10mymailserverXMSExchan

geOrganizationAuthAsAnonymousXGFISMTPSubmission1XGFISMTPHelloDomainp3plwbeou

t1503serverGFISMTPRemoteIPIPIPIPIPXKSEAntiSpamIntercept

orInfoprotectiondisabledXMSExchangeOrganizationAVStampMailboxKaspersk5171608

00XKSEAntivirusInterceptorInfoscansuccessfulXKSEAntivirusInfoCleanMIMEVersio

n10f8c68204d8f2b879567551c3bf13eb7fContentTypemultipart/relatedboundaryc7a02.... .

Basically you can recover the corrupted attachment by selecting this readable text, and then finding in the output where you can not read the information any longer, you then remove everything from the Received text which starts what should be showing only base64 encoded data, to where the base64 encoded information actually starts:

It should be the last place in the file that has something like /pdfnameAttachmentADpdfContentDispositionattachmentfilenameAddachmentADpdf  After this text it should start being valid base64 encoded information, deleting the garbage ahead of that after the correct heading info for the attachment and saving the EML file should result in being able to get to the non corrupted pdf attachment.

Content-Disposition: attachment; filename="attachment.pdf"; size=531340;

  creation-date="Tue, 17 May 2016 19:11:43 GMT";

  modification-date="Tue, 17 May 2016 19:11:43 GMT"

Content-Transfer-Encoding: base64

JVBERi0xLjQNJeLjz9MNCjQgMC

BvYmoNPDwvTGluZWFyaXplZCAxL0wgNTI0MjYxL08gNi9FIDQ3NTk1Ny9OIDEvVCA1MjQwNjcvSC

BbIDQ3NiAxNDRdPj4NZW5kb2JqDSAgICAgICAgICAgICAgICAgIA14cmVmDTQgOQ0wMDAwMDAwMD

E2IDAwMDAwIG4NCjAwMDAwMDA2MjAgMDAwMDAgbg0KMDAwMDAwMDY4MCAwMDAwMCBuDQowMDAwMD

AwOTMwIDAwMDAwIG4NCjAwMDAwMDA5NjMgMDAwMDAgbg0KMDAwMDAwMTA1OCAwMDAwMCBuDQowMD

AwMDAxNDE2IDAwMDAwIG4NCjAwMDAwMDM2ODAgMDAwMDAgbg0KMDAwMDAwMDQ3NiAwMDAwMCBuDQ

p0cmFpbGVyDTw8L1NpemUgMTMvUm9vdCA1IDAgUi9JbmZvIDMgMCBSL0lEWzxBMjdDMTMzMURGND

k0MjAxQUFGMzc5RDI3RUQxQzI2RT48MjQ1RDc2N0VCMkZGNERDOEFFMzA5RDI0OUREMUIzNjg+XS....

Thanks to Davek79 for doing all the leg work in determining the exact lines that are creating the corruption. Now if we could just get an Apple engineer to look at this thread, this may save them some time in resolving it.

We have the same issue with exchange 2013 and office365 (EAS)accounts.

My experience is that if the attachments havent been opened, the problem will occur. If the attachments have been opened before forwarding, the problem will not occur.

We have had the problem from iOS 9.3 to 9.3.2  We do not have problem with MS Outlook app for iOS

I've tested with iOS 9.3.3 beta 1 - now it seems that the problem is solved.

I am also testing with 9.3.3 beta 1 and it keeps the attachment but does not keep the email thread. Still an issue..

We have also this issue in our company. Our bosses are very angry from this issue. What about Apple support? New iOS??

I'm testing 9.3.3 beta 2 and it still works, but i don't know about the issue with the email thread. We have spoken to Apple Support with no luck, they say its an Microsoft issue.

My users report there is no longer an issue since 9.3.2 update. Note: we are running office 365 enterprise E3.

Same Issue here. Iphone 6 with iOS 9.3.2 and activesync with exchange 2010. The user recieved email with 2 jpg images (1.jpg 300kb and 2.jpg 200kb) He forward to another user (including attachs) but other user recieved only one attach (2.jpg 500kb) and cant open in any device (android, outlook, windows, nothing).

do you have reply from Apple? this is very IMPORTANT.

We need a solution...!

Thank you

regards,

I stopped troubleshooting with Apple as my issue is no longer reproducible. I suggest you contact AppleCare and open a case to have their engineers assess the issue.

My company has the same issue with Office365 (EAS) accounts and devices using ios 9.3+

In our company still the same issue. We´ve tested a lot, but the problem is still there. Is there an reply from apple now after nearly a month since the last post??

I have the same problem with several users.  Exchange 2010 w/ iPhone 6, 6s versions.  Affected files are pdf, excel, and jpg.

I can't seem to replicate the problem and had hope that someone who had replicated the issue can try to use the Outlook App (instead of Apple Mail).  I want to see if its an issue with iOS9.3, Apple Mail, or our Exchange server. 

We have android device users and thus can pretty much eliminate the issue with our firewall router or Exchange server.