[horde] ActiveSync does not work after update to 2.0.0beta4

[Michael J Rubinsky]

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.

-- 
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/dbbe225f/attachment-0001.bin>