I've read several messages on the list about timezone issues and that could be the problem here, but as the time varies in the Web UI and Lightning, I'm not completely convinced that is the case.
The invite came from Exchange 2010 to the SOGo user (snipped for brevity): BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Eastern Standard Time BEGIN:STANDARD DTSTART:16010101T020000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN=name:MAILTO:n...@example.com ATTENDEE ...snip.... DTSTART;TZID=Eastern Standard Time:20121120T150000 DTEND;TZID=Eastern Standard Time:20121120T160000 UID:040000008200E00074C5B7101A82E00800000000D025AF766CC6CD01000000000000000 010000000FE873530FB163745BAF8D1F8B633BFB8 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20121119T211350Z As you can see the appointment is from 3-4pm EST. Here is the entry in SOGo (snipped again): "c_content" = "BEGIN:VCALENDAR^MPRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN^M VERSION:2.0^M BEGIN:VEVENT^M LAST-MODIFIED:20121120T174540Z^M DTSTAMP:20121120T174540Z^MUID:040000008200E00074C5B7101A82E00800000000D025AF766CC6CD01000000000000000^M 010000000FE873530FB163745BAF8D1F8B633BFB8 ....snip.... X-MOZ-LASTACK:20121120T165835Z^M DTSTART:20121120T150000^M DTEND:20121120T160000^M Looking at this entry it appears as though the timezone data did not make it. The appointment would appear to start at 3pm and end at 4pm. If the WebUI showed the same I would think timezone error. The WebUI shows 7am to 8am though. Thunderbird Lightning shows 3-4pm which is much better as this is just the 3 hour difference between the sender and the recipient--a timezone issue. Interestingly the original email body that shows the appointment is correct as it shows 12noon to 1pm. In my experience, the WebUI has always been correct even if Lightning was a mess. Now it seems I can't even count on that. This appears to be a bug, but I'm not sure how to further supplement the information for a bug report. Any suggestions would be appreciated. Steve -- users@sogo.nu https://inverse.ca/sogo/lists
