TimeZone wrong

Hi,

I’ve problem with timezone on one installation
WebApp:
3.3.0.610-25.1
Kopano Core:
8.3.0-1042
Z-Push:
2.3.6+0

when receiving a meeting request the time is 2 hours in front of local time (local time = Europe/Vienna)
when creating a meeting request the time is the right one the other (outside) contact receives

I checked the timezone on server (Univention UCS4.2 errata15) this is set to Europe/Vienna

where can i check what timezone Kopano Core uses and how to change this if necessary ?

rg
Christian

Hi Christian,

on which clients is it wrong (Outlook with/without KOE, WebApp, Deskapp, mobile devices)? From which client do you send the meeting request and which client receives meeting request?

Manfred

Hi,

the clients are all (outlook with zarafa-plugin, webapp, outlook 2013 with koe and mobile android) on the receiver side
and sending was done from a different external sites (exchange server with outloook 2016, kopano-server with webapp, koe and iphone)

but as i said when sending a meetingrequest from the site where the incoming meeting requests are 2h in front of local time the time i correct on the destination site

may be theres a problem with postfix on the receiving site ?

rg
Christian

Hi Christian,

do you have the incoming raw email on the server with the wrong time?

As the time is wrong on the all clients it might be an issue with parsing the data.

What timezone is set on the server from which the meeting request arrives?

Have you tried setting another timezone instead of Europe/Vienna which is the same standard west european time (e.g. Europe/Amsterdam)?

Manfred

Hi Christian

it seems as this can happen after a UCS Update. Please take also a look here https://help.univention.com/t/changing-timezone-doesnt-work-wrong-zonefiles/5643
The User has had the same timeshift with Kopano on a UCS. May it’s the same on your server

@hps

thanks for this hint - it could be the same - server was upgraded from UCS4.1 to UCS 4.2 and the UTC File is also wrong
I copied from different server too - don’t know if the server has to be restarted after that but will try this evening and give feedback afterwards

rg
Christian

@hps

Ok,

I can confirm it was same error after recreating the UTC file it’s ok now

rg
christian