[horde] ActiveSync does not work after update to 2.0.0beta4
Michael J Rubinsky
mrubinsk at horde.org
Sat Oct 13 19:56:17 UTC 2012
Quoting Samuel Wolf <samuelwolf85 at googlemail.com>:
> 2012/10/13 Michael J Rubinsky <mrubinsk at horde.org>:
>>
>> Quoting Samuel Wolf <samuelwolf85 at googlemail.com>:
>>
>>> 2012/10/13 Michael J Rubinsky <mrubinsk at horde.org>:
>>>>
>>>>
>>>> Quoting Samuel Wolf <samuelwolf85 at googlemail.com>:
>>>>
>>>>> 2012/10/13 Michael J Rubinsky <mrubinsk at horde.org>:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Quoting Samuel Wolf <samuelwolf85 at googlemail.com>:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I can not use activesync any more (account error) after update to
>>>>>>> 2.0.0beta4.
>>>>>>>
>>>>>>> pear install horde/Horde_ActiveSync
>>>>>>> horde/Horde_ActiveSync is already installed and is the same as the
>>>>>>> released version 2.0.0beta4
>>>>>>> install failed
>>>>>>>
>>>>>>> $conf['activesync']['emailsync'] = true;
>>>>>>> $conf['activesync']['version'] = '12.1';
>>>>>>> $conf['activesync']['autodiscovery'] = 'user';
>>>>>>> $conf['activesync']['logging']['path'] = '/tmp/activesync.log';
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> This is not a valid value for the logging path in Horde 5.
>>>>>
>>>>>
>>>>>
>>>>> What is wrong with the logging path?
>>>>> horde.log work fine
>>>>
>>>>
>>>>
>>>> For custom activesync logging, it's a path to a directory. Each device
>>>> gets
>>>> it's own logfile. So e.g., /tmp would be a valid choice. This changed
>>>> around the same time email support was added.
>>>
>>>
>>> Sorry you are true!
>>>
>>> 2012-10-13T21:21:51+02:00 INFO: Horde_ActiveSync_Driver_Horde::logon
>>> attempt for: samuel
>>> 2012-10-13T21:21:51+02:00 DEBUG: [333536353231303434393936323637]
>>> FOLDERSYNC request received for user samuel
>>> 2012-10-13T21:21:51+02:00 DEBUG: [333536353231303434393936323637]
>>> loadDeviceInfo: samuel
>>> 2012-10-13T21:21:51+02:00 INFO: Request being handled for device:
>>> 333536353231303434393936323637 Supporting protocol version: 12,1
>>> 2012-10-13T21:21:51+02:00 INFO: [Horde_ActiveSync::handleFolderSync]
>>> Beginning FOLDERSYNC
>>> 2012-10-13T21:21:51+02:00 DEBUG: [333536353231303434393936323637]
>>> Checking policykey for device: 0 user: samuel
>>> 2012-10-13T21:21:51+02:00 DEBUG: Policykey: 0 verified.
>>> 2012-10-13T21:21:51+02:00 DEBUG: I <FolderHierarchy:FolderSync>
>>> 2012-10-13T21:21:51+02:00 DEBUG: I <FolderHierarchy:SyncKey>
>>> 2012-10-13T21:21:51+02:00 DEBUG: I 0
>>> 2012-10-13T21:21:51+02:00 DEBUG: I </FolderHierarchy:SyncKey>
>>> 2012-10-13T21:21:51+02:00 DEBUG: [Horde_ActiveSync::handleFolderSync]
>>> syncKey: 0
>>> 2012-10-13T21:21:51+02:00 DEBUG: [1987] Resetting device state.
>>> 2012-10-13T21:21:51+02:00 DEBUG: [333536353231303434393936323637]
>>> Using syncCache
>>> 2012-10-13T21:21:51+02:00 DEBUG: I </FolderHierarchy:FolderSync>
>>> 2012-10-13T21:21:51+02:00 DEBUG: [Horde_ActiveSync::handleFolderSync]
>>> newSyncKey: {5079bf4f-51f0-42bb-a941-07c3c0a8372d}1
>>> 2012-10-13T21:21:51+02:00 DEBUG: [1987] Initializing folder diff engine
>>> 2012-10-13T21:21:51+02:00 DEBUG: Horde::getFolderList()
>>> 2012-10-13T21:21:51+02:00 DEBUG: Horde::getFolders()
>>> 2012-10-13T21:21:51+02:00 DEBUG: Polling
>>> Horde_ActiveSync_Driver_Horde::_getMailFolders()
>>> 2012-10-13T21:21:51+02:00 ERR:
>>
>>
>> It's also worth mentioning that nothing concerning this code changed since
>> the last beta release in ActiveSync code. What was the last version you were
>> running?
>
> Nothing in the apache error log.
> I do not know the last version, add some patchs like the empty email body.
>
> root at wds:/tmp# pear list -c horde
> Installed packages, channel pear.horde.org:
> ===========================================
> Package Version State
> Horde_ActiveSync 2.0.0beta4 beta
> Horde_Alarm 2.0.0beta2 beta
> Horde_Argv 2.0.0beta1 beta
> Horde_Auth 2.0.0beta2 beta
> Horde_Autoloader 2.0.0beta1 beta
> Horde_Browser 2.0.0beta2 beta
> Horde_Cache 2.0.0beta1 beta
> Horde_Cli 2.0.0beta2 beta
> Horde_Compress 2.0.0beta2 beta
> Horde_Constraint 2.0.0beta1 beta
> Horde_Controller 2.0.0beta2 beta
> Horde_Core 2.0.0beta6 beta
> Horde_Crypt 2.0.0beta2 beta
> Horde_Data 2.0.0beta2 beta
> Horde_Date 2.0.0beta3 beta
> Horde_Date_Parser 2.0.0beta1 beta
> Horde_Db 2.0.0beta1 beta
> Horde_Editor 2.0.0beta1 beta
> Horde_Exception 2.0.0beta1 beta
> Horde_Form 2.0.0beta3 beta
> Horde_Group 2.0.0beta1 beta
> Horde_History 2.0.0beta1 beta
> Horde_Http 2.0.0beta2 beta
> Horde_Icalendar 2.0.0beta2 beta
> Horde_Image 2.0.0beta2 beta
> Horde_Imap_Client 2.0.0beta3 beta
> Horde_Injector 2.0.0beta1 beta
> Horde_Itip 2.0.0beta1 beta
> Horde_ListHeaders 1.0.0beta1 beta
> Horde_Lock 2.0.0beta1 beta
> Horde_Log 2.0.0beta1 beta
> Horde_LoginTasks 2.0.0beta1 beta
> Horde_Mail 2.0.0beta2 beta
> Horde_Memcache 2.0.0beta1 beta
> Horde_Mime 2.0.0beta3 beta
> Horde_Mime_Viewer 2.0.0beta1 beta
> Horde_Nls 2.0.0beta2 beta
> Horde_Notification 2.0.0beta1 beta
> Horde_Perms 2.0.0beta2 beta
> Horde_Prefs 2.0.0beta1 beta
> Horde_Rdo 2.0.0beta1 beta
> Horde_Role 1.0.0 stable
> Horde_Rpc 2.0.0beta1 beta
> Horde_Secret 2.0.0beta2 beta
> Horde_Serialize 2.0.0beta1 beta
> Horde_SessionHandler 2.0.0beta2 beta
> Horde_Share 2.0.0beta4 beta
> Horde_SpellChecker 2.0.0beta1 beta
> Horde_Stream_Filter 2.0.0beta2 beta
> Horde_Stream_Wrapper 2.0.0beta1 beta
> Horde_Support 2.0.0beta2 beta
> Horde_Template 2.0.0beta1 beta
> Horde_Text_Diff 2.0.0beta1 beta
> Horde_Text_Filter 2.0.0beta1 beta
> Horde_Text_Filter_Csstidy 2.0.0beta2 beta
> Horde_Text_Flowed 2.0.0beta1 beta
> Horde_Timezone 1.0.0beta1 beta
> Horde_Token 2.0.0beta1 beta
> Horde_Translation 2.0.0beta1 beta
> Horde_Tree 2.0.0beta2 beta
> Horde_Url 2.0.0beta3 beta
> Horde_Util 2.0.0beta2 beta
> Horde_Vfs 2.0.0beta2 beta
> Horde_View 2.0.0beta1 beta
> Horde_Xml_Element 2.0.0beta1 beta
> content 2.0.0beta1 beta
> horde 5.0.0beta6 beta
> imp 6.0.0beta4 beta
> ingo 3.0.0beta2 beta
> kronolith 4.0.0beta2 beta
> mnemo 4.0.0beta1 beta
> nag 4.0.0beta2 beta
> turba 4.0.0beta3 beta
Unfortunately, you will have to track this down yourself then. I can't
reproduce this. You can try clearing any server caches. Horde's
ActiveSync support calls the same code used to build the mailbox tree
as IMP does. You can start by looking at
Horde_Core_ActiveSync_Imap_Factory::getMailboxes().
--
mike
The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- 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/20121013/75b134c3/attachment.bin>
More information about the horde
mailing list