It depends on what version of the Horde_ActiveSync library you have. I 
can verify that this has been fixed for ages, my WP 8 device works 
perfectly.

Hi Mike !

I have Horde 5.1.4 updated and selected EAS 14.1, but the problem 
still persists.

What else could I do ? Shouldn´t this version already be without this bug ?

Regards,
--
Ricardo Auada

You can't just patch the existing 2.3.6 library with a few changes, 
there were MANY changes between 2.3.x and 2.4.x. I.e., there will be 
no 2.3.7

Test Results:

Code from Stable 2.3.6 with your changes from yesterday, 2013-06-03:
same problem.
Code from Beta 2.4.0RC2 with your changes from yesterday, 2013-06-03:
so far all messages are received with Body again. no other problems visible.
Testes Mails from mobile to self, --> body received
Mails from webclient to self --> body received.
Mails from other source -->body received
mails from other source with attachment --> body received, attachment 
received.
reply from mobile to any --> works as expected.

Thanks again for looking at this and fixing it!

Cheers!

Agreed! Good job! Thanks as well, will test later today and let you 
know! Cheers!

YEHAWW! Great job!

That will make my collegue happy with his WP8 :)

Thanks!

This *should* be good to go now in Git, though I can't test since none 
of my clients send mulitiple collections at a time without OPTIONS 
data on each SYNC request (which is what triggers this).

Changes have been made in Git (master):

commit 919dfd8b4a39337a93e3ae55a85944194b44406c
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Mon Jun 3 13:14:56 2013 -0400

     Bug: 12203 Don't delete the collection cache when initializing a sync.

     Don't blow away the cached body prefs when resetting syncstate to 
synckey = 0, since we
     would have just saved the new values to the cache and have no way 
to fetch them again once
     deleted.

  .../ActiveSync/lib/Horde/ActiveSync/State/Sql.php  |    2 +-
  .../ActiveSync/lib/Horde/ActiveSync/SyncCache.php  |   12 +++++++++---
  2 files changed, 10 insertions(+), 4 deletions(-)

http://git.horde.org/horde-git/-/commit/919dfd8b4a39337a93e3ae55a85944194b44406c

That's what the synclog is for; to see what the device receives.

The INFO entry is normal, it's part of the parsing process when 
dealing with WBXML tags that, according to the specs, are allowed to 
be sent as either an empty tag or a tag that contains content. In the 
current git code, in fact, this log entry has been removed.

The "## ??" string is NOT normal, if this is indeed what is being 
output and not something you altered. I've never seen this before and 
have NO idea what it could be - it's not something the client should 
be sending.
Yes, you may email it directly to me at mrubinsk@horde.org

I ment that I can only see FROM, TO and SUBJECT on the device itself. 
There is no source able to display on the device, so I can't tell if 
all Data are there.

I don't have Version 14 as a choice.

That is the line which cought my attention.
It wasn't a copy/paste, I changed details like USER and Device ID's 
for privacy reason. Is there a private email address I could send the 
logifle to you directly? Maybe the one used in here?

Well, my step by step was to upgrade Horde Webmail from 5.0.3 to 
5.0.5. Nothing else changed.

Ah sorry, you are right!

14 and 14.1 are only available as choices in Horde 5.1.0 and 
ActiveSync 2.4.0 - neither of which are stable as of today.

Can you elaborate on what you mean by "only headers arrive"? Do you 
mean that as you watch the sync log (or a wiretrace) during the sync, 
you only see the WBXML containing the <POOMMAIL:Subject> and related 
nodes, or do you mean that in the MIME data being sent in the 
<AIRSYNCBASE:Body> node, only the headers of the Mime email data are 
being sent? Or do you mean you simply don't see the body in the client?

Since I do not have a WP8 on my own:

during the update, did you also upgrade your maximum supported EAS 
settings from 12 to 14, or did you leave it at 12?

thanks,
Torben

Is this really a copy/paste of the complete log snippet? The 
<SYNCronize> should not be capitalized like that, and the PARTIAL sync 
should contain at least *some* collection data (otherwise it's not a 
PARTIAL, but an EMPTY sync). This log snippet doesn't show any email 
being synched. For this to be useful, I will need a portion of the log 
showing an actual email being sent that *doesn't contain the email 
body*.
I cannot reproduce this on my WP8 device (or WP7, or WP 6.5). The log 
the OP posted shows the *full* email data being sent to the device. If 
the device chooses not to display it, there is nothing Horde can do 
about it.

Additionally, the fact that unchecking and checking the "email sync" 
on the client causes the full data to be displayed tells me that the 
client *has* the data to display. There is nothing in the protocol 
that says "Here is the data, but don't display it until I tell you to."

Unless somebody can give me a step by step to reproduce this on my 
device, there is not much I can do since the data *is* being sent to 
the client.

Oh nice, that may help to disentagle whether it is a WP8 or Horde issue.
Torben

As a matter of fact I was not having any issues on my WP 8 Device 
until I upgraded Horde Webmail from 5.0.3 to 5.0.5. Now I have exactly 
the same problem described below.

If Email's are being "pushed" to the device only headers arrive. 
However if I uncheck Mail sync on the WP 8 Device and recheck Mail 
Sync on WP8 device all Mails got synced with body. New Mails pushed to 
the device are then headers only again.

log snip:

2013-06-03T13:31:51+00:00 INFO: Request being handled for device: *** 
Supporting protocol version: 12.1
2013-06-03T13:31:51+00:00 INFO: [15121] Handling SYNC command.
2013-06-03T13:31:51+00:00 DEBUG: [***] Checking policykey for device: 
0 user: user
2013-06-03T13:31:51+00:00 DEBUG: Policykey: 0 verified.
2013-06-03T13:31:51+00:00 DEBUG: [15121] I <SYNChronize>
...
2013-06-03T13:31:51+00:00 DEBUG: [15121] I  <Partial />
2013-06-03T13:31:51+00:00 DEBUG: [15121] I  </SYNChronize>
## ??
2013-06-03T13:31:51+00:00 INFO: Possible unmatched content (peeking or 
empty tag?)
## ??
2013-06-03T13:31:51+00:00 DEBUG: Have SYNCable collections
2013-06-03T13:31:51+00:00 DEBUG: PARTIAL SYNC
2013-06-03T13:31:51+00:00 DEBUG: Removed {***}17 from confirmed_SyncKeys
2013-06-03T13:31:51+00:00 DEBUG: Removed {***}9 from confirmed_SyncKeys
2013-06-03T13:31:51+00:00 DEBUG: Using SYNCCache State for @Contacts@
2013-06-03T13:31:51+00:00 DEBUG: Using SYNCCache State for @Calendar@
2013-06-03T13:31:51+00:00 DEBUG: Using SYNCCache State for @Tasks@
2013-06-03T13:31:51+00:00 DEBUG: All SyncKeys confirmed. Continuing with SYNC
2013-06-03T13:31:51+00:00 DEBUG: [15121] Replacing SYNC_CACHE entry 
for user user and device ***:

I'm sorry but i doubt that its a WP8 problem, as this only occured 
after upgrade to 5.0.5.

Best regards,

okay thanks, sorry for the noise.
I'll contact my buddy that it is not reproducable.

For the sake of completeness, I have since obtained a WP 8.0 device 
and I can't reproduce on this device either.

Going to close as Not a Bug since I am unable to reproduce on any 
client, and the provided sync log shows nothing but valid Wbxml.

Feel free to reopen if able to provide any errors in the sync log.

you are right, ther were two initial messages, both were readable as 
expected. the third email arriving latet was only shown with the header.
hmm this could be the problem: windows phone seems to be buggy and 
much more problematic to use as an iphone is..

I see 2 messages initially sent to the device, one an HTML email and 
one plaintext. Do the two initials emails show up correctly, or just 
the one?

Then I see the third, plaintext, mail towards the end of the log, but 
unfortunately, don't see anything odd that jumps out.

Yes, I have logs:

a small one seems to bet created only suring device setup, it contains 
only some lines:

2013-04-19T19:37:02+00:00 INFO: [1113] 
Horde_Core_ActiveSync_Driver::authenticate() attempt for test2013
2013-04-19T19:37:36+00:00 INFO: [1229] 
Horde_Core_ActiveSync_Driver::authenticate() attempt for 
test2013@dannhauer.de
2013-04-19T19:37:36+00:00 DEBUG: [1229] OPTIONS request received for 
user test2013@dannhauer.de
2013-04-19T19:37:36+00:00 DEBUG: [1229] loadDeviceInfo:
2013-04-19T19:37:36+00:00 DEBUG: [1229] Device entry does not exist 
for device 316752594875C2D7585578E10AF176EA and user 
test2013@dannhauer.de - creating it.
2013-04-19T19:37:36+00:00 INFO: [1229] User test2013@dannhauer.de logged off
2013-04-19T19:45:13+00:00 INFO: [1378] 
Horde_Core_ActiveSync_Driver::authenticate() attempt for 
test2013@dannhauer.de
2013-04-19T19:45:13+00:00 DEBUG: [1378] OPTIONS request received for 
user test2013@dannhauer.de
2013-04-19T19:45:13+00:00 DEBUG: [1378] loadDeviceInfo: test2013@dannhauer.de
2013-04-19T19:45:13+00:00 INFO: [1378] User test2013@dannhauer.de logged off

the other logifle is the standard hordeActiveSync logfile which I attach.

The following situation is logged:
the postbox contains an existing email message which is fullyvisible in WP8.
then a new email with subject "neue email" is sent to the account,   
which is not fully transfere to WP8 via activeSync : only the sender 
and subject is visible on WP8.

I hope the log contains a hint whats wrong -I have trouble to detect it...

thanks,
Torben

Not sure. Do you have a synclog?

I have a WinMo 7.8 client for testing, and this works fine on that device.

With windows phone 8 and Horde Activesync (12.1), new emails are only 
displayed with sender and subject.
If the email sync is disabled an re-enabled, all existing emails are 
now displayed correctly - but still all new incoming eMails are only 
displayed with sender and subject.

Is this more likely a Horde or a WP8 bug?

Thanks,
Torben