Summary | Don't override sticky OPTIONS values with default values. |
Queue | Horde Framework Packages |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | software-horde (at) interfasys (dot) ch |
Created | 02/12/2014 (4170 days ago) |
Due | |
Updated | 10/30/2014 (3910 days ago) |
Assigned | 10/27/2014 (3913 days ago) |
Resolved | 10/30/2014 (3910 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
I thought I did. The revert probably blew it away though. Again,
thanks for the catch.
And sorry for not providing a patch myself. I simply moved the options
from that array to the empty array in _parseSyncOptions, but thought
there might be more to it.
commit 1628efa4bc3e19da7b5dc9e4a34026bc86e7b474
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Wed Oct 29 20:07:23 2014 -0400
This got lost during the revert.
(Hopefully) final fix for
Bug: 12970.../lib/Horde/ActiveSync/Collections.php | 7 +------
1 files changed, 1 insertions(+), 6 deletions(-)
http://github.com/horde/horde/commit/1628efa4bc3e19da7b5dc9e4a34026bc86e7b474
'clientids' => array(),
'fetchids' => array(),
'windowsize' => 100
I thought I did. The revert probably blew it away though. Again,
thanks for the catch.
Better, correct, fix now in place. Thanks for the catch.
'clientids' => array(),
'fetchids' => array(),
'windowsize' => 100
If I understand it correctly, it adds defaults in case options are
not given and we want the opposite: default options when options are
being sent in a sync so that the minimum requirements are met.
Better, correct, fix now in place. Thanks for the catch.
commit cc88e5476914a6f6a41837a71ca4a5bffa8375b8
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Wed Oct 29 19:28:35 2014 -0400
Proper fix for
Bug: 12970.../lib/Horde/ActiveSync/Collections.php | 30
++++++++++++++++++++
.../lib/Horde/ActiveSync/Request/Sync.php | 7 ++--
2 files changed, 34 insertions(+), 3 deletions(-)
http://github.com/horde/horde/commit/cc88e5476914a6f6a41837a71ca4a5bffa8375b8
commit b5fc1d2b2af1132651cd20856c91c5788e8cd42a
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Wed Oct 29 19:27:25 2014 -0400
Revert "
Bug: 12970Don't overwrite sticky OPTIONS."This reverts commit 3902eb2f42197aea6d291816ae204711ff96edb7.
Conflicts:
framework/ActiveSync/lib/Horde/ActiveSync/Collections.php
.../lib/Horde/ActiveSync/Collections.php | 24
+++++---------------
.../lib/Horde/ActiveSync/Request/Sync.php | 5 ----
2 files changed, 6 insertions(+), 23 deletions(-)
http://github.com/horde/horde/commit/b5fc1d2b2af1132651cd20856c91c5788e8cd42a
and it is readable in Horde, as well an another iOS client that
receives it via ActiveSync.
wrong cert...
If I understand it correctly, it adds defaults in case options are not
given and we want the opposite: default options when options are being
sent in a sync so that the minimum requirements are met.
commit 3902eb2f42197aea6d291816ae204711ff96edb7
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Wed Oct 29 13:03:03 2014 -0400
Bug: 12970Don't overwrite sticky OPTIONS..../lib/Horde/ActiveSync/Collections.php | 25 +++++++++++++++----
.../lib/Horde/ActiveSync/Request/Sync.php | 5 ++++
2 files changed, 24 insertions(+), 6 deletions(-)
http://github.com/horde/horde/commit/3902eb2f42197aea6d291816ae204711ff96edb7
exactly what is being sent along each step of the way. Kind of hard
for me to debug without a device to test, or at the very least the
actual data transmitted.
encrypted message from iOS 8.1 can't be read in Horde.
it is readable in Horde, as well an another iOS client that receives
it via ActiveSync.
not following the rules.
the rules...very frustrating.
Horde_ActiveSync_Adapter::_buildMailMessage().
but I'm guessing Horde doesn't touch the message unless it's over
the limit.
limited to 76 characters per line.
following the rules.
Could message truncation have and impact on that? They set a limit,
but I'm guessing Horde doesn't touch the message unless it's over the
limit.
and that throws off the OpenSSL parser.
If I format the data using a max-length of 72 characters, then
OpenSSL can decrypt the data.
length of 76 characters. This is almost certainly a BB bug.
handle it as is. That's one half of the problem.
prevents the BB client from understanding the message it gets or if
the client only understands messages where the data is on one line.
per line allowed in pkcs7 data, so I'm guessing that what they're
doing is legal and one reason most clients can read it.
limited to 76 characters per line.
one from the BB client and one from the iOS client using `openssl cms`.
Message from TB can be decrypted properly
Message from iOS can't be decrypted because iOS got confused and used
the wrong certificate to encrypt the message. Not sure what happened,
but I can't test further as the client just crashes as soon as it
receives certificates from Horde.
Message from BB client can't be decrypted as is
Error reading S/MIME message
34374513640:error:0D07207B:asn1 encoding
routines:ASN1_get_object:header too long:asn1_lib.c:153:
34374513640:error:0D0D106E:asn1 encoding routines:B64_READ_ASN1:decode
error:asn_mime.c:193:
34374513640:error:0D0D40CB:asn1 encoding routines:SMIME_read_ASN1:asn1
parse error:asn_mime.c:528:
After analysis, I found that the pkcs7 data is sent in one long line
and that throws off the OpenSSL parser.
If I format the data using a max-length of 72 characters, then OpenSSL
can decrypt the data.
What's inside is another binary message which starts with
Content-Type: application/x-pkcs7-mime
Content-Transfer-Encoding: base64
but this time it's a signed message with a SignedData structure and
lines with fixed width.
So, my guess is that Horde sends the msg to OpenSSL which can't handle
it as is. That's one half of the problem.
The other half is figuring out if Horde is doing something which
prevents the BB client from understanding the message it gets or if
the client only understands messages where the data is on one line.
I couldn't find a spec regarding the maximum amount of characters per
line allowed in pkcs7 data, so I'm guessing that what they're doing is
legal and one reason most clients can read it.
exactly what is being sent along each step of the way. Kind of hard
for me to debug without a device to test, or at the very least the
actual data transmitted.
encrypted message from iOS 8.1 can't be read in Horde.
I would start by getting wire traces and full debug sync logs to see
exactly what is being sent along each step of the way. Kind of hard
for me to debug without a device to test, or at the very least the
actual data transmitted.
problem remains and I have no idea where to look.
Encrypted message
Horde > BB 10
Device says message is not valid
Horde > iOS
Message can be decrypted
BB10 > Horde
Can't read message
BB10 > iOS
Can read the message just fine
iOS > Horde
Can't decrypt message
iOS > BB10
TBD
Summary ⇒ Don't override sticky OPTIONS values with default values.
State ⇒ Assigned
collections->getNewCollection() which contains defaults which are only
overridden if the sync contains an options block.
I've moved the defaults to Sync->_parseSyncOptions() and it seems to
work as expected.
in the table horde_activesync_cache.
not stored properly.
That's what the logs show
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <Synchronize>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <Folders>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <Folder>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <SyncKey>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I
{542e663e-92d4-4777-a9de-1a73904cae96}132
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </SyncKey>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <FolderId>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I F0b8f474e
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </FolderId>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <GetChanges />
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <WindowSize>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 25
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </WindowSize>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <Options>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <FolderType>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I Email
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </FolderType>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <FilterType>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 0
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </FilterType>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <MIMESupport>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 1
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </MIMESupport>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <MIMETruncation>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 7
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </MIMETruncation>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <AirSyncBase:BodyPreference>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <AirSyncBase:Type>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 2
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </AirSyncBase:Type>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </AirSyncBase:BodyPreference>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <AirSyncBase:BodyPreference>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <AirSyncBase:Type>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 1
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </AirSyncBase:Type>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </AirSyncBase:BodyPreference>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <AirSyncBase:BodyPreference>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <AirSyncBase:Type>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 4
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </AirSyncBase:Type>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I <AirSyncBase:TruncationSize>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I 200000
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </AirSyncBase:TruncationSize>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </AirSyncBase:BodyPreference>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </Options>
2014-10-27T10:30:50+01:00 DEBUG: [88886] I </Folder>
2014-10-27T10:30:50+01:00 INFO: [88886] Collection added to collection
handler: collection: INBOX, synckey:
{542e663e-92d4-4777-a9de-1a73904cae96}132.
and that's what I see in the table
s: 9: "F0b8f474e";a: 13: {
s: 5: "class";s: 5: "Email";s: 10: "windowsize";s: 2: "25";s: 10:
"truncation";i: 0;s: 11: "mimesupport";i: 0;s: 14: "mimetruncation";i:
8;s: 8: "conflict";i: 1;s: 9: "bodyprefs";a: 3: {
i: 2;a: 1: {
s: 4: "type";s: 1: "2";
}i: 1;a: 1: {
s: 4: "type";s: 1: "1";
}i: 4;a: 2: {
s: 4: "type";s: 1: "4";s: 14: "truncationsize";s: 6: "200000";
}
}s: 8: "serverid";s: 5: "INBOX";s: 11: "lastsynckey";s: 41:
"{542e663e-92d4-4777-a9de-1a73904cae96}132";s: 10: "filtertype";s: 1:
"0";s: 2: "id";s: 9: "F0b8f474e";s: 14: "deletesasmoves";b: 1;s: 8:
"pingable";b: 1;
I was misunderstanding what was happening on your end. I thought the
client WAS sending an OPTIONS request, but was just not including the
MIMESUPPORT. We fill in any missing values in
Horde_ActiveSync_SyncCache::validateCollectionsFromCache()
Maybe what is happening is that at some point after the initial sync,
the client IS sending an OPTIONS request either without the
MIMESUPPORT or with it set to 0. This then becomes the cached value of
the OPTIONS to be used when it is omitted.
You can verify that the MIMESUPPORT value is being cached by looking
in the table horde_activesync_cache.
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.
OPTIONS is being sent. It only happens when settings things up.
Afterwards, there is never another SYNC > OPTIONS being sent.
And according to 2.2.3.115.5, these options have to be kept in the
database and re-used across requests:
"The server preserves the Options block across requests, using a
concept referred to as "sticky options". If the Options block is not
included in a request, the previous Options block is used. "
Regarding the patch, it's half working.
For the encrypted message, same as before in the logs, but the device
now knows it's an encrypted message, but still receives it as HTML and
can't decrypt it.
For signed messages, there are now extra steps.
First the message is the usual HTML one with no MIMESUPPORT in
getMessage, but then it triggers an itemoperation which includes
MIMESUPPORT.
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.
Sync>Options request and it is when the collection is being defined.
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.
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.
Sync>Options request and it is when the collection is being defined.
I changed it so that we always at least set the message class value
for S/MIME messages, even if we are not sending the MIME part.
commit 6ed73e0edab15b6132a7ef7918fdbfd2c362fa81
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Sun Oct 26 13:43:14 2014 -0400
Set the SMIME message class regardless of MIME support value.
Another attempt at
Bug: 12970.../lib/Horde/ActiveSync/Imap/Adapter.php | 11 +++++------
1 files changed, 5 insertions(+), 6 deletions(-)
http://github.com/horde/horde/commit/6ed73e0edab15b6132a7ef7918fdbfd2c362fa81
comment
#32, the client supports type 1. It's defined atprovisioning time or when adding a collection.
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.
unencrypted messages and I think it's normal, as it's an optional
element, unless the client is fetching a S/MIME message.
message, but fails to tell the server that it can support it.
sent when receiving the message
method is deprecated.
always being set to IPM.Note, and NOT IPM.Note.SMIME. Below, it
clearly shows that it IS set correctly.
would happen later on in the chain if given the mimetype I think it
expects.
anything related to MIME.
never get the full MIME message as long as the client is sending
MIMESUPPORT of 0.
default value of 0 should be used. See the reference I posted earlier
in this message.
request, but a value of 1 has been sent when adding the collection
via a sync command and I think that it's the value which should be
used since the client is not sending an updated value of 0 per
example.
earlier value of just one OPTION field. The client can omit the entire
collection in a SYNC request, and flag it as a PARTIAL, in which case
the server falls back to the last SYNC information for that collection
in it's entirety. If this is what BB is expecting, it's a bug in their
implementation.
configurable value. It comes from the client and it indicates what
the client is able to understand, or what it is expecting to be
returned. Changing it on the server side after the client sends it
leads to undefined behavior because the device is not longer
receiving what it is expecting in return.
comment
#32, the client supports type 1. It's defined at provisioningtime or when adding a collection.
I've verified that the client never sets it in itemoperations for
unencrypted messages and I think it's normal, as it's an optional
element, unless the client is fetching a S/MIME message. For an
encrypted message, there is no itemoperations command being sent when
receiving the message
always being set to IPM.Note, and NOT IPM.Note.SMIME. Below, it
clearly shows that it IS set correctly.
happen later on in the chain if given the mimetype I think it expects.
never get the full MIME message as long as the client is sending
MIMESUPPORT of 0.
value because it could not find it in the request, but a value of 1
has been sent when adding the collection via a sync command and I
think that it's the value which should be used since the client is not
sending an updated value of 0 per example.
configurable value. It comes from the client and it indicates what the
client is able to understand, or what it is expecting to be returned.
Changing it on the server side after the client sends it leads to
undefined behavior because the device is not longer receiving what it
is expecting in return.
which can't be read on the other side.
always being set to IPM.Note, and NOT IPM.Note.SMIME. Below, it
clearly shows that it IS set correctly.
So this is the log when only the BlackBerry gets the message.
mimesupport is set at 0 (int versus string for the other device)
never get the full MIME message as long as the client is sending
MIMESUPPORT of 0.
which can't be read on the other side.
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <POOMMAIL:Importance>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 1
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </POOMMAIL:Importance>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <POOMMAIL:Read>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 0
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </POOMMAIL:Read>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <POOMMAIL:MessageClass>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O IPM.Note.SMIME
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </POOMMAIL:MessageClass>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <POOMMAIL:InternetCPID>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 65001
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </POOMMAIL:InternetCPID>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:NativeBodyType>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 1
2014-10-26T02:04:10+01:00 DEBUG: [18622] O
</AirSyncBase:NativeBodyType>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:Body>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:Type>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 4
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:Type>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O
<AirSyncBase:EstimatedDataSize>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 17314
2014-10-26T02:04:10+01:00 DEBUG: [18622] O
</AirSyncBase:EstimatedDataSize>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:Truncated>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 0
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:Truncated>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:Data>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O [STREAM]
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:Data>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:Body>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:Attachments>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:Attachment>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:DisplayName>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O S/MIME Encrypted Message
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:DisplayName>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O
<AirSyncBase:FileReference>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O INBOX:3336:1
2014-10-26T02:04:10+01:00 DEBUG: [18622] O
</AirSyncBase:FileReference>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:Method>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 1
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:Method>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O
<AirSyncBase:EstimatedDataSize>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 8826
2014-10-26T02:04:10+01:00 DEBUG: [18622] O
</AirSyncBase:EstimatedDataSize>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <AirSyncBase:IsInline>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O 1
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:IsInline>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:Attachment>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </AirSyncBase:Attachments>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <POOMMAIL:Flag/>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <POOMMAIL:ContentClass>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O urn:content-classes:message
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </POOMMAIL:ContentClass>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O <POOMMAIL:Categories/>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </Data>
2014-10-26T02:04:10+01:00 DEBUG: [18622] O </Add>
Any message sent from outside is detected as being encrypted, but the
device says the message isn't valid.
The reverse is true as well, the device can send encrypted messages
and read them, but Horde doesn't understand them.
Thunderbird can read everything.
So this is the log when only the BlackBerry gets the message.
mimesupport is set at 0 (int versus string for the other device)
2014-10-26T02:26:59+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
bool(false)
["bodyprefs"]=>
array(3) {
[2]=>
array(2) {
["type"]=>
string(1) "2"
["truncationsize"]=>
int(1048576)
}
[1]=>
array(2) {
["type"]=>
string(1) "1"
["truncationsize"]=>
int(1048576)
}
[4]=>
array(2) {
["type"]=>
string(1) "4"
["truncationsize"]=>
string(6) "200000"
}
}
["mimesupport"]=>
int(0)
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T02:26:59+02:00 DEBUG: Variable information:
bool(false)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:989
2014-10-26T02:26:59+02:00 DEBUG: Variable information:
bool(true)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:990
2014-10-26T01:14:14+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
bool(false)
["bodyprefs"]=>
array(3) {
[2]=>
array(2) {
["type"]=>
string(1) "2"
["truncationsize"]=>
int(1048576)
}
[1]=>
array(2) {
["type"]=>
string(1) "1"
["truncationsize"]=>
int(1048576)
}
[4]=>
array(2) {
["type"]=>
string(1) "4"
["truncationsize"]=>
string(6) "200000"
}
}
["mimesupport"]=>
int(0)
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T01:14:14+02:00 DEBUG: Variable information:
bool(true)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:989
2014-10-26T01:14:14+02:00 DEBUG: Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:990
2014-10-26T01:14:15+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
int(4096)
["bodyprefs"]=>
array(1) {
[1]=>
array(2) {
["type"]=>
string(1) "1"
["truncationsize"]=>
string(3) "500"
}
}
["mimesupport"]=>
string(1) "0"
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T01:14:15+02:00 DEBUG: Variable information:
bool(true)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:989
2014-10-26T01:14:15+02:00 DEBUG: Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:990
2014-10-26T01:14:15+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
bool(false)
["bodyprefs"]=>
array(1) {
[4]=>
&array(2) {
["type"]=>
string(1) "4"
["truncationsize"]=>
int(1048576)
}
}
["mimesupport"]=>
string(1) "2"
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Driver_Base->fetch()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:559
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Driver/Base.php:254
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T01:14:15+02:00 DEBUG: Variable information:
bool(true)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Driver_Base->fetch()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:559
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Driver/Base.php:254
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:989
2014-10-26T01:14:15+02:00 DEBUG: Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Driver_Base->fetch()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:559
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Driver/Base.php:254
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:990
global debug log file. Here is the proper output for a meesage which
is both signed and encrypted
2014-10-26T00:57:01+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
int(4096)
["bodyprefs"]=>
array(1) {
[1]=>
array(2) {
["type"]=>
string(1) "1"
["truncationsize"]=>
string(3) "500"
}
}
["mimesupport"]=>
string(1) "0"
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T00:57:01+02:00 DEBUG: Variable information:
bool(false)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:989
2014-10-26T00:57:01+02:00 DEBUG: Variable information:
bool(true)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:990
2014-10-26T00:57:01+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
bool(false)
["bodyprefs"]=>
array(3) {
[2]=>
array(2) {
["type"]=>
string(1) "2"
["truncationsize"]=>
int(1048576)
}
[1]=>
array(2) {
["type"]=>
string(1) "1"
["truncationsize"]=>
int(1048576)
}
[4]=>
array(2) {
["type"]=>
string(1) "4"
["truncationsize"]=>
string(6) "200000"
}
}
["mimesupport"]=>
int(0)
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T00:57:01+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
bool(false)
["bodyprefs"]=>
array(1) {
[4]=>
&array(2) {
["type"]=>
string(1) "4"
["truncationsize"]=>
int(1048576)
}
}
["mimesupport"]=>
string(1) "2"
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Driver_Base->fetch()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:559
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Driver/Base.php:254
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T00:57:01+02:00 DEBUG: Variable information:
bool(false)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Driver_Base->fetch()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:559
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Driver/Base.php:254
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:989
2014-10-26T00:57:01+02:00 DEBUG: Variable information:
bool(true)
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Driver_Base->fetch()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:559
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Driver/Base.php:254
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:990
device. Seems like Horde is sending the plain text and the S/MIME parts.
2014-10-26T00:34:00+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
bool(false)
["bodyprefs"]=>
array(3) {
[2]=>
array(2) {
["type"]=>
string(1) "2"
["truncationsize"]=>
int(1048576)
}
[1]=>
array(2) {
["type"]=>
string(1) "1"
["truncationsize"]=>
int(1048576)
}
[4]=>
array(2) {
["type"]=>
string(1) "4"
["truncationsize"]=>
string(6) "200000"
}
}
["mimesupport"]=>
int(0)
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T00:34:01+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
int(4096)
["bodyprefs"]=>
array(1) {
[1]=>
array(2) {
["type"]=>
string(1) "1"
["truncationsize"]=>
string(3) "500"
}
}
["mimesupport"]=>
string(1) "0"
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Connector_Exporter->sendNextChange()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:613
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Connector/Exporter.php:215
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
2014-10-26T00:34:02+02:00 DEBUG: Variable information:
array(4) {
["protocolversion"]=>
string(4) "14.1"
["truncation"]=>
bool(false)
["bodyprefs"]=>
array(1) {
[4]=>
&array(2) {
["type"]=>
string(1) "4"
["truncationsize"]=>
int(1048576)
}
}
["mimesupport"]=>
string(1) "2"
}
Backtrace:
1. Horde_Rpc_ActiveSync->getResponse() /var/www/html/webmail/rpc.php:159
2. Horde_ActiveSync->handleRequest()
/usr/local/php54/lib/php/Horde/Rpc/ActiveSync.php:143
3. Horde_ActiveSync_Request_Base->handle()
/usr/local/php54/lib/php/Horde/ActiveSync.php:880
4. Horde_ActiveSync_Request_Sync->_handle()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Base.php:253
5. Horde_ActiveSync_Driver_Base->fetch()
/usr/local/php54/lib/php/Horde/ActiveSync/Request/Sync.php:559
6. Horde_Core_ActiveSync_Driver->getMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Driver/Base.php:254
7. Horde_ActiveSync_Imap_Adapter->getMessages()
/usr/local/php54/lib/php/Horde/Core/ActiveSync/Driver.php:1274
8. Horde_ActiveSync_Imap_Adapter->_buildMailMessage()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:535
9. Horde::debug()
/usr/local/php54/lib/php/Horde/ActiveSync/Imap/Adapter.php:988
So, to continue debugging try adding:
Horde::debug($options);
Horde::debug($imap_message->isSigned());
Horde::debug($imap_message->isEncrypted());
in Horde_ActiveSync_Imap_Adapter::_buildMailMessage() right before the
if statement on line 988. The output will be put into a file name
horde_debug.txt in your system's tmp directory.
I'll configure it to sync everything for 1 month and will enable
S/MIME, with forced signatures.
All this can be changed at will if you need to be able to sync data
for a shorter period of time per example.
though it recognises that it's a S/MIME message.
iPhone, but not in Horde.
What do you need from me to attempt to add my simulator to your BES?
So there is no MIMESupport options being sent before the message
itself is being sent in HTML.
Is there another tag to look for?
I've added a new folder to sync to see what would be asked and it
seems it's expecting type 1,2 or 4 (text,html,mime).
Also any message sent by the device can't be decoded by Horde, even
though it recognises that it's a S/MIME message.
Here is the log when adding the folder:
DEBUG: [91873] I <Folder>
DEBUG: [91873] I <SyncKey>
DEBUG: [91873] I {544c0366-24f4-4ee2-841b-66e1904cae96}1
DEBUG: [91873] I </SyncKey>
DEBUG: [91873] I <FolderId>
DEBUG: [91873] I Fc767dd23
DEBUG: [91873] I </FolderId>
DEBUG: [91873] I <GetChanges />
DEBUG: [91873] I <WindowSize>
DEBUG: [91873] I 25
DEBUG: [91873] I </WindowSize>
DEBUG: [91873] I <Options>
DEBUG: [91873] I <FolderType>
DEBUG: [91873] I Email
DEBUG: [91873] I </FolderType>
DEBUG: [91873] I <FilterType>
DEBUG: [91873] I 0
DEBUG: [91873] I </FilterType>
DEBUG: [91873] I <MIMESupport>
DEBUG: [91873] I 1
DEBUG: [91873] I </MIMESupport>
DEBUG: [91873] I <MIMETruncation>
DEBUG: [91873] I 7
DEBUG: [91873] I </MIMETruncation>
DEBUG: [91873] I <AirSyncBase:BodyPreference>
DEBUG: [91873] I <AirSyncBase:Type>
DEBUG: [91873] I 2
DEBUG: [91873] I </AirSyncBase:Type>
DEBUG: [91873] I </AirSyncBase:BodyPreference>
DEBUG: [91873] I <AirSyncBase:BodyPreference>
DEBUG: [91873] I <AirSyncBase:Type>
DEBUG: [91873] I 1
DEBUG: [91873] I </AirSyncBase:Type>
DEBUG: [91873] I </AirSyncBase:BodyPreference>
DEBUG: [91873] I <AirSyncBase:BodyPreference>
DEBUG: [91873] I <AirSyncBase:Type>
DEBUG: [91873] I 4
DEBUG: [91873] I </AirSyncBase:Type>
DEBUG: [91873] I <AirSyncBase:TruncationSize>
DEBUG: [91873] I 200000
DEBUG: [91873] I </AirSyncBase:TruncationSize>
DEBUG: [91873] I </AirSyncBase:BodyPreference>
DEBUG: [91873] I </Options>
DEBUG: [91873] I </Folder>
sent, which doesn't support SMIME. The device must explicitly
request a MIME message.
so I'm guessing it's asking for a MIME message?
the MIME message. Horde just has to do extra work to parse out the
attachment from the message and send it separately.
The device creates a smime.p7m attach
in this case, is just another attachment. Though I thought we were
filtering out signatures in this case, I'll have to double check.
Either way, not an indication the device is requesting a MIME message.
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.
so I'm guessing it's asking for a MIME message?
Horde creates a S/MIME Encrypted Message attachement
The device creates a smime.p7m attach
and not plaintext or html?
not plaintext or html?
the same "plain text" MessageClass of IMP.Note, so it seems the
ActiveSync "parser" is not detecting the message as being encrypted or
signed.
Since my certs expired today, I need to see if this plays a role, but
I doubt it. The next step would be for me to be able to trace which
mime types are detected.
I'm going to send you test emails as soon as I've renewed the certs
commit 9118988317a9e9b08bbd8b512df5c6e8da562ec2
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Sat Oct 25 10:47:01 2014 -0400
Bug: 12970More fixes for S/MIME handling in EAS..../lib/Horde/ActiveSync/Imap/Adapter.php | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
http://github.com/horde/horde/commit/9118988317a9e9b08bbd8b512df5c6e8da562ec2
message? All of my test emails work here, and the unit tests that
detect if they are signed or encrypted currently pass.
User-Agent: Internet Messaging Program (IMP) H5 (6.2.2)
Content-Type: application/pkcs7-mime; smime-type=enveloped-data
Content-Description: S/MIME Encrypted Message
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: base64
I've sent an encrypted message from Horde and the MessageClass is
still IPM.Note
INFO: [8022] Horde_Core_ActiveSync_Driver::getMessage(INBOX, 3301)
INFO: [8022] Sending HTML Message.
INFO: FETCHING VERB
INFO: RETURNING VERB
DEBUG: [8022] O <Commands>
DEBUG: [8022] O <Add>
DEBUG: [8022] O <ServerEntryId>
DEBUG: [8022] O 3301
DEBUG: [8022] O </ServerEntryId>
DEBUG: [8022] O <Data>
DEBUG: [8022] O <POOMMAIL:To>
DEBUG: [8022] O recipient@domain.tld
DEBUG: [8022] O </POOMMAIL:To>
DEBUG: [8022] O <POOMMAIL:From>
DEBUG: [8022] O sender@domain.tld
DEBUG: [8022] O </POOMMAIL:From>
DEBUG: [8022] O <POOMMAIL:Subject>
DEBUG: [8022] O hordesmimepatch
DEBUG: [8022] O </POOMMAIL:Subject>
DEBUG: [8022] O <POOMMAIL:Reply-To>
DEBUG: [8022] O recipient@domain.tld
DEBUG: [8022] O </POOMMAIL:Reply-To>
DEBUG: [8022] O <POOMMAIL:DateReceived>
DEBUG: [8022] O 2014-10-24T22:54:17.000Z
DEBUG: [8022] O </POOMMAIL:DateReceived>
DEBUG: [8022] O <POOMMAIL:DisplayTo>
DEBUG: [8022] O recipient@domain.tld
DEBUG: [8022] O </POOMMAIL:DisplayTo>
DEBUG: [8022] O <POOMMAIL:ThreadTopic>
DEBUG: [8022] O hordesmimepatch
DEBUG: [8022] O </POOMMAIL:ThreadTopic>
DEBUG: [8022] O <POOMMAIL:Importance>
DEBUG: [8022] O 1
DEBUG: [8022] O </POOMMAIL:Importance>
DEBUG: [8022] O <POOMMAIL:Read>
DEBUG: [8022] O 0
DEBUG: [8022] O </POOMMAIL:Read>
DEBUG: [8022] O <POOMMAIL:MessageClass>
DEBUG: [8022] O IPM.Note
DEBUG: [8022] O </POOMMAIL:MessageClass>
DEBUG: [8022] O <POOMMAIL:InternetCPID>
DEBUG: [8022] O 65001
DEBUG: [8022] O </POOMMAIL:InternetCPID>
DEBUG: [8022] O <AirSyncBase:NativeBodyType>
DEBUG: [8022] O 1
DEBUG: [8022] O </AirSyncBase:NativeBodyType>
DEBUG: [8022] O <AirSyncBase:Attachments>
DEBUG: [8022] O <AirSyncBase:Attachment>
DEBUG: [8022] O <AirSyncBase:DisplayName>
DEBUG: [8022] O S/MIME Encrypted Message
DEBUG: [8022] O </AirSyncBase:DisplayName>
DEBUG: [8022] O <AirSyncBase:FileReference>
DEBUG: [8022] O INBOX:3301:1
DEBUG: [8022] O </AirSyncBase:FileReference>
DEBUG: [8022] O <AirSyncBase:Method>
DEBUG: [8022] O 1
DEBUG: [8022] O </AirSyncBase:Method>
DEBUG: [8022] O <AirSyncBase:EstimatedDataSize>
DEBUG: [8022] O 15351
DEBUG: [8022] O </AirSyncBase:EstimatedDataSize>
DEBUG: [8022] O <AirSyncBase:IsInline>
DEBUG: [8022] O 1
DEBUG: [8022] O </AirSyncBase:IsInline>
DEBUG: [8022] O </AirSyncBase:Attachment>
DEBUG: [8022] O </AirSyncBase:Attachments>
DEBUG: [8022] O <POOMMAIL:Flag/>
DEBUG: [8022] O <POOMMAIL:ContentClass>
DEBUG: [8022] O urn:content-classes:message
DEBUG: [8022] O </POOMMAIL:ContentClass>
DEBUG: [8022] O <POOMMAIL:Categories/>
DEBUG: [8022] O </Data>
DEBUG: [8022] O </Add>
INFO: [8022] Updating state during change
DEBUG: [8022] O </Commands>
commit 5a29cb2215a357c9674147615399da22f05b260c
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Fri Oct 24 16:49:16 2014 -0400
Bug: 12970Differentiate between signed and encrypted messages..../lib/Horde/ActiveSync/Imap/Adapter.php | 6 ++-
.../lib/Horde/ActiveSync/Imap/Message.php | 26 ++++++++++--
framework/ActiveSync/lib/Horde/ActiveSync/Mime.php | 41 +++++++++++++++----
3 files changed, 58 insertions(+), 15 deletions(-)
http://github.com/horde/horde/commit/5a29cb2215a357c9674147615399da22f05b260c
framework/ActiveSync/lib/Horde/ActiveSync/Imap/Adapter.php
The default MessageClass is IPM.Note
If the message is signed, then it's set to IPM.Note.SMIME.MultipartSigned
but it's never set to IPM.Note.SMIME which I think is how encrypted
messages are identified.
iOS probably ignores that element, but I think BlackBerry 10 is using
it in order to determine how to parse the message.
Where do I find it?
directly and you can import it from that.
Where do I find it?
directly and you can import it from that.
I still don't have access to a BB that supports s/mime, but I'll at
least try to look at the messages and see what I can figure out.
FWIW though, we pass the raw mime data directly when it's
signed/encrypted so I'm not sure what can be done...
Where do I find it?
- Messages sent from Thunderbird or the phone can be decrypted from
the phone (Yeah! :))
- Messages sent from IMP can't be decrypted by the phone
- Messages sent from the phone can't be decrypted by IMP
I still don't have access to a BB that supports s/mime, but I'll at
least try to look at the messages and see what I can figure out. FWIW
though, we pass the raw mime data directly when it's signed/encrypted
so I'm not sure what can be done...
- Messages sent from Thunderbird or the phone can be decrypted from
the phone (Yeah! :))
- Messages sent from IMP can't be decrypted by the phone
- Messages sent from the phone can't be decrypted by IMP
Messages sent from the phone which are placed in the sent folder can
now be decrypted by the phone.
commit 71ffec6a7d5d9a1bd626febdb3bec09e9d955451
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Mon Apr 7 12:01:48 2014 -0400
One more place to accept the deprecated x-pkcs7-* subtypes.
Bug: 12970.../lib/Horde/ActiveSync/Imap/Message.php | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
http://github.com/horde/horde/commit/71ffec6a7d5d9a1bd626febdb3bec09e9d955451
State ⇒ Feedback
commit 1082153498149b1653ab4f2af67eff0d86c62de8
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Mon Apr 7 11:55:50 2014 -0400
Parse x-pkcs7-mime as well.
Possible fix for
Bug: 12970.../lib/Horde/ActiveSync/Imap/Message.php | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
http://github.com/horde/horde/commit/1082153498149b1653ab4f2af67eff0d86c62de8
State ⇒ Assigned
All accounts are using Horde's activesync v2.12.4
"Sent message" is the one in the Sent box
Sending from Thunderbird
--------------------------------------------------
Sent message can be decrypted by IMP
Received message can be decrypted by IMP
Sent message CANNOT be decrypted by the phone
* NEW* Received message can now be decrypted by the phone
Sending from IMP
----------------------------------------
Sent message can by decrypted by IMP
Received message can be decrypted by IMP
Sent message CANNOT by decrypted by the phone: "The S/MIME message
can't be opened because it isn't valid"
Received message CANNOT be decrypted by phone. I get the MIME
Encrypted message attachment which can't be viewed
Sending from Phone
---------------------------------------
Sent message CANNOT by decrypted by IMP: Here is what's shown in IMP:
"smime.p7m (10 KB)
The data in this part has been encrypted via S/MIME.
application/x-pkcs7-mime X-pkcs7-mime (4 KB)
The data in this part has been encrypted via S/MIME.
Could not decrypt S/MIME data."
Received message CANNOT be decrypted by IMP: "Could not decrypt S/MIME data."
Sent message CANNOT by decrypted by the phone: The attachment is named
smime.p7m and there is no viewer for it on the device.
Received message CANNOT be decrypted by phone: The attachment is named
smime.p7m and there is no viewer for it on the device.
All messages can be decrypted by Thunderbird, so it seems the messages
are correctly assembled. Some are just not properly retrieved by
either IMP or the phone.
The changelog for IMP 6.1.7 mentions " Improved support for broken
S/MIME messages.". If you feel BlackBerry's implementation is breaking
RFCs or common practice, let me know and I'll pass along any feedback
you have.
The problems with signature verification were due to an open_basedir
restriction since the OpenSSL CA certs were not in the path.
When IMP fails to decrypt a message, there is nothing at all in the logs.
Content-Type: application/pkcs7-mime; name="smime.p7m";
smime-type=enveloped-data
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7m"
Content-Description: S/MIME Encrypted Message
Headers from BB
Content-Type: application/x-pkcs7-mime; name=smime.p7m;
smime-type=enveloped-data
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=smime.p7m
I notice a different content type, the lack of quotes and the carriage
return in the middle of the Content-Type header in the BB version
Messages themselves are presented differently. It's a block in the TB
message, it's one line in the BB message.
which supports SMIME.
I could provide a test account which works with clients on BlackBerry,
Android and iOS or you could try registering for a trial since you're
developing software which BES can connect to.
- None of the messages are identified as SMIME as far as I can tell
- Encrypted message contains an attachment which is detected as a
"MIME Encrypted Message" and there is a green "tick" indicating it's
valid, but when tapping on it, the device indicates that there is no
viewer for it on the device.
connected to Horde? If the latter, SMIME is not available, as it is
only available, as SMIME is only available when it's a managed device
through BES, AFAIK. If the former, I really don't know, as I don't
have access to BES to test.
compare raw messages to see if I can find differences.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Problems with S/MIME messages when sent to or received from a BlackBerry 10 device using BES
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
#1Send a S/MIME signed message from Thunderbird#2Send a S/MIME encrypted message from Thunderbird#3Send a S/MIME signed message from a BlackBerry 10 device#4Send a S/MIME encrypted message from a BlackBerry 10 deviceI then used Thunderbird, IMP and a BlackBerry 10 device to check the messages.
On Thunderbird
No problem with any of the messages. They are identified as signed or
encrypted and are successfully verified/decrypted.
On IMP
- Signed message
#1shows this error message: "Message verifiedsuccessfully but the signer's certificate could not be verified". The
certificate is in the addressbook and the public key is stored in IMP
though.
- Encrypted message
#2is successfully decrypted.- Signed message
#3shows this error message: "Verification failed -an unknown error has occurred.". The public key is not in the keyring
and IMP doesn't offer to install it (but that could be because of a
problem with Turba's default addressbook)
- Encrypted message
#4shows: "Could not decrypt S/MIME data.". Noerror in the logs.
On BlackBerry 10 device via ActiveSync
- None of the messages are identified as SMIME as far as I can tell
- Encrypted message contains an attachment which is detected as a
"MIME Encrypted Message" and there is a green "tick" indicating it's
valid, but when tapping on it, the device indicates that there is no
viewer for it on the device.