Re: ActiveSync attachments not downloading, disappearing on devices

Quoting Volker Then <[email protected]>:

> Zitat von Michael J Rubinsky <[email protected]>:
>
>> Quoting Volker Then <[email protected]>:
>>
>>> Zitat von Volker Then <[email protected]>:
>>>
>>>> Zitat von Michael J Rubinsky <[email protected]>:
>>>>
>>>>> Quoting Volker Then <[email protected]>:
>>>>>
>>>>>> Zitat von Michael J Rubinsky <[email protected]>:
>>>>>>
>>>>>>> Quoting Michael J Rubinsky <[email protected]>:
>>>>>>>
>>>>>>>> Quoting Michael J Rubinsky <[email protected]>:
>>>>>>>>
>>>>>>>>> Quoting Volker Then <[email protected]>:
>>>>>>>>>
>>>>>>>>>> Dear list,
>>>>>>>>>>
>>>>>>>>>> since a few days there is a problem with ActiveSync on  
>>>>>>>>>> certain devices. Some of my users report the following  
>>>>>>>>>> issues:
>>>>>>>>>>
>>>>>>>>>> - Outlook 15: Most attachments (jpgs, pdfs) are not getting  
>>>>>>>>>> downloaded. Some get downloaded up to 50%, some others  
>>>>>>>>>> aren't visible at all.
>>>>>>>>>>
>>>>>>>>>> - iOS devices: After tapping on the attachment, it gets  
>>>>>>>>>> downloaded and then it's visible for a few milliseconds  
>>>>>>>>>> until it disappears totally.
>>>>>>>>>>
>>>>>>>>>> I keep the horde pear packages up-to-date on an weekly  
>>>>>>>>>> basis. Recently there was an update of the ActiveSync  
>>>>>>>>>> package. Could this be the problem?
>>>>>>>>>>
>>>>>>>>>> In the logfiles (debug and activesync) I see nothing unusual.
>>>>>>>>>>
>>>>>>>>>> The horde server is running on a Debian squeeze machine,  
>>>>>>>>>> PHP 5.3.3-7+squeeze22.
>>>>>>>>>>
>>>>>>>>>> Thanks in advance for any help,
>>>>>>>>>
>>>>>>>>> *sigh*
>>>>>>>>>
>>>>>>>>> It seems that actually correctly performing MIME truncation  
>>>>>>>>> actually breaks these clients. I give up.
>>>>>>>>
>>>>>>>> This was actually my fault.
>>>>>>>>
>>>>>>>> Should be fixed in Git (fixes in both Core and ActiveSync).  
>>>>>>>> Will push a new release after I run/test for a bit more in my  
>>>>>>>> personal production.
>>>>>>>
>>>>>>>
>>>>>>> I pushed the releases for this, as everything seems good.
>>>>>>>
>>>>>>> There is some issue with emails originally containing only  
>>>>>>> plaintext leaking mime boundry text that I'm still looking  
>>>>>>> into, but I think that's due to some recent changes in  
>>>>>>> Horde_Mime since they still occur when the ActiveSync changes  
>>>>>>> are backed out.
>>>>>>>
>>>>>>
>>>>>> Something is wrong with the dependencies:
>>>>>>
>>>>>> horde/Horde_Core requires package "horde/Horde_Mime" (version  
>>>>>> >= 2.5.0, version <= 3.0.0alpha1, excluded versions:  
>>>>>> 3.0.0alpha1), installed version is 2.4.5
>>>>>
>>>>> I didn't realize Horde_Mime's version requirement was bumped.  
>>>>> Pushing a Horde_Mime now.
>>>>>
>>>> Hi Mike,
>>>>
>>>> After the recent updates with fixed horde_smtp, there is still  
>>>> the problem with ActiveSync on iOS (empty message bodies, not  
>>>> attachments being displayed) and Outlook. In the sync log I see  
>>>> several error messages (Outlook):
>>>>
>>>> 2014-11-23T20:30:58+01:00 ERR: [19950] Attempting to add a collection
>>>>                  to the sync cache while requiring a synckey, but no
>>>>                  synckey could be found. Most likely a client error in
>>>>                  requesting a collection during PING before it  
>>>> has issued a
>>>>                  SYNC.
>>>>
>>>> 2014-11-23T20:30:58+01:00 ERR: [21584]  
>>>> Horde_ActiveSync_Collections::getBackendIdForFolderUid failed  
>>>> because folder was not found in cache.
>>>>
>>>> Volker
>>>
>>> After today's ActiveSync update at least iOS is syncing. But I  
>>> have still the issue with my Outlook clients (see above).
>>
>>
>> You mean with blank email bodies? Can you provide a sync log?  I  
>> wasn't seeing that when I tested before release last night.
>>
>
>
> The issue with the blank email bodies was on the iOS client. This  
> seems to be fixed by now. Outlook stopped syncing at all after the  
> recent updates. I sent you the log a few minutes ago.

It looks like the server side folder cache was removed or corrupted,  
but OL is not responding the the '12' status code that tells it to  
re-initialize the state. Try removing and recreating the account.

-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
sync mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]