Difference between revisions of "Time Zones in ZCS"

m (wacky wiki formatting was collapsing a doublespace)
Line 4: Line 4:
 
* the COS and account object in LDAP
 
* the COS and account object in LDAP
 
* the user's PC (or mobile device)
 
* the user's PC (or mobile device)
* the server
+
* the server OS
  
 
Different clients examine different settings.
 
Different clients examine different settings.
Line 22: Line 22:
 
So you can see there is a preference called zimbraPrefTimeZoneId that stores the string description of the time zone.
 
So you can see there is a preference called zimbraPrefTimeZoneId that stores the string description of the time zone.
  
The server is particular about how this time zone is identified, and right now there is no list of all the allowed time zones.  (Yes, we need to fix this!)
+
The server is particular about how this time zone is identified, and all settings of the attribute must match one of the "known" time zones.  A list of known time zones is provided at the bottom of this page.
  
Note that in past versions of ZCS users may have been provisioned with the US-Pacific time zone if no other time zone was explicitly specified.  If this has occurred you can broadly change all time zones (for any not set in particular) by changing zimbraPrefTimeZoneId on the user's COS.
+
Note that in past versions of ZCS users may have been provisioned with the US-Pacific time zone if no other time zone was explicitly specified.  If this has occurred you can broadly change all time zones (for any not set in particular) by changing zimbraPrefTimeZoneId on the user's COS.  This will change the effect time zone for any user that has not had their account-specific zimbraPrefTimeZoneId set.
  
 
<h3>The user's PC</h3>
 
<h3>The user's PC</h3>
 
This is determined by the user as appropriate for their OS.
 
This is determined by the user as appropriate for their OS.
  
<h3>The server</h3>
+
<h3>The server OS</h3>
 
This is determined by the administrator as appropriate for their OS.
 
This is determined by the administrator as appropriate for their OS.
  
Line 59: Line 59:
  
 
<h3>iCal</h3>iCal uses the PC's time zone.
 
<h3>iCal</h3>iCal uses the PC's time zone.
 +
 +
<h2>Known Time Zones for zimbraPrefTimeZoneId</h2>
 +
As of 4.5.0 and later releases the server understands the following time zones.  Only these strings should be used to set zimbraPrefTimeZoneId.
 +
 +
<li> (GMT-12.00) International Date Line West
 +
<li> (GMT-11.00) Midway Island / Samoa
 +
<li> (GMT-10.00) Hawaii
 +
<li> (GMT-09.00) Alaska
 +
<li> (GMT-08.00) Pacific Time (US & Canada)
 +
<li> (GMT-08.00) Tijuana / Baja California
 +
<li> (GMT-07.00) Arizona
 +
<li> (GMT-07.00) Chihuahua / La Paz / Mazatlan - New
 +
<li> (GMT-07.00) Chihuahua / La Paz / Mazatlan - Old
 +
<li> (GMT-07.00) Mountain Time (US & Canada)
 +
<li> (GMT-06.00) Central America
 +
<li> (GMT-06.00) Central Time (US & Canada)
 +
<li> (GMT-06.00) Guadalajara / Mexico City / Monterrey - New
 +
<li> (GMT-06.00) Guadalajara / Mexico City / Monterrey - Old
 +
<li> (GMT-06.00) Saskatchewan
 +
<li> (GMT-05.00) Bogota / Lima / Quito / Rio Branco
 +
<li> (GMT-05.00) Eastern Time (US & Canada)
 +
<li> (GMT-05.00) Indiana (East)
 +
<li> (GMT-04.00) Atlantic Time (Canada)
 +
<li> (GMT-04.00) Caracas / La Paz
 +
<li> (GMT-04.00) Manaus
 +
<li> (GMT-04.00) Santiago
 +
<li> (GMT-03.30) Newfoundland
 +
<li> (GMT-03.00) Brasilia
 +
<li> (GMT-03.00) Buenos Aires / Georgetown
 +
<li> (GMT-03.00) Greenland
 +
<li> (GMT-03.00) Montevideo
 +
<li> (GMT-02.00) Mid-Atlantic
 +
<li> (GMT-01.00) Azores
 +
<li> (GMT-01.00) Cape Verde Is.
 +
<li> (GMT) Casablanca / Monrovia / Reykjavik
 +
<li> (GMT) Greenwich Mean Time - Dublin / Edinburgh / Lisbon / London
 +
<li> (GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
 +
<li> (GMT+01.00) Belgrade / Bratislava / Budapest / Ljubljana / Prague
 +
<li> (GMT+01.00) Brussels / Copenhagen / Madrid / Paris
 +
<li> (GMT+01.00) Sarajevo / Skopje / Warsaw / Zagreb
 +
<li> (GMT+01.00) West Central Africa
 +
<li> (GMT+02.00) Amman
 +
<li> (GMT+02.00) Athens / Bucharest / Istanbul
 +
<li> (GMT+02.00) Beirut
 +
<li> (GMT+02.00) Cairo
 +
<li> (GMT+02.00) Harare / Pretoria
 +
<li> (GMT+02.00) Helsinki / Kyiv / Riga / Sofia / Tallinn / Vilnius
 +
<li> (GMT+02.00) Jerusalem
 +
<li> (GMT+02.00) Minsk
 +
<li> (GMT+02.00) Windhoek
 +
<li> (GMT+03.00) Baghdad
 +
<li> (GMT+03.00) Kuwait / Riyadh
 +
<li> (GMT+03.00) Moscow / St. Petersburg / Volgograd
 +
<li> (GMT+03.00) Nairobi
 +
<li> (GMT+03.00) Tbilisi
 +
<li> (GMT+03.30) Tehran
 +
<li> (GMT+04.00) Abu Dhabi / Muscat
 +
<li> (GMT+04.00) Baku
 +
<li> (GMT+04.00) Yerevan
 +
<li> (GMT+04.30) Kabul
 +
<li> (GMT+05.00) Ekaterinburg
 +
<li> (GMT+05.00) Islamabad / Karachi / Tashkent
 +
<li> (GMT+05.30) Chennai / Kolkata / Mumbai / New Delhi
 +
<li> (GMT+05.30) Sri Jayawardenepura
 +
<li> (GMT+05.45) Kathmandu
 +
<li> (GMT+06.00) Almaty / Novosibirsk
 +
<li> (GMT+06.00) Astana / Dhaka
 +
<li> (GMT+06.30) Yangon (Rangoon)
 +
<li> (GMT+07.00) Bangkok / Hanoi / Jakarta
 +
<li> (GMT+07.00) Krasnoyarsk
 +
<li> (GMT+08.00) Beijing / Chongqing / Hong Kong / Urumqi
 +
<li> (GMT+08.00) Irkutsk / Ulaan Bataar
 +
<li> (GMT+08.00) Kuala Lumpur / Singapore
 +
<li> (GMT+08.00) Perth
 +
<li> (GMT+08.00) Taipei
 +
<li> (GMT+09.00) Osaka / Sapporo / Tokyo
 +
<li> (GMT+09.00) Seoul
 +
<li> (GMT+09.00) Yakutsk
 +
<li> (GMT+09.30) Adelaide
 +
<li> (GMT+09.30) Darwin
 +
<li> (GMT+10.00) Brisbane
 +
<li> (GMT+10.00) Canberra / Melbourne / Sydney
 +
<li> (GMT+10.00) Guam / Port Moresby
 +
<li> (GMT+10.00) Hobart
 +
<li> (GMT+10.00) Vladivostok
 +
<li> (GMT+11.00) Magadan / Solomon Is. / New Caledonia
 +
<li> (GMT+12.00) Auckland / Wellington
 +
<li> (GMT+12.00) Fiji / Kamchatka / Marshall Is.
 +
<li> (GMT+13.00) Nuku'alofa

Revision as of 17:32, 2 July 2007

This page describes the relationship between the Zimbra Collaboration Suite and time zones. Different parts of ZCS read time zone information from different places, and this page explains it all.

There are three places where time zone information can be examined:

  • the COS and account object in LDAP
  • the user's PC (or mobile device)
  • the server OS

Different clients examine different settings.

Time Zone Sources

COS and Account

The COS and Account objects be can examined (e.g. for an account) by zmprov:
prompt> zmprov ga foo@company.com | grep -i timezone
zimbraPrefTimeZoneId: (GMT-06.00) Central Time (US & Canada)

So you can see there is a preference called zimbraPrefTimeZoneId that stores the string description of the time zone.

The server is particular about how this time zone is identified, and all settings of the attribute must match one of the "known" time zones. A list of known time zones is provided at the bottom of this page.

Note that in past versions of ZCS users may have been provisioned with the US-Pacific time zone if no other time zone was explicitly specified. If this has occurred you can broadly change all time zones (for any not set in particular) by changing zimbraPrefTimeZoneId on the user's COS. This will change the effect time zone for any user that has not had their account-specific zimbraPrefTimeZoneId set.

The user's PC

This is determined by the user as appropriate for their OS.

The server OS

This is determined by the administrator as appropriate for their OS.

Client Behavior

There are several clients in use with Zimbra and they have different behaviors.

Mobile

Different mobile clients have subtle differences in dealing with calendar time zones. Getting the time from the network can exacerbate this problem as network time sometimes includes only an offset from GMT and does not specify a full time zone definition that would include daylight savings time change over days.

There are two factors that determine the presentation of calendar data in mobilesync clients. One is the time zone setting on the mobile device, which can be either manually set or set by the network; the other is the time zone information in each meeting. This works well in most cases except for all day events downloaded to VersaMail clients (PalmOS). All day events don't have an inherent time zone, but mobilesync protocol requires a timezone setting even for these events. Zimbra server therefore uses the user account's default time zone setting when sending all day events to mobile clients. If the user account time zone happens to be different from the mobile device's time zone, VersaMail displays an all day event as two segments spanning two days.

Mobile device time zone settings impact the device only and do not alter data on the server.

The basic (or lite) web client

In 4.5.x the basic client uses the server's time zone for rendering times in message list displays.

In 5.0.0 the basic client will use the account's time zone for message list displays and calendaring.

Note that the basic client ignores the time zone on the PC. In 5.0.0 the basic client does expose the time zone to be used; this impacts the account's zimbraPrefTimeZoneId.

The advanced (or AJAX) web client

The advanced client uses the time zone of the user's PC for rendering times in messages list displays as well as calendar functions.

Note that the advanced client ignores the time zone set on the account. As of ZCS 4.5.6 the account time zone is not exposed for editing in the advanced client.

zmprov

The admin CLI zmprov provides access to the COS and account attributes and will also read them.

Outlook

The Zimbra Connector for Outlook as well as "plain" Outlook using IMAP or POP will use the PC's time zone.

ZDesktop

ZDesktop functions like the advanced/AJAX client.

iCal

iCal uses the PC's time zone.

Known Time Zones for zimbraPrefTimeZoneId

As of 4.5.0 and later releases the server understands the following time zones. Only these strings should be used to set zimbraPrefTimeZoneId.

  • (GMT-12.00) International Date Line West
  • (GMT-11.00) Midway Island / Samoa
  • (GMT-10.00) Hawaii
  • (GMT-09.00) Alaska
  • (GMT-08.00) Pacific Time (US & Canada)
  • (GMT-08.00) Tijuana / Baja California
  • (GMT-07.00) Arizona
  • (GMT-07.00) Chihuahua / La Paz / Mazatlan - New
  • (GMT-07.00) Chihuahua / La Paz / Mazatlan - Old
  • (GMT-07.00) Mountain Time (US & Canada)
  • (GMT-06.00) Central America
  • (GMT-06.00) Central Time (US & Canada)
  • (GMT-06.00) Guadalajara / Mexico City / Monterrey - New
  • (GMT-06.00) Guadalajara / Mexico City / Monterrey - Old
  • (GMT-06.00) Saskatchewan
  • (GMT-05.00) Bogota / Lima / Quito / Rio Branco
  • (GMT-05.00) Eastern Time (US & Canada)
  • (GMT-05.00) Indiana (East)
  • (GMT-04.00) Atlantic Time (Canada)
  • (GMT-04.00) Caracas / La Paz
  • (GMT-04.00) Manaus
  • (GMT-04.00) Santiago
  • (GMT-03.30) Newfoundland
  • (GMT-03.00) Brasilia
  • (GMT-03.00) Buenos Aires / Georgetown
  • (GMT-03.00) Greenland
  • (GMT-03.00) Montevideo
  • (GMT-02.00) Mid-Atlantic
  • (GMT-01.00) Azores
  • (GMT-01.00) Cape Verde Is.
  • (GMT) Casablanca / Monrovia / Reykjavik
  • (GMT) Greenwich Mean Time - Dublin / Edinburgh / Lisbon / London
  • (GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
  • (GMT+01.00) Belgrade / Bratislava / Budapest / Ljubljana / Prague
  • (GMT+01.00) Brussels / Copenhagen / Madrid / Paris
  • (GMT+01.00) Sarajevo / Skopje / Warsaw / Zagreb
  • (GMT+01.00) West Central Africa
  • (GMT+02.00) Amman
  • (GMT+02.00) Athens / Bucharest / Istanbul
  • (GMT+02.00) Beirut
  • (GMT+02.00) Cairo
  • (GMT+02.00) Harare / Pretoria
  • (GMT+02.00) Helsinki / Kyiv / Riga / Sofia / Tallinn / Vilnius
  • (GMT+02.00) Jerusalem
  • (GMT+02.00) Minsk
  • (GMT+02.00) Windhoek
  • (GMT+03.00) Baghdad
  • (GMT+03.00) Kuwait / Riyadh
  • (GMT+03.00) Moscow / St. Petersburg / Volgograd
  • (GMT+03.00) Nairobi
  • (GMT+03.00) Tbilisi
  • (GMT+03.30) Tehran
  • (GMT+04.00) Abu Dhabi / Muscat
  • (GMT+04.00) Baku
  • (GMT+04.00) Yerevan
  • (GMT+04.30) Kabul
  • (GMT+05.00) Ekaterinburg
  • (GMT+05.00) Islamabad / Karachi / Tashkent
  • (GMT+05.30) Chennai / Kolkata / Mumbai / New Delhi
  • (GMT+05.30) Sri Jayawardenepura
  • (GMT+05.45) Kathmandu
  • (GMT+06.00) Almaty / Novosibirsk
  • (GMT+06.00) Astana / Dhaka
  • (GMT+06.30) Yangon (Rangoon)
  • (GMT+07.00) Bangkok / Hanoi / Jakarta
  • (GMT+07.00) Krasnoyarsk
  • (GMT+08.00) Beijing / Chongqing / Hong Kong / Urumqi
  • (GMT+08.00) Irkutsk / Ulaan Bataar
  • (GMT+08.00) Kuala Lumpur / Singapore
  • (GMT+08.00) Perth
  • (GMT+08.00) Taipei
  • (GMT+09.00) Osaka / Sapporo / Tokyo
  • (GMT+09.00) Seoul
  • (GMT+09.00) Yakutsk
  • (GMT+09.30) Adelaide
  • (GMT+09.30) Darwin
  • (GMT+10.00) Brisbane
  • (GMT+10.00) Canberra / Melbourne / Sydney
  • (GMT+10.00) Guam / Port Moresby
  • (GMT+10.00) Hobart
  • (GMT+10.00) Vladivostok
  • (GMT+11.00) Magadan / Solomon Is. / New Caledonia
  • (GMT+12.00) Auckland / Wellington
  • (GMT+12.00) Fiji / Kamchatka / Marshall Is.
  • (GMT+13.00) Nuku'alofa
  • Jump to: navigation, search