[Tickets #13865] Re: Application settings for "horde" application not updatable in IMAP/Kolab back-end

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13865
------------------------------------------------------------------------------
  Ticket             | 13865
  Updated By         | mike.gabriel at das-netzwerkteam.de
  Summary            | Application settings for "horde" application not
                     | updatable in IMAP/Kolab back-end
  Queue              | Kolab
  Type               | Bug
  State              | Unconfirmed
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


mike.gabriel at das-netzwerkteam.de (2015-12-18 10:33) wrote:

> Hi Mike,
>
>> Please check if the patch attached to [1] fixes your issue.
>
> - applied patch
> - ran "horde-clear-cache"
> - logged off, then on again
> - tried to modify a calendar entry
> - same error pop-up as usual:
>
> --- cut here ---
> Failed writing the Kolab object: Failed parsing Kolab object input  
> data of type string! Input was:  
> Æioz»"¢}tzw(v)àQ1|z÷§¶÷«²*'×K¢wž¸q½... [shortened to 50 characters]
> --- cut here ---
>
> I hope to have some time starting next year to set up a new test bed  
> and really dig into this.

The same test should be run with the Null driver for Horde Caching  
(i.e. Horde Caching disabled). Personally, I don't 100% trust  
horde-clear-cache in relation with Kolab.

First, check if the issue is still present with Horde_Caching using  
the Null driver.

Then check if applying the patch fixes the issue.

Also, please verify on your IMAP server the underlying mail object.  
What is the Kolab XML object's transfer encoding? If you decode the  
attachemnt manually, do Umlauts look correct?