> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Loren M. Lang
> Sent: Thursday, March 03, 2005 12:58 PM
> To: Luke
> Cc: freebsd-questions@freebsd.org
> Subject: Re: Received mail timestamp is off by 7 hours
>
>
> On W
ch 02, 2005 10:32 AM
> To: freebsd-questions@freebsd.org
> Subject: Re: Received mail timestamp is off by 7 hours
>
>
> Ted Mittelstaedt writes:
>
> > There's no excuse for a mailserver to not be synced to a NTP source.
>
> I'd extend that to apply to any ser
On Wed, Mar 02, 2005 at 01:00:15PM -0800, Luke wrote:
>
> >>There's no excuse for a mailserver to not be synced to a NTP source.
> >
> >I'd extend that to apply to any server. Practically all the things a
> >server does are dependent in some way on the correct time.
>
> I have three excuses:
> 1
gt; Cc: Loren M. Lang; Pat Maddox; freebsd-questions@freebsd.org
> > Subject: Re: Received mail timestamp is off by 7 hours
> >
>
> > little bit less reliable using local to UTC unless you are not affected
> > by any daylight savings changes like Arizona in the US or, I'm
&g
Tom Trelvik writes:
> That suggests larger problems on your system, to me, but I dunno.
If NTP is configured to step instead of slew, it can cause the clock to
jump a bit for a while. Slewing is smooth and avoids this, but it takes
a lot longer for NTP to initially get the time right.
--
Antho
Luke writes:
> 1) NTP is difficult to configure.
I dunno. I configured it in a few minutes on my test box.
> 2) Finding an NTP server willing to accept traffic from the public isn't
> easy either. For me it involved a scavenger hunt through out-of-date
> websites and a lot of failed attempts.
Luke wrote:
That suggests larger problems on your system, to me, but I dunno.
3) If your clock tends to run noticably fast or slow, constant NTP
corrections
tend to do more harm than good, at least in my experience. It got to
where
I couldn't even run a buildworld because NTP kept tinkering
1) NTP is difficult to configure. I've done it, but it wasn't trivial.
It's always seemed rather straightforward to me, what in particular
gave you trouble, perhaps we could help?
Well, there seemed to be two different services. One was something that
would run only on boot. The other was a
In the last episode (Mar 02), Luke said:
> >>There's no excuse for a mailserver to not be synced to a NTP source.
> >I'd extend that to apply to any server. Practically all the things a
> >server does are dependent in some way on the correct time.
>
> I have three excuses:
> 1) NTP is difficult t
Luke writes:
> 2) Finding an NTP server willing to accept traffic from the
> public isn't easy either. For me it involved a scavenger hunt
> through out-of-date websites and a lot of failed attempts.
The overwhelming majority of ISPs I have used or inquired about
had (at least) one c
Luke wrote:
1) NTP is difficult to configure. I've done it, but it wasn't trivial.
It's always seemed rather straightforward to me, what in particular
gave you trouble, perhaps we could help?
2) Finding an NTP server willing to accept traffic from the public isn't
easy either. For me it invol
There's no excuse for a mailserver to not be synced to a NTP source.
I'd extend that to apply to any server. Practically all the things a
server does are dependent in some way on the correct time.
I have three excuses:
1) NTP is difficult to configure. I've done it, but it wasn't trivial.
2) Fin
Ted Mittelstaedt writes:
> There's no excuse for a mailserver to not be synced to a NTP source.
I'd extend that to apply to any server. Practically all the things a
server does are dependent in some way on the correct time.
This is also increasingly true of desktops. Gone are the days when you
Loren M. Lang writes:
> Well, I haven't looked into all the details of how FreeBSD does this,
> but I gaurentee that there is a point where FreeBSD can crash and the
> clock could be knocked off an hour which wouldn't happen if it's running
> UTC.
Traditionally, UNIX sets the real-time clock to U
On Wed, 2 Mar 2005 03:11:19 -0800, Ted Mittelstaedt wrote:
Loren wrote:
> > little bit less reliable using local to UTC unless you are not affected
> > by any daylight savings changes like Arizona in the US or, I'm
> > sure, many
> > other places around the world.
For a desktop or test machi
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Loren M. Lang
> Sent: Wednesday, March 02, 2005 2:29 AM
> To: Ian Smith
> Cc: Loren M. Lang; Pat Maddox; freebsd-questions@freebsd.org
> Subject: Re: Received mail timestamp is off b
On Tue, Mar 01, 2005 at 02:22:40AM +1100, Ian Smith wrote:
> On Mon, 28 Feb 2005 03:36:41 -0800 Loren M. Lang wrote:
> > On Mon, Feb 28, 2005 at 12:58:17AM +1100, Ian Smith wrote:
> > > On Sun, 27 Feb 2005 03:10:12 -0700 Pat Maddox <[EMAIL PROTECTED]> wrote:
> > >
> > > > Alright, I got it a
On Mon, 28 Feb 2005 03:36:41 -0800 Loren M. Lang wrote:
> On Mon, Feb 28, 2005 at 12:58:17AM +1100, Ian Smith wrote:
> > On Sun, 27 Feb 2005 03:10:12 -0700 Pat Maddox <[EMAIL PROTECTED]> wrote:
> >
> > > Alright, I got it all working now. Not sure how to change the time
> > > zone with co
On Mon, Feb 28, 2005 at 12:58:17AM +1100, Ian Smith wrote:
> On Sun, 27 Feb 2005 03:10:12 -0700 Pat Maddox <[EMAIL PROTECTED]> wrote:
>
> > Alright, I got it all working now. Not sure how to change the time
> > zone with config files, so I just used sysinstall to change it to MST
> > (time zo
On Sun, 27 Feb 2005 03:10:12 -0700 Pat Maddox <[EMAIL PROTECTED]> wrote:
> Alright, I got it all working now. Not sure how to change the time
> zone with config files, so I just used sysinstall to change it to MST
> (time zone is arbitrary, but since this is the zone I live in, it's
> conven
Pat Maddox writes:
> Alright, I got it all working now. Not sure how to change the time
> zone with config files, so I just used sysinstall to change it to MST
> (time zone is arbitrary, but since this is the zone I live in, it's
> convenient for me).
Well, no, time zone isn't arbitrary, it need
Alright, I got it all working now. Not sure how to change the time
zone with config files, so I just used sysinstall to change it to MST
(time zone is arbitrary, but since this is the zone I live in, it's
convenient for me). Then I used ntpdate to sync it, and it's working
well now.
Thanks for p
Pat Maddox writes:
> I've included the headers of messages from both Gmail and Hotmail, to
> show that it's not on Gmail's end. Also, here's the output from date:
> %date
> Sun Feb 27 02:42:21 CET 2005
That can't be right. You sent your message in reply to a message I sent
at 9:34 CET. The tim
I've included the headers of messages from both Gmail and Hotmail, to
show that it's not on Gmail's end. Also, here's the output from date:
%date
Sun Feb 27 02:42:21 CET 2005
They should show up in my inbox as being received at 1:40am or so, but
they show up as 6:40pm instead.
>From Gmail:
Ret
Pat Maddox writes:
> I forgot to give a bit of info. My local machine has the correct time
> of 10:05PM, and the server has the correct time of 11:05PM. If I send
> an email from a mail account on the server to gmail, it has the
> correct time. If I send an email from gmail back to the server,
It doesn't only happen when I receive mail from my gmail account -
it's with all email that passes through this server.
On Sun, 27 Feb 2005 17:54:56 +1000, Timothy Smith
<[EMAIL PROTECTED]> wrote:
> check your gmail account
> it's set to the wrong time zone or something. if "date" gives the
> cor
I forgot to give a bit of info. My local machine has the correct time
of 10:05PM, and the server has the correct time of 11:05PM. If I send
an email from a mail account on the server to gmail, it has the
correct time. If I send an email from gmail back to the server,
that's when it has the weird
On Saturday 26 February 2005 08:38 pm, Pat Maddox wrote:
> I've been having a weird problem lately...when I download an email
> from my mailserver, the time is off by 7 hours. For example, if I
> receive an email at 9:30pm, it lists the time as 2:30pm in my mail
> client. I've determined that it'
28 matches
Mail list logo
