[Kolab-devel] base64 encoding

[Christian Mollekopf]

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

We may improve that though if there are good reasons to use base64 over 
quoted-printable.

Cheers,
Christian

-- 
Christian Mollekopf
Software Engineer

Kolab Systems AG
Zürich, Switzerland

e: mollekopf at kolabsys.com
w: http://kolabsys.com

pgp: EA657400 Christian Mollekopf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20130219/6f654ad7/attachment.sig>