Today is 21 Feb 2017. You were asked by your boss to check when the last time Amylia, the new staff login into her Zimbra account. Then you quickly check in Zimbra admin console, her last time login was 18 Feb 2017. But then you remembered that yesterday (20 Feb 2017) she was sent you an email. Then how in Zimbra admin console stated Amylia last login was 18 Feb 2017?
The server will update the user’s
zimbraLastLogonTimestamp attribute at most once every
zimbraLastLogonTimestampFrequency. Default value was 7d to cutdown on ldap writes every time we auth. we can change the value to 1d, 1h, 1m, 1s or 0 to disable.
To check current configuration use below command (as zimbra user);
zmprov gacf | grep Timestamp
To change the value use following command;
zmprov mcf zimbraLastLogonTimestampFrequency 3d
Above command will update timestamp into Zimbra admin console every 3 days.
however, I highly recommend you to leave this configuration untouched. Let it be default 7d, since there’s a bunch of bugs related to changing this configuration. Think of the pure volume of some systems, updating an attribute for several million active users all day long makes for a lot of writes and replication.
But fear not, as an admin you can always login to the server and check
/opt/zimbra/log/audit.log as it is continuously updating the logon time, IP address, etc in real time =)