Bug: Non valid DTSTART and DTEND in caldav VEVENT



  • Hello,

    I don’t know if it is ok to post a bugreport in this subforum. If not please move it to the right place.

    I’m using the community version of Kopano 8.5.4 (Debian Testing Packages).
    When I create a new calendar event (it doesn’t matter if I create it with webapp, thunderbird, evolution or with an iphone) and download it by using a http GET request (kopano-ical), the properties “DTSTART” and “DTEND” are not valid.

    Example:

    BEGIN:VCALENDAR
    VERSION:2.0
    PRODID:-//Kopano//8.5.4//EN
    CALSCALE:GREGORIAN
    METHOD:PUBLISH
    BEGIN:VTIMEZONE
    TZID:Europe/Berlin
    BEGIN:STANDARD
    DTSTART:19700101T030000
    TZOFFSETFROM:+0200
    TZOFFSETTO:+0100
    RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;WKST=SU
    END:STANDARD
    BEGIN:DAYLIGHT
    DTSTART:19700101T020000
    TZOFFSETFROM:+0100
    TZOFFSETTO:+0200
    RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3;WKST=SU
    END:DAYLIGHT
    END:VTIMEZONE
    BEGIN:VEVENT
    TRANSP:OPAQUE
    X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
    CREATED:20180314T091312Z
    LAST-MODIFIED:20180314T091312Z
    DTSTAMP:20180314T091312Z
    DTSTART;TZID=Europe/Berlin:20180315T080000Z
    DTEND;TZID=Europe/Berlin:20180315T090000Z
    SUMMARY:Thunderbird 8 Uhr
    CLASS:PUBLIC
    UID:07246d77-b3c4-4a6c-94e4-4e306083b920
    X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE:20180314T091654Z
    X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE:20180314T091654Z
    X-MICROSOFT-CDO-APPT-SEQUENCE:0
    X-MICROSOFT-CDO-OWNERAPPTID:-1
    X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
    END:VEVENT
    END:VCALENDAR
    

    Here DTSTART contains a timezone and a UTC-Time. Regarding to https://icalendar.org/iCalendar-RFC-5545/3-3-5-date-time.html this is not valid. For my example only the following forms are valid:

    DTSTART;TZID=Europe/Berlin:20180315T080000

    or

    DTSTART:20180315T090000Z

    Because of this bug, some clients (like thunderbird and outlook) does not handle these events in a correct way. For example thunderbird shows this event one hour late. The same for outlook.

    Does anyone know if this is a known bug and there is a bugfix or workaround?

    Thank you very much
    Christian


  • Kopano

    Hi @chrisk ,

    yes of course is this forum a good place to put your request. I have now only moved your thread from the general section to the core server part. Just for me to better understand, do you use a client that trips over this or this a matter of “not according to rfc”?



  • @fbartels Thanks for your help

    This is not only a matter of “not according to rfc”. We are using thunderbird and outlook as our mailclients and after upgrading to 8.5.4 (from 8.3.something) we can’t use the calendar anymore because all of our events are shown with a wrong time.
    So I really need a bugfix or workaround for this.

    Christian


  • Kopano

    Hi @chrisk ,

    I did a quick test with our packages (and also a slightly newer version) and here it shows up correctly:

    BEGIN:VCALENDAR
    VERSION:2.0
    PRODID:-//Kopano//8.6.0//EN
    CALSCALE:GREGORIAN
    METHOD:PUBLISH
    BEGIN:VEVENT
    TRANSP:OPAQUE
    X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
    CREATED:20180312T140856
    LAST-MODIFIED:20180312T141315
    DTSTAMP:20180312T141315
    DTSTART:20180313T130000Z
    DTEND:20180313T140000Z
    SUMMARY:test 2
    PRIORITY:5
    CLASS:PUBLIC
    UID:
     040000008200E00074C5B7101A82E0080000000080FC3902ACBBD301000000000000000001
     0000004424B23B0C54473F9FECB6597527D6DF
    X-MOZ-SNOOZE-TIME:20180313T124500Z
    X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE:20180314T154917Z
    X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE:20180314T154917Z
    X-MICROSOFT-CDO-APPT-SEQUENCE:0
    X-MICROSOFT-CDO-OWNERAPPTID:-1
    X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
    BEGIN:VALARM
    TRIGGER;VALUE=DURATION:-PT15M
    ACTION:DISPLAY
    DESCRIPTION:Reminder
    END:VALARM
    END:VEVENT
    BEGIN:VEVENT
    TRANSP:OPAQUE
    X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
    CREATED:20180312T140525
    LAST-MODIFIED:20180312T143729
    DTSTAMP:20180312T143729
    DTSTART:20180312T150000Z
    DTEND:20180312T160000Z
    SUMMARY:Testtermin
    PRIORITY:5
    CLASS:PRIVATE
    UID:
     040000008200E00074C5B7101A82E0080000000080FC3902ACBBD301000000000000000001
     000000CA12DB371D8148CD8F58E66140C853B8
    X-MOZ-SNOOZE-TIME:20180312T110000Z
    X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE:20180314T154917Z
    X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE:20180314T154917Z
    X-MICROSOFT-CDO-APPT-SEQUENCE:0
    X-MICROSOFT-CDO-OWNERAPPTID:-1
    X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
    BEGIN:VALARM
    TRIGGER;VALUE=DURATION:-PT4H
    ACTION:DISPLAY
    DESCRIPTION:Reminder
    END:VALARM
    END:VEVENT
    END:VCALENDAR
    

    So it seems this is something either with the dependencies used in the Debian packaging or maybe another side effect. Maybe you want to give our packages a try if you need an immediate fix.



  • After subscription, removing all of the debian testing packages and reinstalling the latest Kopano 8.5.5, it seems to work now.

    Thanks for your help.


  • Kopano

    Hi @chrisk ,

    thanks for the update.