OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: clock problem and postfix behaviour

From: Patrick Ben Koetter (pstate-of-mind.de)
Date: Wed Mar 01 2006 - 06:18:18 CST


* cbaegerteuropeanservers.net <cbaegerteuropeanservers.net>:
> Hi,
>
> we had a big problem yesterday : a power loss in our datacenter.
>
> Our mail server restarted with a clock set to 2003, although it's a brand new
> server (and I supposed it was a brand new battery !)
>
> When I saw that, I hurried to set the clock to 2006. Then the mail server
> rejected all the messages it received but not delivered during the time it
> was set to 2003, with "status=expired, returned to sender"
>
> I'm wondering if I could have done something differently to avoid this
> problem, but I don't have the answer for now. Any idea ?
>
> Or maybe something in Postfix could be implemented to avoid this annoying
> behaviour ? I imagine it's not the first time that this problem occurs, and
> it certainly won't be the last time ! After a power loss, we don't have to
> time to read the whole Postfix manual, so I think it will be better if
> Postfix could handle this problem automatically whatever the admin mistakes !

Postfix uses the time the system provides. Use NTP or a hardware clock to set
the system time correctly.

<http://www.ntp.org/>

prick

--
The Book of Postfix
<http://www.postfix-book.com>
saslfinger (debugging SMTP AUTH):
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>