[sync] ActiveSync stopped working after upgrade to Horde-5.1.0

[Michael J Rubinsky]

Quoting Arjen de Korte <arjen+horde at de-korte.org>:

> Citeren Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Arjen de Korte <arjen+horde at de-korte.org>:
>>
>>> After upgrading to the latest stable versions from PEAR, my  
>>> ActiveSync clients (Moxier Mail on Android) could no longer sync  
>>> e-mail (calendar, contacts and tasks were fine). Worse, they even  
>>> proceeded removing all messages that were already synchronized.
>>>
>>> It turned out that somehow the activesync database scheme had not  
>>> been migrated.
>>
>> How did you attempt to run the migration when it was "somehow" not migrated?
>
> As usual, 'pear upgrade -c horde'. No errors, just the usual  
> messages about optional packages that I don't need.

Migrations do not automatically run. The main configuration screen  
will show which migrations (as well as configurations) are currently  
"out of date" and need to be updated. Additionally, when logging in as  
an administrator, a notification bubble should be shown indicating  
that there are migrations that need to be run.


>>> After running horde-db-migrate from the console, the database  
>>> scheme was migrated up from version 16 to 17 and things started  
>>> working again. The only thing that remained, was that the lists of  
>>> folders to sync needed to be configured again on the clients. And  
>>> of course, messages needed to be sync'ed again from the server.
>>
>> The 17 migration simply forces the sync state to be refreshed for  
>> all devices. This was necessary because of a required change in the  
>> way the folder hierarchy is maintained. Non-broken clients will  
>> then automatically initiate a new FOLDERSYNC that will repopulate  
>> the folder hierarchy on the client.
>
> The folder hierarchy was sync'ed alright, it was just that the  
> client would give up all existing subscriptions to folders and hence  
> the messages it already had were removed from the phone (all 2000+  
> or so).
>
>> Unfortunately though, if the user has selected any email folders  
>> for PUSH that are not pushed by default on that client these will  
>> have to be re-selected by the user on the client since the internal  
>> identifiers for the folders have changed.
>
> Which is indeed the case. So far, the Android ActiveSync clients  
> that I tried will only sync INBOX by default (and some will not even  
> allow you to select additional ones either). All other folders need  
> to be selected manually. So that I had to re-select them again was a  
> bit unexpected, but given the changes I understand this is  
> unavoidable.
>
> Note this was not intended as a bug report, just a heads-up for  
> others that may run into the same issues. Luckily, my ActiveSync  
> userbase is small, so the load for a dozen or so people re-syncing  
> their mail is not that bad. If you have many more, it may be more  
> significant and one might want to stage this, so that not all  
> clients will attempt to re-sync at the same time.

Thanks for the feedback.

-- 
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/sync/attachments/20130605/d2fdc12d/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/sync/attachments/20130605/d2fdc12d/attachment-0003.bin>