Outlook 2007 inbox wrong time

[Alan]

Just got OL 2007 on a new computer and when I send myself an email from the
old XP machine, although both are recording the correct time, the message
shows being received 1 hour before. I don't know what to change, all clock
settings are corrrect. Thanks in advance,

 

[Brian Tillman]

Just got OL 2007 on a new computer and when I send myself an email
from the old XP machine, although both are recording the correct
time, the message shows being received 1 hour before. I don't know
what to change, all clock settings are corrrect. Thanks in advance,

Make sure both systems are using the same Windows timezone and DST settings
and that the Outlook calendar settings for those values also agree.

 

[Daryl Wyatt]

I am having the same problems.
Received emails have time stamp 1 hour behind.
I have tried reseting time zone and checking and unchecking the DST box.
So any help will be great.

 

[Brian Tillman]

I am having the same problems.
Received emails have time stamp 1 hour behind.
I have tried reseting time zone and checking and unchecking the DST
box. So any help will be great.

Perhaps it's the sender's PC with the problem. What you describe is typical
of one of the PCs having a wrong DST setting.

 

[jrm]

I have a similar problem, inbox says email received at 12:10 pm but when open
email states actual received time of 9:59 am for example. This is not just
for email comming from one other PC. It is for all emails received under
this account.

 

[Brian Tillman]

I have a similar problem, inbox says email received at 12:10 pm but
when open email states actual received time of 9:59 am for example.

Where do you see this received tie and what is the exact time string?

 

[jrm]

In Outlook 2007, the main Inbox screen which lists all emails received sorted
by date and time, in the "Received" column, shows a date and a time of
12:10pm.

When I open that email message, in the message header, it shows the email
sent time as 9:49am.

The email was sent at 9:49am and I received it a minute or two after that,
but the Inbox received time is approx. 2 hours and 20 minutes into the future.

This only happens for one of my email accounts. I have checked the time
zones for Outlook, Windows and the email server and all are set correctly.

Thanks for any assistance you can provide.

-JAY-

 

[Brian Tillman]

In Outlook 2007, the main Inbox screen which lists all emails
received sorted by date and time, in the "Received" column, shows a
date and a time of 12:10pm.

When I open that email message, in the message header, it shows the
email sent time as 9:49am.

The email was sent at 9:49am and I received it a minute or two after
that, but the Inbox received time is approx. 2 hours and 20 minutes
into the future.

Is there a Date header on that message?

 

[jrm]

Here you go:

Return-Path: <[email protected]>
Delivered-To: (e-mail address removed)
Received: (qmail 19381 invoked from network); 6 Dec 2007 12:10:19 -0500
Received: from ourhost.com (xxx.xx.xx.xxx)
by su1022277.aspadmin.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 6 Dec
2007 12:10:19 -0500
Received: from xxxxxxxxxx (c-xx-xxx-xx-xxx.hsd1.nh.comcast.net
[xx.xxx.xx.xxx])
(authenticated bits=0)
by ourhost.com (8.13.6.20060614/8.13.6) with ESMTP id lB6Enfbe000799;
Thu, 6 Dec 2007 09:49:42 -0500 (EST)
Reply-To: <[email protected]>
From: "xxxxx" <[email protected]>
To: "'xxx'" <[email protected]>
Cc: <[email protected]>
Subject: RE: when can we meet?
Date: Thu, 6 Dec 2007 09:48:44 -0500
Organization: xxxxxxxx
Message-ID: <002d01c83817$20f37ad0$6801a8c0@xxxxxxx>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_002E_01C837ED.381D72D0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <006e01c837b9$c06c9c80$4145d580$@com>

This is a multi-part message in MIME format.

------=_NextPart_000_002E_01C837ED.381D72D0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


As you can see, the first two Received lines have the wrong time, but the
third Received line is the correct time. Not sure who or what is generating
the wrong times or why Outlook is picking them up.

This is just one example. Happens for all emails associated with this
account regardless of who the sender is.

 

[Brian Tillman]

Here you go: ....snip...
Date: Thu, 6 Dec 2007 09:48:44 -0500 ....snip...

As you can see, the first two Received lines have the wrong time, but
the third Received line is the correct time. Not sure who or what is
generating the wrong times or why Outlook is picking them up.

This is just one example. Happens for all emails associated with this
account regardless of who the sender is.

The Date header is usualy added either by the sender or a server but there
is no correlation between the Date header and the actual transmission dates.
Outlook, however, will show the Date header value in the open message. It
will show the date in the most recent Received header in the Received
column. The Received headers look to me like "ourhost.com" is the first
server that accepted the message from Comcast and it is that server whose
time is valid, since it's the first header added (lowest on the list). The
server su1022277.aspadmin.net, accepting the message from the ourhost.com
server, appears to have an incorrect clock that's about 2 hours 20 minutes
off. the mail program qmail probably doesn't care and uses whatever time is
on the message already or qmail is running on su1022277.aspadmin.net and so
uses the time on that server. Your Outlook got the message from the qmail
program. If the account referencing the su1022277.aspadmin.net server is
the only account that does so, it's understandable that you see what you do.

 

[jrm]

OK, so one of the email servers has an incorrect time. So would need to
contact the host of that server and see if they can fix the problem. I could
not figure out why Outlook was reading two different received times. Thanks
for your help in locating the problem. Now to see if I can find someone to
fix it.

 

[soon-to-retire-teacher]

Sorry for jumping in on your coat tails here... I don't know how to post a
new Q.

When I look in my Outlook "sent" folder, I see categories that read...
'Date: Later This Month', 'Next Month', '3 Weeks Away'. All e-mails in the
"Next Month" area are dated 'Tues 1/1/2008'; those in "Later this Month" are
dated 'Mon 12/31/2007'.

Although this may be an chance to peek into the future, it suggests
something is out of balance here... Any help will be appreciated. I did
open my Time/Date dialog box by right-click the time on the task tray, but
it's set to our current date.

Also: how to I post my own Question?

 

[Brian Tillman]

Sorry for jumping in on your coat tails here... I don't know how to
post a new Q.

There shod be an "Ask a question" button or something similar.

When I look in my Outlook "sent" folder, I see categories that read...
'Date: Later This Month', 'Next Month', '3 Weeks Away'. All
e-mails in the "Next Month" area are dated 'Tues 1/1/2008'; those in
"Later this Month" are dated 'Mon 12/31/2007'.

Although this may be an chance to peek into the future, it suggests
something is out of balance here... Any help will be appreciated. I
did open my Time/Date dialog box by right-click the time on the task
tray, but it's set to our current date.

I'd double check both the WIndows clock settings (time, timezone, and DST),
and the Outlook Calendar settings (timezone and DST)

Also: how to I post my own Question?

It's easier if you use a newsreader.

 

[soon-to-retire-teacher]

What's a newsreader & how can I acquire/access it?

 

[Brian Tillman]

What's a newsreader & how can I acquire/access it?

Outlook Express or WIndows Mail are newsreaders that come with WIndows
XP/2000 and Windows Vista respectively. Forté Agent is another free
newsreader. Google for it.

 

[Robin Ferguson]

You need to change the time settings in vista to read GMT 0. I think outlook takes the time from those settings. I changed mine and it's fine now.