Hi,

After importing certain .ics files into my SOGo calendar (using Thunderbird), 
the SOGo EAS calendar stops working. New calendar entries added or changed 
after importing the .ics file are not shown on EAS clients, rendering the 
calendar unreliable and therefore unusable. The calendar entries are shown in 
Thunderbird and the SOGo webmail application. I noticed that the offending .ics 
files are generally from external entities sending me meeting confirmations (e. 
g. a website providing appointments to medical doctors, a car repair chain).

It seems that the XML file generated from the offending .ics file causes an 
error in xml2wbxml. In the logs, I see an entry

Mar 03 13:51:42 sogod [844]: [ERROR] <0x0x55b129c6a520[NSDataMalloc]> xml2wbxml 
failed: Parsing of XML Document Failed

Deleting the calendar entry restores functionality. However, it is not always 
easy to identify the offending calendar entry. The behaviour is reproducible. I 
don't know which .ics data field entry causes the behaviour. If requested, I 
can send an example of such an offending .ics file directly via e-mail (not to 
the list, though, I don't want to sanitize it, risking deleting the data that 
causes the behavior).

If requested and if my user is provided the necessary privileges (I am 
currently only an observer), I can also file a bug report in the SOGo bug 
tracker.

Best regards,

Paul

Reply via email to