Re: base64 encoding
"Jeroen van Meeuwen (Kolab Systems)" <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <752488475ff59b697d8e3bd701419784__20812.7384110869$1361306831$gmane$org@kolabsys.com> |
On 2013-02-19 12:24, Niko Berger wrote: > Am 02/19/2013 04:16 PM, schrieb Jeroen van Meeuwen (Kolab Systems): >> On 2013-02-19 05:17, Christian Mollekopf wrote: >>> On Friday 15 February 2013 11.35:37 Mihai Badici wrote: >>>> When testing synkolab I encountered an issue we discussed in a >>>> previous >>>> thread. >>>> >>>> In fact, contacts modified in thunderbird are transfered in kolab >>>> v3 >>>> format >>>> but base 64 encoded: >>>> >>>> >>>> --Boundary-00=EE071EE390D7733C >>>> Content-Type: application/vcard+xml; >>>> name="kolab.xml" >>>> Content-Transfer-Encoding: base64 >>>> Content-Disposition: attachment; >>>> filename="kolab.xml" >>>> >>>> >>>> There are not decrypted nor in roundcube or kontact; >>>> So the question is: base64 can be considered as valid encoding for >>>> kolab >>>> objects? >>> That is currently not supported, see >>> http://wiki.kolab.org/Kolab_3.0_Storage_Format#XML_Object_Part >>> >> Small correction - Roundcube decodes the payload in it's MIME >> handling. >> >> Kind regards, >> >> Jeroen van Meeuwen >> > The newest nightly uses quoted-printable encoding - I hope this fixes > this incompatibility > Please see: http://www.intevation.de/pipermail/kolab-users/2013-February/014470.html http://www.intevation.de/pipermail/kolab-users/2013-February/014484.html http://www.intevation.de/pipermail/kolab-users/2013-February/014491.html Kind regards, Jeroen van Meeuwen -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08