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

2008-08-19 Thread Charles Marcus
On 8/19/2008, Scott Silva ([EMAIL PROTECTED]) wrote: > During a cold start is probably the ONLY time ntpdate would be > appropriate. Call ntpdate right after the network starts, but before > the other services get started and your time should be very close. > Then a ntp client can keep it that way.

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

2008-08-19 Thread Scott Silva
on 8-18-2008 1:54 PM Charles Marcus spake the following: On 8/18/2008, Ville Walveranta ([EMAIL PROTECTED]) 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 ntpdat

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

2008-08-18 Thread Charles Marcus
On 8/18/2008, Ville Walveranta ([EMAIL PROTECTED]) 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 result

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

2008-08-18 Thread Ville Walveranta
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. Unless the drift is gr

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

2008-08-18 Thread Stephen Feyrer
Hi. I now have a running ntp client running. I think that has solved my timing problems but time will only tell on that score. On the other hand, I am still getting a connection refused message. Is there any way to get back in? -- Thanks Stephen. Charles Marcus wrote: On 8/15/2008, Da

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

2008-08-16 Thread Charles Marcus
On 8/15/2008, Daniel L. Miller ([EMAIL PROTECTED]) wrote: > Umdo you have a UPS? If not - get one! > Are you running running an ntp server? I'm assuming not. It's time to start. He doesn't need an ntp server, he needs to be running an ntp CLIENT... But first he needs to fix his hardware cl

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

2008-08-15 Thread Daniel L. Miller
Stephen Feyrer wrote: Daniel L. Miller wrote: Stephen Feyrer wrote: Hi Everyone. Ooops I just broke my dovecot install. I've looked through the mailing list archives and not found anything relevant. When I try to connect to my mail server I get this message. "Could not connect to mail s

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

2008-08-15 Thread Stephen Feyrer
Daniel L. Miller wrote: Stephen Feyrer wrote: Hi Everyone. Ooops I just broke my dovecot install. I've looked through the mailing list archives and not found anything relevant. When I try to connect to my mail server I get this message. "Could not connect to mail server chen.home.org; co

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

2008-08-15 Thread Daniel L. Miller
Stephen Feyrer wrote: Hi Everyone. Ooops I just broke my dovecot install. I've looked through the mailing list archives and not found anything relevant. When I try to connect to my mail server I get this message. "Could not connect to mail server chen.home.org; connection was refused" T