Am 03.03.26 um 14:08 schrieb Paul Leiber ([email protected]):
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).
I found out which entry causes the error. In the ORGANIZER field, the mailto
address is given in angle brackets / chevrons:
ORGANIZER;CN=John Doe:mailto:<[email protected]>
This seems to be compliant with iCalendar specs, at least online validators
don't state any issue with this line. However, the angular brackets trigger the
error described in my initial mail. If I remove the brackets from this field,
the calendar entry is processed and synchronized without any error.
It seems more reasonable to adapt SOGo to process this type of ics files than
to try to make third parties change their invitations, especially because this
way of specifying the mailto address it is not confined to one single mail
sender.
Again, if there is something I can do to help fixing this bug, let me know.
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
I
