[horde] service.activesync has stopped

[Michael J Rubinsky]

Quoting Samuel Wolf <samuel at sheepflock.de>:

> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Samuel Wolf <samuel at sheepflock.de>:
>>
>>> Zitat von Samuel Wolf <samuel at sheepflock.de>:
>>>
>>>> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>>>>
>>>>> I was wrong. My test Droids at home are running 2.2.2. Don't  
>>>>> have time to mess with changing the ROM at the moment.
>>>>>
>>>>> Anyway, those devices work fine with sending email. I checked  
>>>>> all the commits between 2.3.2 and 2.3.3 and there is NOTHING  
>>>>> changed with email sending. There was a typo in the code that  
>>>>> saves the device information during the first pairing (see the  
>>>>> fix at  
>>>>> https://github.com/horde/horde/commit/cb6a1130bbc9924bc46e65319b7ab5a84a162f98#framework/ActiveSync) but since you said no errors in the logs, and this code is not executed during sending email, that's not the  
>>>>> issue.
>>>>
>>>> Mike, work fine now with Horde_ActiveSync-2.3.4.
>>>> Maybe I overlook a error yesterday in the log :-(
>>>>
>>>> Anyway, it is solved, thank you.
>>>
>>> Unfortunately it is not solved, same error with Horde_ActiveSync-2.3.4.
>>> Nothing in horde.log with loglevel ERR.
>>>
>>> ActiveSync log:
>>> 2013-04-14T10:02:05+00:00 INFO: [21971] User petra logged off
>>> 2013-04-14T12:02:06+02:00 DEBUG: [21548] SyncCache collections refreshed.
>>> 2013-04-14T12:02:06+02:00 DEBUG: [21548] Detected another PING  
>>> process started. Exit and let the newest process handle the PING.
>>> 2013-04-14T12:02:06+02:00 INFO: [21548] User petra logged off
>>> 2013-04-14T10:02:07+00:00 INFO: [21533]  
>>> Horde_Core_ActiveSync_Driver::authenticate() attempt for petra
>>> 2013-04-14T10:02:07+00:00 DEBUG: [21533] PING request received for  
>>> user petra
>>> 2013-04-14T10:02:07+00:00 DEBUG: [21533] loadDeviceInfo: petra
>>> 2013-04-14T10:02:07+00:00 INFO: Request being handled for device:  
>>> 333xxxxxxx Supporting protocol version: 12.1
>>> 2013-04-14T10:02:07+00:00 INFO: [21533] Handling PING command  
>>> received at timestamp: 1365933727.
>>> 2013-04-14T10:02:07+00:00 DEBUG: [21533] I <Ping:Ping>
>>>
>>> I can reproduce by follwoing steps:
>>> * shutdown smartphone
>>> * power on and open mail (inbox)
>>> * wait for a complete refresh
>>> * change into sent mail folder
>>> -> service.activesync has stopped
>>>
>>> My wife has a lot of sent mails with attachments (pictures,..).
>>
>> I flashed a 2.3.7 ROM on one of my Droids. I still am only showing  
>> EAS version 2.5 on it, not 12.1. What device does your wife have?
>
> Interesting, my log show 12.1 maybe that's the problem?

It's not necessarily a problem, it's just that since your client is  
obviously not the AOSP's stock client it's not something I can  
accurately test.

> Motorola MB632 Android 2.3.6

Ah, that's the "Pro" IIRC. That device doesn't use AOSP's ActiveSync,  
it uses a proprietary implementation. It's geared toward corporate  
usage, so I imagine it includes the more recent versions to get better  
security/policy support.

>> Anyway, the only change that would have anything at all to do with  
>> what you are experiencing is:
>>
>> https://github.com/horde/horde/commit/19037036bd96bf4be64e2b018654dff86a122a33#framework/ActiveSync
>>
>> You can try reversing those changes and see if this helps. Though,  
>> this is not going to be reversed in our code since it is required  
>> for proper display of inline content.
>
> How can I reversing such a commit?

Basically, just comment out the two lines that were added in the top  
section of the if clause.

>  And what should than change (EAS 2.5?)?

No, it won't change the version - it's to see if those changes are  
what broke loading the sent mail folder for you. If all else fails,  
you can force Horde to only use EAS 2.5 but you would loose a lot of  
functionality. Horde 5.1 will include a mechanism to limit the version  
per-device (instead of horde-wide like it is now).


A long shot, it was hard to tell from the log you sent me, but if you  
look at the message content being sent in the log - is that all UTF-8  
data? Are you using the absolute latest stable package of all  
packages, especially Horde_Util?
-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2200 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/horde/attachments/20130415/0c7f87db/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6062 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/horde/attachments/20130415/0c7f87db/attachment-0003.bin>