[Tickets #13711] Re: ActiveSync via Outlook 2013: Empty Mails

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/13711
------------------------------------------------------------------------------
  Ticket           | 13711
  Aktualisiert Von | patrick at spamreducer.eu
  Zusammenfassung  | ActiveSync via Outlook 2013: Empty Mails
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Feedback
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


patrick at spamreducer.eu (2014-12-04 19:43) hat geschrieben:

> You would need to find all the horde_activesync_cache table entries  
> that correspond to your OL clients, then look at the "collections"  
> array in the serialized data, and change the value of mimetruncation  
> to false (which in serialized format would be b:0. Better yet, you  
> should write a small script to read the cache data, unserialize it,  
> change the mimetruncation value and rewrite it out to the database.
>
> Additionally, there are a few different ways that a client can  
> indicate it wants truncated data (which caused this problem in the  
> first place). I'm going on the assumption that your OL is requesting  
> this data in the same way as my test install.
>
> Before doing anything this destructive though, I would recommend  
> resetting at least one of your accounts to be SURE that this is the  
> issue.

Thank you very much! I will try to do that tomorrow.

Another thought:
All new received messages in OL show some of the MIME headers in  
message body. Special chars like the german "ä" appear as ecoded  
strings.. Messages are very hard to read since a lot of escaping chars  
in body tend to be unreadable..
could this be an issue with this mime truncation problem?