Currently Being ModeratedSep 20, 2013 11:18 AM (in response to loucie)
Remove and re-add the account on the device.
If possible, turn off the size restriction in Exchange then re-enable to see if that rectifies the issue.
Currently Being ModeratedSep 21, 2013 7:33 PM (in response to loucie)
Anyone else have this same problem. Only happens with IOS 7 devices. Attachments smaller than 40KB go through, others get stuck in outbox. However it works fine over wireless. Fails over Cellular.
We are using certificate based authentication Active Sync. Not sure if that matters.
Currently Being ModeratedSep 23, 2013 11:12 AM (in response to loucie)
We are seeing intermittent issues with IOS 7 devices on Exchange with smaller messages. Cannot find a log of the message on the iPhone, but it indicated it was rejected by the server. At first it seemed to be an issue of a period at the end of the email. We were able to recreate this once, but then subsequent attempts to recreate faile and all emails were processed correctly.
Currently Being ModeratedSep 23, 2013 1:17 PM (in response to loucie)
I justed tested with an iPhone 5 and an iPhone 5s, both running iOS7.0.1, both AT&T, both with Wi-Fi disabled. I sent a 1MB photo attachment to an iCloud account. Both worked just fine.
Does not seem to be a general issue with iOS7. Running Exch 2010 SP2 RU 6, though.
Currently Being ModeratedSep 23, 2013 1:52 PM (in response to loucie)
I just received the same message when trying to send a reply to a message on my corporate Exchange Mail account. This has only occurred since I upgraded to ios7. I can compose a new email fine but received the message that the emails was too large when trying to send a reply.
Currently Being ModeratedSep 23, 2013 2:23 PM (in response to dennisfromgalt)
Currently Being ModeratedSep 23, 2013 8:14 PM (in response to loucie)
Update to my scenario. I figured it out. We are on Exchange 2007 on Server 2003 and we are using Active Sync with Client Certificates. We did not notice much of a problem when sending using IOS 6 but with IOS 7 it was much more prevalent, any message over 100K would get rejected as too large. turns out it was a problems with IIS 6 and the uploadreadaheadsize value in the IIS metabase. Here is a link regarding it for 2010
here is one for 2007
I bumped mine up to 10Mb and now attachments are going through fine. THis probably should have been done a long time ago, but the symptoms really just reared its ugly head after the ios 7 upgrade.
I hope this helps others, as i was pulling my hair out all weekend trying to figure this out.
Currently Being ModeratedSep 24, 2013 7:34 PM (in response to tsmith06117)
We applied that change and so far our testing has been successful.
Thanks for your efforts!
Currently Being ModeratedSep 27, 2013 6:48 PM (in response to tsmith06117)
We are having the same issue since we upgraded to ios7 but we have Exchange 2010 on Windows 2008 R2 so we have IIS7. Is that solution applicable to our case as well? Don't want to be the Guinea pig and be the first one trying in a Prod env. :-)
Currently Being ModeratedSep 27, 2013 7:21 PM (in response to cli1010)
I would go for it. THis is the link to do it on 2008. Just look up how to back up the metabase first. Also find out how to query the current values in metabase to ensure your changes went through and or to revert back. At lease look for more information using the link below as a starting point.
Currently Being ModeratedSep 28, 2013 7:02 AM (in response to tsmith06117)
We've had this setting in place for a few days with no issues.
Some research on the UploadReadAheadSize setting:
Setting the UploadReadAheadSize property above 64KB is not recommended for web sites that do not require client certificate authentication, otherwise you run the risk of allowing an anonymous Denial of Service (DOS) attack. When UploadReadAheadSize needs to be set at a value higher than 64KB, it is recommended that you set the SSLAlwaysNegoClientCert property to True, which will require that the client has a valid client certificate installed.
We are investigating the possibility of turning this on instead.
Currently Being ModeratedSep 30, 2013 11:35 AM (in response to tsmith06117)
See thread here for similar issues
Currently Being ModeratedDec 4, 2013 7:08 PM (in response to loucie)
I had a similar problem when sending large attachments and used the solution below. I tried everything on here without luck.. Just a small change in he web.config and it solved my issue:
hope it helps...
Currently Being ModeratedJan 28, 2014 7:16 AM (in response to loucie)
I dont get it, why do people spend their time try to fix this when there is dropbox or sites like http://emailattachment.net/ , you can send much larger files, safer and quicker :/