View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006133SOGoBackend Calendarpublic2025-06-26 07:512025-06-26 07:52
Reporterjordi Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version5.12.1 
Summary0006133: Timezone updates not being taken into account
Description

The executive summary:

  • One of our Brazilian users scheduled a meeting at 11:00 Sao Paulo time (16:00 CEST).
  • People looking at the event via the SOGo web interface saw the event at 15:00 CEST
SUMMARY:Meeting
DTSTART;TZID=America/Sao_Paulo:20250624T110000
DTEND;TZID=America/Sao_Paulo:20250624T120000

If you inspect the ics for the meeting that was shared by Thunderbird, you can see it included the entire historical timezone changes for Sao Paulo since 1914.

Is it possible SOGo is unable to parse the entire thing and ends up not knowing Brazil stopped doing DST in 2019?

These are the last entries in the Sao Paulo section:

BEGIN:DAYLIGHT
TZOFFSETTO:-020000
TZOFFSETFROM:-030000
TZNAME:America/Sao_Paulo(DST)
DTSTART:20181104T000000
RDATE:20181104T000000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETTO:-030000
TZOFFSETFROM:-020000
TZNAME:America/Sao_Paulo(STD)
DTSTART:20160221T000000
RRULE:FREQ=YEARLY;UNTIL=20190217T000000;BYMONTH=2;BYDAY=3SU
END:STANDARD
END:VTIMEZONE
TagsNo tags attached.

Activities

jordi

jordi

2025-06-26 07:52

reporter   ~0018284

Note that we have the same problem with a Chilean user, so this isn't specific to Sao Paulo.

Issue History

Date Modified Username Field Change
2025-06-26 07:51 jordi New Issue
2025-06-26 07:52 jordi Note Added: 0018284