https://bugs.kde.org/show_bug.cgi?id=306114

            Bug ID: 306114
          Severity: major
           Version: 4.9
          Priority: NOR
          Assignee: kdepim-bugs@kde.org
           Summary: libkolab can not handle z-push generated (base64
                    encoded) kolab mail objects
    Classification: Unclassified
                OS: Linux
          Reporter: thorsten.schnebeck@gmx.net
          Hardware: Other
            Status: UNCONFIRMED
         Component: general
           Product: Akonadi

I use Kolab 2.4 + zpush to sync between mobile and PC
When I create an Event on my mobile z-push service creates a Kolab (V2)
compatible event on the imap server that is fine for e.g. the Horde web client
or 4.8 Kontact (when there was no libkolab)
Now I use
libkolab.so.0.3.1 with Kontact 4.9.0
and every event created from zpush leads to an error message on the desktop.

The problem is that zpush creates encoded mail bodies while libkolab search for
a special clear text XML header


Reproducible: Always

Steps to Reproduce:
1. Create an event on your mobile 
2. use active sync service + zpush to sync created event to server
3. Look in Webclient if event is there (-> Ok)
4. Resync Kontact folders
> Error about missing XML header
5. Look in Kontact Calendar for synced event (-> Missing)

Actual Results:  
No support for active synced data

Expected Results:  
support for active synced data

Example of a zpush imap object body (based 64 encoded):
=============================
This is a multi-part message in MIME format

--DA6675847BAA8C6FCAE214789EA7D603
Content-Type:text/plain
Content-Transfer-Encoding:plain

kolab message

--DA6675847BAA8C6FCAE214789EA7D603
Content-Type: application/x-vnd.kolab.event; name="kolab.xml"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="kolab.xml"
Content-Description: kolab.xml

PD94bWwgdmVyc2lvbj0iMS4wIj8+CjxldmVudCB2ZXJzaW9uPSIxLjAiPgogIDx1aWQ+QzE5NTAzMEMtNjMwMC00Njg0LUI3RUItRkIwOTNDNTk1MUJCPC91aWQ+CiAgPGJvZHk+PC9ib2R5PgogIDxjYXRlZ29yaWVzPjwvY2F0ZWdvcmllcz4KICA8Y3JlYXRpb24tZGF0ZT4yMDEyLTA4LTMxVDEzOjQzOjIzWjwvY....

Example of std imap object body:
=============================
MIME-Version: 1.0


--nextPart1664366.J9Iqkd24Xp
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit

This is a Kolab Groupware object.
To view this object you will need an email client that can understand the Kolab
Groupware format.
For a list of such email clients please visit
http://www.kolab.org/get-kolab

--nextPart1664366.J9Iqkd24Xp
Content-Type: application/x-vnd.kolab.event; name="kolab.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="kolab.xml"

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<event version=3D"1.0">
 <product-id>Libkolab-0.3.1, Kolab resource</product-id>
 <uid>01d8b18d-02dc-4fea-87de-6204677fa44c</uid>
 <creation-date>2012-08-29T22:11:02Z</creation-date>
...

-- 
You are receiving this mail because:
You are watching all bug changes.