[Tickets #12289] Re: Attachments larger than 100k are missing from emails synced using ActiveSync

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12289
------------------------------------------------------------------------------
  Ticket             | 12289
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Attachments larger than 100k are missing from emails
                     | synced using ActiveSync
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-06-01 15:45) wrote:

What do you mean by "missing"? I have no problems receiving  
attachments, of any size, on my devices. This has been available since  
email was originally implemented.

Do the messages show on the device as *having* an attachment? EAS does  
not send the attachment data itself, only the fact that there is an  
attachment, on the initial SYNC. Later requests fetch the data if the  
user attempts to view/download the attachment. This is done in a  
variety of different ways, depending on the client and the version of  
EAS that is being used.

It could be that this is related to the other bug you posted, Bug:  
12292.  Without a sync log, it's impossible for me to tell.

> Could it be that maxRequestLength has not been set or set to a very  
> low value?

There is no such configuration for Horde or PHP. This is an Exchange  
server configuration, not an ActiveSync policy. There is a  
MaxAttachmentSize policy that is enforced on the client if  
provisioning is enabled - but that defaults to 5MB and can be  
configured higher by an admin. Though this doesn't prevent the  
attachment information from being sent to the device, it only prevents  
the device from fetching the full attachment.