[Tickets #12970] Re: Problems with S/MIME messages when sent to or received from a BlackBerry 10 device using BES

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/12970
------------------------------------------------------------------------------
  Ticket             | 12970
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Problems with S/MIME messages when sent to or received
                     | from a BlackBerry 10 device using BES
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-10-26 17:47) wrote:

>> That doesn't matter. It's supposed to be set for each
>> fetch/sync/itemoperation to tell the server the client can accept the
>> MIME blob. If it's missing, it's assumed to be zero. See MS-ASCMD
>> section 2.2.3.100.3.
>
> I don't think so. 2.2.3.100.3 says that it has to be part of every  
> Sync>Options request and it is when the collection is being defined.

There is no such thing as "being defined" in EAS. The only time we  
look at previously sent values for a collection's OPTIONS is when the  
client issues a PARTIAL SYNC. Then we load the ENTIRE previously  
requested collection data. If a SYNC request sends an OPTIONS  
structure, it MUST contain the MIMESUPPORT field, or it defaults to 0.