Re: Email TimeStamp




Susan wrote:
can you examine the header info on one of these emails that are going out?
that should be able to tell you where the timestamp is wrong...

--
Susan Conkey [MVP]



<justeralt@xxxxxxxxx> wrote in message
news:1159888453.185591.18700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am having an issue with timestamps on emails. Internally the
timestamp is correct. Any email that goes to the outside world ends up
an hour behind it is 8:30 but the email sent shows 7:30. I verified
the workstation has the correct time and timezone with daylight savings
selected. I verified the server has the correct time and timezone
selected with daylight savings selected. I attempted using OWA
directly from the server and get the same result. The preferences in
OWA has the correct timezone set. There is an external spam filtering
company I thought might be modifying the timestamp so I bypassed
forwarding out through them directly to other systems and still have
the same results. I verified our firewall has the correct time. Could
this be the isp? I am running out of ideas on where to get this
resolved.


Thanks, Jared

This message was sent 11:00CST
Below is the header info.
The message was from matrix@xxxxxxxxxxxxxxxx to justeralt@xxxxxxxxx

X-Gmail-Received: 1fa73e3d321f84a3639072118fc1191497b7be0e
Delivered-To: justeralt@xxxxxxxxx
Received: by 10.66.240.2 with SMTP id n2cs66320ugh;
Tue, 3 Oct 2006 09:02:44 -0700 (PDT)
Received: by 10.78.164.13 with SMTP id m13mr4640708hue;
Tue, 03 Oct 2006 09:02:44 -0700 (PDT)
Return-Path: <Matrix@xxxxxxxxxxxxxxxx>
Received: from outbound1-cpk-R.bigfish.com
(outbound-cpk.frontbridge.com [207.46.163.16])
by mx.gmail.com with ESMTP id
33si5483381hue.2006.10.03.09.02.43;
Tue, 03 Oct 2006 09:02:44 -0700 (PDT)
Received-SPF: neutral (gmail.com: 207.46.163.16 is neither permitted
nor denied by best guess record for domain of Matrix@xxxxxxxxxxxxxxxx)
Received: from outbound1-cpk.bigfish.com (localhost.localdomain
[127.0.0.1])
by outbound1-cpk-R.bigfish.com (Postfix) with ESMTP id 5FA94156A60F
for <justeralt@xxxxxxxxx>; Tue, 3 Oct 2006 16:00:45 +0000 (UTC)
Received: from mail118-cpk-R.bigfish.com (unknown [192.168.21.3])
(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
(No client certificate requested)
by outbound1-cpk.bigfish.com (Postfix) with ESMTP id 5AF1F156A51D
for <justeralt@xxxxxxxxx>; Tue, 3 Oct 2006 16:00:45 +0000 (UTC)
Received: from mail118-cpk.bigfish.com (localhost.localdomain
[127.0.0.1])
by mail118-cpk-R.bigfish.com (Postfix) with ESMTP id 4739C537AE3
for <justeralt@xxxxxxxxx>; Tue, 3 Oct 2006 16:00:45 +0000 (UTC)
Received: by mail118-cpk (MessageSwitch) id 1159891245235874_32478;
Tue, 3 Oct 2006 16:00:45 +0000 (UCT)
Received: from DC-Exchange.reelfootbank.com (unknown [208.62.150.1])
by mail118-cpk.bigfish.com (Postfix) with ESMTP id C3B49537AB0
for <justeralt@xxxxxxxxx>; Tue, 3 Oct 2006 16:00:44 +0000 (UTC)

.



Relevant Pages

  • Re: Email TimeStamp
    ... Susan Conkey [MVP] ... I verified the server has the correct time and timezone ...
    (microsoft.public.exchange.admin)
  • Re: Email TimeStamp
    ... verified the workstation has the correct time and timezone with ... time and timezone selected with daylight savings selected. ... timestamp so I bypassed forwarding out through them directly to other ... date/time/timezone/DST and the same on the sending workstation. ...
    (microsoft.public.exchange.admin)
  • Re: Email TimeStamp
    ... verified the workstation has the correct time and timezone with ... time and timezone selected with daylight savings selected. ... attempted using OWA directly from the server and get the same result. ... timestamp so I bypassed forwarding out through them directly to other ...
    (microsoft.public.exchange.admin)
  • Re: Email TimeStamp
    ... that should be able to tell you where the timestamp is wrong... ... I verified the server has the correct time and timezone ... OWA has the correct timezone set. ...
    (microsoft.public.exchange.admin)
  • Re: Python 2.5.1 broken os.stat module
    ... |>> when DST starts and also when DST ends, even though the file has NOT ... Windows is not claiming ... | That local textual representation of the modification timestamp is what ... And without a timezone attached, ...
    (comp.lang.python)