Tickets :: Comment on [#14199] Decoding of base64 encoded Kolab (.xml) objects is broken

* Your Email Address
* Spam protection	Enter the letters below: .__.. .. .. ,. . [__]\ /\|_/ \./ \| \| \| \| \/ \| \ \| \|__\|
Comment	>>> This sounds familiar, like something that was fixed previously - >>> though maybe the fix itself wasn't in the Kolab library. >>> >>> Thomas, do you remember this, or can you even reproduce it? With all >>> the torture testing we did recently, I'd be very surprised if this >>> somehow escaped our notice. I'm sure you have 8-bit characters in >>> your data ... :) >> >> yes, even the automate test suite controlling the browser specifially >> uses umlauts in the Kolab data. > > Ok... > >> @Mike: Which IMAP backend are you using for Kolab? I've seen you sent >> a patch for the Pear backend in bug entry #14200. > > I use the Horde_Imap_Client (i.e., Horde_Kolab_Storage_Driver_Imap). > > The patch in #14200 was a side catch when testing other > Kolab_Storage_Driver_* implementations. > >> The Horde Imap_Client backend is the only real maintained one, the >> others haven't been supported for years. In fact I don't see much >> point in keeping this extra maintenance burden in the future. IIRC >> Horde Imap_Client even outperforms the others... > > Yeah, I noticed that. > > Please check with your test cases if your attachments are really > stored with base64 transfer encoding. > > I have seen Kolab XML objects stored in quoted-printable with base64 > encoded Umlauts / special chars (single letters). > > The issue only occurs, when Kolab XML objects have transfer encoding > base64. However, that is the default way of Horde_Kolab_Storage > storing attachments (at least here).
Attachment
Watch this ticket

Saved Queries