Time Stamp problem on Incoming and Outgoing emails
in [Outlook Express]
|
Prev: conferma
Next: lourdes te amo
From: Dori A Schmetterling on 30 Oct 2009 13:42 That might be a clue, since EST will be on GMT - 4 h until North American clocks go back. Brad said his clock is set at GMT - 5 h. FYI Europe switched last weekend. DAS To send an e-mail directly replace "spam" with "schmetterling" --- "Rich/rerat" <rrr_news(a)isp.com> wrote in message news:OIo05CYWKHA.3720(a)TK2MSFTNGP02.phx.gbl... > Brad, > Remember this weekend is the end of Daylights Savings Time, so some > ISP/Mail > server may have jump the gun, and made the changes to their system > already. > > -- > Add MS to your News Reader: news://msnews.microsoft.com > Rich/rerat > (RRR News) <message rule> > <<Previous Text Snipped to Save Bandwidth When Appropriate>> > > > "Brad" <brad_roberts(a)cogeco.ca> wrote in message > news:TxEGm.7139$rl7.2983(a)newsfe16.iad... > It's set at (GMT-5:00)Eastern Time (US and Canada) which seems correct to > me > based upon the choices. Only problem with your suggestion is that I'm > exchanging emails with someone using the same ISP, so it would seem > logical > to me that the problem should not appear with her (it's my fuzzy logic, > and > it could be wrong). > > Thanks for the suggestion Bruce, I'll call my ISP > > > "Bruce Hagen" <Nospam(a)mymail.invalid> wrote in message > news:Oint0uXWKHA.4704(a)TK2MSFTNGP06.phx.gbl... >> Check your Time Zone setting. This post shows one hour in the future. If >> it isn't your time zone setting, it's your ISP's. >> -- >> >> Bruce Hagen >> MS-MVP [Mail] >> Imperial Beach, CA >> >> >> "Brad" <brad_roberts(a)cogeco.ca> wrote in message >> news:a5EGm.216$v47.1(a)newsfe23.iad... >>> For some reason the Timestamp on my emails is off by one hour. When I >>> receive an email at 9am for example, it appears in my Inbox as 8am.A >>> similar >>> but opposite problem appears on my emails received by my friends ... >>> they >>> are showing it as being received one hour later. >>> >>> My clock shows the correct Time and Time Zone, with and without box >>> checked >>> for 'Automatically adjust clock for daylight saving changes'. The >>> problem >>> was first noticed with the box checked. >>> >>> One problem within the Date and Time Properties option (in Control >>> Panel) >>> is >>> that the 'Automatically synchronize with an Internet time server' does >>> not >>> work properly once Update Now button is hit. With time.windows.com I get >>> the >>> following message ' An error occurred while windows was synchronizing >>> with >>> time.windows.com. The time sample was rejected because : The peer's >>> stratum >>> is less than the host's stratum. With time.nist.com, when it's >>> successful, I >>> get the wrong time displayed even when the message states the correct >>> time >>> (The time has been successfully synchronized with time.nist.gov ... ). >>> >>> I'm in the EST time zone (Toronto, Canada). >>> >>> Any help would be appreciated, thanks in advance. >>> >>> >> > > >
From: DL on 30 Oct 2009 13:53 I seem to recall that ms released an update some considerable time ago for this. Is your version of Win updated? "Brad" <brad_roberts(a)cogeco.ca> wrote in message news:TxEGm.7139$rl7.2983(a)newsfe16.iad... > It's set at (GMT-5:00)Eastern Time (US and Canada) which seems correct to > me based upon the choices. Only problem with your suggestion is that I'm > exchanging emails with someone using the same ISP, so it would seem > logical to me that the problem should not appear with her (it's my fuzzy > logic, and it could be wrong). > > Thanks for the suggestion Bruce, I'll call my ISP > > > "Bruce Hagen" <Nospam(a)mymail.invalid> wrote in message > news:Oint0uXWKHA.4704(a)TK2MSFTNGP06.phx.gbl... >> Check your Time Zone setting. This post shows one hour in the future. If >> it isn't your time zone setting, it's your ISP's. >> -- >> >> Bruce Hagen >> MS-MVP [Mail] >> Imperial Beach, CA >> >> >> "Brad" <brad_roberts(a)cogeco.ca> wrote in message >> news:a5EGm.216$v47.1(a)newsfe23.iad... >>> For some reason the Timestamp on my emails is off by one hour. When I >>> receive an email at 9am for example, it appears in my Inbox as 8am.A >>> similar >>> but opposite problem appears on my emails received by my friends ... >>> they >>> are showing it as being received one hour later. >>> >>> My clock shows the correct Time and Time Zone, with and without box >>> checked >>> for 'Automatically adjust clock for daylight saving changes'. The >>> problem >>> was first noticed with the box checked. >>> >>> One problem within the Date and Time Properties option (in Control >>> Panel) is >>> that the 'Automatically synchronize with an Internet time server' does >>> not >>> work properly once Update Now button is hit. With time.windows.com I get >>> the >>> following message ' An error occurred while windows was synchronizing >>> with >>> time.windows.com. The time sample was rejected because : The peer's >>> stratum >>> is less than the host's stratum. With time.nist.com, when it's >>> successful, I >>> get the wrong time displayed even when the message states the correct >>> time >>> (The time has been successfully synchronized with time.nist.gov ... ). >>> >>> I'm in the EST time zone (Toronto, Canada). >>> >>> Any help would be appreciated, thanks in advance. >>> >>> >> > >
From: VanguardLH on 30 Oct 2009 15:43 Brad wrote: > For some reason the Timestamp on my emails is off by one hour. When I > receive an email at 9am for example, it appears in my Inbox as 8am.A similar > but opposite problem appears on my emails received by my friends ... they > are showing it as being received one hour later. > > My clock shows the correct Time and Time Zone, with and without box checked > for 'Automatically adjust clock for daylight saving changes'. The problem > was first noticed with the box checked. > > One problem within the Date and Time Properties option (in Control Panel) is > that the 'Automatically synchronize with an Internet time server' does not > work properly once Update Now button is hit. With time.windows.com I get the > following message ' An error occurred while windows was synchronizing with > time.windows.com. The time sample was rejected because : The peer's stratum > is less than the host's stratum. With time.nist.com, when it's successful, I > get the wrong time displayed even when the message states the correct time > (The time has been successfully synchronized with time.nist.gov ... ). > > I'm in the EST time zone (Toronto, Canada). > > Any help would be appreciated, thanks in advance. If you visit http://www.timeanddate.com/worldclock/ and pick a city in your timezone (Toronto, in your case), does the time on your computer match with theirs? If not, you need to fix the timezone or DST setting on your computer. If yes, inquire at cogeco.net as to why their clock is off by an hour. From the headers in your post (spaces added to align values in fixed font display): NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 UTC Date: Fri, 30 Oct 2009 12:01:05 -0500 The Date header is what you added (assuming it didn't get overwritten). The NNTP-Post-Date was added by your newsgroups service provider (NSP). Removing the timezone bias means the times for those headers are: NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 GMT Date: Fri, 30 Oct 2009 17:01:05 GMT So you are your NSP are different by 1 hour. Contact your NSP. Microsoft's NTP servers are not reliable because they are overly busy (and haven't been updated to handle the load). That means you get lots of timeouts trying to connect to their time server. Use a different NTP server. The defaults that the Windows install give you are limited to just the Microsoft and NIST servers and both are heavy accessed (i.e., they're very busy so you might not get a time sync). NIST is more reliable than Microsoft. Also remember that the Windows Time service in Windows may not sync your computer for *many* days which means you could drift quite aways in your time (computer clocks are not very accurate; well, the hardware clock is okay for a month but that doesn't get used under an OS and processes generating heavy loads on the host can generate a lot of drift in the OS-managed clock). I'm not sure that those are the only 2 NTP servers that Windows will use. On occasion when looking at the Internet Time tab of the Date and Time applet, I've seen it mention the time sync was with pool.ntp.org, a worldwide mesh of voluntary NTP servers (see http://en.wikipedia.org/wiki/NTP_pool). You can add more servers to the list by a registry edit at: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DateTime\Servers Yet I know that you can set the NTP server using the command line, like: net time /setsntp:us.pool.ntp.org See http://www.pool.ntp.org/. I use the US pool of NTP servers. You might want to use the Canadian one (ca.pool.ntp.org). Using a country zone for their pool of NTP servers ensures a shorter delay but which one to which you connect in the pool is random (the list changes every hour). Yet specifying that NTP pooled server using the "net time" command won't have it show up in the above registry key (so it isn't available in the drop-down list in the Internet Time tab in the Date and Time applet). Instead that value shows up as the NtpServer data item at: HKLM\SYSTEM\ControlSet001\Services\W32Time\Parameters However, you can add <countryzone>.pool.ntp.org to the list by adding another data item (next higher numbered) in the above Servers registry key to see it in the drop-down list (and then make it the default in the Internet Time tab in the Date and Time applet). A Google search can find NTP servers in your area (although that does not guarantee a minimal delay). I use SocketWatch (not free) but there are other time sync utilities that can poll a list of NTP servers. Some will even try to determine which ones have the least delay to give you the most accurate time sync over a network. Although I have my nearby university's NTP servers in the list that SocketWatch uses, often the delay to NTP servers a state or two away is shorter and better candidates for a time sync. Make sure it is a *public* NTP server to which you are allowed connect.
From: Bill in Co. on 30 Oct 2009 18:32 VanguardLH wrote: > Brad wrote: > >> For some reason the Timestamp on my emails is off by one hour. When I >> receive an email at 9am for example, it appears in my Inbox as 8am.A >> similar >> but opposite problem appears on my emails received by my friends ... they >> are showing it as being received one hour later. >> >> My clock shows the correct Time and Time Zone, with and without box >> checked >> for 'Automatically adjust clock for daylight saving changes'. The problem >> was first noticed with the box checked. >> >> One problem within the Date and Time Properties option (in Control Panel) >> is >> that the 'Automatically synchronize with an Internet time server' does >> not >> work properly once Update Now button is hit. With time.windows.com I get >> the >> following message ' An error occurred while windows was synchronizing >> with >> time.windows.com. The time sample was rejected because : The peer's >> stratum >> is less than the host's stratum. With time.nist.com, when it's >> successful, I >> get the wrong time displayed even when the message states the correct >> time >> (The time has been successfully synchronized with time.nist.gov ... ). >> >> I'm in the EST time zone (Toronto, Canada). >> >> Any help would be appreciated, thanks in advance. > > If you visit http://www.timeanddate.com/worldclock/ and pick a city in > your timezone (Toronto, in your case), does the time on your computer > match with theirs? If not, you need to fix the timezone or DST setting > on your computer. If yes, inquire at cogeco.net as to why their clock > is off by an hour. > > From the headers in your post (spaces added to align values in fixed > font display): > > NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 UTC > Date: Fri, 30 Oct 2009 12:01:05 -0500 > > The Date header is what you added (assuming it didn't get overwritten). > The NNTP-Post-Date was added by your newsgroups service provider (NSP). > Removing the timezone bias means the times for those headers are: > > NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 GMT > Date: Fri, 30 Oct 2009 17:01:05 GMT > > So you are your NSP are different by 1 hour. Contact your NSP. > > Microsoft's NTP servers are not reliable because they are overly busy > (and haven't been updated to handle the load). That means you get lots > of timeouts trying to connect to their time server. Use a different NTP > server. The defaults that the Windows install give you are limited to > just the Microsoft and NIST servers and both are heavy accessed (i.e., > they're very busy so you might not get a time sync). It seems the "time.windows.com" one for the last week has had some problems. I don't know if it's working now or not (without constant timeouts), since I gave up on it for now. Wonder what happened in just the last week to create this problem? It had been "fairly reliable" up to then. I use Dimension 4 for the time sync. I don't remember if it was free or not at this point.
From: Brad on 30 Oct 2009 21:35
Thanks to all who responded. Much of what V(a)nguardLH has written is so far over my head he'd better have a pilots license. Ill finish off the thread tomorrow letting everyone know whether the problem has been solved by Updates or whether it was an ISP issue. "VanguardLH" <V(a)nguard.LH> wrote in message news:hcffl2$42r$1(a)news.albasani.net... > Brad wrote: > >> For some reason the Timestamp on my emails is off by one hour. When I >> receive an email at 9am for example, it appears in my Inbox as 8am.A >> similar >> but opposite problem appears on my emails received by my friends ... they >> are showing it as being received one hour later. >> >> My clock shows the correct Time and Time Zone, with and without box >> checked >> for 'Automatically adjust clock for daylight saving changes'. The problem >> was first noticed with the box checked. >> >> One problem within the Date and Time Properties option (in Control Panel) >> is >> that the 'Automatically synchronize with an Internet time server' does >> not >> work properly once Update Now button is hit. With time.windows.com I get >> the >> following message ' An error occurred while windows was synchronizing >> with >> time.windows.com. The time sample was rejected because : The peer's >> stratum >> is less than the host's stratum. With time.nist.com, when it's >> successful, I >> get the wrong time displayed even when the message states the correct >> time >> (The time has been successfully synchronized with time.nist.gov ... ). >> >> I'm in the EST time zone (Toronto, Canada). >> >> Any help would be appreciated, thanks in advance. > > If you visit http://www.timeanddate.com/worldclock/ and pick a city in > your timezone (Toronto, in your case), does the time on your computer > match with theirs? If not, you need to fix the timezone or DST setting > on your computer. If yes, inquire at cogeco.net as to why their clock > is off by an hour. > > From the headers in your post (spaces added to align values in fixed > font display): > > NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 UTC > Date: Fri, 30 Oct 2009 12:01:05 -0500 > > The Date header is what you added (assuming it didn't get overwritten). > The NNTP-Post-Date was added by your newsgroups service provider (NSP). > Removing the timezone bias means the times for those headers are: > > NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 GMT > Date: Fri, 30 Oct 2009 17:01:05 GMT > > So you are your NSP are different by 1 hour. Contact your NSP. > > Microsoft's NTP servers are not reliable because they are overly busy > (and haven't been updated to handle the load). That means you get lots > of timeouts trying to connect to their time server. Use a different NTP > server. The defaults that the Windows install give you are limited to > just the Microsoft and NIST servers and both are heavy accessed (i.e., > they're very busy so you might not get a time sync). NIST is more > reliable than Microsoft. Also remember that the Windows Time service in > Windows may not sync your computer for *many* days which means you could > drift quite aways in your time (computer clocks are not very accurate; > well, the hardware clock is okay for a month but that doesn't get used > under an OS and processes generating heavy loads on the host can > generate a lot of drift in the OS-managed clock). I'm not sure that > those are the only 2 NTP servers that Windows will use. On occasion > when looking at the Internet Time tab of the Date and Time applet, I've > seen it mention the time sync was with pool.ntp.org, a worldwide mesh of > voluntary NTP servers (see http://en.wikipedia.org/wiki/NTP_pool). You > can add more servers to the list by a registry edit at: > > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DateTime\Servers > > Yet I know that you can set the NTP server using the command line, like: > > net time /setsntp:us.pool.ntp.org > > See http://www.pool.ntp.org/. I use the US pool of NTP servers. You > might want to use the Canadian one (ca.pool.ntp.org). Using a country > zone for their pool of NTP servers ensures a shorter delay but which one > to which you connect in the pool is random (the list changes every > hour). > > Yet specifying that NTP pooled server using the "net time" command won't > have it show up in the above registry key (so it isn't available in the > drop-down list in the Internet Time tab in the Date and Time applet). > Instead that value shows up as the NtpServer data item at: > > HKLM\SYSTEM\ControlSet001\Services\W32Time\Parameters > > However, you can add <countryzone>.pool.ntp.org to the list by adding > another data item (next higher numbered) in the above Servers registry > key to see it in the drop-down list (and then make it the default in the > Internet Time tab in the Date and Time applet). > > A Google search can find NTP servers in your area (although that does > not guarantee a minimal delay). I use SocketWatch (not free) but there > are other time sync utilities that can poll a list of NTP servers. Some > will even try to determine which ones have the least delay to give you > the most accurate time sync over a network. Although I have my nearby > university's NTP servers in the list that SocketWatch uses, often the > delay to NTP servers a state or two away is shorter and better > candidates for a time sync. Make sure it is a *public* NTP server to > which you are allowed connect. |