[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
noreply at bugs.horde.org
Sat Oct 25 19:12:11 UTC 2014
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-25 19:12) wrote:
That's why I'm asking. The logs below show an HTML message being sent,
which doesn't support SMIME. The device must explicitly request a MIME
message. E.g., this is the OPTIONS portion of a SYNC request the is
NOT requesting a MIME message:
2014-10-25T14:48:23-04:00 DEBUG: [281] I <Options>
2014-10-25T14:48:23-04:00 DEBUG: [281] I <FilterType>
2014-10-25T14:48:23-04:00 DEBUG: [281] I 5
2014-10-25T14:48:23-04:00 DEBUG: [281] I </FilterType>
2014-10-25T14:48:23-04:00 DEBUG: [281] I <MIMETruncation>
2014-10-25T14:48:23-04:00 DEBUG: [281] I 1
2014-10-25T14:48:23-04:00 DEBUG: [281] I </MIMETruncation>
2014-10-25T14:48:23-04:00 DEBUG: [281] I <MIMESupport>
2014-10-25T14:48:23-04:00 DEBUG: [281] I 0
2014-10-25T14:48:23-04:00 DEBUG: [281] I </MIMESupport>
2014-10-25T14:48:23-04:00 DEBUG: [281] I <AirSyncBase:BodyPreference>
2014-10-25T14:48:23-04:00 DEBUG: [281] I <AirSyncBase:Type>
2014-10-25T14:48:23-04:00 DEBUG: [281] I 1
2014-10-25T14:48:23-04:00 DEBUG: [281] I </AirSyncBase:Type>
2014-10-25T14:48:23-04:00 DEBUG: [281] I <AirSyncBase:TruncationSize>
2014-10-25T14:48:23-04:00 DEBUG: [281] I 500
2014-10-25T14:48:23-04:00 DEBUG: [281] I </AirSyncBase:TruncationSize>
2014-10-25T14:48:23-04:00 DEBUG: [281] I </AirSyncBase:BodyPreference>
2014-10-25T14:48:23-04:00 DEBUG: [281] I </Options>
The MIMESupport element is set to '0' - which means no mime support.
The BodyPreference Type is set to '1', which indicates plaintext. So
the client is requesting only a plaintext representation of the
message. No MIME and no S/MIME. This results in the following log
snippits:
2014-10-25T14:48:23-04:00 INFO: [281]
Horde_Core_ActiveSync_Driver::getMessage(INBOX, 255000)
2014-10-25T14:48:23-04:00 INFO: [281] Sending PLAINTEXT Message.
.
.
.
2014-10-25T14:48:23-04:00 DEBUG: [281] O <POOMMAIL:MessageClass>
2014-10-25T14:48:23-04:00 DEBUG: [281] O IPM.Note
2014-10-25T14:48:23-04:00 DEBUG: [281] O </POOMMAIL:MessageClass>
.
.
2014-10-25T14:48:23-04:00 DEBUG: [281] O <POOMMAIL:MessageClass>
2014-10-25T14:48:23-04:00 DEBUG: [281] O IPM.Note
2014-10-25T14:48:23-04:00 DEBUG: [281] O </POOMMAIL:MessageClass>
2014-10-25T14:48:23-04:00 DEBUG: [281] O <POOMMAIL:InternetCPID>
2014-10-25T14:48:23-04:00 DEBUG: [281] O 65001
2014-10-25T14:48:23-04:00 DEBUG: [281] O </POOMMAIL:InternetCPID>
2014-10-25T14:48:23-04:00 DEBUG: [281] O <AirSyncBase:NativeBodyType>
2014-10-25T14:48:23-04:00 DEBUG: [281] O 1
2014-10-25T14:48:23-04:00 DEBUG: [281] O </AirSyncBase:NativeBodyType>
2014-10-25T14:48:23-04:00 DEBUG: [281] O <AirSyncBase:Body>
2014-10-25T14:48:23-04:00 DEBUG: [281] O <AirSyncBase:Type>
2014-10-25T14:48:23-04:00 DEBUG: [281] O 1
2014-10-25T14:48:23-04:00 DEBUG: [281] O </AirSyncBase:Type>
2014-10-25T14:48:23-04:00 DEBUG: [281] O
<AirSyncBase:EstimatedDataSize>
2014-10-25T14:48:23-04:00 DEBUG: [281] O 139
2014-10-25T14:48:23-04:00 DEBUG: [281] O
</AirSyncBase:EstimatedDataSize>
2014-10-25T14:48:23-04:00 DEBUG: [281] O <AirSyncBase:Data>
2014-10-25T14:48:23-04:00 DEBUG: [281] O [STREAM]
2014-10-25T14:48:23-04:00 DEBUG: [281] O </AirSyncBase:Data>
2014-10-25T14:48:23-04:00 DEBUG: [281] O </AirSyncBase:Body>
The following is the OPTIONS request from the same client, but
asking for the MIME data:
2014-10-25T14:48:23-04:00 DEBUG: [282] I <Options>
2014-10-25T14:48:23-04:00 DEBUG: [282] I <FilterType>
2014-10-25T14:48:23-04:00 DEBUG: [282] I 5
2014-10-25T14:48:23-04:00 DEBUG: [282] I </FilterType>
2014-10-25T14:48:23-04:00 DEBUG: [282] I <MIMESupport>
2014-10-25T14:48:23-04:00 DEBUG: [282] I 2
2014-10-25T14:48:23-04:00 DEBUG: [282] I </MIMESupport>
2014-10-25T14:48:23-04:00 DEBUG: [282] I <AirSyncBase:BodyPreference>
2014-10-25T14:48:23-04:00 DEBUG: [282] I <AirSyncBase:Type>
2014-10-25T14:48:23-04:00 DEBUG: [282] I 4
2014-10-25T14:48:23-04:00 DEBUG: [282] I </AirSyncBase:Type>
2014-10-25T14:48:23-04:00 DEBUG: [282] I <AirSyncBase:TruncationSize>
2014-10-25T14:48:23-04:00 DEBUG: [282] I 32768
2014-10-25T14:48:23-04:00 DEBUG: [282] I </AirSyncBase:TruncationSize>
2014-10-25T14:48:23-04:00 DEBUG: [282] I </AirSyncBase:BodyPreference>
2014-10-25T14:48:23-04:00 DEBUG: [282] I </Options>
This time, MIMESupport is '2', which means the client can support any
MIME messages (including S/MIME). It could also be set to '1', which
means only S/MIME data is allowed. This results in the following
output (same message as in previous example):
2014-10-25T14:48:23-04:00 INFO: [282]
Horde_Core_ActiveSync_Driver::getMessage(INBOX, 255000)
2014-10-25T14:48:24-04:00 INFO: [282] Sending MIME Message.
2014-10-25T14:48:24-04:00 INFO: [282] Checking MIMETRUNCATION: ,
ServerData: 10353
.
.
.
2014-10-25T14:48:24-04:00 DEBUG: [282] O <POOMMAIL:MessageClass>
2014-10-25T14:48:24-04:00 DEBUG: [282] O
IPM.Note.SMIME.MultipartSigned
2014-10-25T14:48:24-04:00 DEBUG: [282] O </POOMMAIL:MessageClass>
2014-10-25T14:48:24-04:00 DEBUG: [282] O <POOMMAIL:InternetCPID>
2014-10-25T14:48:24-04:00 DEBUG: [282] O 65001
2014-10-25T14:48:24-04:00 DEBUG: [282] O </POOMMAIL:InternetCPID>
2014-10-25T14:48:24-04:00 DEBUG: [282] O <AirSyncBase:NativeBodyType>
2014-10-25T14:48:24-04:00 DEBUG: [282] O 1
2014-10-25T14:48:24-04:00 DEBUG: [282] O </AirSyncBase:NativeBodyType>
2014-10-25T14:48:24-04:00 DEBUG: [282] O <AirSyncBase:Body>
2014-10-25T14:48:24-04:00 DEBUG: [282] O <AirSyncBase:Type>
2014-10-25T14:48:24-04:00 DEBUG: [282] O 4
2014-10-25T14:48:24-04:00 DEBUG: [282] O </AirSyncBase:Type>
2014-10-25T14:48:24-04:00 DEBUG: [282] O
<AirSyncBase:EstimatedDataSize>
2014-10-25T14:48:24-04:00 DEBUG: [282] O 10353
2014-10-25T14:48:24-04:00 DEBUG: [282] O
</AirSyncBase:EstimatedDataSize>
2014-10-25T14:48:24-04:00 DEBUG: [282] O <AirSyncBase:Truncated>
2014-10-25T14:48:24-04:00 DEBUG: [282] O 0
2014-10-25T14:48:24-04:00 DEBUG: [282] O </AirSyncBase:Truncated>
2014-10-25T14:48:24-04:00 DEBUG: [282] O <AirSyncBase:Data>
2014-10-25T14:48:24-04:00 DEBUG: [282] O [STREAM]
2014-10-25T14:48:24-04:00 DEBUG: [282] O </AirSyncBase:Data>
2014-10-25T14:48:24-04:00 DEBUG: [282] O </AirSyncBase:Body>
The BodyType of '4' indicates it is a MIME message, and the
MessageClass indicates it's S/MIME Signed. I have similar tests with
just encrypted and signed/encrypted.
More information about the bugs
mailing list