This bug report is related to https://bugs.kde.org/show_bug.cgi?id=342031 but as the original problem (creation of malformed http request) does not exist any more in version 4.14.6 I think it is reasonable to create a new bug report. If one receives an event invitation via ics file where a RECURRENCE-ID is given (meaning the incidence is an exception to a recurrent event), but KOrganizer/Akonadi does not know about the recurring parent event, the incidence is written to the Akonadi database but not displayed in KOrganizer. Secondly, if the calendar the invitation is written to happens to be a CalDAV calendar, the incidence is synced up to the CalDAV resource. In case of ownCloud, it is not displayed there either and also not synchronized to other clients. Reproducible: Always Steps to Reproduce: 1. Send yourself an email with the recurrence-id.ics attached. 2. Accept the invitation. 3. See that you don't see the event. Actual Results: Event is not displayed. Expected Results: Event is displayed. apt-cache policy korganizer korganizer: Installed: 4:4.14.6-0ubuntu1 Candidate: 4:4.14.6-0ubuntu1 Version table: *** 4:4.14.6-0ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status apt-cache policy akonadi-server akonadi-server: Installed: 1.13.0-2ubuntu4 Candidate: 1.13.0-2ubuntu4 Version table: *** 1.13.0-2ubuntu4 0 500 http://pl.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status
Created attachment 93511 [details] event invitation with RECURRENCE-ID
Created attachment 93512 [details] script for removing RECURRENCE-ID s from external ics files
I attached an ics file which causes described behaviour and a python script one can use as a KMail filter to mitigate the problem.
Created attachment 93681 [details] updated work-around script We have updated our script to backup filtered messages before trying to "fix" broken ics files.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.