Inconsistent Time Zone code

[nbctcp]

SW INFO:
-FortiMail vm trial license 7.2.0

PROBLEMS:
1. timezone code of fortimail is different than fortigate code

for example I wanna set Jakarta timezone

In fortigate the Jakarta code is 53

https://docs.fortinet.com/document/fortigate/6.4.0/hardening-your-fortigate/582009/system-administra...

but in fortimail I have to set 54 to get Jakarta

?
1. is that has been fixed in the latest release?

tq

[srajeswaran]

Hello @nbctcp,

I checked my Fortimail running 7.2.4 and I can see the timezone numbers are different between Fortigate and Fortimail. It looks like both Fortigate and Fortimail maintains separate timezone lists , it is better to use the GUI to set the timezone based on the place name instead of the numeric values.

I am not sure if this will be synced between both devices/platforms, do you see any specific challenges with this ?

[nbctcp]

Maybe you can propose to be fixed in the next release
I prefer to have consistent setting between same brand
Rather than using number for timezone which hard to remember.

Maybe you can follow Cisco way which using something like this
https://www.cisco.com/c/en/us/td/docs/security/asa/asa913/configuration/general/asa-913-general-conf....
either
#clock timezone Asia/Jakarta or
#clock timezone GMT +7
Cisco way is much easier to remember

GUI is not always preferable way to modify tenth of devices.
I prefer to use Ansible which using cli to modify many devices at once

Other thing that inconsistent in FortiMail are these
1. https://community.fortinet.com/t5/Support-Forum/FortiMail-enable-more/m-p/262296#M215279
2. can't rename or disable default admin a/c

[srajeswaran]

@nbctcp thanks, we will share the feedback with concerned teams.