Email shows sent March 19, 2008 but not received until August 6

C

ckuhn

An employee received an email yesterday, August 6 but it shows it was
sent on March 19, 2008. Is there a way to check to see what happened
and if it really was sent in March? I wasn't sure if the internet
headers or source would show anything.

Thanks.
 
A

Adam Bailey

An employee received an email yesterday, August 6 but it shows it was
sent on March 19, 2008. Is there a way to check to see what happened
and if it really was sent in March? I wasn't sure if the internet
headers or source would show anything.

Yes, look at the Received lines in the Internet header. If you read the
lines very carefully, you will see the path the email took and any delays.
 
B

Barry Wainwright

An employee received an email yesterday, August 6 but it shows it was
sent on March 19, 2008. Is there a way to check to see what happened
and if it really was sent in March? I wasn't sure if the internet
headers or source would show anything.

Thanks.

was it really sent in March, or has the sender just got their computer's
clock set wrong?
 
C

ckuhn

Yes, look at the Received lines in the Internet header. If you read the
lines very carefully, you will see the path the email took and any delays.

Internet headers shows:

Return-Path: <[email protected]>
Received: from murder ([unix socket])
by server.mwsw.com (Cyrus v2.2.12-OS X 10.4.8) with LMTPA;
Wed, 06 Aug 2008 09:09:56 -0700
X-Sieve: CMU Sieve 2.2
Received: from [192.168.0.6] (unknown [192.168.0.6])
by server.mwsw.com (Postfix) with ESMTP id B4EA0100C70
for <[email protected]>; Wed, 6 Aug 2008 09:09:52 -0700 (MST)
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Wed, 06 Aug 2008 09:16:22 -0700
Subject: FW: Important Communication
From: Michelle <[email protected]>
To: Cheryl <[email protected]>
Message-ID: <C4BF1C74.12283%[email protected]>
Thread-Topic: Important Communication
Thread-Index: AciD1DZzsSrsoXM/QSOWblr+xpZVEAGGFCqAG3zPQF4=
In-Reply-To:
<[email protected]>
X-Priority: 1
Mime-version: 1.0
Content-type: multipart/mixed;
boundary="B_3300859002_76612"

If it was sent in March, that should have been noted in the internet
header?

Thanks, Cheryl
 
B

Barry Wainwright

Yes, look at the Received lines in the Internet header. If you read the
lines very carefully, you will see the path the email took and any delays.

Internet headers shows:

Return-Path: <[email protected]>
Received: from murder ([unix socket])
by server.mwsw.com (Cyrus v2.2.12-OS X 10.4.8) with LMTPA;
Wed, 06 Aug 2008 09:09:56 -0700
X-Sieve: CMU Sieve 2.2
Received: from [192.168.0.6] (unknown [192.168.0.6])
by server.mwsw.com (Postfix) with ESMTP id B4EA0100C70
for <[email protected]>; Wed, 6 Aug 2008 09:09:52 -0700 (MST)
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Wed, 06 Aug 2008 09:16:22 -0700
Subject: FW: Important Communication
From: Michelle <[email protected]>
To: Cheryl <[email protected]>
Message-ID: <C4BF1C74.12283%[email protected]>
Thread-Topic: Important Communication
Thread-Index: AciD1DZzsSrsoXM/QSOWblr+xpZVEAGGFCqAG3zPQF4=
In-Reply-To:
<[email protected]>
X-Priority: 1
Mime-version: 1.0
Content-type: multipart/mixed;
boundary="B_3300859002_76612"

If it was sent in March, that should have been noted in the internet
header?

Thanks, Cheryl

there is noting in those headers that indicates anything other than the
email being sent on 6th August and taking about 5 minutes to go through
th email system.

why do you think is was sent last March?
 
C

ckuhn

Internet headers shows:
Return-Path: <[email protected]>
Received: from murder ([unix socket])
by server.mwsw.com (Cyrus v2.2.12-OS X 10.4.8) with LMTPA;
Wed, 06 Aug 2008 09:09:56 -0700
X-Sieve: CMU Sieve 2.2
Received: from [192.168.0.6] (unknown [192.168.0.6])
by server.mwsw.com (Postfix) with ESMTP id B4EA0100C70
for <[email protected]>; Wed, 6 Aug 2008 09:09:52 -0700 (MST)
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Wed, 06 Aug 2008 09:16:22 -0700
Subject: FW: Important Communication
From: Michelle <[email protected]>
To: Cheryl <[email protected]>
Message-ID: <C4BF1C74.12283%[email protected]>
Thread-Topic: Important Communication
Thread-Index: AciD1DZzsSrsoXM/QSOWblr+xpZVEAGGFCqAG3zPQF4=
In-Reply-To:
<[email protected]>
X-Priority: 1
Mime-version: 1.0
Content-type: multipart/mixed;
boundary="B_3300859002_76612"
If it was sent inMarch, that should have been noted in the internet
header?
Thanks, Cheryl

there is noting in those headers that indicates anything other than the
email being sent on 6th August and taking about 5 minutes to go through
th email system.

why do you think is was sent lastMarch?

It looks like it was a forwarded email from March 19, 2008. It shows
the original message dated 3/11/08 in the date line (from, date, to,
conversation area.). It then shows a forwarded message dated 3/19/08
in the to, from, etc area. Isn't this date whatever date and time is
on the sender's computer whether it be the correct date or not? I
just want to make sure emails aren't in space for a few months before
it lands here :) But if the internet headers only show dates of 8/6
then that's when it was sent and received, correct? Thanks for your
help.
 
W

William Smith [MVP]

It looks like it was a forwarded email from March 19, 2008. It shows
the original message dated 3/11/08 in the date line (from, date, to,
conversation area.). It then shows a forwarded message dated 3/19/08
in the to, from, etc area. Isn't this date whatever date and time is
on the sender's computer whether it be the correct date or not? I
just want to make sure emails aren't in space for a few months before
it lands here :) But if the internet headers only show dates of 8/6
then that's when it was sent and received, correct? Thanks for your
help.

Daylight Saving Time is about a week earlier than that and I'd expect
only an hour's difference not several months.

The fact that you're saying messages are getting forwarded leads me to
believe user error is involved. You'd have to actually have forwarded
each message as an attachment to a new message to preserve the headers
of the original messages. I doubt that happened since it's not common
practice.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>
 
Top