kolab wallace: ERROR event|todo_from_ical() exception: InvalidAttendeeCutypeError("Invalid cutype u'ROOM'",);
Closed, ResolvedPublic


I received a calender invitation email which did not create a placeholder in my calender, even when the kolab policy is configured to create calendar placeholders for received invitations.. I found this from pykolab wallace logs:

2019-11-06 14:06:10,419 pykolab.wallace ERROR [1112] event|todo_from_ical() exception: InvalidAttendeeCutypeError("Invalid cutype u'ROOM'",);

and indeed /usr/lib/python2.7/site-packages/pykolab/xml/ only has the following:

cutype_map = {
        "INDIVIDUAL": kolabformat.CutypeIndividual,
        "RESOURCE": kolabformat.CutypeResource,
        "GROUP": kolabformat.CutypeGroup,

Relevant line(s) in the received .ics file:


I'm currently running the following versions:

I wonder if the quick fix/hack would be to define "ROOM" as a "kolabformat.CutypeResource", same as the "RESOURCE" type ? or would that cause other problems..?



Ticket Type

Event Timeline

pasik created this task.Nov 6 2019, 10:21 PM
pasik added projects: PyKolab, Kolab 16.

According to RFC5545 ROOM, UNKNOWN, X-* are valid values. Those aren't supported by Kolab, but we definitely should not throw exceptions on these. I wouldn't touch the map variable. Probably better to handle these in set_cutype().

ps. what software did that iTip come from?

Further investigation shows that actually Kolab format has CutypeRoom and CutypeUnknown defined. So, we can add these to the map, but still we should probably silently ignore unsupported values.

machniak closed this task as Resolved.Nov 8 2019, 11:30 AM
machniak claimed this task.


pasik added a comment.Nov 8 2019, 12:30 PM

@machniak Thanks a lot! I'll try the patch. This .ics arrived from Microsoft Exchange Server 2010 (based on the PRODID field in .ics).

pasik added a comment.Jan 9 2020, 10:56 PM

Patch seems to work. I haven't seen this issue after applying the patch. Thanks a lot!