[Dovecot] dovecot: Fatal: Time just moved backwards by 3603 seconds.

[Charles Marcus]

On 8/18/2008, Ville Walveranta (walveranta at gmail.com) wrote:
> ntp client as a service (daemon) is the way to go... I had the same
> problem; I wasn't aware of the fact that dovecot would be sensitive to
> time going backwards. I was running ntpdate via cron, and the first
> time the time-check resulted in backwards correction, dovecot bombed.

This is nothing new... time has *always* been considered extremely
critical on servers - and ntpdate has *always* been seen as the WRONG
way to keep a server in time - it moves time in much too large increments.

An ntp client has always been the way to go...

But you should also make sure your hardware clock is not totally crapped
out, as that can make a [successful] cold start problematic...

-- 

Best regards,

Charles